164.308(a)(6)(ii) Response and reporting (R)

HIPAA Security Rule · 2013

What the standard requires

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.

Quoted verbatim from 45 CFR Part 164 (eCFR, as in force 2026-01-01), which is in the public domain.

Maps to 3 controls in 1 other framework

Framework	Control
HITRUST CSF v11	11.b.03 Containment, eradication and recovery actions are executed during incidents
	11.b.05 Lessons learned from incidents are captured to improve controls
	11.b.07 Security incidents involving ePHI trigger breach-assessment obligations

Mappings are CMDash’s own, seeded with the product and shown on both frameworks they connect. In the product they mean evidence you attach here also counts against the controls listed above.

Integrations that carry evidence for this family

Gusto

Employee roster & joiner/leaver dates

KnowBe4

Maturity telemetry

These connectors produce data relevant to HIPAA Security Rule’s Administrative Safeguards family, which is the granularity CMDash publishes — there is no pre-built per-control mapping, and claiming one would be inventing it. You decide which evidence answers which control.

Track 164.308(a)(6)(ii) with evidence behind it

In CMDash this control is a row with an owner, a status, uploaded evidence kept with its full history, and an export an assessor can read.

Start free trial All HIPAA Security Rule controls