HOME / SERVICES / NIST SP 800-171 GUIDE
// The technical standard

NIST 800-171 explained: The standard behind CMMC Level 2

NIST SP 800-171 sets 110 security requirements for protecting Controlled Unclassified Information (CUI) on contractor systems. DFARS 7012 makes it a contract requirement, while CMMC Level 2 assesses whether you meet those requirements.

30 min · No sales pitch · Signed NDA

Talk to a CMMC Advisor

Submit your details below to schedule your confidential 30-minute scoping review:

✓ Machine Shops & Precision CNC
✓ Defense Aerospace & Avionics
✓ Defense Software & IT Contractors
✓ Electronics & Specialized Hardware
Get the 110-control checklist today → →
// WHAT IT REQUIRES

What NIST 800-171 requires and who must follow it

NIST SP 800-171 sets out the security requirements for protecting CUI in nonfederal systems used by defense contractors. Its full title is NIST Special Publication 800-171, “Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations.”

You may also see it written as NIST 800 171, NIST 800171, NIST 171 or simply 800-171.

These requirements apply to contractors and subcontractors that store, process or transmit CUI for a defense contract, regardless of company size. If a prime contractor shares CUI with you, the applicable requirements flow to your organization.

Rev. 2 remains the version used for current contract requirements. It contains 110 security requirements across 14 families. NIST has published Rev. 3, and the comparison below explains where each version stands.

// 14 CONTROL FAMILIES

The 14 NIST 800-171 control families

Family Security requirements
AC – Access Control 22
AT – Awareness and Training 3
AU – Audit and Accountability 9
CM – Configuration Management 9
IA – Identification and Authentication 11
IR – Incident Response 3
MA – Maintenance 6
MP – Media Protection 9
PS – Personnel Security 2
PE – Physical Protection 6
RA – Risk Assessment 3
CA – Security Assessment 4
SC – System and Communications Protection 16
SI – System and Information Integrity 7
// CONTRACT CLAUSES

DFARS 7012, 7019 and 7020: Each clause requirements

Three DFARS clauses establish the contract requirements for NIST 800-171 compliance.

DFARS 252.204-7012 requires adequate security for systems that handle CUI. This includes implementing NIST SP 800-171, reporting cyber incidents within 72 hours and using cloud providers that meet FedRAMP Moderate equivalency.

DFARS 252.204-7019 and 7020 address assessment and verification. Under 7019, you must have a current Basic Assessment posted in SPRS before contract award. Under 7020, the Department can review your assessment and request access to your systems.

CMMC Level 2 adds an independent assessment of your implementation.

// SCORING METHODOLOGY

SPRS score: How your assessment is calculated

The Supplier Performance Risk System (SPRS) records your NIST 800-171 self-assessment score. You start with 110 points. Each requirement you have not fully met deducts 1, 3 or 5 points, based on its assigned weight. The lowest possible score is -203.

Contracting officers use this score to assess supplier risk. It must reflect the actual state of your environment. A score without supporting evidence can create problems during contract review. An accurate score, backed by a remediation plan, gives buyers a clear picture of your current status.

// CORE DOCUMENTATION

SSP and POA&M: The documents behind your assessment

System Security Plan (SSP)

Your System Security Plan (SSP) describes the CUI boundary, the systems within scope and how your organization meets each applicable requirement. NIST 800-171 requires an SSP, and assessors will ask to review it.

Plan of Action and Milestones (POA&M)

The Plan of Action and Milestones (POA&M) records open gaps, the person responsible for each one and its target completion date. Under the CMMC rule, only a limited number of lower-weighted requirements can remain open at assessment. A POA&M tracks remediation; it does not replace implemented controls.

// VERSION COMPARISON

NIST 800-171 Rev. 2 vs. Rev. 3

Comparison NIST 800-171 Rev. 2 NIST 800-171 Rev. 3
Requirements 110 across 14 families 97 across 17 families
Status Used for DFARS 7012 and CMMC Level 2 Published by NIST; not yet required by contract
Assessment guide NIST SP 800-171A (Rev. 2) NIST SP 800-171A (Rev. 3)
What to do Build and assess against Rev. 2 now Track Rev. 3; do not switch mid-contract
// COMPREHENSIVE COMPLIANCE ANALYSIS

Long form sections

Explanations of requirements, timelines, and assessor expectations.

1 · Basic and derived requirements

Each NIST 800-171 family splits into basic requirements and derived requirements. Basic ones set the goal, and derived ones add the specifics. An assessor scores all 110 the same way.

