Security Assessment is the first requirement in the Security Assessment and Monitoring (03.12) family, and it is how you confirm that your controls actually work. It requires assessing the security requirements for the system and its environment of operation on a defined frequency to determine whether those requirements have been satisfied. Security Assessment (03.12.01) is what produces the findings that Risk Response (03.11.04) acts on and that the Plan of Action and Milestones (03.12.02) tracks. Per the NIST discussion, assessing the security requirements determines whether safeguards are implemented correctly, operating as intended, and producing the desired outcome, and the results are documented in assessment reports and provided to the appropriate individuals or roles.
A common difficulty with this requirement is treating the assessment as a one-time event tied only to certification, rather than a recurring activity. R3 ties the assessment to a defined frequency, so an assessment that happens once and is never repeated does not satisfy the requirement. For Department of Defense (DoD) contractors, that frequency is specified.
Where things stand for companies facing the transition from NIST 800-171 R2 to R3:
The following is reproduced verbatim from NIST 800-171 R3, requirement 03.12.01 Security Assessment. Only the formatting has been adjusted for readability. This is a single statement with no lettered parts:
The source control is CA-02 from NIST 800-53. The bracketed assignment is the Organization-Defined Parameter (ODP): the assessment frequency. Per the NIST discussion, security assessments identify weaknesses in the system and provide the essential information needed to make risk-based decisions, and assessment reports document results in sufficient detail to determine their accuracy and completeness. You can read the requirement directly at NIST 800-171 R3, 03.12.01 (p. 55).
One (1) value sits inside this requirement. Depending on your contract, your organization may be permitted to define it. Organizations in the DIB subject to CMMC are not, because the DoD has defined it as policy.
The value below comes from Attachment A of the DoD Chief Information Officer (CIO) memorandum dated 10 April 2025 (signed David W. McKeown). The memo identifies each parameter by requirement sub-part, while NIST 800-171A R3 identifies the same parameter by ODP number. Both identifiers appear below so you can match your System Security Plan (SSP) language to either document.
The memo states that its values "will be updated as necessary," so confirm against the current version before writing them into policy.
NIST 800-171A R3 breaks 03.12.01 into two (2) assessment objectives: one (1) Organization-Defined Parameter (ODP) and one (1) determination statement. These AOs are:
The determination statement is that the requirements are assessed at the defined frequency. If you are a DoD contractor, the ODP is specified. Per the DoD-specified ODP value in ComplianceForge's NIST 800-171 R3 Transition Guide, the assessment frequency (ODP[01]) is at least every twelve (12) months, or when there are significant incidents or significant changes to risks. The full guidance on assessment methods and objects, is in NIST 800-171A R3, 03.12.01 (p. 71).
Note that the requirement is titled Security Assessment in both the NIST 800-171 R3 and NIST 800-171A R3 publications. Some control listings use the underlying NIST 800-53 control name, Control Assessments.
Examine: security assessment and monitoring policy and procedures; procedures for security assessment planning; security assessment plan; security assessment report; system security plan.
Interview: personnel with security assessment responsibilities; personnel with information security responsibilities.
Test: mechanisms for supporting security assessments, processes for security assessment plan development, or security assessment reporting.
03.12.01 maps from NIST 800-171 R2 requirement 3.12.1 (periodically assess the security controls in organizational systems to determine if the controls are effective in their application):
Mapped against the two (2) AOs, both (2) are direct (minimal effort), with no net-new AOs and none with no mapping. This is a clean carry-forward. R2 assessed security controls; R3 assesses the security requirements for the system and its environment of operation, which is a wording shift consistent with the R3 use of requirements. If you assessed controls periodically under R2, confirm the assessment now covers the requirements and their environment on the defined frequency.
Source Control in NIST 800-53 R5:
Secure Controls Framework (SCF) Crosswalk
Organizations running a single control set across multiple frameworks can satisfy 03.12.01 through the following SCF controls:
The crosswalks from NIST 800-171 R3 and NIST 800-171A R3 to the SCF are available at no cost through the SCF Set Theory Relationship Mapping (STRM): https://securecontrolsframework.com/start-here/set-theory-relationship-mapping-strm. The STRM also carries the relationship type for each mapping (Equal, Subset Of, Intersects With), which tells you whether an SCF control fully satisfies the requirement or only part of it. Mapping above taken from SCF 2026.3.
The following are issues teams may encounter rather than certainties. They are about cadence and scope, each of which needs documented evidence of due diligence and due care such as policies, standards, procedures, and configuration screenshots:
Reasonable objective evidence for an assessment is often subjective. The following examples of evidence to address NIST 800-171 R3 03.12.01 are sourced from the SCF Evidence Request List (ERL), available at https://securecontrolsframework.com/free-content/scf-download. These ERL artifacts are mapped to NIST 800-171 R3 03.12.01 through SCF controls. They establish a starting point for discussions on what an organization needs to have for evidence of due diligence and due care to withstand external scrutiny by an assessor or regulator.
Alongside these, keep the System Security Plan (SSP) narrative for 03.12.01 recording the ODP values you adopted.
With both AOs mapping directly, 03.12.01 is a light lift once the cadence is set. A realistic sequence:
What value does the DoD require for the organization-defined parameter in NIST 800-171 R3 03.12.01? R3 leaves the value to the organization. For the DIB, the DoD set it in the 10 April 2025 memorandum under ODP identifier 03.12.01: at least every 12 months, or when there are significant incidents or significant changes to risks.
How many assessment objectives does NIST 800-171 R3 03.12.01 have? NIST 800-171A R3 breaks 03.12.01 into two (2) assessment objectives: one (1) Organization-Defined Parameters (ODPs) and one (1) determination statements. An assessor works through each one separately, so each needs its own evidence.
Which NIST 800-53 R5 control does NIST 800-171 R3 03.12.01 come from? CA-02.
Where does NIST 800-171 R3 03.12.01 sit in the NIST 800-171 R3 Kill Chain? Phase 22, Internal Audit (IA). The Kill Chain is a phased model for sequencing R3 implementation, and it assigns this requirement to that phase.
03.12.01 Security Assessment assesses the security requirements for the system and its environment on a defined frequency to determine whether they are satisfied. It maps directly from R2 3.12.1, so there is no net-new work. The recurring problem is a one-time, certification-only assessment. Set the frequency (for DoD, at least every twelve months), assess the requirements and environment, document the results, and feed findings into risk response and your plan of action and milestones.
Authoritative sources:
Authoritative sources:
This guide reproduces U.S. Government text from NIST 800-171 R3 and NIST 800-171A R3 and references the DoD ODP memorandum of 10 April 2025. It is educational, not legal or assessment advice. Last reviewed: 2026-09-22.
