NIST 800-171 Explained for Manufacturers Who Aren't IT People
A plain-English guide to NIST 800-171 for small manufacturers: what it covers, CUI vs. FCI, SPRS scoring, where CMMC stands in 2026, and how to start.
It usually starts with a line buried in a purchase order. Your quality manager notices a reference to DFARS 252.204-7012, or a prime contractor sends a supplier survey asking for your SPRS score and whether you "meet NIST 800-171." The owner walks over to the one person who handles IT and asks, "Do we?" Nobody knows, and the survey is due in two weeks.
If that sounds familiar, you're not behind. Most small and mid-sized shops I talk to are in exactly this spot. NIST 800-171 for manufacturers is less mysterious than it looks, but it is real work, and it helps to understand what you're signing up for before you answer that survey.
I'm a network engineer, not a lawyer, and my partner Mukesh has spent 25 years in cybersecurity. This guide is the plain-English version we give owners and plant managers who don't live in IT. It is not legal advice, and the rules have been moving this year, so confirm anything contract-specific with your attorney, contracting officer, or assessor.
In this guide
- What NIST 800-171 actually is
- FCI vs. CUI: the question that decides everything
- Where NIST 800-171 and CMMC stand in late 2026
- The 14 control families in plain English
- Your SPRS score: what it is and how it's calculated
- A 6-step plan to get started with NIST 800-171
- Mistakes we see manufacturers make
What NIST 800-171 actually is
NIST Special Publication 800-171 is a set of security requirements for protecting Controlled Unclassified Information (CUI) when it sits on a company's own computers and networks. NIST wrote it, but NIST doesn't enforce it. The Department of Defense does, through contract clauses.
The key clause is DFARS 252.204-7012. If it's in your contract and you handle CUI, you're required to implement NIST 800-171 and report cyber incidents to the DoD within 72 hours. That clause has been in defense contracts for years, so many shops have technically been on the hook longer than they realized.
The version DoD uses today, Revision 2, contains 110 security requirements grouped into 14 families. That sounds like a lot. In practice, many of them are things a well-run network should already be doing, such as unique logins, multi-factor authentication, patching, and logging.
Who it applies to
It applies to any contractor or subcontractor that stores, processes, or transmits CUI for a DoD contract. That includes a lot of small manufacturers who never deal with the government directly. If a prime sends you controlled drawings for a part, the requirement flows down to you.
FCI vs. CUI: the question that decides everything
Before you do anything else, figure out what kind of information you actually receive. This one answer determines whether you need a basic program or a full NIST 800-171 program.
- Federal Contract Information (FCI) is non-public information provided under a government contract. Think basic order details that aren't meant for public release. FCI is covered by 15 basic safeguarding requirements, which line up with CMMC Level 1.
- Controlled Unclassified Information (CUI) is more sensitive. For manufacturers, it's often technical drawings, specifications, or data marked with export control or distribution statements. CUI is where NIST 800-171 and CMMC Level 2 come in.
Look at the markings on the drawings and documents your customers send. "CUI" banners, distribution statements, and ITAR or EAR notices are the clues. When in doubt, ask your prime contractor in writing what they're sending you and how it's marked.
We wrote a full breakdown of this decision in CMMC Level 1 vs. Level 2: Which One Does Your Manufacturing Shop Need? if you want to go deeper.
Where NIST 800-171 and CMMC stand in late 2026
This is the part that has confused a lot of people this year, so here's where things stand as of late October 2026.
Revision 2 vs. Revision 3
NIST published Revision 3 of 800-171 in May 2024. It reorganizes the requirements into 97 items across 17 families. However, DoD has continued to use Revision 2 (110 requirements) for DFARS 7012, SPRS scoring, and CMMC Level 2. Rev 3 has been discussed as a future transition, but no CMMC effective date for it has been set as I write this.
My practical advice: build your program on Rev 2 today, because that's what your score and any assessment will be measured against. Most of the work carries over to Rev 3 anyway.
The CMMC Phase 2 suspension
CMMC (Cybersecurity Maturity Model Certification) is how DoD verifies that contractors actually meet these requirements. Phase 1 began in late 2025 and centers on self-assessments. Phase 2, which would have required third-party certification for many Level 2 contracts starting November 10, 2026, was suspended by a Department of War memo on July 13, 2026, while a reform task force reviews the program.
Here's the important part: the suspension did not remove your obligations. Based on public guidance, the following still apply:
- DFARS 252.204-7012, including NIST 800-171 and 72-hour incident reporting
- Self-assessments against NIST 800-171 Rev 2 for Level 2 work
- A current score posted in SPRS and the annual affirmation, which are generally needed to be eligible for award
This situation is still developing, and the outcome of the review hasn't been finalized publicly. Check with your attorney or a registered assessor before making contract decisions based on the pause.
The 14 control families in plain English
You don't need to memorize all 110 requirements to understand the shape of the work. Here's what each family is really asking, in shop-floor terms.
- Access Control: Only the right people can reach CUI, and only what they need.
- Awareness and Training: Employees know how to spot phishing and handle CUI.
- Audit and Accountability: You keep logs and can tell who did what, and when.
- Configuration Management: You know what hardware and software you have, and it's set up securely.
- Identification and Authentication: Everyone has a unique login, and multi-factor authentication protects remote and privileged access.
- Incident Response: You have a plan for when something goes wrong, and you can report it within 72 hours.
- Maintenance: Repairs and remote vendor access are controlled and supervised.
- Media Protection: USB drives, printed drawings, and old hard drives are handled and destroyed properly.
- Personnel Security: People are screened before getting access, and access is removed when they leave.
- Physical Protection: Offices, server closets, and visitors are controlled.
- Risk Assessment: You regularly look for vulnerabilities and weaknesses.
- Security Assessment: You check your own controls and track fixes in a plan.
- System and Communications Protection: Firewalls, encryption, and network separation keep CUI contained.
- System and Information Integrity: Patching, malware protection, and monitoring are in place.
If your plant has CNC machines, PLCs, or other shop-floor equipment on the network, families 4 and 13 get tricky fast. Our guide on securing shop-floor (OT) networks without stopping production covers how to segment those systems without disrupting the line.
Your SPRS score: what it is and how it's calculated
The Supplier Performance Risk System (SPRS) is where DoD contractors post the results of their NIST 800-171 self-assessment. Primes and contracting officers can see that score.
The scoring follows the DoD Assessment Methodology. You start at 110, one point for each requirement. For every requirement you don't meet, you subtract its weight, which is 1, 3, or 5 points depending on how important it is. A company that meets nothing ends up at -203.
A few things to know about the score:
- A low or negative score is common when companies first assess honestly. It's a starting point, not a verdict.
- The score must reflect reality. Posting an inflated score is a serious risk, because it's an affirmation to the federal government.
- High-weight items like multi-factor authentication, encryption of CUI, and incident response tend to move the number the most, so they're good early targets.
A 6-step plan to get started with NIST 800-171
Here's the order we usually work in with manufacturers. It keeps the project focused and avoids buying tools before you know what you need.
1. Find your CUI
List every place CUI enters and lives. Email attachments from primes, CAD and CAM workstations, file shares, ERP attachments, and the printed travelers on the shop floor all count.
2. Draw your boundary
Decide which systems, people, and locations are in scope. The smaller and cleaner the boundary, the less you have to protect. Some shops move CUI into a separate, tightly controlled enclave rather than securing the whole company network.
3. Assess against all 110 requirements
Walk through each requirement and mark it met, not met, or partially met, with notes on the evidence. Be honest. This is where an outside set of eyes often pays for itself, because it's easy to mark something "done" that only works on paper.
4. Write your System Security Plan and POA&M
The System Security Plan (SSP) describes your environment and how you meet each requirement. The Plan of Action and Milestones (POA&M) lists the gaps, who owns each fix, and target dates. Without an SSP, you can't credibly claim compliance.
5. Post your score in SPRS
Calculate your score using the DoD Assessment Methodology and post it in SPRS. Keep a copy of your worksheet and evidence. If a prime asks for your score, this is what they're looking for.
6. Fix the gaps and re-score
Work through the POA&M, starting with the high-weight items. Update the SSP as things change and re-score when you close meaningful gaps. Treat this as an ongoing program, not a one-time project.
Mistakes we see manufacturers make
These come up again and again, and most of them are avoidable.
- Assuming "we don't have CUI" without checking. Look at the markings on your drawings before deciding.
- Using commercial cloud email or storage for CUI without checking the requirements. DFARS 7012 has specific expectations for cloud services that handle CUI, often described as FedRAMP Moderate equivalent. Many defense suppliers end up on government-focused cloud offerings for this reason.
- Forgetting the shop floor. CNC machines and engineering workstations often hold CUI and run older software.
- Buying tools before writing the plan. An expensive security product doesn't help if it isn't tied to a specific requirement in your SSP.
- Treating the CMMC pause as a reason to stop. The underlying contract requirements are still there, and primes are still asking.
If you're still building the basics, our 10 cybersecurity steps for Roanoke small businesses covers many of the same fundamentals in a lighter format.
Frequently asked questions
Does NIST 800-171 apply to my small manufacturing company?
It applies if you handle Controlled Unclassified Information under a DoD contract or subcontract that includes DFARS 252.204-7012. Size doesn't exempt you. If you only handle Federal Contract Information, you're generally looking at the 15 basic safeguarding requirements instead.
What is the difference between NIST 800-171 and CMMC?
NIST 800-171 is the list of security requirements. CMMC is DoD's program for verifying that contractors meet them, through self-assessments or third-party assessments depending on the level. For CMMC Level 2, the requirements are the 110 controls in NIST 800-171 Rev 2.
Do I still need NIST 800-171 now that CMMC Phase 2 is suspended?
Yes, based on current public guidance. The July 2026 suspension paused the third-party certification milestones, but DFARS 7012, self-assessments, and SPRS score requirements remain in place. Confirm the details for your contracts with your attorney or contracting officer.
How long does NIST 800-171 compliance take?
It varies with how much CUI you have and how mature your network already is. For a small manufacturer starting from scratch, it's commonly a multi-month effort, and sometimes longer if you need to move email or file storage to a new platform. A well-scoped boundary is the biggest factor in shortening it.
What is a good SPRS score?
The maximum is 110, which means every requirement is met. There's no official "passing" self-assessment score, but primes increasingly ask for it, and an accurate score with a credible plan is better than a high number you can't back up.
Start with an honest look at where you stand
NIST 800-171 isn't something you finish in a weekend, but it also isn't as overwhelming once you break it into steps. The hardest part for most shops is the first one: figuring out where CUI lives and how far your gaps really go.
That's what our free cybersecurity assessment is for. Mukesh and I will look at your environment, talk through what you're receiving from your customers, and give you a clear picture of where you stand and what to tackle first. No pressure, and no jargon. Reach out here to set it up.
Related reading
- CMMC Level 1 vs. Level 2: Which One Does Your Manufacturing Shop Need?
- How to Secure Shop-Floor (OT) Networks Without Stopping Production
- MSP vs. Hiring a Full-Time IT Person: A Real Cost Breakdown
Harsha is a co-founder of SoftwarePac Technologies in Roanoke, VA, and a network engineer with 15 years of experience.




