compliance.tf
Azure Compliance FrameworksRetired Frameworks

HIPAA Security Rule 2003

Deprecated Framework

This framework has been superseded by HIPAA Omnibus Final Rule 2013. Organizations should migrate to the 2013 rule, which strengthened privacy and security protections and expanded compliance obligations to business associates.

Best for: A covered entity or business associate must comply with the applicable standards, implementation specifications, and requirements of this subpart with respect to electronic protected health information of a covered entity.

Mandatory?Mandatory for covered entities and business associates
Who validates?No formal certification; HHS/OCR enforcement
RenewalNo fixed cycle; periodic risk assessments required
ScopeElectronic protected health information (ePHI)

Controls by Category

164.308(a)(1)(ii)(B) Risk Management (30 controls)

Azure subscriptions should have a custom role for administering resource locksNetwork security groups should prohibit inbound HTTP (port 80) access from the internetUnattached managed disks should be encrypted with ADE or customer-managed keysOS and data disks should use customer-managed keys for encryptionUnattached managed disks should use customer-managed keys (CMK) for encryptionCosmos DB accounts should use private linkAzure Cosmos DB accounts should have firewall rulesAzure subscriptions should prohibit Custom Subscription Administrator rolesCustom roles should not grant overly permissive subscription permissionsKey vault keys should have automatic rotation enabledKey vaults should have Role-Based Access Control (RBAC) enabledAzure Key Vaults should use private linkKubernetes cluster nodes should prohibit public accessKubernetes clusters should have public access restrictions configuredStorage accounts containing operational log containers should use customer-managed keys for encryptionNetwork security groups should have RDP access restrictions configuredNetwork security groups should have SSH access from the internet restrictedNetwork security groups should have UDP services restricted from the internetSQL databases should prohibit ingress from 0.0.0.0/0 (ANY IP)SQL databases should have transparent data encryption enabledSQL servers should use customer-managed keys to encrypt data at restSQL databases should have Transparent Data Encryption enabledStorage accounts should have 'Allow Blob Anonymous Access' set to 'Disabled'Storage accounts containing VHD OS disks should use customer-managed keys (CMK) for encryptionStorage accounts should have the default network access rule set to denyStorage accounts should have network access restrictions configuredStorage accounts should use customer-managed key for encryptionStorage accounts should have infrastructure encryption enabledStorage accounts should use virtual network rules to restrict network accessStorage accounts should use private link

164.312(e)(2)(ii) Encryption (22 controls)

NIS2 Directive (EU 2022/2555) — 🟢 High overlap (84%)

BSI C5:2025 — 🟢 High overlap (82%)

RBI Cyber Security Framework for UCBs — 🟢 High overlap (81%)

On this page

Controls by Category164.308(a)(1)(ii)(A) Risk analysis (6)164.308(a)(1)(ii)(B) Risk Management (30)164.308(a)(1)(ii)(D) Information system activity review (13)164.308(a)(3)(i) Workforce security (8)164.308(a)(3)(ii)(A) Authorization and/or supervision (4)164.308(a)(3)(ii)(B) Workforce clearance procedure (5)164.308(a)(4)(i) Information access management (8)164.308(a)(4)(ii)(A) Isolating health care clearinghouse functions (10)164.308(a)(4)(ii)(B) Access authorization (10)164.308(a)(4)(ii)(C) Access establishment and modification (6)164.308(a)(5)(ii)(B) Protection from malicious software (6)164.308(a)(5)(ii)(C) Log-in monitoring (4)164.308(a)(5)(ii)(D) Password management (4)164.308(a)(6)(i) Security incident procedures (8)164.308(a)(6)(ii) Response and reporting (11)164.308(a)(7)(i) Contingency plan (8)164.308(a)(7)(ii)(A) Data backup plan (8)164.308(a)(7)(ii)(B) Disaster recovery plan (7)164.308(a)(7)(ii)(C) Emergency mode operation plan (5)164.308(a)(8) Evaluation (4)164.310(a)(1) Facility access controls (3)164.310(d)(1) Device and media controls (5)164.312(a)(1) Access control (19)164.312(a)(2)(i) Unique user identification (5)164.312(a)(2)(ii) Emergency access procedure (4)164.312(a)(2)(iv) Encryption and decryption (13)164.312(b) Audit controls (17)164.312(c)(1) Integrity (7)164.312(c)(2) Mechanism to authenticate electronic protected health information (4)164.312(d) Person or entity authentication (9)164.312(e)(1) Transmission security (16)164.312(e)(2)(i) Integrity controls (3)164.312(e)(2)(ii) Encryption (22)Related Frameworks

Ask AI about this

Help improve this page