HIPAA Security Rule
Administrative

HIPAA Security Rule 164.308(a)(4)(i): Information Access Management (Standard)

Implement policies authorizing access to ePHI consistent with applicable HIPAA Privacy Rule requirements. NIST recommends minimum necessary, role-based, and least-privilege access.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 69 controls across 23 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

NIST SP 800-53 Rev 5 · 8 controls

CIS Controls v8 · 7 controls

  • CIS-3.3 Configure Data Access Control Lists
  • CIS-5.4 Restrict Administrator Privileges to Dedicated Administrator Accounts
  • CIS-6.1 Establish an Access Granting Process
  • CIS-6.2 Establish an Access Revoking Process
  • CIS-6.6 Establish and Maintain an Inventory of Authentication and Authorization Systems
  • CIS-6.8 Define and Maintain Role-Based Access Control
  • CIS-9.1 Ensure Use of Only Fully Supported Browsers and Email Clients

CMMC 2.0 · 7 controls

PCI DSS 4.0 · 7 controls

  • 1.2.5 1.2.5 Allowed services, protocols and ports justified
  • 3.3.3 3.3.3 Issuer SAD storage limited, justified and encrypted
  • 7.2.1 7.2.1 Access control model defined
  • 9.2.3 9.2.3 Physical protection of network hardware and lines
  • 7.2.4 7.2.4 User accounts and privileges reviewed every six months
  • 7.2.5 7.2.5 Application and system accounts least privilege
  • 7.3.1 7.3.1 Need-to-know access control system covers all components

FedRAMP High · 4 controls

  • AC-1 Policy and Procedures
  • AC-2 Account Management
  • AC-3 Access Enforcement
  • AC-6 Least Privilege

FedRAMP Moderate · 4 controls

  • AC-1 Policy and Procedures
  • AC-2 Account Management
  • AC-3 Access Enforcement
  • AC-6 Least Privilege

SOC 2 · 4 controls

  • SOC2-CC6.1 CC6.1 Logical access security over protected information assets
  • SOC2-CC6.2 CC6.2 Registering and authorising users before issuing credentials
  • SOC2-CC6.3 CC6.3 Role-based access, least privilege and segregation of duties
  • SOC2-P5.1 P5.1 Data subject access
  • ASBv3-GS-6 Define and implement identity and privileged access strategy
  • ASBv3-PA-7 Follow just enough administration (least privilege) principle

C5 (Germany) · 2 controls

ISO 27001:2022 · 2 controls

  • 5.15 Access control
  • 8.3 Information access restriction

ISO 27002:2022 · 2 controls

  • 5.15 Access control
  • 5.17 Authentication information

ISO 27701:2019 · 2 controls

  • 6.6.2 User access management
  • 7.4.4 PII minimization objectives
  • NIST-CSF-PR.AA-05 Access permissions, entitlements, and authorizations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties
  • NIST-CSF-PR.PS-05 Installation and execution of unauthorized software are prevented

NIST SP 800-161 Rev 1 · 2 controls

NIST SP 800-171 Rev 3 · 2 controls

  • E8-ADMIN-ML3 Restrict Administrative Privileges (ML3)
  • ANSSI-HYG-09 Assign the Correct Rights on Sensitive Resources
  • AUCDR-IS-1 Limit risk of unauthorised access to the CDR data environment

UK Cyber Essentials · 1 control

  • CE-AC.1 User Account Approval Process

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in Administrative

You are reading one control. How much of HIPAA Security Rule have you already done?

HIPAA Security Rule 164.308(a)(4)(i) is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of HIPAA Security Rule your existing evidence covers. Hold ISO 27001:2022 and 53 of 67 HIPAA Security Rule controls already carry evidence.

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 64 were rejected on the ISO 27001:2022 pair alone.

Query this from an agent

The graph holds this control, the 69 it maps to, and the evidence behind each claim, over MCP and REST.