Organization should have breach notification procedures
Critical
Cross-cloud
General
manual-hipaa-breach-notification
How to fix it
Implement procedures for notifying affected individuals, HHS, and potentially media in the event of a breach of unsecured PHI. Follow the 60-day notification timeline for breaches affecting 500+ individuals.
How to verify
- Verify breach notification procedures exist
- Confirm notification templates and contact lists are current
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