---
title: "NIST 800-171 3.1.2 (AC.L2-3.1.2): Transaction Control"
description: "NIST SP 800-171 3.1.2 Transaction Control: 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/access-control/3.1.2
sealed: 2026-11-11
amended: 2026-11-11
register: nist-800-171/access-control/3.1.2
records: 7
digest: sha3:54f77720438c819d0843ed237e31d43e0b11c9dd0d1f79fed1a7a1694d1b22de
---

# NIST 800-171 3.1.2 (AC.L2-3.1.2): Transaction Control

NIST 800-171 / Access Control / 3.1.2

"Limit system access to the types of transactions and functions that authorized users are permitted to execute." ([NIST SP 800-171 Rev. 2, requirement 3.1.2](https://doi.org/10.6028/NIST.SP.800-171r2))

CMMC Level 2 practice AC.L2-3.1.2.

## What 3.1.2 means in practice

Being allowed in is not the same as being allowed to do everything. Define what each role may do in each system, such as read, approve, change configuration or export data, and enforce those limits in the systems themselves, usually through roles and groups rather than grants to individual users.

## SPRS points and the CMMC POA&M

- **CMMC Level 2 practice**: AC.L2-3.1.2
- **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.1.2

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

- 3.1.2[a] the types of transactions and functions that authorized users are permitted to execute are defined.
- 3.1.2[b] system access is limited to the defined types of transactions and functions for authorized users.

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

## Evidence that shows 3.1.2 is met

- A role and permission matrix mapping job functions to what each role may do in each system.
- Role and group assignments exported from the identity provider and the key applications.
- Role definitions showing permissions are enforced through roles, such as Azure RBAC role definitions.
- A sample of users whose actual permissions match their documented role.

## How PolicyCortex gathers the evidence

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

- **Azure: Role assignments.** Checks that Azure role assignments restrict users to the transactions and functions their roles permit.

## Related pages

- **Calculator**: [SPRS score calculator: mark 3.1.2 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.1: Authorized Access](https://policycortex.com/nist-800-171/access-control/3.1.1)
- **Next**: [3.1.3: CUI Flow Control](https://policycortex.com/nist-800-171/access-control/3.1.3)
- **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 | 59d5a600cd08 | 363f058cc8a4 |
| REC 0001 | MEANING | aeb6d25b5930 | 59d5a600cd08 |
| REC 0002 | POINTS AND POA&M | 43ced80953e8 | aeb6d25b5930 |
| REC 0003 | ASSESSMENT OBJECTIVES | 52d361b83017 | 43ced80953e8 |
| REC 0004 | EVIDENCE | 08829ee007fb | 52d361b83017 |
| REC 0005 | COLLECTORS | 866de2d210ab | 08829ee007fb |
| REC 0006 | RELATED | 54f77720438c | 866de2d210ab |

Head sha3:54f77720438c819d0843ed237e31d43e0b11c9dd0d1f79fed1a7a1694d1b22de. 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.