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 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.
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:
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:
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.
Four reasons, from our work with federal suppliers:
In our field experience, five patterns show up again and again:
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.
This approach works for a team of five or five hundred:
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.