Organization should develop a system security plan (PL-2)
High
Cross-cloud
General
manual-nist-security-planning
How to fix it
Develop a system security plan (SSP) that describes the security requirements, controls, and authorization boundaries. Review and update at least annually.
How to verify
- Verify SSP document exists
- Confirm annual review date
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