Organization should conduct annual PCI risk assessments
High
Cross-cloud
General
manual-pci-risk-assessment
How to fix it
Conduct a formal risk assessment at least annually that identifies critical assets, threats, and vulnerabilities. Use a recognized methodology. Results should drive prioritization of security controls.
How to verify
- Verify risk assessment report (dated within 12 months)
- Confirm recognized methodology is used (NIST, OCTAVE, ISO 27005)
- Verify risk treatment plan exists
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