AC-6 Access Control

Least Privilege

High Risk Moderate Medium Cost

AC-6 requires employing the principle of least privilege by allowing only authorized accesses for users (or processes acting on behalf of users) that are necessary to accomplish assigned organizational tasks. In healthcare programs it pairs tightly with HIPAA minimum necessary and is one of the highest-leverage controls for shrinking blast radius when credentials are phished or a workstation is misused.

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.

Implementation Guidance

  1. Build roles from job tasks, not from copying an existing power user.
  2. Default new accounts to a restrictive baseline; add entitlements only with approval.
  3. Split privileged activities onto separate admin accounts; daily email/EHR work uses a standard account.
  4. Time-limit elevated access (just-in-time / temporary group membership) for changes and troubleshooting.
  5. Restrict software install rights, local admin, and PowerShell remoting on clinical endpoints.
  6. Limit bulk export, report, and API scopes that can extract large ePHI sets.
  7. Re-certify high-risk entitlements frequently; remove unused privileges automatically where tooling allows.
  8. Apply least privilege to service accounts and integrations — not only humans.

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.

Best Practices

  • Use just-in-time elevation for IT admins.
  • Ban everyday use of domain-admin or EHR-security accounts.
  • Review 'report all patients' and bulk-export rights aggressively.
  • Prefer allow-lists for admin tools on workstations.
  • Align role design with HIPAA minimum necessary policies.
  • Monitor for privilege escalation events and newly added high-risk entitlements.

Common Gaps & Violations

  • Everyone in 'Clinical' gets the same broad EHR template.
  • IT staff browse the web while logged in as domain admin.
  • Temporary elevated access never expires.
  • Vendors given full admin 'to make support easier.'
  • Service accounts with Domain Admin or db_owner for convenience.

Required Documentation

  • Least privilege / privileged access policy
  • Role design standard and high-risk entitlement catalog
  • JIT / temporary access procedure
  • Privileged account inventory
  • Evidence of privilege reduction initiatives or access certifications

How to Test & Validate

  1. Inspect a sample of users for standing local admin or EHR security roles they do not need.
  2. Confirm separate admin accounts exist for privileged staff and are not used for email.
  3. Test that temporary elevation expires automatically.
  4. Review service account privileges against required functions.
  5. Attempt a bulk export with a standard clinical role; confirm deny or strong controls.

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.

Compliance Tips

  • Run a quarterly 'top 25 over-privileged accounts' cleanup sprint.
  • Add least-privilege checks to new EHR module go-live criteria.
  • In BAAs and vendor access forms, require least-privilege vendor accounts by default.

Frequently Asked Questions

Is least privilege the same as minimum necessary?

They are aligned. Minimum necessary is a HIPAA Privacy Rule standard for PHI uses/disclosures; AC-6 is the technical/organizational privilege principle across systems. Implement them together.

Do clinicians need broad chart access for emergencies?

Use break-glass emergency access with monitoring instead of standing enterprise-wide rights for everyone.

Where should we start if privileges are a mess?

Start with privileged IT accounts, bulk-export rights, and terminated-user cleanup — highest risk, fastest win.

References & Resources

  • NIST SP 800-53 Rev. 5 — AC-6 Least Privilege
  • HIPAA Privacy Rule minimum necessary (§§ 164.502(b), 164.514(d))
  • Related controls: AC-2, AC-3, AC-5, AC-17, IA-2, CM-7

Need Help Implementing AC-6?

Our auditors map NIST SP 800-53 controls to your HIPAA Security Rule program — policies, technical evidence, and audit readiness.