We.ProtectAcademy

Learn to protect what matters

26

Guided lesson

How We.Protect Creates Incidents

Understand how a risk becomes a tracked piece of work with an owner and a deadline.

Not Started 7 min Intermediate
Step 1 of 714% contentKnowledge check pending

Objectives

By the end of this lesson, you will understand:

  • Describe what makes a risk become an incident.
  • List the evidence attached to a new incident.
  • Explain why an owner is assigned.
  • Read an incident status and timeline.

Concept flow

Risk crosses a threshold

Stage 1 of 4

A finding needs more than a notification.

Possible defensive checkpoints

ThresholdsOwnerTimeline

The threshold is crossed

A risk becomes large enough to need more than a notification.

What you are seeing
  1. Risk Score bar reaches a marked line
  2. Threshold line is labelled
  3. Alert card changes into an incident card

Simple explanation

A threshold is an agreed level. Each organisation chooses it based on its own systems and appetite for risk.

When the Risk Score goes past that level, We.Protect decides that the finding needs tracked work.

Example

At fictional Cedarline Assembly, any production-system risk above the agreed level opens an incident.

Why this matters

Thresholds stop small findings from flooding the incident queue. They also stop serious ones slipping through.

Key termThreshold

Knowledge check

Show what you learned

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

3 questions
  1. 01What causes We.Protect to create an incident?
  2. 02An incident without a named owner is likely to move quickly.
  3. 03A production risk crosses the threshold. What should happen immediately after We.Protect packages the evidence?

SIMULATION

From Risk to Owned Work

A Brightline Parts risk crosses its threshold and needs more than a notification.

Order the steps from evidence packaging to an incident with clear ownership.

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 threshold is crossed. What comes first?

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 threshold is crossed. What comes first?

Ready to read
SIMULATION

Using a system fallback voice; quality may vary.

Read instead

Captions: Welcome to this simulation: From Risk to Owned Work. 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. 01Why create a tracked incident instead of only sending a notification when a risk crosses a threshold?

    Difficulty 3 · multiple choice

  2. 02Fourth Coffee generates an incident from a risk, but nobody is assigned and no deadline is set. What is the most likely consequence?

    Difficulty 4 · scenario

  3. 03A production risk crosses the threshold. What should happen immediately after We.Protect packages the evidence?

    Difficulty 4 · scenario

  4. 04An incident without a named owner is likely to move quickly.

    Difficulty 2 · true false

  5. 05What causes We.Protect to create an incident?

    Difficulty 2 · multiple choice

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