Skip to Content

Security & Compliance

Lynx Compliance - HIPAA Security Rule

HIPAA Security Rule (45 CFR §§ 164.302–164.318) seeded as a compliance.framework — Administrative, Physical, Technical, Organizational, and Documentation safeguards.

lynx_compliance_hipaa · v19.0.1.0.0 · Premium

What this solves

Lynx Compliance - HIPAA Security Rule

The full HIPAA Security Rule (45 CFR 164.302-318) seeded as a compliance framework - Administrative, Physical, Technical, Organizational, and Documentation safeguards - cross-mapped to ISO 27001:2022 and NIST CSF 2.0.

US healthcare customers and any business associate handling PHI need to defend HIPAA on demand. This module ships the published Security Rule as a first-class framework so it sits next to CSF, ISO, and PCI DSS in the picker, with the implementation specifications correctly tagged as (R)equired or (A)ddressable, and cross-mappings filled where NIST SP 800-66 r2 publishes a clean alignment.

Key Features

  • Five-safeguard structure - Administrative, Physical, Technical, Organizational, and Documentation safeguards mapped as compliance functions.

  • Standards as categories - the standards within each safeguard appear as categories so the navigation matches the regulation text.

  • R/A tagging - implementation specifications carry (R)equired or (A)ddressable in the control name to avoid the most common misclassification mistake.

  • NIST 800-66 r2 mappings - cross-references to ISO 27001:2022 and CSF 2.0 seeded where authoritative mappings exist.

  • Business-associate ready - control set covers both covered entities and BAs without separate configuration.

Integrates With

  • lynx_compliance - registers as a framework alongside CSF, ISO, SOC 2, PCI DSS, GDPR, Law 25.

Try Lynx Compliance - HIPAA Security Rule on your team.

Free trial, no credit card. Talk to sales when you're ready.