Updated November 2026 to reflect the CMMC Phase 2 suspension and current Department of War guidance.
If your company handles Controlled Unclassified Information (CUI) for a defense contract, NIST SP 800-171 is the security standard you are expected to meet. That has not changed, even with the July 2026 pause on CMMC Phase 2 certifications.
This guide walks through what NIST 800-171 compliance actually involves, what is still required right now, and a practical checklist Colorado contractors can use to get organized. If you want the bigger picture of how the rules fit together, start with our breakdown of DFARS vs. CMMC vs. NIST 800-171.
What Is NIST SP 800-171?
NIST SP 800-171 is a set of security requirements published by the National Institute of Standards and Technology. It explains how non-federal organizations, like manufacturers, engineering firms, and other subcontractors, should protect CUI on their own systems.
Revision 2, the version defense contracts currently require, includes 110 security requirements organized into 14 families:
- Access Control
- Awareness and Training
- Audit and Accountability
- Configuration Management
- Identification and Authentication
- Incident Response
- Maintenance
- Media Protection
- Personnel Security
- Physical Protection
- Risk Assessment
- Security Assessment
- System and Communications Protection
- System and Information Integrity
NIST published Revision 3 in 2024, but the Department of War has continued to point contractors to Revision 2 for CMMC Level 2 self-assessments. If you are just getting started, build to Revision 2 and keep an eye on Revision 3.
Do You Still Need NIST 800-171 During the CMMC Pause?
Yes. On July 13, 2026, the Department of War suspended CMMC Phase 2, which would have required third-party (C3PAO) certifications starting November 10, 2026. A CMMC Reform Task Force is now reviewing the program.
The pause only affected the third-party assessment mandate. According to Holland & Knight’s summary of the memoranda, contractors are still expected to:
- Implement the NIST SP 800-171 Rev. 2 requirements
- Meet DFARS 252.204-7012, including reporting cyber incidents within 72 hours
- Post and maintain a current self-assessment score in the Supplier Performance Risk System (SPRS)
- Complete annual affirmations of compliance from a senior official
- Meet existing contract terms until a formal modification changes them
In other words, the work you do on NIST 800-171 now is not wasted. It is what keeps you eligible for awards today, and it is the foundation for whatever version of CMMC comes next.
NIST 800-171 Compliance Checklist
Here is the order we recommend for small and midsize contractors. Each step builds on the one before it.
1. Confirm Which Contracts Involve CUI
Review your contracts and subcontracts for DFARS 252.204-7012, 7019, 7020, or 7021 clauses. Ask your prime contractor what information they will share with you and how it is marked. Knowing exactly where CUI enters your business is the first step.
2. Map Where CUI Lives
Follow the data. Which inboxes, file shares, laptops, cloud apps, and shop floor systems touch CUI? Many companies shrink their compliance scope (and cost) by keeping CUI in a dedicated, well-controlled environment instead of spreading it across the whole network.
3. Run a Gap Assessment
Compare your current setup against all 110 requirements. Be honest about what is fully in place, partially in place, or missing. A gap assessment is the most useful document you can have before spending money on tools.
4. Write Your System Security Plan (SSP)
The SSP describes your environment and explains how you meet each requirement. It is required, and it is usually the first thing an assessor or prime contractor asks to see.
5. Build a Plan of Action and Milestones (POA&M)
For every gap, document what you will do, who owns it, and when it will be done. A clear POA&M shows you are making real progress and helps you budget the work over time.
6. Calculate and Post Your SPRS Score
The DoD assessment methodology starts at 110 points and subtracts points for each requirement not met, so scores can range from 110 down to -203. Post your score in SPRS and update it as you close gaps. Accuracy matters more than a high number, since your affirmation says the score is true.
7. Close the High-Impact Gaps First
Some requirements carry more weight in the scoring and do more to protect you. Common priorities include:
- Multi-factor authentication (MFA) for all users
- Endpoint detection and response (EDR) on every device
- Encryption for CUI at rest and in transit
- Centralized logging and regular log review
- Security awareness training for every employee
- Tested, protected backups
8. Prepare for Incidents
DFARS 7012 requires reporting cyber incidents to the DoD within 72 hours. Write an incident response plan, know who makes the call, and make sure your team has access to the DoD reporting portal before you ever need it.
9. Flow Requirements Down to Your Subcontractors
If you share CUI with your own vendors or subcontractors, they need to meet the same requirements. Add this to your vendor onboarding process.
10. Keep Evidence and Review Regularly
Compliance is not a one-time project. Keep screenshots, policies, training records, and change logs organized, and review your SSP and POA&M at least once a year or whenever your environment changes.
Where Colorado Contractors Usually Get Stuck
In our work with manufacturers and engineering firms along the Front Range, the same challenges come up again and again:
- Scope creep. CUI ends up in personal email, shared drives, or shop floor PCs nobody planned for.
- Documentation lag. The technology is in place, but the SSP and policies do not reflect it.
- Cloud choices. Not every cloud service is suitable for CUI. Some contracts require FedRAMP Moderate equivalent services.
- Bandwidth. A small internal IT team is already busy keeping the business running.
None of these are a reason to panic. They are a reason to have a plan and a partner.
How eCreek Helps
We are a Denver-based IT partner, and we help defense suppliers in Colorado work through NIST 800-171 one step at a time: gap assessments, SSP and POA&M development, MFA and EDR rollout, logging, and ongoing support so your compliance stays current. Learn more about our compliance services and our support for the defense industrial base.
Not sure where you stand? Talk with our team and we will help you map out your next steps.
Frequently Asked Questions About NIST 800-171 Compliance
Who needs to comply with NIST 800-171?
Any contractor or subcontractor that stores, processes, or transmits Controlled Unclassified Information for the Department of War, and increasingly for other federal agencies, is expected to meet NIST SP 800-171.
Is NIST 800-171 still required if CMMC Phase 2 is paused?
Yes. The July 2026 suspension paused third-party CMMC certifications. It did not remove DFARS 252.204-7012, NIST 800-171 implementation, SPRS scoring, or annual affirmations.
Should we follow NIST 800-171 Revision 2 or Revision 3?
Current defense contracts and CMMC Level 2 self-assessments reference Revision 2. Build to Revision 2 now and plan for Revision 3 as guidance changes.
What is a good SPRS score?
The maximum score is 110, which means all requirements are met. The most important thing is that your score is accurate and backed by an SSP and a POA&M showing how you will close remaining gaps.
How long does NIST 800-171 compliance take?
It depends on your size and starting point. Many small and midsize contractors need several months to close their gaps, so starting with a gap assessment now gives you the most room to plan.

