164.308(a)(6)(ii) Response and Reporting (Required)
Identify and respond to suspected or known incidents, mitigate harmful effects, and document incidents and their outcomes. NIST recommends linkage to HIPAA Breach Notification Rule timelines.
Source: HIPAA Security Rule, 164.308(a)(6)(ii). The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open HIPAA Security Rule in the compliance library.
Applies to covered entities and business associates. An addressable specification can be met by a documented, reasonable alternative.
These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.
system holds itEvidence a system already holds
- Incident ticket log · SIEM / log platform
- Post-incident reports · Document repository
periodic reviewEvidence produced at each review
- Breach risk assessments per 164.402 · Document repository
- Notification records (individuals, HHS, media) · Data governance / DLP tooling
governing documentDocuments that govern the control
none for this control
First move
Common gaps auditors find
- Incident closure without root cause
- Breach risk assessment not performed
- Missed 60-day notification windows
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheet164.308(a)(6)(i) Security Incident Procedures (Standard) · 164.308(a)(7)(i) Contingency Plan (Standard)