Response and Reporting: Response and reporting, and where breach analysis begins

45 CFR 164.308(a)(6)(ii) covers response and reporting. 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

Identify and respond to suspected or known security incidents; mitigate, to the extent practicable, harmful effects of security incidents that are known to the covered entity or business associate; and document security incidents and their outcomes.

That is the operative language of 45 CFR 164.308(a)(6)(ii). Read it closely: it describes an outcome to achieve, not a product to buy, which is why two practices of the same size can satisfy it in different ways and both be right.

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.

What this looks like in practice

In an assessment, 45 CFR 164.308(a)(6)(ii) is not one question. It resolves into several, and each one is really asking for a different artifact:

• Document every reported security incident in a central log, including the actions taken to mitigate impact
• Provide and communicate clear channels for workforce members to report suspected security incidents, policy violations, or errors

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 and every business associate, at any size. 45 CFR 164.306(b) allows flexibility of approach, so a two-provider practice and a hospital system may implement this differently and both comply. What flexibility does not allow is skipping the decision: the smaller the organization, the more the written reasoning carries the weight, because there is no scale of operation to make the control self-evident.

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. Maintain a centralized log capturing every reported security incident.
2. For each entry record the date discovered, a description, affected systems and data, and the response and mitigation actions taken.
3. Retain log entries for the required retention period to support inquiries and demonstrate due diligence.
4. Upload the incident log and the procedure governing it.
5. Define the channels available to workforce members for reporting suspected incidents, potential violations, and errors.
6. Publish the responsible contact and how to reach them.

What else this satisfies

The same evidence answers more than one framework. The questions behind 45 CFR 164.308(a)(6)(ii) also map to NIST CSF RS.AN-06; ISO 27001 A.5.24, A.5.25, A.5.28; SOC 2 CC7.3, CC7.4; NIST 800-53 IR-4, IR-5, IR-6; CIS v8 17.2, 17.3, 17.4; HITRUST 11.a, 11.c. That matters for scoping: if you are working toward SOC 2 or an ISO certification alongside HIPAA, this control is one piece of work and several answers, provided the artifact is written once and referenced rather than rewritten per framework.

Evidence an assessor asks for

For this requirement the artifact types that satisfy it are log 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 artifact and keep the superseded versions. 45 CFR 164.316(b)(2)(i) requires documentation 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

The usual gap is a control that exists in practice and nowhere in writing. Someone does the work, reliably, and it has never been written down, so the organization cannot demonstrate it and cannot notice when it stops. The fix is not more control, it is a dated record and a named owner.

What to do about it

• Produce the artifact, not the intention. For 45 CFR 164.308(a)(6)(ii) that means retained logs plus evidence somebody actually reviewed them 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 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.
• Set a review cadence and keep the evidence of each review. An annual date with a dated output is enough; what fails an assessment is a control implemented once and never re-checked against a changed environment.
• There is no documented-alternative route here. This one is required, so a risk-based decision not to do it is not available. If you cannot implement it as written, that is a finding to remediate rather than a position to document.

If 45 CFR 164.308(a)(6)(ii) is new to you, the useful first step is not a policy template. It is writing down what you already do, dating it, and naming an owner. That turns an undocumented practice into evidence, and it usually reveals the real gap.

References

• 45 CFR 164.308(a)(6)(ii), in 45 CFR 164.308 on eCFR. Quoted text verified against the eCFR snapshot of 2026-01-01.
• The Required and Addressable designations are defined at 45 CFR 164.306(d).
• Crosswalk references in this post are our own mapping 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).