Control Objective
Grant the minimum rights needed for each role to do its job — no standing admin rights, no clinic-wide chart access by default, no leftover permissions from prior roles.
Real-World Use Cases
How this control shows up in healthcare and HIPAA-covered environments.
Phished office manager without domain admin
An office manager clicks a phishing link. Because her daily account has no local admin or EHR security roles, the attacker cannot push ransomware widely or create new privileged users. AC-6 limited the incident to password reset and session revoke.
Floater nurse across three clinics
Instead of enterprise-wide chart access, the nurse receives location-scoped EHR roles for the clinics on her schedule. That aligns least privilege with operational reality and minimum necessary.
Integration engine account
An HL7 interface account previously used a full SQL login. AC-6 remediation replaces it with a constrained account that can only read/write required interface tables — cutting exfiltration risk from a compromised interface host.
Audit Considerations
Expect sampling of privileged users and questions about why each high-risk entitlement exists. 'Historical reasons' without business justification is a finding. Map AC-6 narratives to HIPAA minimum necessary.
HIPAA Mapping
How this NIST control supports HIPAA Security Rule expectations.
- 164.502(b) and 164.514(d) Minimum Necessary — Privacy Rule counterpart to least privilege for uses and disclosures of PHI.
- 164.312(a)(1) Access Control — technical access limited to authorized persons aligns with least privilege.
- 164.308(a)(4) Information Access Management — policies to authorize and establish access based on duties.
- 164.308(a)(1) Risk Analysis/Management — excessive privilege is a standard identified risk.