HIPAA (45 CFR Part 164) 164.412 — Law Enforcement Delay

What this control requires

Law Enforcement Delay. If a law enforcement official states to a covered entity or business associate that a notification, notice, or posting required under this subpart would impede a criminal investigation or cause damage to national security, a covered entity or business associate shall: (a) If the statement is in writing and specifies the time for which a delay is required, delay such notification, notice, or posting for the time period specified by the official; or (b) If the statement is made orally, document the statement, including the identity of the official making the statement, and delay the notification, notice, or posting temporarily and no longer than 30 days from the date of the oral statement, unless a written statement as described in paragraph (a) of this section is submitted during that time.

In plain English

Law Enforcement Delay. In practice, this means you can prove you security security-level controls on a defined cadence.

Why it matters

HIPAA non-compliance is a strict-liability matter: OCR civil monetary penalties are assessed per-record per-violation (up to USD 1.9 million per identical-violation calendar year as of 2024), and willful neglect can trigger criminal referral.

What an auditor looks for

HHS OCR investigators and SOC-2+HIPAA auditors look for the specific 45 CFR § citation, whether the safeguard is required vs addressable (and if addressable, the documented decision), the implementation specification, the workforce member responsible, and the records that show it runs.

Within Breach Notification Rule, the assessor will trace your implementation back to the catalogue reference (§ 164.412) and look for objective evidence on the latest two assessment cycles.

How to implement

Policy Management

Docs. Keep each policy in version-controlled Markdown alongside the code that implements it; ship a signed PDF snapshot at each annual review and link the SHA into the SoA.

Operational checklist

• Security. Document the trigger, the owner and the cadence.
• Business. Document the trigger, the owner and the cadence.
• Policy. Document the trigger, the owner and the cadence.
• Notice. Document the trigger, the owner and the cadence.
• Notification. Document the trigger, the owner and the cadence.
• Scope: security, management, notification, business associate, enforcement delay, notice, policy, section.

Evidence to collect

• Policy Document. A signed and version-controlled policy / standard / procedure document.

Signed policy or standard documents the safeguard. Focus: Law Enforcement Delay.

Common pitfalls

• Policies that no engineer has read; the version in Confluence drifts from the version that's actually being enforced.

How it maps to other frameworks

Computed from shared tags, control component and key-operation subjects — handy when you are reconciling controls across an audit.

• BSI C5:2020 SP-01 — Documentation, communication and provision of policies and instructions
• NIST SP 800-53 Rev. 5 PL-2(3) — Plan And Coordinate With Other Organizational Entities
• ISO/IEC 27001:2022 A.5.1 — Policies for information security

Related controls in HIPAA (45 CFR Part 164)

• § 164.410 — Notification by a Business Associate
• § 164.402(b) — Definitions: Breach - exceptions (unsecured PHI)
• § 164.404(a) — Notice to Individuals
• § 164.404(b) — Timeliness of Notification
• § 164.414(b) — Burden of Proof
• § 164.402(a) — Definitions: Breach - Risk Assessment

References

• U.S. HHS Office for Civil Rights — HIPAA (45 CFR Part 164)
• Catalogue identifier: § 164.412

Topics: governance riskpolicy management