Diagnose
A proposed workflow
The sequence below is a starting design, not a claim about the current operation.
- 01Inventory business services, applications, data and ownersDefine evidence and the exception path
- 02Map identity, network, job, device and vendor dependenciesDefine evidence and the exception path
- 03Assess retain, remediate, integrate, replace or retire optionsDefine evidence and the exception path
- 04Prepare target controls and data migrationDefine evidence and the exception path
- 05Pilot a low-coupling slice with parallel validationDefine evidence and the exception path
- 06Cut over in waves with rollback and handoverConfirm ownership and handover
Design
Data inputs
Use the minimum information needed and define its source and retention.
| Reference | Input or decision to establish |
|---|---|
| 01 | Application, version, owner and criticality |
| 02 | Network flows, identities and scheduled jobs |
| 03 | Data stores, interfaces, licenses and vendors |
| 04 | Recovery needs, maintenance windows and acceptance tests |
Design
Human responsibilities
Automation routes information; accountable people retain operational decisions.
01Business owner sets continuity priority
Use a representative example to confirm the cause, owner, decision rule, and exception path.
02Application owner validates function
Use a representative example to confirm the cause, owner, decision rule, and exception path.
03IT/security approves target controls
Use a representative example to confirm the cause, owner, decision rule, and exception path.
04Users perform acceptance and fallback tests
Use a representative example to confirm the cause, owner, decision rule, and exception path.
Measure
Limitations
Replacement is not always the lowest-risk option. Some machine-adjacent or vendor-bound workloads should remain on-site, isolated, or supported through a different plan.