Organization should maintain a PCI incident response plan
Critical
Cross-cloud
General
manual-pci-incident-response-plan
How to fix it
Create and maintain an incident response plan specifically addressing payment card data breaches. Include roles, communication procedures, card brand notification requirements, and forensic investigation procedures.
How to verify
- Verify incident response plan exists with PCI-specific procedures
- Confirm card brand notification procedures are documented
- Verify plan is tested at least annually
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