Business Associate Breach Notification: What a business associate owes the covered entity

45 CFR 164.410 covers business associate breach notification. In most assessments the control itself is present and the record proving it is not, which is why this requirement produces findings at organizations that are, in practice, doing the work.

What the rule says

45 CFR 164.410 governs business associate breach notification. The operative text is not reproduced here: read it at the source linked below, because the conditions in it are the requirement and a summary of a conditional rule is not a safe substitute for the rule.

What this looks like in practice

In an assessment, 45 CFR 164.410 is not one question. It resolves into several, and each one is really asking for different evidence. These are among the questions asked about it:

• If the organization is a business associate, does it notify the covered entity of a breach of unsecured PHI without unreasonable delay and no later than 60 calendar days after discovery (§164.410(b)), treating a breach as discovered when known, or by reasonable diligence knowable, to any employee, officer or other agent of the business associate other than the person committing it (§164.410(a)(2)), and including, to the extent possible, each affected individual's identification and the other information the covered entity needs for its own notice (§164.410(c))?
• Do the organization's agreements require third parties to notify the organization of a breach of its data without unreasonable delay and within the required time limit, with sufficient detail to meet the organization's own obligations?
• Does the organization have a procedure to receive, evaluate, and act on security incident reports from its third parties, including determining whether a notifiable event has occurred?

Ownership usually sits with the privacy and security officials, though the evidence is often produced by someone else, which is where the trail breaks. A control that works but has no owner tends to stop working the month the person who quietly maintained it changes roles.

Who this applies to

Business associates. 45 CFR 164.410 binds a business associate directly, whatever its agreement says. The covered entity's side is the contract term at 45 CFR 164.504(e)(2)(ii)(C) and 164.314(a)(2)(i)(C), and its own clocks under 164.404 to 164.408.

Building it, in order

The sequence below is the order that produces evidence as a by-product rather than as a separate documentation exercise:

1. Write a breach notification procedure for the covered entities the organization serves, naming who notifies each and how.
2. Treat a breach as discovered on the first day it is known, or by exercising reasonable diligence would have been known, to any employee, officer or other agent of the business associate other than the person committing it (§164.410(a)(2)).
3. Notify the covered entity without unreasonable delay and no later than 60 calendar days after discovery (§164.410(b)), or sooner where the business associate agreement requires.
4. Include, to the extent possible, the identification of each affected individual and the other information the covered entity needs for its own notice (§164.410(c)), and supplement it as information becomes available.
5. Audit active third-party agreements to confirm each includes an explicit breach-notification clause.
6. Require the third party to report suspected or confirmed breaches without unreasonable delay and within the required deadline.

Where else this maps

The questions behind 45 CFR 164.410 also map to HHS 405(d) HICP (2023 Edition) CSP 8 and NIST SP 800-66 Rev. 2 5.4.1, which are voluntary guidance rather than law; following them does not by itself establish compliance with any law. That matters for scoping: the same evidence can be written once and referenced from each, rather than rewritten per framework.

Evidence an assessor asks for

For this requirement the evidence types that satisfy it are agreement and procedure. The distinction matters more than it looks: a policy states what you intend to do, a procedure states how, and a record proves it happened on a date. Auditors ask for all three, and a practice that has written the first two often has nothing for the third.

Date every document and keep the superseded versions. Under 45 CFR 164.530(j)(2) the documentation 164.530(j)(1) requires (applied to a covered entity by 164.414(a)) is kept six years from the date of its creation or the date when it last was in effect, whichever is later. It is the same period the Security Rule sets at 164.316(b)(2)(i), under a different provision, so cite the one that governs the document you are holding.

Where this usually goes wrong

In our question bank this is weighted Critical: a gap here is raised as a critical finding (a partial answer as high). The usual cause of a gap is drift: the control was implemented once, the environment changed, and nothing re-checked it. A dated review on a fixed cadence is cheaper than the remediation.

What to do about it

• Produce the evidence, not the intention. For 45 CFR 164.410 that means the executed agreement, with the signature date on it and a step-by-step procedure someone unfamiliar with the task could follow. If the only evidence is that someone knows how this works, you have a practice and not a record.
• Put a name on it. Your privacy and security officials should be recorded as the owners. A control with no owner stops working the month the person who quietly maintained it changes roles, and nobody notices.
• Review it on a fixed date, not when you remember. In our question bank this is weighted Critical: a gap here is raised as a critical finding (a partial answer as high). Put the review on the calendar with an owner, and keep the dated output of each one.

None of this makes business associate breach notification harder than it is. The requirement asks for a decision, an implementation, and a record. Organizations that struggle at assessment time are rarely the ones without controls; they are the ones that cannot show when a control started or who owns it now.

Related requirements

• Notification to the Secretary: The two HHS deadlines and which applies
• Burden of Proof: Documenting why notification was not required
• Media Notification: The more-than-500-residents threshold

References

• 45 CFR 164.410, in 45 CFR 164.410 on eCFR.
• Crosswalk references in this post are the mappings in our question bank, and are not verified against the published text of those standards.
• This post describes what a requirement asks for and what evidence documents it. It is not legal advice, and your counsel owns the conclusion. State law may impose stricter obligations (45 CFR 160.203).