---
title: "NIST 800-171 3.1.10 (AC.L2-3.1.10): Session Lock"
description: "NIST SP 800-171 3.1.10 Session Lock: 1 SPRS point, allowed on a CMMC POA&M. The text, what assessors check and the evidence."
url: https://policycortex.com/nist-800-171/access-control/3.1.10
sealed: 2026-11-11
amended: 2026-11-11
register: nist-800-171/access-control/3.1.10
records: 7
digest: sha3:fe2ac0401cc064f09cedba94058169165243f42088883795f5327c618e293501
---

# NIST 800-171 3.1.10 (AC.L2-3.1.10): Session Lock

NIST 800-171 / Access Control / 3.1.10

"Use session lock with pattern-hiding displays to prevent access and viewing of data after a period of inactivity." ([NIST SP 800-171 Rev. 2, requirement 3.1.10](https://doi.org/10.6028/NIST.SP.800-171r2))

CMMC Level 2 practice AC.L2-3.1.10.

## What 3.1.10 means in practice

When a user walks away, the screen locks after a set period of inactivity and hides what was on it. Pick the period (15 minutes or less is common), enforce it centrally on every workstation and mobile device, and make sure the lock screen itself shows nothing that reveals CUI.

## SPRS points and the CMMC POA&M

- **CMMC Level 2 practice**: AC.L2-3.1.10
- **SPRS points**: 1 point. When it is not met, the DoD Assessment Methodology subtracts 1 from the score of 110.
- **CMMC POA&M**: Allowed. It is worth 1 point, and 32 CFR 170.21(a)(2)(ii) admits requirements worth 1 point. Conditional status also needs a score of at least 88, and the item must be closed within 180 days.

Sources: [NIST SP 800-171 DoD Assessment Methodology, version 1.2.1 (June 24, 2020), Annex A](https://www.acq.osd.mil/asda/dpc/cp/cyber/docs/safeguarding/NIST-SP-800-171-Assessment-Methodology-Version-1.2.1-6.24.2020.pdf); [32 CFR 170.21, Plan of Action and Milestones requirements](https://www.ecfr.gov/current/title-32/section-170.21).

## What an assessor checks for 3.1.10

NIST SP 800-171A gives 3 determination statements for 3.1.10, each found satisfied or other than satisfied. Determine if:

- 3.1.10[a] the period of inactivity after which the system initiates a session lock is defined.
- 3.1.10[b] access to the system and viewing of data is prevented by initiating a session lock after the defined period of inactivity.
- 3.1.10[c] previously visible information is concealed via a pattern-hiding display after the defined period of inactivity.

[NIST SP 800-171A (June 2018), assessment objectives for 3.1.10](https://doi.org/10.6028/NIST.SP.800-171A)

## Evidence that shows 3.1.10 is met

- The defined inactivity period before the screen locks.
- Group Policy or device management profiles that enforce the screen lock and a password to unlock.
- A device compliance report showing the lock setting applied across managed devices.

## How PolicyCortex gathers the evidence

PolicyCortex reads this evidence with the collectors below, read only, and grades 3.1.10 from it. Each line says what the product checks.

- **Microsoft Intune: Compliance policies · Device configurations.** Checks that every device Intune manages locks after 15 minutes or less of inactivity and needs a password to unlock.

## Related pages

- **Calculator**: [SPRS score calculator: mark 3.1.10 and the other 109 requirements and see the score.](https://policycortex.com/sprs-score-calculator#family-AC)
- **Sample package**: [Sample package: an SSP, a POA&M and an evidence chain the product generated from demonstration data.](https://policycortex.com/sample-package)
- **Family**: [All 22 Access Control requirements (3.1).](https://policycortex.com/nist-800-171/access-control)
- **Previous**: [3.1.9: System Use Notices](https://policycortex.com/nist-800-171/access-control/3.1.9)
- **Next**: [3.1.11: Session Termination](https://policycortex.com/nist-800-171/access-control/3.1.11)
- **All requirements**: [All 110 NIST SP 800-171 requirements, by family.](https://policycortex.com/nist-800-171)

Meet the requirement once. Keep the evidence current. [Request Access](https://app.policycortex.com/auth?mode=request-access) · [Book a call](https://policycortex.com/book)

## Register colophon

| Seq | Label | SHA3-256 | Prev |
|---|---|---|---|
| REC 0000 | REQUIREMENT | 92585dbab7b7 | 051425f4b314 |
| REC 0001 | MEANING | abd49dcb5d00 | 92585dbab7b7 |
| REC 0002 | POINTS AND POA&M | c1b8bbf59c73 | abd49dcb5d00 |
| REC 0003 | ASSESSMENT OBJECTIVES | d41e64274dd5 | c1b8bbf59c73 |
| REC 0004 | EVIDENCE | 022a507efc08 | d41e64274dd5 |
| REC 0005 | COLLECTORS | 61110b623fd4 | 022a507efc08 |
| REC 0006 | RELATED | fe2ac0401cc0 | 61110b623fd4 |

Head sha3:fe2ac0401cc064f09cedba94058169165243f42088883795f5327c618e293501. Each digest is SHA3-256 over the previous digest, the register key, the record label, and the record copy; a second party can recompute it from this document.