CMMC 2.0
Access Control

CMMC 2.0 AC.L2-3.1.8: Unsuccessful Logon Attempts

Cap the number of consecutive failed logon attempts allowed and take a defined action, such as account lockout, once that limit is reached.

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

What else in your programme already covers this

This control maps to 23 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.

  • NIST-CSF-DE.AE-02 Potentially adverse events are analyzed to better understand associated activities
  • NIST-CSF-DE.CM-03 Personnel activity and technology usage are monitored to find potentially adverse events
  • NIST-CSF-PR.AA-03 Users, services, and hardware are authenticated
  • NIST-CSF-PR.PS-04 Log records are generated and made available for continuous monitoring

ISO 27001:2022 · 3 controls

  • 8.15 Logging
  • 8.16 Monitoring activities
  • 8.5 Secure authentication

CIS Controls v8 · 2 controls

  • CIS-4.10 Enforce Automatic Device Lockout on Portable End-User Devices
  • CIS-8.5 Collect Detailed Audit Logs

NIST SP 800-53 Rev 5 · 2 controls

  • NIST800-AC-7 AC-7 Unsuccessful Logon Attempts
  • SP800-53-AC Access Control Family

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

FedRAMP High · 1 control

  • AC-7 Unsuccessful Logon Attempts

FedRAMP Moderate · 1 control

  • AC-7 Unsuccessful Logon Attempts

HIPAA Security Rule · 1 control

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

SOC 2 · 1 control

  • SOC2-CC6.1 CC6.1 Logical access security over protected information assets

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 Access Control

You are reading one control. How much of CMMC 2.0 have you already done?

CMMC 2.0 AC.L2-3.1.8 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of CMMC 2.0 your existing evidence covers. Hold FedRAMP Moderate and 108 of 110 CMMC 2.0 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. 1 were rejected on the FedRAMP Moderate pair alone.

Query this from an agent

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