← All posts

Security Incident Reporting in Business Associate Contracts: Who tells whom, and how fast

April 2, 2026 · Ken Armstrong

45 CFR 164.314(a)(2)(i)(C) is the requirement on security incident reporting in business associate contracts. It is short to read and easy to underestimate, because satisfying it means producing evidence rather than holding an intention.

What the rule says

45 CFR 164.314(a)(2)(i)(C) governs security incident reporting in business associate contracts. 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.

This is a required implementation specification. 45 CFR 164.306(d)(2) gives no documented-alternative route: you implement it, or you have a finding.

The Security Rule sets no deadline for a security incident report: 45 CFR 164.314(a)(2)(i)(C) requires only that the contract provide the business associate will "Report to the covered entity any security incident of which it becomes aware, including breaches of unsecured protected health information as required by § 164.410." For a breach of unsecured PHI, 45 CFR 164.410(b) requires notice "without unreasonable delay and in no case later than 60 calendar days after discovery of a breach", except as § 164.412 provides. A shorter period, and what counts as reportable, are set in the contract.

What this looks like in practice

In an assessment, 45 CFR 164.314(a)(2)(i)(C) 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:

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?
Does the organization have a written contract or other arrangement with every business associate that creates, receives, maintains, or transmits ePHI on its behalf, providing that the business associate will comply with the applicable requirements of the Security Rule, ensure that its subcontractors that handle ePHI agree to the same by contract, and report to the organization any security incident of which it becomes aware, including breaches of unsecured PHI?
Does the organization follow a documented offboarding procedure that revokes access and recovers or confirms destruction of sensitive data when a third-party relationship ends?

Ownership usually sits with the security official, 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

Every covered entity that permits a business associate to create, receive, maintain, or transmit ePHI on its behalf, and every business associate that does the same with a subcontractor (45 CFR 164.308(b)(1) and (b)(2), 164.314(a)(2)(iii)). The clauses bind the contract; the business associate performs them.

Building it, in order

These steps are one way to meet it, drawn from our question bank. Unless a step names a provision, the Security Rule does not require that particular measure: 45 CFR 164.306(b)(1) lets you use any security measures that allow you to reasonably and appropriately implement the standards and implementation specifications, chosen with the factors in 45 CFR 164.306(b)(2).

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

Designate a named intake point to receive incident and breach reports from third parties and record the date received.
Evaluate whether a reported third-party incident rises to a notifiable event and trigger the organization's own notification timeline accordingly.
Coordinate notification obligations and, where warranted, exercise contractual remedies.
Document the evaluation and actions taken.
Maintain a current master agreement template, reviewed by counsel, that includes the required protection obligations.
Include in each contract the terms 45 CFR 164.314(a)(2)(i) requires: that the business associate will comply with the applicable requirements of the Security Rule, will ensure under § 164.308(b)(2) that any subcontractor that creates, receives, maintains, or transmits ePHI on its behalf agrees to the same by a contract or other arrangement that complies with § 164.314, and will report to the organization any security incident of which it becomes aware, including breaches of unsecured PHI as § 164.410 requires.

Where else this maps

The questions behind 45 CFR 164.314(a)(2)(i)(C) also map to HHS 405(d) HICP (2023 Edition) CSP 8 and NIST SP 800-66 Rev. 2 5.1.9, 5.2.4, 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, procedure, record, and report. 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. 45 CFR 164.316(b)(2)(i) requires the documentation 164.316(b)(1) calls for (the Security Rule policies and procedures, and the written record of any action, activity or assessment the Security Rule requires to be documented) to be retained for six years from the date of its creation or the date when it last was in effect, whichever is later, so a policy you replaced two years ago is still part of the record.

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.314(a)(2)(i)(C) that means the executed agreement, with the signature date on it, a step-by-step procedure someone unfamiliar with the task could follow, dated records of each occurrence, not a description of the process, and a dated report with the period it covers and who reviewed it. 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 security official should be recorded as the owner. 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.
There is no documented-alternative route for the requirement itself. It is required (45 CFR 164.306(d)(2) for a specification, 164.306(c) for a standard), so a risk-based decision not to meet it is not available. How you meet it is yours to choose under 45 CFR 164.306(b); the measures in this post are examples, not the rule's text.

The recurring lesson with security incident reporting in business associate contracts is that documentation is not the paperwork after the control. It is the part an assessor can read, and therefore the part that has to exist.

Related requirements

References

45 CFR 164.314(a)(2)(i)(C), in 45 CFR 164.314 on eCFR.
The Required and Addressable designations are defined at 45 CFR 164.306(d).
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 additional obligations; HIPAA preempts a State law only where it is contrary to HIPAA (45 CFR 160.202, 160.203).