# HIPAA (45 CFR Part 164) 164.410 — Notification by a Business Associate - Source: https://support.icompaas.com/compliance/hipaa/164-410-notification-by-a-business-associate - Section: [Compliance](https://support.icompaas.com/compliance) › [HIPAA Security, Privacy & Breach-Notification Rules](https://support.icompaas.com/compliance/hipaa) › Breach Notification Rule — §164.410 - Last updated: 2026-06-05 - Publisher: iCompaas, Inc. (https://www.icompaas.com) **HIPAA (45 CFR Part 164)**·§ `164.410`·medium·Component: **Breach Notification Rule** ## What this control requires > Notification by a Business Associate. (a) Standard. (1) General Rule. A business associate shall, following the discovery of a breach of unsecured protected health information, notify the covered entity of such breach. (2) For purposes of paragraph (a)(1) of this section, a breach shall be treated as discovered by a business associate as of the first day on which such breach is known to the business associate or, by exercising reasonable diligence, would have been known to the business associate. A business associate shall be deemed to have knowledge of a breach if the breach is known, or by exercising reasonable diligence would have been known, to any person, other than the person committing the breach, who is an employee, officer, or other agent of the business associate (determined in accordance with the federal common law of agency). (b) Except as provided in 164.412, a business associate 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)(1) The notification required by paragraph (a) of this section shall include, to the extent possible, the identification of each individual whose unsecured protected health information has been, or is reasonably believed by the business associate to have been, accessed, acquired, used, or disclosed during the breach. (2) A business associate shall provide the covered entity with any other available information that the covered entity is required to include in notification to the individual under 164.404(c) at the time of the notification required by paragraph (a) of this section or promptly thereafter as information becomes available. > > — HIPAA (45 CFR Part 164), § 164.410 ### In plain English Notification by a Business Associate. In practice, this means you can prove you general management-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.410) 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 - **General.** Document the trigger, the owner and the cadence. - **Information.** Document the trigger, the owner and the cadence. - **Business.** Document the trigger, the owner and the cadence. - **Person.** Document the trigger, the owner and the cadence. - **Other.** Document the trigger, the owner and the cadence. - **Scope:** management, notification, business associate, policy, accordance, 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 by a Business Associate. ## 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. - [**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) - [**NIST SP 800-53 Rev. 5 CP-7(2)** — Accessibility](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/cp-7-2-accessibility) - [**ISO/IEC 27001:2022 A.5.5** — Contact with authorities](https://support.icompaas.com/compliance/iso-27001-2022/a-5-5-contact-with-authorities) - [**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) ## 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.404(a)** — Notice to Individuals](https://support.icompaas.com/compliance/hipaa/164-404-a-notice-to-individuals) - [**§ 164.414(b)** — Burden of Proof](https://support.icompaas.com/compliance/hipaa/164-414-b-burden-of-proof) - [**§ 164.402(b)** — Definitions: Breach - exceptions (unsecured PHI)](https://support.icompaas.com/compliance/hipaa/164-402-b-definitions-breach-exceptions-unsecured-phi) - [**§ 164.412** — Law Enforcement Delay](https://support.icompaas.com/compliance/hipaa/164-412-law-enforcement-delay) - [**§ 164.406** — Notification to the Media](https://support.icompaas.com/compliance/hipaa/164-406-notification-to-the-media) ## 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.410` 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.