If your defense contracts include DFARS 252.204-7012, your NIST SP 800-171 implementation is summarized as one number in the Supplier Performance Risk System (SPRS): a score out of 110. This guide explains what DFARS 252.204-7019 and 252.204-7020 require, how the DoD Assessment Methodology subtracts 5, 3, or 1 point for each unmet requirement, why a plan of action does not earn points back, and what the CMMC rule allows on a POA&M, based on the official regulation text.
If your defense contracts include DFARS 252.204-7012, you are required to implement the security requirements in NIST SP 800-171. DoD does not read every supplier's security documentation before award. Instead, it looks at a summary score posted in the Supplier Performance Risk System (SPRS), written as a number out of 110.
That number comes from the NIST SP 800-171 DoD Assessment Methodology, which DFARS 252.204-7019 and 252.204-7020 reference. This guide explains how the score is calculated, what you report, and why a plan of action does not earn points back. It is written for Inland Empire aerospace and defense suppliers, from machine shops in Ontario and Chino to engineering firms in Rancho Cucamonga.
DFARS 252.204-7019 says that, to be considered for award, an offeror that is required to implement NIST SP 800-171 must have a current assessment for each covered contractor information system relevant to the offer. Current means not more than 3 years old, unless the solicitation specifies a shorter period. The offeror must verify that the summary level score is posted in SPRS.
DFARS 252.204-7020 adds the contract side. You must give the Government access to your facilities, systems, and personnel if it needs to conduct a Medium or High Assessment. The clause also flows down: a contractor may not award a subcontract that is subject to NIST SP 800-171 unless the subcontractor has completed at least a Basic Assessment within the last 3 years. If you supply a larger prime, expect them to ask whether your score is posted and current.
A Basic Assessment is your own self-assessment. DFARS 252.204-7020 says it is based on your review of your system security plan (SSP), follows the DoD Assessment Methodology, and results in a confidence level of "Low" because the score is self-generated. This is the assessment most small suppliers post.
A Medium Assessment is conducted by the Government. It reviews your Basic Assessment, includes a thorough document review, and involves discussions with you as needed. It results in a "Medium" confidence level.
A High Assessment is also conducted by Government personnel, using NIST SP 800-171A. On top of the Medium steps, it includes verification, examination, and demonstration of your SSP to confirm the requirements are implemented as described. It results in a "High" confidence level. For Medium and High Assessments, the clause gives you 14 business days after the assessment to provide additional information or rebut findings.
The DoD Assessment Methodology starts from 110, the total number of NIST SP 800-171 security requirements. If every requirement is implemented, the score is 110. For each requirement that is not implemented, its value is subtracted. Because some requirements are worth more than one point, the score can go negative.
The methodology weights requirements by their effect on the system and the CUI on it:
5 points: requirements that, if not implemented, could lead to significant exploitation of the network or exfiltration of CUI. Examples include 3.1.1 (limit system access to authorized users), 3.5.1 and 3.5.2 (identify and authenticate users and devices), 3.6.1 and 3.6.2 (incident handling and reporting), 3.8.7 (control removable media), 3.12.1 and 3.12.3 (assess and monitor security controls), and 3.14.1 through 3.14.3 (flaw remediation, malicious code protection, and security alerts).
3 points: requirements with a specific and confined effect, such as 3.1.19 (encrypt CUI on mobile devices), 3.8.2 (limit access to CUI on system media), 3.11.1 (risk assessments), and 3.12.2 (plans of action).
1 point: all remaining derived requirements, which have a limited or indirect effect, such as 3.5.5 (prevent reuse of identifiers for a defined period).
The methodology is not designed to credit partial implementation, with two exceptions. For multifactor authentication (3.5.3), 3 points are subtracted if MFA is implemented only for remote and privileged users, and 5 points if it is not implemented for any users. For FIPS-validated cryptography (3.13.11), 3 points are subtracted if encryption is used but is not FIPS validated, and 5 points if encryption is not used at all.
Here is a hypothetical company, for illustration only. It has implemented everything except three items: MFA covers only remote and privileged users (minus 3), file encryption is not FIPS validated (minus 3), and one 1-point requirement is not yet in place (minus 1). Its score is 110 minus 7, or 103. The same company with no MFA at all would lose 5 points instead of 3 for that requirement.
The methodology is based on reviewing your system security plan (requirement 3.12.4). Without an SSP, the result is a finding that an assessment could not be completed due to incomplete information and noncompliance with DFARS 252.204-7012. The SSP is the foundation, not paperwork to finish later.
You need a plan of action (requirement 3.12.2) for each requirement you have not implemented, describing how and when it will be met. If you are missing a plan of action, 3.12.2 itself is scored as not implemented.
A plan of action does not earn points back. The methodology says plans of action are not a substitute for a completed requirement, and its own example is MFA that is 75 percent rolled out: it is still scored as not implemented. The exception is a temporary deficiency, such as a patch that unexpectedly breaks FIPS validation after a requirement was implemented. If it is addressed in a plan of action with milestones and progress, it can be scored as implemented.
The CMMC rule sets stricter limits. Under 32 CFR 170.21, a POA&M is never permitted for a Level 1 self-assessment. To reach a Conditional Level 2 status, all of the following must be true:
1. The score divided by the number of Level 2 requirements is at least 0.8, which works out to at least 88 of 110.
2. No requirement on the POA&M is worth more than 1 point, except 3.13.11 when encryption is used but is not FIPS validated.
3. None of these six are on the POA&M: 3.1.20 external connections, 3.1.22 control public information, 3.12.4 system security plan, 3.10.3 escort visitors, 3.10.4 physical access logs, and 3.10.5 manage physical access.
The POA&M must then be closed out within 180 days of the Conditional status date, or the Conditional status expires. For a Level 2 self-assessment, you perform the closeout the same way as the initial self-assessment. For a Level 2 certification assessment, an authorized C3PAO must perform it. The CMMC scoring at 32 CFR 170.24 uses the same 5, 3, and 1 point structure, and adds that evidence must be in final form; drafts, working papers, and unapproved policies are not acceptable.
For a Basic Assessment, DFARS 252.204-7020 lists what to submit for posting to SPRS: the version of NIST SP 800-171 assessed, who conducted the assessment (for example, a contractor self-assessment), the CAGE codes covered by each SSP, a brief description of the SSP architecture if you have more than one plan, the date the assessment was completed, the summary score (for example, 95 out of 110, not the value of each requirement), and the date you expect to reach 110 based on your plans of action. The clause describes submitting this by encrypted email to webptsmh@navy.mil; check the SPRS site for current instructions.
NIST lists SP 800-171 Revision 2 as withdrawn on May 14, 2024 and superseded by Revision 3. The CMMC rule, however, says the CMMC Level 2 requirements are identical to those in NIST SP 800-171 R2 (32 CFR 170.14), and the DoD Assessment Methodology scores the 110 Revision 2 requirements. Before you score, confirm the version your contract and solicitation require, and record it in your submission.
1. Scoring a policy instead of practice. A written MFA policy does not earn 3.5.3 if MFA is not enforced.
2. Taking partial credit the methodology does not allow, such as counting a half-finished rollout as implemented.
3. Leaving out systems that store, process, or transmit CUI, such as a file share, a CAD workstation, or a cloud mailbox, so the SSP does not match reality.
4. Letting the score go stale. A score older than 3 years is not current for award purposes.
5. Posting a 110 completion date that the plans of action cannot support.
1. Confirm which contracts include DFARS 252.204-7012, 7019, or 7020, and which systems handle CUI.
2. Write or update your SSP so it matches how your systems actually work today.
3. Score each of the 110 requirements honestly against the DoD Assessment Methodology, using evidence rather than intent.
4. Build a plan of action for every gap, with owners and dates, and start with the 5-point items.
5. Post the summary score in SPRS, and calendar a reassessment well before the 3-year mark or whenever your environment changes significantly.
6. If you expect a CMMC Level 2 requirement, close gaps so you are not relying on a POA&M for anything the CMMC rule excludes.
SPRS scores and the DoD Assessment Methodology apply to defense contractors. Law firms and medical and dental practices have their own obligations, which they should confirm with counsel. The approach still translates: know where sensitive data lives, document how it is protected, measure gaps honestly, and track fixes to completion. Our industries page covers how we support each of these practices.
Integrity Security Defense Corp helps Inland Empire defense suppliers prepare for assessment through CMMC readiness support, including gap reviews, SSP and plan of action development, and score preparation, backed by managed cybersecurity and managed IT to close the gaps. We are not a C3PAO, we are not an authorized CMMC assessor, and we do not certify companies or post scores on your behalf. This article is general information, not legal advice; your contract and the current regulations control. To review where your score stands, contact us or call (909) 310-2022.
eCFR, DFARS 252.204-7019 Notice of NIST SP 800-171 DoD Assessment Requirements
eCFR, DFARS 252.204-7020 NIST SP 800-171 DoD Assessment Requirements
eCFR, DFARS 252.204-7012 Safeguarding Covered Defense Information and Cyber Incident Reporting
DoD, NIST SP 800-171 DoD Assessment Methodology, Version 1.2.1 (PDF)
eCFR, 32 CFR 170.21 Plan of Action and Milestones requirements
eCFR, 32 CFR 170.24 CMMC Scoring Methodology
Integrity Security Defense Corp helps Inland Empire defense contractors with CMMC readiness and managed cybersecurity. We are not a C3PAO and do not perform official certification assessments.