We.ProtectAcademy

Learn to protect what matters

18

Guided lesson

How Remediation Works

Understand the difference between stopping an incident and removing its root cause.

Not Started 8 min Intermediate
Step 1 of 617% contentKnowledge check pending

Objectives

By the end of this lesson, you will understand:

  • Explain what a root cause is.
  • Describe how a fix is chosen.
  • Explain what change control means.
  • Name the evidence that should be kept.

Concept flow

Root cause is identified

Stage 1 of 4

The underlying weakness is named.

Possible defensive checkpoints

Change controlOwner assignedEvidence captured

Root cause is identified

The team names the real reason the problem happened.

What you are seeing
  1. Timeline is reviewed
  2. Cause is written in plain words
  3. Supporting log lines are linked

Simple explanation

They look past the alert to the underlying weakness. It might be missing software updates, a wrong setting, or a weak access rule.

A clear cause prevents a guess-based fix.

Example

At fictional Meridian Maps, the cause is an outdated version of a web tool.

Why this matters

Fixing the wrong thing wastes time and leaves the risk in place.

Key termRoot cause

Knowledge check

Show what you learned

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

3 questions
  1. 01What is the main goal of remediation?
  2. 02A Common Vulnerabilities and Exposures (CVE) name is itself the fix.
  3. 03Fictional company Meridian Maps needs to update a customer-facing server. What is the safest approach?

SIMULATION

Fix the Cause

Brightline Parts works through a confirmed finding after the immediate response is over.

Order remediation from root cause through to recorded evidence.

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

Score: 0% · Best: 0%

Stage 1 of 3
UserPersonDeviceEndpointIdPIdentityGatewayPolicyWebFront doorAPIInterfaceSIEMDetectionDataStore
REQUESTWhat should happen first in remediation?

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
IDENTITY-CORE
Exposure
internal
Production criticality
medium
EDR health
88
Approval required
No
Maintenance window
02:00–03:00 UTC (planned)

Simulation paused at a decision point

What should happen first in remediation?

Ready to read
SIMULATION

Using a system fallback voice; quality may vary.

Read instead

Captions: Welcome to this simulation: Fix the Cause. 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. 01Fictional company Meridian Maps needs to update a customer-facing server. What is the safest approach?

    Difficulty 4 · scenario

  2. 02What is the main goal of remediation?

    Difficulty 2 · multiple choice

  3. 03What is the main difference between containment and remediation?

    Difficulty 2 · multiple choice

  4. 04Isolating one affected laptop without addressing the shared underlying weakness can allow the same issue to appear on other machines later.

    Difficulty 3 · true false

  5. 05A Common Vulnerabilities and Exposures (CVE) name is itself the fix.

    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