Contingency Planning Guide for Federal Information Systems¶
Swanson, M., Bowen, P., Phillips, A. W., Gallup, D., & Lynes, D. (2010). Contingency Planning Guide for Federal Information Systems.
Cited by¶
5 citations across 5 artifacts.
Each citation links to the sentence it supports in the citing article.
Primes¶
- Recovery
- The possibly-transformed endpoint appears as build-back-better: after a ransomware recovery, the organization typically does not restore the identical vulnerable configuration but rebuilds with segmented networks and immutable backups — a transformed working state suited to the changed threat environment.
This sourceSpecifies IT contingency and disaster-recovery planning, including rebuilding to a hardened (build-back-better) configuration after a major incident.
- The possibly-transformed endpoint appears as build-back-better: after a ransomware recovery, the organization typically does not restore the identical vulnerable configuration but rebuilds with segmented networks and immutable backups — a transformed working state suited to the changed threat environment.
Mechanisms¶
- Checkpoint Hardening Window
- Its strength is that it converts a hope ("the backup is fine") into a passed test
This sourceStates that contingency-plan testing validates recovery capabilities rather than leaving them assumed.
- Its strength is that it converts a hope ("the backup is fine") into a passed test
- Critical Function Triage Matrix
- Pre-set targets are defensible
This sourceUses business-impact analysis to establish recovery objectives and priorities from criticality, outage impact, and tolerable downtime.
- Pre-set targets are defensible
- Governance RACI With Backups
- Its strength is that it removes the "who's even allowed to decide?" hesitation before it can cost days, and it turns key-person risk from a surprise into a visible map
This sourceMaps contingency roles, key personnel, contact information, and alternates so dependencies are explicit.
- Its strength is that it removes the "who's even allowed to decide?" hesitation before it can cost days, and it turns key-person risk from a surprise into a visible map
- Manual Fallback Workflow
- Its failure mode is the dormant path that decayed
This sourceRequires contingency procedures to be maintained and periodically exercised so recovery capability does not quietly degrade.
- Its failure mode is the dormant path that decayed
Verification¶
This reference passed the adversarial substantiation pipeline: it was checked to exist and to support the claim it is attached to. See how references were verified.
Registry ID ref:0dcd2f0e78f8 · see in the full table