Ransomware Resilience
Agile
Compare delivery trajectory, scope, flow, and milestone velocity
Work remaining
21 person-days remainForecast finish March 26, 2027 · 49 days late
Remaining workIdeal pathCurrent forecast
Work completed
27 of 48 person-days complete56% complete · +4 person-days new scope
Completed workTotal scopeBaseline planCurrent forecast
Cumulative flow
PlannedIn progressBlockedComplete
- Current work in progress
- 2 milestones
- Currently blocked
- 2 milestones
- Completed to date
- 11 milestones
Milestone velocity
PlannedCompleted per monthObserved monthly average
- Completed
- 11 of 12 milestones
- Average per month
- 1.8 milestones per month
- Latest month
- Dec 2026 · 1 milestone
Project drivers
- RR-P2Prepare recovery access and restoration4 of 6 milestones completed1 blocked milestone; 2 critical-path milestones remaining
- RR-P4Reduce, detect, and exercise ransomware risk3 of 6 milestones completed1 blocked milestone; 1 critical-path milestone remaining
- RR-P1Govern ransomware resilience2 of 4 milestones completedNo blockers recorded
- RR-P3Design resilient service boundaries2 of 2 milestones completedNo blockers recorded
Next actions
- RR-P2-M17Test restoration of critical servicesBlocked; Technical prerequisite
- RR-P4-M18Run and review a ransomware exerciseBlocked; External dependency
- RR-P2-M01Validate clean-room identity recovery accessCritical path
- RR-P1-M15Operationalize the ransomware response playbookPlanned
Completed milestones
- RR-P1-M02Define critical services and data
- RR-P1-M03Approve recovery priorities and objectives
- RR-P3-M04Design resilient service architecture
- RR-P2-M05Separate daily and privileged administration
- RR-P2-M06Require strong authentication
- RR-P2-M07Define recovery access procedures
- RR-P4-M08Set endpoint detection and isolation coverage
- RR-P4-M09Prioritize vulnerability remediation
- RR-P4-M10Restrict and monitor privileged access
- RR-P3-M11Segment critical networks and services
- RR-P2-M12Establish isolated backup copies
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.