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.
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.
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.