Organization should test contingency plans periodically
High
Cross-cloud
General
manual-hipaa-contingency-testing
How to fix it
Implement procedures for periodic testing and revision of contingency plans. Test backup restoration, failover procedures, and emergency operations at least annually.
How to verify
- Verify test results from most recent contingency test
- Confirm plans were updated based on test 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