Each engagement at Sure Centric begins a site visit. We learn about your facility and interact with the team that handles CUI, so each requirement is read against how work gets done.

2 · NIST SP 800-171A: how requirements are assessed

NIST SP 800-171A turns the 110 requirements into 320 assessment objectives. Assessors check each objective in three ways: they examine documents, interview staff, and test the system.

A policy on paper may not take care of everything. At Secure-Centric, we prepare your objective in detail, so the evidence you hand over answers what an assessor questions.

3 · Common NIST 800-171 gaps

Five gaps come up most often on site. MFA does not cover every remote path (3.5.3). Encryption is not FIPS-validated (3.13.11). Audit logs are not reviewed (3.3.5). The incident response plan has never been tested (3.6.3). The CUI boundary is drawn accurately.

The sixth is documentation. An SSP that does not match what is running fails an assessment, even when the controls are sound.

4 · A practical order of work

Each step depends on the one before it. Scope first: decide where CUI lives. Then assess all 110 requirements, and write the SSP and POA&M.

Close the 5-point gaps first, since they cost the most SPRS points. Collect evidence as you go and run a mock assessment before the real one.

5 · Undertaking an honest self-assessment

Score only what is entirely in place. A half-done requirement counts as not met.

An inflated score creates risk with contracting officers and with the Department of Justice, which pursues false cybersecurity claims under the False Claims Act. We run the self-assessment with your team, so the number in SPRS is one you can support with evidence.

6 · How NIST SP 800-171 relates to other frameworks (800-53)

NIST SP 800-171 is drawn from NIST SP 800-53, the larger control catalog written for federal agencies. NIST cut it down to protect CUI on contractor systems and detailed in simple terms.

If you already follow 800-53 or another framework, you have a head start, not a scope. We map your existing controls to the 110 requirements and help you identify the gaps.

// KEY METRICS

NIST SP 800-171 in four numbers

What the standard asks for, and our record with it.

110
NIST SP 800-171 requirements

Rev. 2’s requirements span 14 families and form the basis of CMMC Level 2 assessments.

320
Assessment objectives

The testing criteria in NIST SP 800-171A that assessors examine and verify.

100%
Assessment pass record

Every client we have prepared for a CMMC assessment has passed to date.

120+
Defense Industrial Base companies

Contractors and suppliers of every size and industry trust Secure-Centric with their compliance.

// FREQUENTLY ASKED QUESTIONS

FAQs about NIST 800-171

Still have questions regarding your specific CMMC clauses or audit dates? Speak directly with our lead Registered Practitioner.

1. How many requirements are in NIST SP 800-171?
Rev. 2 contains 110 security requirements across 14 families. These are the requirements assessed under CMMC Level 2. Rev. 3 has 97 requirements across 17 families, but contracts have not yet moved to that version.
2. How do I map NIST 800-171 to CMMC?
CMMC Level 2 uses the same 110 requirements as NIST SP 800-171 Rev. 2. The DoW CIO alignment document maps each requirement to its corresponding CMMC practice. Our checklist follows that mapping.
3. What is the difference between CMMC and NIST 800-171?
NIST 800-171 defines the security requirements. CMMC is the Department's program for assessing whether contractors meet them. The standard defines what you must implement; CMMC verifies your implementation.
4. Rev. 2 or Rev. 3: Which version applies to my contract?
Rev. 2 applies until DFARS 7012, and the CMMC rule is formally updated to Rev. 3. Check out the clauses in your contract and assess Rev. 2 unless your contract specifies otherwise.
5. What is SPRS, and how is the score calculated?
SPRS is the DoW system where you submit your NIST 800-171 self-assessment score. The score starts at 110. Each unmet requirement deducts 1, 3 or 5 points, depending on its weight. The minimum possible score is -203.
6. What is the difference between NIST 800-171 and NIST 800-53?
NIST 800-53 is a broad security control catalog for federal systems. NIST 800-171 draws a smaller set of requirements for nonfederal organizations handling CUI. Defense contractors handling CUI must follow the applicable 800-171 requirements.
7. Is there a NIST 800-171 certification?
No. NIST does not issue certifications for NIST 800-171. Compliance is documented through your SPRS assessment score and verified through the applicable CMMC Level 2 assessment process.

Ready to know where your NIST 800-171 compliance stands?

Get a clear assessment of your current structure, identify open requirements, and plan your next steps with Secure-Centric.

📬 CMMC Newsletter