← All posts

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

February 13, 2026 · Ken Armstrong

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

Implementation specification: Response and reporting (Required). 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 text 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.

A security incident is not always a breach. Where an incident involves an acquisition, access, use, or disclosure of PHI in a manner not permitted under subpart E, 45 CFR 164.402 presumes it is a breach unless the covered entity or business associate demonstrates a low probability that the PHI has been compromised, based on a risk assessment of at least four factors: the nature and extent of the PHI involved, the unauthorized person, whether the PHI was actually acquired or viewed, and the extent to which the risk has been mitigated. The incident documentation 164.308(a)(6)(ii) requires is where that assessment starts.

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 different evidence. These are among the questions asked about it:

Does the organization document every reported security incident in a central log, including the actions taken to mitigate impact?
Does the organization provide and communicate clear channels for workforce members to report suspected security incidents, policy violations, or errors?
When a potential security event is detected, does the organization analyze and document its estimated impact and scope?

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

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:

Maintain a centralized log capturing every reported security incident.
For each entry record the date discovered, a description, affected systems and data, and the response and mitigation actions taken.
Retain log entries for the required retention period to support inquiries and demonstrate due diligence.
Define the channels available to workforce members for reporting suspected incidents, potential violations, and errors.
Publish the responsible contact and how to reach them.
Communicate the reporting process to all workforce members and reinforce it periodically.

Where else this maps

The questions behind 45 CFR 164.308(a)(6)(ii) also map to HHS 405(d) HICP (2023 Edition) CSP 4, CSP 8 and NIST SP 800-66 Rev. 2 5.1.5, 5.1.6, 5.1.7, 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 configuration, log, plan, 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

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 evidence, not the intention. For 45 CFR 164.308(a)(6)(ii) that means a configuration export or screenshot showing the setting live, dated, retained logs plus evidence somebody actually reviewed them, a written plan naming who does what, and evidence it was tested, 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. Where the work is done by someone else, say so in the document: the split between who owns it and who performs it is where the trail usually breaks. 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 a common floor; what fails an assessment is a control implemented once and never re-checked against a changed environment.
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.

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.

Related requirements

References

45 CFR 164.308(a)(6)(ii), in 45 CFR 164.308 on eCFR. Quoted text verified against the eCFR text current as of 2026-10-06.
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).