Organization should perform vulnerability scanning (RA-5)
High
Cross-cloud
General
manual-nist-vulnerability-scanning
How to fix it
Scan for vulnerabilities in the information system and hosted applications at least monthly and when new vulnerabilities are identified. Remediate legitimate vulnerabilities within defined timeframes.
How to verify
- Verify monthly vulnerability scan reports
- Confirm remediation tracking for high/critical 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