Organization should maintain formal change management procedures
High
Cross-cloud
General
manual-soc2-change-management-policy
How to fix it
Implement formal change management procedures for infrastructure, applications, and configuration changes. Changes should be requested, reviewed, approved, tested, and documented before production deployment.
How to verify
- Verify change management policy exists
- Review sample change records for approval workflow
- Confirm emergency change procedures are documented
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