We.ProtectAcademy

Learn to protect what matters

19

Guided lesson

Why Verification Matters

A fix is only a fix when someone confirms the original problem is really gone.

Not Started 6 min Beginner
Step 1 of 617% contentKnowledge check pending

Objectives

By the end of this lesson, you will understand:

  • Explain why a 'Resolved' click is not proof.
  • Describe how fresh evidence is collected.
  • Explain what happens when verification fails.
  • Name one way We.Protect supports verification.

Concept flow

Fix is reported

Stage 1 of 4

A team says the work is done.

Possible defensive checkpoints

Independent checkRe-scanClosure criteria

A fix is reported

A team says the work is done.

What you are seeing
  1. Status changes to 'Fix reported'
  2. Fix note is attached
  3. Original finding remains visible

Simple explanation

Someone marks the task as complete and adds a note. That is useful information, but it is only a claim.

The original finding stays on record until it is checked.

Why this matters

A clear claim gives the verifier something specific to test.

Key termFix report

Knowledge check

Show what you learned

Answer every question. You do not need a perfect score to complete the lesson.

3 questions
  1. 01Why is a 'Resolved' click not enough to close an incident?
  2. 02If a re-scan still detects the original finding, the incident should be reopened.
  3. 03Fictional Larkspur Clinic gets a clean scan while a laptop is offline the next day. What should the verifier do?

SIMULATION

Proof, Not a Promise

A Brightline Parts team reports that a vulnerable application has been patched.

Choose the verification outcome after fresh evidence is collected.

SIMULATION · weprotect-demo-tenant · FIXTURES · Demo tenant · isolated fixtures · no customer data

Score: 0% · Best: 0%

Stage 1 of 4
OperatorPlant teamScannerFinding sourceRisk engineBusiness contextChange boardProduction approvalOT gatewaySegmentationHMIOperator viewPLCControl systemMFG-SQL-01Production data
REQUESTBefore closure, what should happen?

Live metrics

USERS1240
AUTHENTICATIONS / MIN86
FAILED LOGINS4
ALERTS2
CRITICAL FINDINGS0
RISK SCORE24 / 100
OPEN INCIDENTS0
SLA TIME45 min
ENDPOINT HEALTH98%
ASSETS AT RISK0
verificationStatusPending
productionImpactNone

Scenario parameters

Asset
MFG-SQL-01
Exposure
internal
Production criticality
critical
EDR health
96
Approval required
Yes
Maintenance window
02:00–03:00 UTC (planned)

Simulation paused at a decision point

Before closure, what should happen?

Ready to read
SIMULATION

Using a system fallback voice; quality may vary.

Read instead

Captions: Welcome to this simulation: Proof, Not a Promise. This is an isolated training environment with demo fixtures.

Assessment

Formal lesson assessment

5 questions. A score of 70% or higher demonstrates mastery. Answers stay hidden until you submit.

0/5 answered
  1. 01Proseware applies a patch and the engineer marks the incident resolved. The original scan still reports the same finding on that asset. What should happen?

    Difficulty 4 · scenario

  2. 02Why is a 'Resolved' click not enough to close an incident?

    Difficulty 2 · multiple choice

  3. 03Fictional Larkspur Clinic gets a clean scan while a laptop is offline the next day. What should the verifier do?

    Difficulty 4 · scenario

  4. 04If a re-scan still detects the original finding, the incident should be reopened.

    Difficulty 2 · true false

  5. 05A team reporting that a fix is complete is enough to close an incident; no further check is needed.

    Difficulty 2 · true false

Answer every question before submitting.

AI tutor

Help only. The tutor never changes scores, progress records, or certificates.

What makes this lesson complete

  • Lesson content: pending
  • Simulation: pending
  • Assessment: pending