Set program ownership and decisions
Govern ransomware resilience
Demo data. Any changes do not save and are reset on refresh.
Ransomware Resilience
- Organization
- Demo
- Unit
- Not attached
- Site
- London
PERT
Critical pathComplete→Dependencies
Define critical services and data
Govern ransomware resilience
Approve recovery priorities and objectives
Govern ransomware resilience
Operationalize the ransomware response playbook
Govern ransomware resilience
Confirm the executive crisis decision process
Govern ransomware resilience
Design resilient service architecture
Design resilient service boundaries
Separate daily and privileged administration
Prepare recovery access and restoration
Require strong authentication
Prepare recovery access and restoration
Define recovery access procedures
Prepare recovery access and restoration
Set endpoint detection and isolation coverage
Reduce, detect, and exercise ransomware risk
Prioritize vulnerability remediation
Reduce, detect, and exercise ransomware risk
Restrict and monitor privileged access
Reduce, detect, and exercise ransomware risk
Segment critical networks and services
Design resilient service boundaries
Establish isolated backup copies
Prepare recovery access and restoration
Define detection and escalation procedures
Reduce, detect, and exercise ransomware risk
Test alert triage and isolation
Reduce, detect, and exercise ransomware risk
Test restoration of critical services
Prepare recovery access and restoration
On critical path
Blocked by Technical prerequisite
Run and review a ransomware exercise
Reduce, detect, and exercise ransomware risk
On critical path
Blocked by External dependency
Validate clean-room identity recovery access
Prepare recovery access and restoration
On critical path
Critical path
3 remaining, Validate clean-room identity recovery access, Next, December 18, 2026
Dependencies
9 handoffs, 0 date conflicts, 9 blocked, 2 target conflicts
Next handoff
Operationalize the ransomware response playbook, Incident response lead, November 9, 2026
Recommendations
| Actions | ||||||
|---|---|---|---|---|---|---|
| London | Ransomware ResilienceProgram | USD 180M | Resolve “Test restoration of critical services” with Recovery lead. Agree a recovery sequence for the remaining work and confirm achievable milestone dates.Forecast finish 2027-03-19 is 42 days after the target. | Nov 04, 2026 | ||
| London | RR-P02 Prepare recovery access and restorationProject | USD 180M | Resolve the technical dependency, then retest affected work.RR-17 finishes on Feb 26, 2027, 21 days after its Feb 05, 2027 target. | Feb 05, 2027 | ||
| London | RR-P04 Reduce, detect, and exercise ransomware riskProject | USD 180M | Confirm the external owner, commitment, and date.RR-18 finishes on Mar 19, 2027, 42 days after its Feb 05, 2027 target. | Feb 05, 2027 |
- Site
- London
Ransomware ResilienceProgramUSD 180MRecommendation
Resolve “Test restoration of critical services” with Recovery lead. Agree a recovery sequence for the remaining work and confirm achievable milestone dates.Forecast finish 2027-03-19 is 42 days after the target.- Site
- London
RR-P02 Prepare recovery access and restorationProjectUSD 180MRecommendation
Resolve the technical dependency, then retest affected work.RR-17 finishes on Feb 26, 2027, 21 days after its Feb 05, 2027 target.- Site
- London
RR-P04 Reduce, detect, and exercise ransomware riskProjectUSD 180MRecommendation
Confirm the external owner, commitment, and date.RR-18 finishes on Mar 19, 2027, 42 days after its Feb 05, 2027 target.