Cybersecurity Fundamentals
RecruitScenario sim

Risk Management End to End

Follow risk from business context through analysis, treatment and continuing review.

100 min 500 XPSkills: Risk analysis, Risk treatment, Risk registers, Risk monitoring

What you'll be able to do

  • ›Define context, appetite and tolerance
  • ›Calculate qualitative scores and annual loss estimates
  • ›Evaluate treatment and residual exposure
  • ›Assign owners and monitor register entries
  • ›Recalculate uncertain losses without mixing units or counting shared losses twice

Loading the lessons...

Labs

160 bonus XP

Hands-on work. You edit the artefact, the server runs the checks: the expectations and the reference solution never reach your browser.

Lab 1 · YAML lab

Complete the flood risk record

Briefing 40 XP

Use Willow's evidence to calculate annual losses and record accountable decisions.

Dispatch assessment

Asset: dispatch equipment. Threat: flooding. Weakness: floor-level equipment. Owner: operations director. Value £100,000; loss fraction 0.40; annual frequency 0.2. Raising equipment reduces event loss to £10,000. Frequency stays 0.2. Treatment: mitigate. Annual loss tolerance: £3,000. Review date: 2027-06-01.

Checks

  • Identify accountability
  • Calculate the baseline
  • Evaluate remaining exposure
  • Schedule review
Lab 2 · Review lab

Review a risk committee note

Briefing 40 XP

Review each proposed statement before the committee relies on it.

Verdicts are accept or reject. Every rejection needs one reason code from: transfer-overstated | average-not-cap | review-missing.

Committee claims

R-1 | A score of 12 is a ranking aid, not £12 of expected loss.
R-2 | Buying insurance removes every business consequence.
R-3 | A named risk owner remains accountable after treatment.
R-4 | Annual average loss is the maximum loss in any year.
R-5 | An accepted risk needs no future review.
R-6 | Control failures can trigger a fresh assessment.

Checks

  • Every line in the fixture carries a verdict
  • Accept and reject land on the right lines
  • Each rejection cites a valid reason code
Lab 3 · YAML lab

Build an evidence-linked risk update

Briefing 40 XP

Write the decision record in YAML, a simple text format for structured data.

Use the fixture rather than inventing missing evidence.

Decision evidence

Willow Parcel assesses equipment valued at £240,000. Exposure factor is 0.25. Annual frequency is 0.5. The calculated single loss is £60,000 and annual loss is £30,000. Treatment is barrier repair. Effectiveness is not verified, so verified is false. Operations director owns the risk. Review date is 2027-08-01.

Checks

  • Complete basis
  • Complete estimate
  • Complete treatment
  • Complete review
Lab 4 · Review lab

Review risk decision notes

Briefing 40 XP

Review each claim against the deeper lesson. Accept accurate claims and reject misleading ones.

Verdicts are accept or reject. Every rejection needs one reason code from: effectiveness-unproven | frequency-not-schedule | constraint-ignored.

Review notes

D-1 | Paying the installation invoice proves the forecast residual exposure is achieved.
D-2 | A changed drainage pattern can justify reassessment before the scheduled review.
D-3 | An annual frequency of 0.5 guarantees exactly one event every two years.
D-4 | Adding estimates requires checking whether both include the same loss.
D-5 | A £9,000 yearly cost can be compared with a £12,000 yearly loss reduction.
D-6 | A positive financial benefit permits Willow to ignore its mandatory safety duties.

Checks

  • Every line in the fixture carries a verdict
  • Accept and reject land on the right lines
  • Each rejection cites a valid reason code

Next on your path · Cybersecurity Fundamentals

Identity and Access Management

Manage identities, authentication and permissions across the full access lifecycle.

Recruit 100 min 500 XP
Start next room

Community

Discussion & writeups

Sign in to post

Share how you approached the room or ask where you got stuck. Never paste task answers or full lab solutions: write the reasoning, not the key.

Loading discussion…