AC-7 Access Control

Unsuccessful Logon Attempts

High Risk Moderate Low Cost

AC-7 requires the organization to enforce a limit on consecutive unsuccessful logon attempts to an information system and take an organization-defined action (such as locking the account for a defined period or delaying the next logon) when that limit is exceeded. The control slows automated password guessing and credential stuffing without becoming a denial-of-service weapon against legitimate clinicians.

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:

  1. Set a consecutive failed-attempt threshold (commonly 5–10 for healthcare workstations; lower for privileged admin accounts).
  2. Choose the lockout action: temporary lock (e.g., 15–30 minutes), permanent lock requiring help-desk reset, or progressive delay between attempts.
  3. 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.
  4. Exclude or specially handle shared clinical break-glass / emergency access accounts so a lockout cannot block patient care; monitor those accounts heavily instead.
  5. Log every failed and successful logon with user ID, source IP/device, timestamp, and application name; forward to your SIEM or audit repository.
  6. Align help-desk identity proofing for unlocks with your AC-2 account management procedures so social engineering cannot bypass lockouts.
  7. 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.

Best Practices

  • Prefer MFA + rate limiting over aggressive permanent lockouts for clinical end users.
  • Use shorter lockouts for standard users and permanent locks only for privileged accounts.
  • Never leave default 'unlimited retries' on legacy EHR clients, RDP, or VPN appliances.
  • Alert on lockout storms and geographically impossible failures.
  • Document emergency unlock procedures that still require identity verification.
  • Pair AC-7 with AC-2 (account management) and IA-5 (authenticator management).

Common Gaps & Violations

  • No lockout policy on legacy clinical apps that authenticate locally.
  • Shared 'nurse station' accounts that lock everyone when one person mistypes a password.
  • Help desk unlocking accounts with no identity proofing.
  • Permanent lockouts that create care delays with no break-glass path.
  • Failed logons not retained long enough to meet audit / HIPAA documentation needs.

Required Documentation

  • Access Control / Authentication Policy stating thresholds and actions
  • Account lockout and unlock standard operating procedure
  • Emergency / break-glass unlock procedure
  • Log retention settings for failed authentication events
  • Screenshots or config exports from IdP, AD, EHR, VPN showing enforced limits

How to Test & Validate

  1. From a test account, intentionally fail logon N+1 times and confirm the configured action triggers.
  2. Verify the lockout is recorded in authentication logs with correct user and source.
  3. Confirm unlock requires the documented process (time expiry or help-desk verification).
  4. Spot-check at least one clinical app, one remote access path, and one privileged path.
  5. Review SIEM alerts for lockout threshold breaches over the prior 30 days.

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.

Compliance Tips

  • Put numeric thresholds in policy so assessors are not guessing from screenshots alone.
  • If a clinical system cannot enforce lockout natively, place it behind an IdP/SSO that can.
  • Track vendor systems in your BAA inventory and require AC-7-equivalent controls in contract security exhibits.

Frequently Asked Questions

Will AC-7 lockouts disrupt clinicians during busy shifts?

Use moderate thresholds and temporary locks for clinical roles, reserve hard locks for admins, and document a verified unlock path so care is not blocked.

Is account lockout enough without MFA?

No. AC-7 slows guessing; MFA stops most stolen-password logons. Use both for remote and privileged access to ePHI.

How does AC-7 differ from AC-2?

AC-2 covers the account lifecycle (create, modify, disable). AC-7 is the runtime defense that reacts when logon attempts fail repeatedly.

References & Resources

  • NIST SP 800-53 Rev. 5 — AC-7 Unsuccessful Logon Attempts
  • NIST SP 800-63B Digital Identity Guidelines (authentication & throttling)
  • HIPAA Security Rule §§ 164.312(a), 164.312(d), 164.308(a)(5)
  • Related controls: AC-2, AC-11, AC-12, IA-2, IA-5, AU-2

Need Help Implementing AC-7?

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