NIST SP 800-171 Rev. 3: Why It Matters to Federal Suppliers
If your company sells to the federal government, or to a prime that does, you probably already hold information the government expects you to protect. It might be a drawing, a specification, or a set of records a customer passed down to you. That information has a name: Controlled Unclassified Information, or CUI.
NIST Special Publication 800-171 Revision 3 is the rulebook for protecting it on your systems, and a coming federal acquisition rule is about to make it matter to far more companies.
This post covers what Rev. 3 is, what changed, the FAR clause that’s on the way, and a practical way to get started this week.
CUI is easy to miss, and the responsibility travels with it
CUI is information the government creates or possesses, or that someone creates or possesses for the government, that a law, regulation, or government-wide policy says needs safeguarding or dissemination controls (32 CFR Part 2002). It isn’t classified, and that’s exactly why it gets missed. The National Archives keeps the CUI Registry, which lists the approved categories.
In practice, CUI turns up in technical drawings and specifications, export-controlled data, and personnel, legal, and financial records tied to the work. It rarely stays put. It lands in email, shared drives, laptops, cloud storage, and sometimes on a shop floor machine. In our experience, most companies don’t ignore CUI. They just don’t know everywhere it has gone.
When an agency shares CUI with you, its obligation doesn’t disappear. NIST puts it plainly:
“The responsibility of federal agencies to protect CUI does not change when such information is shared with nonfederal organizations.” (NIST SP 800-171r3, Section 1)
So the agency writes protection requirements into the contract or agreement. The prime accepts them and flows them down to the subcontractors and suppliers who touch the same information. That’s why a small machine shop three tiers down can get the same questionnaire as a large prime.
There’s good news in the fine print. The requirements apply only to the system components that process, store, or transmit CUI, or that protect those components. Keep that boundary tight and the job gets smaller.
Rev. 3 at a glance
NIST published Revision 3 in May 2024.
| Rev. 2 | Rev. 3 | |
|---|---|---|
| Security requirements | 110 | 97 |
| Families | 14 | 17 |
| Organization-defined parameters | none | 88 |
| Assessment items in SP 800-171A | 320 objectives | 510 statements |
Fewer requirements doesn’t mean less work. Many requirements were combined, and the rest became more specific. Three families are new: Planning, System and Services Acquisition, and Supply Chain Risk Management. The companion publication, SP 800-171A Rev. 3, breaks every requirement into determination statements that an assessor checks one at a time.
Three changes matter most:
- Organization-defined parameters. In 88 places a requirement leaves a blank, such as how often to review something or how many failed sign-in attempts to allow. NIST doesn’t fill those blanks. If your agreement sets a value, you use it. If not, you set your own and should be able to explain why. The Department of Defense published its values in an April 10, 2025 memo, which is one agency’s example of how this works.
- Closer to SP 800-53. The wording now tracks NIST’s SP 800-53 controls closely, so there’s less room to interpret your way out.
- Governance and supply chain. Planning, acquisition, and supplier risk now sit beside the technical safeguards. Policies, rules of behavior, and how you choose suppliers are part of the job.
The coming FAR CUI clause is the reason to start now
The FAR Council has proposed a CUI clause that would reach federal contracts across agencies, not just one department. The current version was published on June 23, 2026 (91 FR 37550) as part of the FAR overhaul. As proposed, it would:
- Require contractor systems that handle CUI to meet SP 800-171 Rev. 3
- Require CUI incidents to be reported within 72 hours of discovery, up from the 8 hours in the January 2025 draft
- Ask offerors that don’t meet every requirement to disclose the gaps with a plan of action and milestones
Comments closed on July 23, 2026. As of mid-November no final rule has been published, and details can still change.
The timing is what matters. Finding your CUI, setting parameter values, closing gaps, and building evidence takes months, not weeks. If you wait until the clause shows up in a solicitation, you’re already behind. Some agencies aren’t waiting either: GSA’s January 2026 guide moved its contractors to Rev. 3.
Your agreements still decide which requirements and values apply to you. Read them, and plan for Rev. 3.
Why business owners should care
Four reasons, from our work with federal suppliers:
- Win the work. When an agreement includes these requirements, meeting them is part of being eligible, not a bonus.
- Answer your customers. Primes are asking suppliers harder questions, and a vague answer can cost you a spot on the team.
- Back your claims. If you tell a customer you meet a requirement, it has to be true and provable. Misstatements can carry legal and financial consequences, so ask your counsel what applies to you.
- Protect your IP. The same safeguards that protect government information also protect your own designs, pricing, and customer data. That pays off even if nobody ever audits you.
Where companies stumble
In our field experience, five patterns show up again and again:
- Nobody can say everywhere the CUI lives, so the boundary is a guess.
- Parameter values were never decided, so the settings have nothing to be measured against.
- The policy says one thing and the systems do another.
- The safeguards are real, but there’s no evidence an assessor can examine.
- Administrators, the people with the most power on the system, never got formal training for that role. This is the miss we see most often.
None of these is solved by buying a tool. Each one comes down to knowing the requirement well enough to do it and prove it.
A practical path, and how we can help
This approach works for a team of five or five hundred:
- Find and scope. Locate your CUI and draw a tight boundary around the systems that touch it.
- Understand. Learn what each requirement asks for and the risk behind it.
- Implement. Put it in place, including the parameter values and who approved them.
- Assess and prove. Check yourself the way an assessor would, using the SP 800-171A determination statements. Record each gap with an owner and a date.
There’s no step called “buy a product.” Tools can help, but they don’t replace knowing what a requirement asks for.
We built our training at Evolved Cyber around that same path. Foundations is the starting point: how Rev. 3 works, from CUI and scoping to parameters and assessment. NIST SP 800-171 Rev. 3 Control Mastery goes deeper, with 17 family courses and a chapter for every requirement. Each chapter follows the same three steps (Understand, Implement, and Assess and Prove) and none runs longer than 15 minutes. A fictional manufacturer, Harbor Point Machining, keeps the examples concrete. You record your values, evidence, owners, and gaps in one Master Readiness Workbook, get a reference guide for every requirement, and earn a certificate with CPE credit. Take one family, or a bundle built around your role.
If you hold CUI, the requirements came with it. Rev. 3 is more specific, with values you have to set and defend. And the FAR clause is coming while the work takes months. Pick the family that worries you most and start this week at evolvedcyberacademy.com.
Contact us if you have any questions.
Sources
- NIST SP 800-171 Rev. 3 and SP 800-171A Rev. 3, May 2024
- 32 CFR Part 2002, Controlled Unclassified Information and the CUI Registry
- FAR CUI proposed rule, June 2026: Wiley, Greenberg Traurig, Mayer Brown
- GSA contractor CUI guide, January 2026: TrustedSec, Holland & Knight
