We.ProtectAcademy

Learn to protect what matters

27

Guided lesson

How We.Protect Verifies Remediation

Why the final step is proof — not a promise — that a fix worked.

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

Objectives

By the end of this lesson, you will understand:

  • Explain why clicking Resolved is not proof.
  • Describe the patch, rescan and compare loop.
  • Read Verification PASSED and Verification FAILED.
  • Explain evidence-based closure.

Concept flow

Remediation is reported

Stage 1 of 4

A team marks the work as complete.

Possible defensive checkpoints

Re-scanTelemetryClosure rule

The original finding

A scanner records a weakness on a specific system.

What you are seeing
  1. Initial scan result appears
  2. CVE ID and asset name are stored
  3. Reference snapshot is saved

Simple explanation

The first scan produces a CVE (Common Vulnerabilities and Exposures) ID and the asset name. This is the starting point for comparison.

We.Protect keeps that record unchanged. Later checks need a fixed reference point.

Why this matters

You cannot prove a fix without knowing exactly what was found before the fix.

Key term

Knowledge check

Show what you learned

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

3 questions
  1. 01A rescan still finds the original weakness. What happens next?
  2. 02Clicking Resolved proves that a vulnerability has been fixed.
  3. 03A team patches one of two identical servers. The rescan still shows the weakness on the second server. What is the right outcome?

SIMULATION

Proof Before Closure

Solstice Labs reports that a vulnerable service has been fixed and wants the case closed.

Decide when fresh evidence justifies verified closure.

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

Score: 0% · Best: 0%

Stage 1 of 3
OperatorPlant teamScannerFinding sourceRisk engineBusiness contextChange boardProduction approvalOT gatewaySegmentationHMIOperator viewPLCControl systemMFG-SQL-01Production data
REQUESTThe team marks the work complete. What should be collected next?

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

The team marks the work complete. What should be collected next?

Ready to read
SIMULATION

Using a system fallback voice; quality may vary.

Read instead

Captions: Welcome to this simulation: Proof Before Closure. 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. 01Clicking Resolved proves that a vulnerability has been fixed.

    Difficulty 2 · true false

  2. 02A rescan still finds the original weakness. What happens next?

    Difficulty 2 · multiple choice

  3. 03Lucerne Publishing marks a vulnerability incident resolved after a patch is deployed, but the next scan still reports it. What should the closure rule require?

    Difficulty 4 · scenario

  4. 04A team patches one of two identical servers. The rescan still shows the weakness on the second server. What is the right outcome?

    Difficulty 4 · scenario

  5. 05Verification means collecting fresh evidence and comparing it with the original finding before an incident is closed.

    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