Set program ownership and decisions
Govern ransomware resilience
Complete · Not recorded1 person-day
Ransomware Resilience
PERT
Review the dependency network. Drag to pan, or use the scrollbars, to explore the full dependency map.
Define critical services and data
Govern ransomware resilience
3 person-daysCritical
Approve recovery priorities and objectives
Govern ransomware resilience
2 person-days
Operationalize the ransomware response playbook
Govern ransomware resilience
3 person-days
Confirm the executive crisis decision process
Govern ransomware resilience
2 person-days
Design resilient service architecture
Design resilient service boundaries
3 person-days
Separate daily and privileged administration
Prepare recovery access and restoration
2 person-daysCritical
Require strong authentication
Prepare recovery access and restoration
2 person-days
Define recovery access procedures
Prepare recovery access and restoration
2 person-daysCritical
Set endpoint detection and isolation coverage
Reduce, detect, and exercise ransomware risk
2 person-days
Prioritize vulnerability remediation
Reduce, detect, and exercise ransomware risk
2 person-days
Restrict and monitor privileged access
Reduce, detect, and exercise ransomware risk
2 person-days
Segment critical networks and services
Design resilient service boundaries
3 person-days
Establish isolated backup copies
Prepare recovery access and restoration
4 person-daysCritical
Define detection and escalation procedures
Reduce, detect, and exercise ransomware risk
3 person-days
Test alert triage and isolation
Reduce, detect, and exercise ransomware risk
2 person-days
Test restoration of critical services
Prepare recovery access and restoration
4 person-daysCritical
Blocked by Technical prerequisite
Run and review a ransomware exercise
Reduce, detect, and exercise ransomware risk
3 person-daysCritical
Blocked by External dependency
Validate clean-room identity recovery access
Prepare recovery access and restoration
4 person-daysCritical
Critical path
3 remaining · Validate clean-room identity recovery access · In progress · December 18, 2026
Dependencies
9 handoffs · 2 date conflicts · 9 blocked · 2 target conflicts
Next handoff
Operationalize the ransomware response playbook · Incident response lead · February 15, 2027
Recommendations
| Actions | |||||
|---|---|---|---|---|---|
| London | RR-P02 Prepare recovery access and restorationProject | RR-17 finishes on Feb 26, 2027, 21 days after its Feb 05, 2027 target. | Resolve the technical dependency, then retest affected work. | Feb 05, 2027 | |
| London | RR-P04 Reduce, detect, and exercise ransomware riskProject | RR-18 cannot meet its Feb 05, 2027 target while RR-14 finishes on Mar 26, 2027. | Confirm the external owner, commitment, and date. | Feb 05, 2027 | |
| London | RR-P02 Prepare recovery access and restorationProject | 21 person-days short of the capacity needed by 2027-02-05. Forecast finish 2027-03-26 is 49 days after the target. | Resolve “Test restoration of critical services” with Recovery lead. Close the 21 person-day shortfall: confirm capacity, reduce remaining scope, or agree a revised target. | Feb 12, 2027 |
- Site
- London
RR-P02 Prepare recovery access and restorationProjectImpact
RR-17 finishes on Feb 26, 2027, 21 days after its Feb 05, 2027 target.Recommendations
Resolve the technical dependency, then retest affected work.
- Site
- London
RR-P04 Reduce, detect, and exercise ransomware riskProjectImpact
RR-18 cannot meet its Feb 05, 2027 target while RR-14 finishes on Mar 26, 2027.Recommendations
Confirm the external owner, commitment, and date.
- Site
- London
RR-P02 Prepare recovery access and restorationProjectImpact
21 person-days short of the capacity needed by 2027-02-05. Forecast finish 2027-03-26 is 49 days after the target.Recommendations
Resolve “Test restoration of critical services” with Recovery lead. Close the 21 person-day shortfall: confirm capacity, reduce remaining scope, or agree a revised target.