AC.L2-3.1.2 Transaction & function control
What the standard requires
Limit system access to the types of transactions and functions that authorized users are permitted to execute.
Quoted verbatim from NIST SP 800-171 Rev 2 (NIST CPRT), which is in the public domain.
Maps to 2 controls in 2 other frameworks
| Framework | Control |
|---|---|
| CMMC Level 1 | AC.L1-3.1.2 Limit access to authorized transactions and functions |
| NIST Cybersecurity Framework (1.1, legacy) | PR.AC-4 Access permissions and authorizations managed |
Mappings are CMDash’s own, seeded with the product and shown on both frameworks they connect. In the product they mean evidence you attach here also counts against the controls listed above.
Integrations that carry evidence for this family
These connectors produce data relevant to CMMC Level 2’s Access Control family, which is the granularity CMDash publishes — there is no pre-built per-control mapping, and claiming one would be inventing it. You decide which evidence answers which control.
In CMDash this control is a row with an owner, a status, uploaded evidence kept with its full history, and an export an assessor can read.