Organization should test the incident response plan annually
High
Cross-cloud
General
manual-pci-incident-response-testing
How to fix it
Test the incident response plan at least annually through tabletop exercises or simulated incidents. Update the plan based on lessons learned and changes in the environment.
How to verify
- Verify test results from most recent incident response test
- Confirm plan updates 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