Organization should establish incident management procedures
Critical
Cross-cloud
General
manual-iso-incident-management
How to fix it
Establish incident management procedures including reporting, assessment, response, and learning. Define roles, communication channels, and escalation paths. Conduct post-incident reviews.
How to verify
- Verify incident management procedures document
- Confirm incident response team and contact details
- Review post-incident review records
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