---
title: "NIST 800-171 3.5.1 (IA.L2-3.5.1): Identification"
description: "NIST SP 800-171 3.5.1 Identification: 5 SPRS points, not allowed on a CMMC POA&M. The text, what assessors check and the evidence."
url: https://policycortex.com/nist-800-171/identification-and-authentication/3.5.1
sealed: 2026-11-11
amended: 2026-11-11
register: nist-800-171/identification-and-authentication/3.5.1
records: 7
digest: sha3:557a9808586ba0dc37f086e5161a9a8e5fe764232480504a9054c63c73575097
---

# NIST 800-171 3.5.1 (IA.L2-3.5.1): Identification

NIST 800-171 / Identification and Authentication / 3.5.1

"Identify system users, processes acting on behalf of users, and devices." ([NIST SP 800-171 Rev. 2, requirement 3.5.1](https://doi.org/10.6028/NIST.SP.800-171r2))

CMMC Level 2 practice IA.L2-3.5.1.

## What 3.5.1 means in practice

Every user, service process and device gets its own identifier, so the system always knows who or what is acting. Shared logins for interactive use defeat this, and so do service accounts that nobody can tie to an application and an owner.

## SPRS points and the CMMC POA&M

- **CMMC Level 2 practice**: IA.L2-3.5.1
- **SPRS points**: 5 points. When it is not met, the DoD Assessment Methodology subtracts 5 from the score of 110.
- **CMMC POA&M**: Not allowed. It is worth 5 points, and 32 CFR 170.21(a)(2)(ii) admits only requirements worth 1 point, with one exception: 3.13.11 when encryption is used but not FIPS validated.

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.5.1

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

- 3.5.1[a] system users are identified.
- 3.5.1[b] processes acting on behalf of users are identified.
- 3.5.1[c] devices accessing the system are identified.

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

## Evidence that shows 3.5.1 is met

- The procedure for issuing identifiers to users, service accounts and devices.
- A list of service accounts and managed identities, each with the application it runs and its owner.
- Device identity records, such as directory objects or device management enrollments.

## How PolicyCortex gathers the evidence

No PolicyCortex collector reads the evidence for 3.5.1. Your team provides the evidence listed above.

## Related pages

- **Calculator**: [SPRS score calculator: mark 3.5.1 and the other 109 requirements and see the score.](https://policycortex.com/sprs-score-calculator#family-IA)
- **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 11 Identification and Authentication requirements (3.5).](https://policycortex.com/nist-800-171/identification-and-authentication)
- **Previous**: [3.4.9: User-Installed Software](https://policycortex.com/nist-800-171/configuration-management/3.4.9)
- **Next**: [3.5.2: Authentication](https://policycortex.com/nist-800-171/identification-and-authentication/3.5.2)
- **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 | 16b230837d01 | eac2f3c66c53 |
| REC 0001 | MEANING | d3441455e076 | 16b230837d01 |
| REC 0002 | POINTS AND POA&M | 04b9ccd2858b | d3441455e076 |
| REC 0003 | ASSESSMENT OBJECTIVES | 92ef4c0a4f4c | 04b9ccd2858b |
| REC 0004 | EVIDENCE | 155999d356e5 | 92ef4c0a4f4c |
| REC 0005 | COLLECTORS | b2fb9af76fb2 | 155999d356e5 |
| REC 0006 | RELATED | 557a9808586b | b2fb9af76fb2 |

Head sha3:557a9808586ba0dc37f086e5161a9a8e5fe764232480504a9054c63c73575097. 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.