# HIPAA (45 CFR Part 164) 164.406 — Notification to the Media - Source: https://support.icompaas.com/compliance/hipaa/164-406-notification-to-the-media - Section: [Compliance](https://support.icompaas.com/compliance) › [HIPAA Security, Privacy & Breach-Notification Rules](https://support.icompaas.com/compliance/hipaa) › Breach Notification Rule — §164.406 - Last updated: 2026-06-05 - Publisher: iCompaas, Inc. (https://www.icompaas.com) **HIPAA (45 CFR Part 164)**·§ `164.406`·medium·Component: **Breach Notification Rule** ## What this control requires > Notification to the Media. For a breach of unsecured PHI involving more than 500 residents of a State or jurisdiction, a covered entity shall, following the discovery of the breach as provided in 164.404(a)(2), notify prominent media outlets serving the State or jurisdiction. (b)Except as provided in 164.412, a covered entity shall provide the notification required by paragraph (a) of this section without unreasonable delay and in no case later than 60 calendar days after discovery of a breach. (c) The content of the notification required by paragraph (a) of this section shall meet the requirements of 164.404(c). > > — HIPAA (45 CFR Part 164), § 164.406 ### In plain English Notification to the Media. In practice, this means you can prove you requirements requirements-level controls on a defined cadence. ## Why it matters HIPAA non-compliance is a strict-liability matter: OCR civil monetary penalties are assessed per-record per-violation (up to USD 1.9 million per identical-violation calendar year as of 2024), and willful neglect can trigger criminal referral. ## What an auditor looks for HHS OCR investigators and SOC-2+HIPAA auditors look for the specific 45 CFR § citation, whether the safeguard is required vs addressable (and if addressable, the documented decision), the implementation specification, the workforce member responsible, and the records that show it runs. Within **Breach Notification Rule**, the assessor will trace your implementation back to the catalogue reference (§ 164.406) and look for objective evidence on the latest two assessment cycles. ## How to implement #### Policy Management **Docs.** Keep each policy in version-controlled Markdown alongside the code that implements it; ship a signed PDF snapshot at each annual review and link the SHA into the SoA. ### Operational checklist - **Requirements.** Document the trigger, the owner and the cadence. - **Policy.** Document the trigger, the owner and the cadence. - **Content.** Document the trigger, the owner and the cadence. - **Notification.** Document the trigger, the owner and the cadence. - **Scope:** requirements, management, notification, media, policy, section, b, c. ## Evidence to collect - **Policy Document.** A signed and version-controlled policy / standard / procedure document. Signed policy or standard documents the safeguard. Focus: Notification to the Media. ## Common pitfalls - Policies that no engineer has read; the version in Confluence drifts from the version that's actually being enforced. ## How it maps to other frameworks Computed from shared tags, control component and key-operation subjects — handy when you are reconciling controls across an audit. - [**ISO/IEC 27001:2022 A.7.7** — Clear desk and clear screen](https://support.icompaas.com/compliance/iso-27001-2022/a-7-7-clear-desk-and-clear-screen) - [**NIST SP 800-53 Rev. 5 PL-2(1)** — Concept Of Operations](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/pl-2-1-concept-of-operations) - [**BSI C5:2020 SP-01** — Documentation, communication and provision of policies and instructions](https://support.icompaas.com/compliance/bsi-c5-2020/sp-01-documentation-communication-and-provision-of-policies-and-instructions) - [**SOC 2 (2017 TSC) CC2.3** — External Communication on Internal Control Matters](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/cc2-3-external-communication-on-internal-control-matters) - [**NIST SP 800-171 Rev. 3 3.8.4** — Media Marking](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-8-4-media-marking) ## Related controls in HIPAA (45 CFR Part 164) - [**§ 164.404(b)** — Timeliness of Notification](https://support.icompaas.com/compliance/hipaa/164-404-b-timeliness-of-notification) - [**§ 164.414(a)** — Administrative Requirements](https://support.icompaas.com/compliance/hipaa/164-414-a-administrative-requirements) - [**§ 164.510(b)(4)** — Uses and disclosures for disaster relief purposes](https://support.icompaas.com/compliance/hipaa/164-510-b-4-uses-and-disclosures-for-disaster-relief-purposes) - [**§ 164.404(a)** — Notice to Individuals](https://support.icompaas.com/compliance/hipaa/164-404-a-notice-to-individuals) - [**§ 164.410** — Notification by a Business Associate](https://support.icompaas.com/compliance/hipaa/164-410-notification-by-a-business-associate) - [**§ 164.530(e)(1)** — Sanctions](https://support.icompaas.com/compliance/hipaa/164-530-e-1-sanctions) ## References - [U.S. HHS Office for Civil Rights — HIPAA (45 CFR Part 164)](https://www.hhs.gov/hipaa/for-professionals/index.html) - Catalogue identifier: `§ 164.406` Topics: governance riskpolicy management ## Related compliance guidance - [HIPAA compliance for SaaS: a practical implementation guide](https://support.icompaas.com/compliance/hipaa): Start with the full HIPAA implementation guide — scope, roadmap, evidence and how the assessment runs. - [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Most covered-entity customers accept a SOC 2 Type II report as the independent evidence that your HIPAA controls operate, since no HIPAA attestation exists. - [NIST SP 800-53 Rev. 5: a practical implementation guide for cloud teams](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5): NIST publishes mappings of the Security Rule standards and implementation specifications to SP 800-53 Rev. 5 controls alongside SP 800-66 Rev. 2, so an 800-53 control set doubles as a HIPAA crosswalk.