Control Objective
Reduce the chance that attackers guess or spray passwords against systems that store or process ePHI, while keeping lockout thresholds practical for busy clinical and revenue-cycle workflows.
Implementation Guidance
Define policy values before you configure tools:
- Set a consecutive failed-attempt threshold (commonly 5–10 for healthcare workstations; lower for privileged admin accounts).
- Choose the lockout action: temporary lock (e.g., 15–30 minutes), permanent lock requiring help-desk reset, or progressive delay between attempts.
- Apply the control on every system that authenticates users to ePHI — EHR, practice management, patient portal admin, VPN, RDP gateways, cloud IdP, and privileged bastion hosts.
- Exclude or specially handle shared clinical break-glass / emergency access accounts so a lockout cannot block patient care; monitor those accounts heavily instead.
- Log every failed and successful logon with user ID, source IP/device, timestamp, and application name; forward to your SIEM or audit repository.
- Align help-desk identity proofing for unlocks with your AC-2 account management procedures so social engineering cannot bypass lockouts.
- Review lockout metrics monthly: spikes often signal phishing campaigns or misconfigured MFA, not only malicious brute force.
Real-World Use Cases
How this control shows up in healthcare and HIPAA-covered environments.
Outpatient clinic EHR under password spray
A 12-provider clinic sees hundreds of failed EHR logons overnight from foreign IPs. With AC-7 enforced at the identity provider (5 failures → 30-minute lock), automated sprays stall, and the SOC uses the lockout surge as an early warning to force password resets and enable MFA for remote roles.
Billing vendor portal abuse
A third-party billing company accesses your practice management cloud. Without account lockout, a compromised contractor password can be guessed offline forever. AC-7 on the vendor IdP, plus unique vendor accounts (not shared logins), contains the blast radius and produces audit evidence for BA oversight.
Privileged IT admin on a jump host
Domain admin attempts against a bastion host use a stricter threshold (3 failures → permanent lock requiring dual approval to unlock). Clinical user thresholds stay higher so nurses are not constantly locked out during shift change.
Audit Considerations
Auditors look for written thresholds, technical enforcement evidence (not just policy text), consistent application across systems holding ePHI, and proof that unlocks are controlled. Be ready to show sample lockout tickets and that clinical emergency access was considered.
HIPAA Mapping
How this NIST control supports HIPAA Security Rule expectations.
- 164.312(a)(1) Access Control — technical policies limiting system access to authorized users.
- 164.312(d) Person or Entity Authentication — verifying that a person seeking access is who they claim to be; lockout supports this by resisting guessing attacks.
- 164.308(a)(1)(ii)(A) Risk Analysis — brute-force and credential stuffing should appear as identified risks with AC-7 as a mitigating control.
- 164.308(a)(5)(ii)(C) Log-in Monitoring — procedures for monitoring log-in attempts and reporting discrepancies complement AC-7 telemetry.