What this control covers
Develop and maintain a contingency plan to ensure continuity of essential functions during disruptions. Define recovery objectives, roles, restoration steps, and align with incident response. Review/update regularly and protect from unauthorized access. This control supports the Planning capability within the Contingency Planning family.
Why it matters
How quickly and methodically you contain an incident determines the regulatory consequence — most fines are not for the breach itself but for the slow or absent response.
How to implement
AWS
Wire GuardDuty, Security Hub and Macie findings into your ticketing/SIEM via EventBridge. Maintain documented playbooks for IAM-key compromise, EC2 instance compromise, S3 data exposure, and run quarterly tabletop exercises.
Azure
Use Defender for Cloud + Microsoft Sentinel with playbooks (Logic Apps) for automated containment — disable user, isolate VM (NSG), revoke session tokens. Keep an on-call rotation in Teams with PagerDuty.
GCP
Org Policy Service for guardrails and Config Validator in CI to pre-check Terraform plans against policy as code (Rego).
Google Workspace
Google Vault retention rules cover Gmail/Drive/Chat; combine with periodic third-party backups (e.g., Spanning, Backupify) for full restore-by-user.
GitHub
Subscribe to secret-scanning alerts and Dependabot security advisories; require triage SLAs by severity. For exposed secrets, rotate at the cloud provider FIRST then revoke at GitHub — order matters.
Evidence to collect
ticketing_workflow— See the iCompaas Evidence library for the canonical source for this evidence type.
Workflow metrics (ServiceNow, Jira) show approvals and remediation. Focus: Contingency Plan.
Quick checklist
- Access — Management / Functions
- Review — Management / Functions
- Response — Management / Functions
- Unauthorized — Management / Functions
- Control — Management / Functions
- Plan — Management / Functions
Related articles on this site
- Ensure EBS Volume in AWS Backup Plan
- Business Continuity and Disaster Recovery
- NIST 800-171 3.6.1 Establish an operational incident-handling capability for organizational systems that includes preparation, detection, analysis, containment, recovery, and user response activities.
- CMMC 2.0 IR.2.092 Establish an operational incident-handling capability for organizational systems that includes preparation, detection, analysis, containment, recovery, and user response activities.