HIPAA Security Rule
Administrative

HIPAA Security Rule 164.308(a)(4)(ii)(B): Access Authorization (Addressable)

Implement policies for granting access to ePHI via workstation, transaction, program, or process. NIST recommends formal access request workflow with approval and provisioning records.

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

What else in your programme already covers this

This control maps to 59 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.

PCI DSS 4.0 · 7 controls

  • 7.2.2 7.2.2 User access assigned by job function and least privilege
  • 7.2.3 7.2.3 Privileges approved by authorized personnel
  • 8.2.4 8.2.4 User ID lifecycle changes authorized
  • 9.3.2 9.3.2 Visitor access procedures for the CDE
  • 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

ISO 27001:2022 · 5 controls

  • 5.1 Policies for information security
  • 5.15 Access control
  • 5.16 Identity management
  • 5.18 Access rights
  • 8.3 Information access restriction
  • ASBv3-PA-7 Follow just enough administration (least privilege) principle
  • IM-7 Restrict resource access based on conditions
  • PA-2 Avoid standing access for user accounts and permissions
  • PA-3 Manage lifecycle of identities and entitlements

CIS Controls v8 · 4 controls

  • CIS-2.3 Address Unauthorized Software
  • CIS-6.1 Establish an Access Granting Process
  • CIS-6.7 Centralize Access Control
  • CIS-6.8 Define and Maintain Role-Based Access Control

CMMC 2.0 · 4 controls

NIST SP 800-53 Rev 5 · 4 controls

SOC 2 · 4 controls

  • SOC2-CC5.3 CC5.3 Deploying controls through policies and procedures (COSO principle 12)
  • 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
  • ANSSI-HYG-09 Assign the Correct Rights on Sensitive Resources
  • ANSSI-HYG-29 Limit Administration Rights on Workstations to Operational Need

FedRAMP High · 2 controls

  • AC-2 Account Management
  • AC-6 Least Privilege

FedRAMP Moderate · 2 controls

  • AC-2 Account Management
  • AC-6 Least Privilege

ISO 27002:2022 · 2 controls

  • 5.18 Access rights
  • 8.19 Installation of software on operational systems
  • NIST-CSF-PR.AA-01 Identities and credentials for authorized users, services, and hardware are managed by the organization
  • 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 SP 800-161 Rev 1 · 2 controls

NIST SP 800-171 Rev 3 · 2 controls

UK Cyber Essentials · 2 controls

  • CE-AC.1 User Account Approval Process
  • CE-AC.4 Privileged Account Approval and Tracking
  • E8-ADMIN-ML1 Restrict Administrative Privileges (ML1)
  • ASD37-18 Restrict administrative privileges (Essential)

C5 (Germany) · 1 control

  • C5-IDM-02 Granting and change of user accounts and access rights

ISO 27701:2019 · 1 control

  • 6.6.2 User access management

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)(ii)(B) 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 59 it maps to, and the evidence behind each claim, over MCP and REST.