NIST 800-171 3.12.1 (CA.L2-3.12.1): Control Assessment

Periodically assess the security controls in organizational systems to determine if the controls are effective in their application.

NIST SP 800-171 Rev. 2, requirement 3.12.1

CMMC Level 2 practice CA.L2-3.12.1Published 2026-11-11

What 3.12.1 means in practice

Check, on a defined schedule, whether the security controls actually work, not only whether they exist. The assessment can be internal or independent, and its findings feed the plan of action.

SPRS points and the CMMC POA&M

CMMC Level 2 practice: CA.L2-3.12.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; 32 CFR 170.21, Plan of Action and Milestones requirements.

What an assessor checks for 3.12.1

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

3.12.1[a] the frequency of security control assessments is defined.
3.12.1[b] security controls are assessed with the defined frequency to determine if the controls are effective in their application.

NIST SP 800-171A (June 2018), assessment objectives for 3.12.1

Evidence that shows 3.12.1 is met

The defined assessment frequency.
The most recent assessment report, with its findings.
The plan of action items the findings created.

How PolicyCortex gathers the evidence

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

Microsoft Defender for Cloud: Secure score and security contacts · Recommendations and assessments. Checks the Microsoft Defender for Cloud secure score against a minimum, and that security assessments ran with documented results.

Related pages

Calculator: SPRS score calculator: mark 3.12.1 and the other 109 requirements and see the score.
Sample package: Sample package: an SSP, a POA&M and an evidence chain the product generated from demonstration data.
Family: All 4 Security Assessment requirements (3.12).
Previous: 3.11.3: Fixing Vulnerabilities
Next: 3.12.2: Plans of Action
All requirements: All 110 NIST SP 800-171 requirements, by family.

Related records

Guides and articles describe the work. The evidence that work produces is described in three proof pages, the architecture page, and the two pages on authorization.

proof.state: Proof of State. What the environment was, as of a date someone else picks: point-in-time records, content hashed and chained.
proof.change: Proof of Change. Who or what altered the environment, under what authority, with before and after state hashes.
proof.agency: Proof of Agency. What a machine was permitted to do before it acted, what it did, and what would have stopped it.
architecture: Architecture. How the chain is built and where the evidence is stored in each delivery mode.
authorization: Continuous ATO. How an authorizing official's decision is recorded with its package, and how the authorized system is checked against it every hour.
baseline: NIST SP 800-53. The Low, Moderate and High baselines as evidence, with the SSP, SAR and POA&M generated from one record.