AC-14 Access Control

Permitted Actions Without Identification or Authentication

Medium Risk Moderate Low Cost

AC-14 requires identifying user actions that can be performed on the information system without identification or authentication, and documenting or providing a rationale for why those actions are permitted. Anything left anonymous expands attack surface. Healthcare organizations must deliberately inventory public and pre-login functions — patient self-scheduling landing pages, status boards, guest Wi-Fi captive portals, and device discovery protocols — and keep them free of ePHI exposure.

Control Objective

Know every unauthenticated action your systems allow, justify each one, and ensure none of them disclose ePHI or weaken pathways into authenticated clinical systems.

Implementation Guidance

  1. Inventory all services reachable without login: public websites, patient portal pre-auth pages, appointment request forms, EHR recovery endpoints, API health checks, guest Wi-Fi, digital signage, fax-to-email gateways, and vendor remote tools in pre-auth state.
  2. For each action, document: what it does, why authentication is not required, what data is exposed, and who owns residual risk.
  3. Prohibit unauthenticated access to any resource containing ePHI or detailed clinical operational data.
  4. Place anonymous functions on segmented networks or separate cloud apps — not on the same host as EHR admin interfaces.
  5. Rate-limit and monitor anonymous endpoints for abuse (scraping, account enumeration, form spam).
  6. Re-review the inventory after new digital front-door or telehealth projects.
  7. If a legacy system requires anonymous access for clinical workflow, record compensating controls (physical area limits, read-only data, no PHI) in the risk analysis.

Real-World Use Cases

How this control shows up in healthcare and HIPAA-covered environments.

Patient portal 'forgot password' enumeration

An unauthenticated password-reset page reveals whether an email is registered. Attackers harvest valid patient portal accounts. AC-14 review flags this action, and the team switches to generic responses plus rate limiting — still unauthenticated, but safer and documented.

Waiting-room status board

A clinic displays first-name + appointment status on a lobby screen with no login. AC-14 documentation justifies limited non-sensitive display data, bans full names/MRNs, and segments the player device from the clinical VLAN.

Misplaced diagnostic web UI

A medical device exposes an unauthenticated web admin page on the clinic LAN. AC-14 inventory during a risk analysis discovers it; the team disables remote admin or puts it behind authentication and network ACL — preventing anonymous configuration changes.

Best Practices

  • Maintain a living register of unauthenticated actions and review it annually.
  • Default to authentication required; treat anonymous access as an exception.
  • Never put ePHI on anonymous pages 'for convenience.'
  • Segment public-facing apps from clinical networks.
  • Log and alert on spikes to anonymous endpoints.
  • Include IoT/biomed devices in the AC-14 inventory — not only websites.

Common Gaps & Violations

  • No inventory; teams discover anonymous interfaces only after an incident.
  • Patient forms collecting SSNs or clinical details without authentication or TLS controls.
  • Biomed devices with default unauthenticated admin interfaces on production LAN.
  • Directory listings or test pages left reachable without login.
  • Guest Wi-Fi that can route to EHR subnets.

Required Documentation

  • AC-14 inventory of permitted unauthenticated actions with rationale
  • Network diagrams showing public vs authenticated zones
  • Risk-acceptance records for any residual anonymous access
  • Change tickets when anonymous endpoints are added or removed
  • Screenshots/config of rate limits and WAF rules where used

How to Test & Validate

  1. From an unauthenticated browser/network stance, crawl public and internal pre-auth surfaces; compare findings to the inventory.
  2. Confirm anonymous pages do not display or return ePHI.
  3. Verify guest/public VLANs cannot reach EHR or file servers.
  4. Test password-reset and registration flows for account enumeration.
  5. Spot-check biomed/IoT admin interfaces for open access.

Audit Considerations

Auditors expect a documented list — empty lists are fine if true — and sampling that anonymous functions match the rationale. Surprise unauthenticated admin interfaces are high-severity findings.

HIPAA Mapping

How this NIST control supports HIPAA Security Rule expectations.

  • 164.312(a)(1) Access Control — access to systems with ePHI must be limited to authorized persons; anonymous actions must not undermine that.
  • 164.312(d) Person or Entity Authentication — document where authentication is intentionally not applied and why.
  • 164.308(a)(1) Risk Analysis — unauthenticated services are risks that must be identified and treated.
  • 164.312(e) Transmission Security — public forms and portals still require integrity/encryption protections even when pre-auth.

Compliance Tips

  • Add AC-14 inventory updates to the digital front-door project checklist.
  • Have privacy review any unauthenticated form that collects patient data.
  • Include 'no open admin interfaces' in biomed procurement requirements.

Frequently Asked Questions

Does AC-14 ban all anonymous access?

No. It requires you to identify and justify permitted unauthenticated actions — and keep them free of inappropriate ePHI exposure.

Are public marketing websites in scope?

Yes if they are organizational information systems. They usually appear on the inventory with a simple rationale and no PHI.

How does AC-14 relate to AC-3?

AC-14 covers the rare actions allowed before identity is established; AC-3 enforces authorizations after authentication.

References & Resources

  • NIST SP 800-53 Rev. 5 — AC-14 Permitted Actions without Identification or Authentication
  • HIPAA Security Rule §§ 164.308(a)(1), 164.312(a), 164.312(d), 164.312(e)
  • Related controls: AC-3, AC-7, AC-17, IA-2, SC-7, SI-10

Need Help Implementing AC-14?

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