# HIPAA (45 CFR Part 164) 164.512(f)(5) — Disclosures for law enforcement purposes: crime on premises

- Source: https://support.icompaas.com/compliance/hipaa/164-512-f-5-disclosures-for-law-enforcement-purposes-crime-on-premises
- Section: [Compliance](https://support.icompaas.com/compliance) › [HIPAA Security, Privacy & Breach-Notification Rules](https://support.icompaas.com/compliance/hipaa) › Privacy Rule — §164.512
- Last updated: 2026-06-05
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

**HIPAA (45 CFR Part 164)**·§ `164.512(f)(5)`·medium·Component: **Privacy Rule**

## What this control requires

> Permitted disclosure: Crime on premises. A covered entity may disclose to a law enforcement official protected health information that the covered entity believes in good faith constitutes evidence of criminal conduct that occurred on the premises of the covered entity.
> 
> — HIPAA (45 CFR Part 164), § 164.512(f)(5)

### In plain English

Permitted disclosure: Crime on premises. In practice, this means you can prove you information management-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 **Privacy Rule**, the assessor will trace your implementation back to the catalogue reference (§ 164.512(f)(5)) 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

-   **Information.** Document the trigger, the owner and the cadence.
-   **Policy.** Document the trigger, the owner and the cadence.
-   **Law.** Document the trigger, the owner and the cadence.
-   **Disclosures.** Document the trigger, the owner and the cadence.
-   **Scope:** management, policy, law enforcement purposes, disclosure.

## Evidence to collect

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

Signed policy or standard documents the safeguard. Focus: Disclosures for law enforcement purposes: crime on premises.

## 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](https://support.icompaas.com/compliance/bsi-c5-2020/sp-01-documentation-communication-and-provision-of-policies-and-instructions)
-   [**NIST SP 800-53 Rev. 5 PT-3(2)** — Automation](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/pt-3-2-automation)
-   [**ISO/IEC 27001:2022 A.5.5** — Contact with authorities](https://support.icompaas.com/compliance/iso-27001-2022/a-5-5-contact-with-authorities)
-   [**SOC 2 (2017 TSC) CC2.3** — External Communication on Internal Control Matters](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/cc2-3-external-communication-on-internal-control-matters)
-   [**GDPR Article 62** — Joint operations of supervisory authorities](https://support.icompaas.com/compliance/gdpr/article-62-joint-operations-of-supervisory-authorities)

## Related controls in HIPAA (45 CFR Part 164)

-   [**§ 164.512(f)(4)** — Disclosures for law enforcement purposes- an individual who has died as a result of suspected criminal conduct](https://support.icompaas.com/compliance/hipaa/164-512-f-4-disclosures-for-law-enforcement-purposes-an-individual-who-has-died-as-a)
-   [**§ 164.512(f)(3)** — Disclosures for law enforcement purposes- PHI of a possible victim of a crime](https://support.icompaas.com/compliance/hipaa/164-512-f-3-disclosures-for-law-enforcement-purposes-phi-of-a-possible-victim-of-a-crime)
-   [**§ 164.512(f)(6)** — Disclosures for law enforcement purposes](https://support.icompaas.com/compliance/hipaa/164-512-f-6-disclosures-for-law-enforcement-purposes)
-   [**§ 164.512(k)(6)** — Uses and disclosures for specialized government functions - Providing public benefits](https://support.icompaas.com/compliance/hipaa/164-512-k-6-uses-and-disclosures-for-specialized-government-functions-providing-public)
-   [**§ 164.502(j)(2)** — Disclosures by workforce members who are victims of a crime](https://support.icompaas.com/compliance/hipaa/164-502-j-2-disclosures-by-workforce-members-who-are-victims-of-a-crime)
-   [**§ 164.510(a)(3)** — Uses and Disclosures for Facility Directories in Emergency Circumstances](https://support.icompaas.com/compliance/hipaa/164-510-a-3-uses-and-disclosures-for-facility-directories-in-emergency-circumstances)

## References

-   [U.S. HHS Office for Civil Rights — HIPAA (45 CFR Part 164)](https://www.hhs.gov/hipaa/for-professionals/index.html)
-   Catalogue identifier: `§ 164.512(f)(5)`

Topics: governance riskpolicy management

## Related compliance guidance

- [HIPAA compliance for SaaS: a practical implementation guide](https://support.icompaas.com/compliance/hipaa): Start with the full HIPAA implementation guide — scope, roadmap, evidence and how the assessment runs.
- [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Most covered-entity customers accept a SOC 2 Type II report as the independent evidence that your HIPAA controls operate, since no HIPAA attestation exists.
- [NIST SP 800-53 Rev. 5: a practical implementation guide for cloud teams](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5): NIST publishes mappings of the Security Rule standards and implementation specifications to SP 800-53 Rev. 5 controls alongside SP 800-66 Rev. 2, so an 800-53 control set doubles as a HIPAA crosswalk.
