Under the DoD Assessment Methodology, 42 of the 110 NIST SP 800-171 requirements carry a fixed weight of 5 points, and two more (3.5.3 multifactor authentication and 3.13.11 FIPS-validated cryptography) cost 3 to 5 depending on how far they are implemented. Together, those 44 requirements account for 220 of the 313 points a company can lose, about 70 percent of the entire downside, while making up 40 percent of the requirement list. They are also the requirements that cannot sit on a plan of action if you ever need a conditional CMMC status. If your shop has a limited number of hours to spend on compliance this quarter, the Department has already told you where to spend them. This article lists every five-point requirement by family, says what done looks like at a 40-person shop, and lays out the order for the first 30 to 60 days.
The scoring mechanics (why you start at 110, why the floor is −203, the partial-credit rules) are covered in Your SPRS Score, Explained. This article assumes that background and goes straight to the triage.
Why weight decides the order of work
The methodology does not treat the 110 requirements as equal. Section 5(d) assigns 5 points to requirements whose absence "could lead to significant exploitation of the network, or exfiltration of DoD CUI," 3 points to those with "a specific and confined effect," and 1 point to everything else. The arithmetic that follows is simple and brutal: one five-point gap costs as much as five one-point gaps.
Consider a shop that assesses honestly and finds 36 gaps: 12 five-point requirements unmet (60 points), 4 three-point requirements unmet (12 points), and 20 one-point requirements unmet (20 points). Total deduction 92; score 18.
Now compare two quarters of work.
- Close the 20 one-point gaps: recover 20 points. Score 38.
- Close the 12 five-point gaps: recover 60 points. Score 78.
Fewer fixes, three times the recovery. And because the five-point weights were assigned by exploitability, the second path also removes the gaps an attacker would use first. Score and security point the same direction here, which is not always true in compliance work.
Where the 42 actually sit
Access Control holds the most five-pointers (7), but they are spread across every family. Here is the count per family, from Annex A of the methodology:
| Family | Fixed 5-point | Variable (3 to 5) |
|---|---|---|
| 3.1 Access Control | 7 | |
| 3.2 Awareness and Training | 2 | |
| 3.3 Audit and Accountability | 2 | |
| 3.4 Configuration Management | 6 | |
| 3.5 Identification and Authentication | 3 | 3.5.3 |
| 3.6 Incident Response | 2 | |
| 3.7 Maintenance | 2 | |
| 3.8 Media Protection | 2 | |
| 3.9 Personnel Security | 1 | |
| 3.10 Physical Protection | 2 | |
| 3.11 Risk Assessment | 1 | |
| 3.12 Security Assessment | 2 | |
| 3.13 System and Communications Protection | 5 | 3.13.11 |
| 3.14 System and Information Integrity | 5 | |
| Total | 42 | 2 |
Four families hold 23 of the 42: Access Control (7), Configuration Management (6), System and Communications Protection (5), and System and Information Integrity (5). Add the three fixed five-pointers in Identification and Authentication plus MFA, and the honest summary is: identity, boundaries, configuration, and integrity. Who can get in, what the network lets through, how machines are built and locked down, and whether patches, malware protection, and monitoring are running. Most of that is settings and bookkeeping on systems you already own, not purchases.
The list, by family
Each line gives the requirement in plain English and what done looks like at a 40-person shop with an outsourced IT provider. The requirement numbers are NIST SP 800-171 Rev 2; the weights are from Annex A of the methodology.
3.1 Access Control (7)
- 3.1.1 Limit system access to authorized users, processes, and devices. Done: an account list that matches the current employee list, no shared logins, and every device on the CUI network known and approved.
- 3.1.2 Limit users to the transactions and functions they are permitted. Done: role-based permissions; a machinist cannot open the admin console or the HR share.
- 3.1.12 Monitor and control remote access sessions. Done: one approved remote path (VPN or the IT provider's managed tool), logged, or a written policy that remote access is not permitted.
- 3.1.13 Encrypt remote access sessions. Done: that VPN or remote tool encrypts the session; moot if remote access is not permitted.
- 3.1.16 Authorize wireless access before allowing the connection. Done: any Wi-Fi that reaches CUI systems admits only approved devices, and guest Wi-Fi is a separate network.
- 3.1.17 Protect wireless access with authentication and encryption. Done: modern wireless security on that network; no open or legacy-protected Wi-Fi touching CUI.
- 3.1.18 Control connection of mobile devices. Done: phones and tablets either cannot reach CUI systems or are enrolled and managed, or policy says they are not permitted.
3.2 Awareness and Training (2)
- 3.2.1 Make managers, administrators, and users aware of security risks and the applicable policies. Done: annual awareness training with a dated roster.
- 3.2.2 Train personnel for their assigned security duties. Done: the person who runs accounts, backups, or the firewall has documented role training, even if that person is at the IT provider.
3.3 Audit and Accountability (2)
- 3.3.1 Create and retain system audit logs sufficient to monitor and investigate activity. Done: logging on for servers, the domain controller, and the firewall, with a retention period set and kept.
- 3.3.5 Correlate audit review, analysis, and reporting. Done: logs from different sources reviewed together, usually through the IT provider's logging tool, with a record that reviews happen.
3.4 Configuration Management (6)
- 3.4.1 Maintain baseline configurations and inventories of systems. Done: a current inventory of in-scope hardware, software, and firmware, and a documented standard build.
- 3.4.2 Establish and enforce security configuration settings. Done: a hardening baseline applied through group policy or device management and checked periodically.
- 3.4.5 Define, document, and enforce access restrictions for changes to systems. Done: only named administrators can change systems, and changes are recorded.
- 3.4.6 Configure systems to provide only essential capabilities. Done: unnecessary services and features turned off on CUI machines.
- 3.4.7 Restrict nonessential programs, functions, ports, protocols, and services. Done: firewall rules and workstation policy block what the shop does not use.
- 3.4.8 Apply a deny-by-exception or allow-by-exception policy to software execution. Done: application control that blocks unauthorized software, enforced by tooling rather than by asking nicely.
3.5 Identification and Authentication (3 fixed, plus MFA)
- 3.5.1 Identify users, processes, and devices. Done: a unique identity for every person and device; no "shop floor" account.
- 3.5.2 Authenticate users, processes, and devices before granting access. Done: nothing in scope is reachable without credentials, and devices authenticate to the domain or network.
- 3.5.3 Multifactor authentication for privileged accounts (local and network) and for all network access. 3 to 5 points. Done: MFA for every user; MFA only for remote and privileged users is the 3-point partial state.
- 3.5.10 Store and transmit only cryptographically protected passwords. Done: no plaintext password files or spreadsheets; systems hash and encrypt credentials.
3.6 Incident Response (2)
- 3.6.1 Maintain an incident-handling capability covering preparation, detection, analysis, containment, recovery, and user response. Done: a written incident plan with names, steps, and the IT provider's role.
- 3.6.2 Track, document, and report incidents to designated officials and authorities. Done: an incident log, and someone assigned to DFARS 252.204-7012's 72-hour report to DoD.
3.7 Maintenance (2)
- 3.7.2 Control the tools, techniques, mechanisms, and personnel used for maintenance. Done: who may service in-scope systems, and with what tools, written down; vendor laptops do not plug into the CUI network unvetted.
- 3.7.5 Require MFA for nonlocal maintenance sessions and terminate them when complete. Done: the IT provider's remote maintenance path requires MFA and sessions are closed when work ends.
3.8 Media Protection (2)
- 3.8.3 Sanitize or destroy media containing CUI before disposal or reuse. Done: a wipe-or-destroy procedure with a record for retired drives, USB sticks, and machines.
- 3.8.7 Control the use of removable media. Done: USB storage blocked by policy or restricted to approved, encrypted devices.
3.9 Personnel Security (1)
- 3.9.2 Protect systems during and after personnel actions such as terminations and transfers. Done: an offboarding checklist that disables accounts the same day and recovers devices and keys.
3.10 Physical Protection (2)
- 3.10.1 Limit physical access to systems and equipment to authorized individuals. Done: servers and network gear in a locked room or cabinet with a key list.
- 3.10.2 Protect and monitor the physical facility and support infrastructure. Done: locks, alarms or cameras where equipment lives, and visitor controls at the door.
3.11 Risk Assessment (1)
- 3.11.2 Scan for vulnerabilities periodically and when new vulnerabilities are identified. Done: scheduled vulnerability scans of in-scope systems with results kept and acted on.
3.12 Security Assessment (2)
- 3.12.1 Periodically assess whether security controls are effective. Done: a self-assessment against all 110 requirements at least annually, with the result recorded.
- 3.12.3 Monitor security controls on an ongoing basis. Done: the recurring checks (access reviews, scan reviews, log reviews) on a calendar, with records that they ran.
3.13 System and Communications Protection (5 fixed, plus FIPS)
- 3.13.1 Monitor, control, and protect communications at external and key internal boundaries. Done: a managed firewall at the edge and the CUI segment separated from the rest of the shop network.
- 3.13.2 Use architectural designs and engineering principles that promote security. Done: the enclave design is deliberate and documented, starting with a current network diagram.
- 3.13.5 Separate publicly accessible components from internal networks. Done: anything public-facing is on its own segment; many shops have nothing public-facing and document that.
- 3.13.6 Deny network traffic by default and allow by exception. Done: firewall rules that default to deny, with explicit allows.
- 3.13.11 FIPS-validated cryptography when used to protect CUI confidentiality. 3 to 5 points. Done: the VPN, disk encryption, and file transfer modules that protect CUI are FIPS 140 validated; encryption that is present but not validated is the 3-point state.
- 3.13.15 Protect the authenticity of communications sessions. Done: modern TLS and VPN settings; no plaintext protocols carrying CUI.
3.14 System and Information Integrity (5)
- 3.14.1 Identify, report, and correct system flaws in a timely manner. Done: patching on a schedule with a record of what was patched and when.
- 3.14.2 Provide malicious code protection at designated locations. Done: endpoint protection on every in-scope machine and on the mail path.
- 3.14.3 Monitor security alerts and advisories and act on them. Done: someone is subscribed to vendor and CISA advisories, and responses are logged.
- 3.14.4 Update malicious code protection when new releases are available. Done: endpoint protection updates automatically, and someone verifies it.
- 3.14.6 Monitor systems, including inbound and outbound traffic, to detect attacks. Done: firewall and endpoint alerting with a person watching, usually the IT provider.
Five that may cost nothing
Section 5(i)(i) of the methodology addresses 3.1.12, 3.1.16, and 3.1.18 directly: companies that do not allow remote access, wireless access, or mobile devices may mark these not applicable, and "The evaluator should not deduct points in such cases." Annex A carries the same instruction for 3.1.13 and 3.1.17 ("Do not subtract points if remote access not permitted" and "if wireless access not permitted"). The condition is a policy and procedure ensuring the capability stays disabled; the methodology says that if those are not in place, "a point should be assessed." For a shop with no remote work, no Wi-Fi on the CUI segment, and no phones touching technical data, that is up to 25 points recovered by writing down what is already true.
Why five-pointers cannot wait on a POA&M
For the SPRS score itself, a plan of action never restores points; an unimplemented requirement is scored not met whether or not a plan exists. But there is a second reason the five-pointers come first, and it is written into the CMMC program rule.
32 CFR 170.21(a)(2) sets the conditions for a conditional Level 2 status, the status that lets a company hold a POA&M for a limited time. The assessment score "divided by the total number of CMMC Level 2 security requirements is greater than or equal to 0.8" (that is 88 of 110), and "None of the security requirements included in the POA&M have a point value of greater than 1," with one carve-out: "SC.L2-3.13.11 CUI Encryption may be included on a POA&M if encryption is employed but it is not FIPS-validated." Six requirements are excluded outright (3.1.20, 3.1.22, 3.12.4, 3.10.3, 3.10.4, 3.10.5). And under 170.21(b), "The closing of a POA&M must be confirmed by a POA&M closeout assessment within 180-days of the Conditional CMMC Status Date," or the conditional status expires.
Read together: every open five-point gap, and every open three-point gap other than the FIPS partial case, blocks a conditional status entirely. The POA&M is a parking lot for one-pointers. If the five-pointers are not closed, there is no conditional path, and under DFARS 252.204-7019 and 7020 your posted score and projected completion date still describe those gaps to every prime that asks.
The first 30 to 60 days
This sequence follows the first-90-days plan: know where you stand, then the doors, then the record, then the documents. The first two months are the first two steps plus the start of the third.
Days 1 to 14: know where you stand. Assess honestly against all 110 requirements and compute the score from the official weights. Do not round up. An accurate −120 survives a prime's questions and a government assessment; an invented 40 does not. Mark the five not-permitted cases (3.1.12, 3.1.13, 3.1.16, 3.1.17, 3.1.18) correctly, and sort the remaining gaps by weight.
Days 14 to 45: the doors. Work the identity and boundary five-pointers first, because they recover the most and most of them are settings:
- Accounts and identity: 3.1.1, 3.1.2, 3.5.1, 3.5.2, 3.9.2. Reconcile the account list to the payroll list, remove shared logins, write the offboarding checklist. One afternoon with the IT provider.
- MFA: 3.5.3 and 3.7.5. Turn on MFA for remote and privileged users this week (5 becomes 3), then for everyone (3 becomes 0).
- Boundaries: 3.13.1, 3.13.6, 3.13.5, 3.13.2, 3.13.15, 3.13.11. Confirm the firewall defaults to deny, separate the CUI segment, diagram it, retire any plaintext protocols carrying CUI, and confirm the VPN and disk encryption modules are FIPS validated (encryption that is present but not validated moves the FIPS deduction from 5 to 3).
- Remote, wireless, mobile: 3.1.12, 3.1.13, 3.1.16, 3.1.17, 3.1.18. Either lock down the one approved path or write the policy that there is none.
- Media and physical: 3.8.7, 3.8.3, 3.10.1, 3.10.2. Block USB storage, lock the rack, write the disposal procedure.
Days 30 to 60: configuration and integrity, and the record begins. Overlapping the doors, move to the families that hold the remaining 22:
- Integrity: 3.14.1, 3.14.2, 3.14.4, 3.14.6, 3.14.3. Patching schedule, endpoint protection everywhere, updates verified, alerting watched, advisories assigned.
- Configuration: 3.4.1, 3.4.2, 3.4.6, 3.4.7, 3.4.8, 3.4.5. Inventory, hardening baseline, remove nonessential services, application control, change authority.
- Logging and scanning: 3.3.1, 3.3.5, 3.11.2. Logs on and retained, reviewed together, vulnerability scans scheduled.
- Program requirements: 3.6.1, 3.6.2, 3.2.1, 3.2.2, 3.7.2, 3.12.1, 3.12.3, 3.5.10. Incident plan, training roster, maintenance rules, the assessment and monitoring cadence.
As each item closes, record it on the day it closes: the setting, who changed it, the screenshot or export, the date. That is the record step starting early, and it is what makes weeks 10 to 13 (the SSP, the POA&M with honest dates, the posted score) describe something real instead of something reconstructed.
The IT provider does most of the hands-on work in this list. What the shop owns is the order, the honest status of each requirement, and the record. Valontir was built for that part: it carries the 42 fixed and 2 variable weights per requirement, recomputes the SPRS score as statuses change so the triage order is visible from day one, and keeps the evidence behind each closed requirement attached and dated, working alongside whoever does the IT.
FAQ
How many five-point requirements are there in NIST 800-171? Under the DoD Assessment Methodology v1.2.1, 42 requirements carry a fixed 5-point value (23 basic and 19 derived), and two more, 3.5.3 and 3.13.11, carry 3 to 5 points depending on implementation.
Can a five-point requirement go on a POA&M? Not for a conditional CMMC Level 2 status. 32 CFR 170.21(a)(2) limits the POA&M to requirements with a point value of 1, with the single exception of 3.13.11 when encryption is in place but not FIPS-validated. For the SPRS score, no plan of action restores points at any weight.
Which family has the most five-point requirements? Access Control, with 7. Configuration Management follows with 6, and System and Communications Protection and System and Information Integrity have 5 each.
Do I lose points for remote access requirements if we have no remote access? No. Section 5(i)(i) of the methodology says the evaluator should not deduct points for 3.1.12, 3.1.16, or 3.1.18 when the capability is not permitted, and Annex A extends the same treatment to 3.1.13 and 3.1.17, provided a policy and procedure keep the capability disabled.
What is the minimum score for a conditional Level 2 status? 88. 32 CFR 170.21(a)(2)(i) requires the score divided by the total number of Level 2 requirements to be at least 0.8, and 0.8 times 110 is 88.
Does fixing the five-pointers first make the shop more secure, or just raise the score? Both. The weights were assigned by what an unimplemented requirement would let an attacker do, so the highest-weight gaps are the ones with the largest security effect.
Valontir is a compliance workspace for small defense contractors: every 800-171 requirement, every piece of evidence, and your live SPRS score in one place, so your annual affirmation has evidence behind it. Book a demo or request access.
Sources: NIST SP 800-171 DoD Assessment Methodology, v1.2.1 (June 24, 2020) · 32 CFR 170.21 (Plan of Action and Milestones requirements) · NIST SP 800-171 Rev. 2 · DFARS 252.204-7012 · DFARS 252.204-7019 · DFARS 252.204-7020