NIST SP 800-171 Rev 3
03.01 AC (Access Control)

NIST SP 800-171 Rev 3 03.01.08: Unsuccessful Logon Attempts

Enforce a limit of consecutive invalid logon attempts and lock the account/node for a defined period.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 16 controls across 15 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

UK Cyber Essentials · 2 controls

  • CE-SC.5 Password-Based Authentication Quality
  • CE-SC.9 Device Unlocking Credentials and Brute-Force Protection
  • ASBv3-LT-2 Enable threat detection for identity and access management

C5 (Germany) · 1 control

  • C5-IDM-03 Locking and withdrawal of user accounts in the event of inactivity or multiple failed logins

CIS Controls v8 · 1 control

  • CIS-4.10 Enforce Automatic Device Lockout on Portable End-User Devices

CMMC 2.0 · 1 control

FedRAMP High · 1 control

  • AC-7 Unsuccessful Logon Attempts

FedRAMP Moderate · 1 control

  • AC-7 Unsuccessful Logon Attempts

HIPAA Security Rule · 1 control

ISO 27001:2022 · 1 control

  • 8.5 Secure authentication

ISO 27002:2022 · 1 control

  • 8.5 Secure authentication

PCI DSS 4.0 · 1 control

  • 8.3.4 8.3.4 Lockout after 10 attempts for 30 minutes

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in 03.01 AC (Access Control)

You are reading one control. How much of NIST SP 800-171 Rev 3 have you already done?

NIST SP 800-171 Rev 3 03.01.08 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of NIST SP 800-171 Rev 3 your existing evidence covers. Hold PCI DSS 4.0 and 69 of 97 NIST SP 800-171 Rev 3 controls already carry evidence.

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 0 were rejected on the PCI DSS 4.0 pair alone.

Query this from an agent

The graph holds this control, the 16 it maps to, and the evidence behind each claim, over MCP and REST.