Organization should test the contingency plan (CP-4)
High
Cross-cloud
General
manual-nist-contingency-testing
How to fix it
Test the contingency plan at least annually using tabletop exercises, functional tests, or full-scale tests. Update the plan based on test results.
How to verify
- Verify test results from most recent contingency test
- Confirm plan updates based on findings
Compliance frameworks
Is your environment compliant with this rule?
CGPulse checks it — and 621 others — against your Azure and AWS accounts with read-only access.
Related Cross-cloud rules
- Block storage volumes must be encrypted
- Cache service security hardening
- Cache services must enforce TLS encryption in transit
- Container registry security hardening
- Database authentication must use managed identities
- Databases must not be publicly accessible
- IAM password policy must require minimum length of 14
- Key management service security hardening