Demo data. Any changes do not save and are reset on refresh.
Ransomware Resilience
Kanban
Move milestones through delivery states
Drag cards between columns or use each card's Move to status control. Complete requires a date and acceptance confirmation; Blocked requires a category.
Planned
2
RR-P1-M15At risk
Operationalize the ransomware response playbook
3 person-days
RR-P1-M16At risk
Confirm the executive crisis decision process
2 person-days
Waiting onRR-P1-M15
In progress
3
RR-P4-M13At risk
Define detection and escalation procedures
3 person-days
RR-P4-M14At risk
Test alert triage and isolation
2 person-days
Waiting onRR-P4-M13
RR-P2-M01Off track
Validate clean-room identity recovery access
4 person-daysCritical
Blocked
2
RR-P2-M17Off track
Test restoration of critical services
4 person-daysCritical
Blocked byTechnical prerequisite
Waiting onRR-P2-M01
RR-P4-M18Off track
Run and review a ransomware exercise
3 person-daysCritical
Blocked byExternal dependency
Waiting onRR-P4-M14, RR-P1-M16, RR-P2-M17
Complete
12
RR-P1-M01On track
Set program ownership and decisions
1 person-day
RR-P1-M02On track
Define critical services and data
3 person-daysCritical
RR-P1-M03On track
Approve recovery priorities and objectives
2 person-days
RR-P3-M04On track
Design resilient service architecture
3 person-days
RR-P2-M05On track
Separate daily and privileged administration
2 person-daysCritical
RR-P2-M06On track
Require strong authentication
2 person-days
RR-P2-M07On track
Define recovery access procedures
2 person-daysCritical
RR-P4-M08On track
Set endpoint detection and isolation coverage
2 person-days
RR-P4-M09On track
Prioritize vulnerability remediation
2 person-days
RR-P4-M10On track
Restrict and monitor privileged access
2 person-days
RR-P3-M11On track
Segment critical networks and services
3 person-days
RR-P2-M12On track
Establish isolated backup copies
4 person-daysCritical
Recommendations
Recommendations requiring attention
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 restorationProject
Impact
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 riskProject
Impact
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 restorationProject
Impact
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.