CMMC 2.0
Access Control

CMMC 2.0 AC.L2-3.1.10: Session Lock

Lock the user session after a defined period of inactivity and conceal previously displayed content behind a pattern hiding display until the user reauthenticates.

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

What else in your programme already covers this

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

CIS Controls v8 · 3 controls

  • CIS-14.4 Train Workforce on Data Handling Best Practices
  • CIS-4.10 Enforce Automatic Device Lockout on Portable End-User Devices
  • CIS-4.3 Configure Automatic Session Locking on Enterprise Assets

FedRAMP High · 2 controls

  • AC-11 Device Lock
  • AC-11(1) Device Lock | Pattern-hiding Displays (AC-11(1))

FedRAMP Moderate · 2 controls

  • AC-11 Device Lock
  • AC-11(1) Device Lock | Pattern-hiding Displays (AC-11(1))

ISO 27001:2022 · 2 controls

  • 7.7 Clear desk and clear screen
  • 8.1 User end point devices

NIST SP 800-53 Rev 5 · 2 controls

C5 (Germany) · 1 control

HIPAA Security Rule · 1 control

ISO 27002:2022 · 1 control

  • 7.7 Clear desk and clear screen

PCI DSS 4.0 · 1 control

  • 8.2.8 8.2.8 Re-authentication after 15 minutes idle

SOC 2 · 1 control

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

UK Cyber Essentials · 1 control

  • CE-SC.9 Device Unlocking Credentials and Brute-Force Protection

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.10 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 20 it maps to, and the evidence behind each claim, over MCP and REST.