How it is structured
NIST CSRC lists SP 800-171 Revision 3, “Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations”, as final, published May 2024 (the document history gives 14 May 2024), and says it supersedes Revision 2. CSRC lists Revision 2 as withdrawn on 14 May 2024 and superseded by Revision 3. The publication says its requirements are organised into 17 families and are based on the controls in the NIST SP 800-53B moderate baseline, tailored to the confidentiality of CUI. It is a requirements catalogue rather than a certification: NIST describes the security requirements as intended for federal agencies to use in contracts and other agreements with non-federal organisations.
NIST’s own change log lists what differs from Revision 2. The right-hand column paraphrases that log, so it only covers changes NIST documents.
| Change in Rev 3 | What NIST’s change log says |
|---|---|
| Source of the requirements | Requirements and families were modified to reflect the controls in the SP 800-53B moderate baseline and the tailoring actions in Appendix C |
| Families | The requirements sit in 17 families; some SP 800-53 families are left out, for example Contingency Planning because it addresses availability |
| Basic and derived | The distinction between basic and derived security requirements was eliminated |
| Specificity | Requirements are more specific, to remove ambiguity and clarify the scope of assessments |
| Organisation-defined parameters | Introduced in selected requirements for flexibility; where an agency does not set a value, the non-federal organisation must assign it |
| Grouping and removals | Requirements were grouped where possible, and outdated and redundant ones were removed |
| New requirements and titles | New security requirements were added, and every requirement now has a title |
| Discussion sections | Restructured and streamlined |
| Tailoring categories | Two new categories: Other Related Controls and Not Applicable |
| Appendix | A new appendix lists the organisation-defined parameters |
NIST does not state a total number of requirements on the CSRC page, and this guide does not quote one. Use NIST’s publication text and its SP 800-171A assessment procedures for the requirement-level detail.
Which of your clients it applies to
It applies to organisations that hold CUI outside federal systems. NIST says the requirements cover components of non-federal systems that process, store or transmit CUI, or that provide protection for such components. Commonly that means US defence supply-chain clients, and any other client whose contract carries a clause that points at the publication.
A clause that commonly brings it into a contract is DFARS 252.204-7012 (May 2024 version, on acquisition.gov). For covered contractor information systems that are not part of a government-operated service, it says the system is subject to NIST SP 800-171 “in effect at the time the solicitation is issued or as authorized by the Contracting Officer”. That wording is why you confirm the revision from the contract rather than assuming Revision 3. The clause also requires the contractor to include it in subcontracts involving covered defense information, which is how a small supplier ends up in scope.
A separate and lighter clause, FAR 52.204-21, covers Federal Contract Information and is the basis of CMMC Level 1 (see the checklist below). Triage a new client with two questions: does it hold CUI, FCI or neither, and which clause in its contract or flow-down says so?
How an MSP delivers it
This is practitioner guidance, not text from NIST. NIST notes that non-federal organisations can implement requirements directly or use external service providers, which is the opening for an MSP. A sequence we suggest:
- Scope and qualify. Confirm what the client holds (CUI, FCI or neither), which contract clause applies, and which revision that clause points to. Look for DFARS references in contracts and security questionnaires from primes.
- Draw the boundary. Agree in writing which systems, people and sites process, store or transmit CUI, or protect those that do. NIST’s scope is these components, so a tight boundary keeps the work proportionate.
- Baseline assessment. Assess the client against the requirements using SP 800-171A procedures, and set any organisation-defined parameter values the contract leaves open. Deliver a gap list, an executive summary and a roadmap.
- Write the SSP and the POA&M. Revision 3 has a System Security Plan requirement (03.15.02, Planning family) and a Plan of Action and Milestones requirement (03.12.02). The SSP describes the system and the safeguards in place or planned; the POA&M records how unmet requirements will be fixed. Use one structure for every client.
- Map evidence to what already exists. Tie each family to evidence the client already produces: identity and email platform settings, endpoint management, ticketing, backup records, the policy library. Evidence produced by normal operations is easier to defend than evidence assembled for an assessment.
- Remediate. Technical items such as access, authentication, logging, backup and patching fit an MSP’s stack. Policy ownership, training and risk decisions need client leadership.
- Run it as governance. After the first remediation push, offer a recurring service: evidence reviews, change-impact checks, POA&M tracking and reporting. Controls drift as staff, suppliers and systems change, so a one-off assessment goes stale.
Split responsibilities in writing. A vCISO-style lead usually owns governance and risk decisions, and the MSP owns day-to-day operation of the technical controls. Package the work as baseline, remediation and recurring governance so each phase has a defined scope, and price for ownership of the outcome rather than hours.
Requirements checklist
CMMC Level 1 is the entry point many clients are asked about first. Under 32 CFR 170.14 (eCFR, current to 19 November 2026), “the security requirements in CMMC Level 1 are those set forth in 48 CFR 52.204-21(b)(1)(i) through (xv)”. The table below is the CMMC Level 1 (FAR 52.204-21) basic safeguarding checklist: fifteen items, paraphrased from the clause text (November 2021 version on acquisition.gov). The third column is a working example of what an assessor may ask to see, not text from the clause.
| FAR 52.204-21 item | Safeguarding requirement (paraphrased) | Evidence an assessor may ask to see |
|---|---|---|
| (i) | Limit system access to authorised users, processes acting for them, and devices | User and device lists, account approval records |
| (ii) | Limit access to the types of transactions and functions authorised users may perform | Role definitions, permission assignments |
| (iii) | Verify and control or limit connections to, and use of, external systems | Firewall rules, approved external connection list |
| (iv) | Control information posted or processed on publicly accessible systems | Review procedure for public posts, website approval records |
| (v) | Identify system users, processes acting for users, and devices | Account inventory, device inventory |
| (vi) | Authenticate (verify) the identities of users, processes and devices before allowing access | Sign-in settings, MFA and password configuration |
| (vii) | Sanitise or destroy media holding Federal Contract Information before disposal or reuse | Media disposal log, destruction certificates |
| (viii) | Limit physical access to systems, equipment and operating environments to authorised individuals | Access list, door and key records |
| (ix) | Escort visitors and monitor their activity, keep physical access audit logs, manage physical access devices | Visitor log, key or badge register |
| (x) | Monitor, control and protect communications at external and key internal boundaries | Boundary device configuration, monitoring settings |
| (xi) | Use subnetworks for publicly accessible components, separated from internal networks | Network diagram, segmentation rules |
| (xii) | Identify, report and correct information and system flaws in a timely manner | Patch records, vulnerability reports, remediation tickets |
| (xiii) | Protect against malicious code at appropriate locations | Endpoint protection deployment report |
| (xiv) | Update malicious code protection when new releases are available | Update policy, signature or version status |
| (xv) | Perform periodic scans of the system and real-time scans of files from external sources as they are downloaded, opened or executed | Scan schedule, scan results, real-time protection settings |
FAR 52.204-21 says it does not relieve a contractor of other safeguarding requirements, including those for CUI, so passing this list says nothing about SP 800-171.
Overlap with other frameworks
NIST SP 800-53 is the source catalogue. The publication starts from the controls in the SP 800-53B moderate baseline, removes those that are the federal government’s responsibility, unrelated to confidentiality of CUI, covered elsewhere or not applicable, and lists the source controls under each requirement. If a client already maps to SP 800-53, much of the evidence carries across, but confirm each requirement against NIST’s publication and its tailoring appendix instead of assuming it. The frameworks list shows the catalogue entries, and how control mapping works explains how overlaps are handled.
CMMC is the Department of Defense assessment programme built on these documents. Under 32 CFR 170.14, Level 1 uses FAR 52.204-21, and “the security requirements in CMMC Level 2 are identical to the requirements in NIST SP 800-171 R2”, as the eCFR text read when we accessed it. So Level 2 is tied to Revision 2 in that rule even though NIST withdrew Revision 2 and published Revision 3, and a contract may point at either. Check the current rule and the contract. Our CMMC compliance page covers the CMMC programme itself, which this guide leaves alone.
Common mistakes
- Assuming the revision. DFARS 252.204-7012 ties the requirement to the version in effect when the solicitation was issued, or as the Contracting Officer authorises, and the CMMC rule text names Revision 2 for Level 2. Confirm the revision per contract before scoping.
- Treating Level 1 as the same thing as 800-171. The FAR 52.204-21 list covers Federal Contract Information and is shorter than the SP 800-171 catalogue. A client that holds CUI needs more.
- Skipping the boundary. The requirements apply to components that process, store or transmit CUI, or protect them. An undefined boundary makes the assessment and the SSP unreliable.
- Leaving organisation-defined parameters blank. If the agency sets no value, NIST says the non-federal organisation must assign it. Record each value and who approved it.
- Letting the SSP and POA&M drift. Update both when systems, suppliers or contracts change, and keep them aligned with the real environment.
- Selling a one-off project. Evidence and controls go stale; agree who owns the recurring review before the first engagement ends.