Downtime break-glass board
Enabling read-only downtime board without normal auth requires dual authorization from house supervisor and IT.
Dual Authorization
High Risk
Complex
Medium Cost
AC-14(1) enhances AC-14 by focusing on dual authorization. Require dual authorization before permitting specific actions without normal identification/authentication (emergency downtime workflows). Covered entities and business associates should implement this with clear ownership, technical enforcement where feasible, and audit evidence aligned to HIPAA Security Rule expectations.
Control Objective
Enforce dual authorization for organization-defined permitted actions that bypass standard identification or authentication.
Implementation Guidance
- List permitted actions that may skip normal ID/auth.
- Require dual authorization before those actions.
- Log both approvers and scope/time.
- Time-box the permitted window.
- Mandate after-action review.
- Train house supervisors on the workflow.
- Prohibit expanding the list casually.
- Tabletop downtime dual-auth activation.
Real-World Use Cases
How this control shows up in healthcare and HIPAA-covered environments.
Emergency code cart PC
Special permitted action to unlock emergency workstation image needs two authorized roles.
Mass casualty identity bypass
Temporary census workflow without full auth requires dual authorization and after-action review.
Best Practices
- Tie AC-14(1) to named owners in IAM/privacy/security.
- Prefer system enforcement over informal email approval.
- Measure coverage on systems that store or transmit ePHI.
- Review exceptions at least quarterly.
- Correlate events into SIEM use cases.
- Document mapping to HIPAA safeguards in the SSP.
Common Gaps & Violations
- Policy claims dual authorization but no technical enforcement on EHR paths.
- Exceptions granted permanently without review.
- Vendors and research feeds left out of scope.
- Logs not retained or not reviewed.
- Upgrades silently disable the control.
Required Documentation
- Policy/procedure for Dual Authorization (AC-14(1))
- Configuration baselines and diagrams
- Exception register
- Sample logs/alerts
- Training or runbook evidence
How to Test & Validate
- Attempt a prohibited action related to dual authorization; confirm block or required workflow.
- Complete an authorized path; confirm success and logging.
- Sample exceptions for expiry and approval.
- Verify ePHI systems in scope are covered (not only corporate IT).
- Confirm SIEM/alert or retention evidence for the last 90 days.
Audit Considerations
Assessors look for operating evidence of Dual Authorization on systems touching ePHI — screenshots, logs, and failed-test results — not only a policy paragraph referencing AC-14(1).
HIPAA Mapping
How this NIST control supports HIPAA Security Rule expectations.
- 164.312(a)(1) Access Control — unique user identification; privileged actions need identified users.
- 164.312(a)(2)(ii) Emergency Access Procedure — tightly bound exceptions when normal auth is unavailable.
- 164.312(d) Person or Entity Authentication — verify identity before privileged functions.
- 164.308(a)(4) Information Access Management — limit unauthorized capability.
Compliance Tips
- List AC-14(1) explicitly in the system security plan control matrix.
- Prioritize EHR, VPN, HIE, and BA file-transfer paths.
- Keep a one-page evidence pack (config + sample log + exception list) ready for assessors.
Frequently Asked Questions
When without auth?
Only for rare permitted actions (e.g., certain downtime) and still dual-authorized.
Same as AC-3(2)?
Related idea; here dual auth gates permitted actions that skip normal identification/authentication.
After-action needed?
Yes — review every use.
References & Resources
- NIST SP 800-53 Rev. 5 — AC-14(1)
- Related controls: AC-14, AC-3(2), AC-5
Related Guidelines
Related controls that commonly accompany AC-14(1).
Need Help Implementing AC-14(1)?
Our auditors map NIST SP 800-53 controls to your HIPAA Security Rule program — policies, technical evidence, and audit readiness.