How a risk is worked in Operate
RISK-001Ransomware attack on core infrastructure
Technology & Cybersecurity · Owner: Marie Dubois
1. Scenario
2. Controls
3. Matrix
4. Treatment
5. Plan
6. Health
Scenario: describe what could happen, what would be affected and what the consequences would be.
Description
A ransomware attack encrypts core servers and the SAP S/4HANA database, halting order processing. Estimated downtime of 3 to 5 days without backup restoration.
Controls: link the controls that already mitigate this risk. Their health feeds the risk's health.
CTRL-002Vulnerability ScanHealthy
CTRL-003Backup Restoration TestHealthy
CTRL-005Firewall Rule ReviewAt risk
CTRL-007Patch Management Compliance CheckUnhealthy
Risk Matrix: place the risk by impact and likelihood. Switch the view between Actual and Target and click a cell to move it.
View:
Showing current risk positions
Likelihood ↓ · Impact →
Treatment: choose how the gap between the actual and the target position will be closed.
Mitigate
Transfer
Avoid
Accept
Treatment plan: a Risk Treatment Plan groups the work that moves the risk to its target, with an owner and a target date.
RTP-001 Ransomware Mitigation Plan
In progress · Target date: 09-10-2026 · Owner: Marie Dubois
Immutable backups (linked to DAT-03)
Network segmentation (linked to ASM-03)
Quarterly ransomware recovery test (linked to BCM-03)
Close patching gaps (linked to CTRL-007)
Health: the risk's health is computed from its linked controls, measures and treatment plan, and is never set by hand. The weakest one wins. Toggle any item to see the badge react.
Linked controls
CTRL-002Vulnerability ScanHealthy
CTRL-003Backup Restoration TestHealthy
CTRL-005Firewall Rule ReviewAt risk
Linked measures
DAT-03Backup & Recovery IntegrityHealthy
Risk Treatment Plan
RTP-001Ransomware Mitigation PlanUnhealthy
Risk healthUnhealthy