The hosts argue that the FAR CUI rule applies NIST SP 800-171 Rev 3 to all federal contractors without the CMMC scoping framework: five asset categories, restricted VDI treatment, and specialized and security protection asset rules. NIST’s scoping language is a sentence or two, so federal contractors face the same ambiguity defense contractors spent years resolving. Defense contractors also don’t know whether other agencies will accept CMMC scoping decisions.
Key Takeaways
- NIST scoping is minimal. SP 800-171 covers components that process, store, or transmit CUI or protect those components, with no asset taxonomy.
- CMMC fills the gap, but only for CMMC. Its five asset categories and VDI treatment don’t carry into FAR CUI.
- Three recurring problems: personal devices and remote access, specialized systems (such as CNC machines and lab instruments), and security protection assets (firewalls, identity providers, MSPs).
- Missing guidance: FAR CUI offers ODPs and a single out-of-scope classification (VDI) but no asset categories or external service provider guidance.
- Expect more overhead. Without scoping guidance, contractors must lean on architecture, data flow, and SSP documentation and on each agency’s interpretation.
- Reciprocity is unknown. Other agencies may not accept the DoD’s scoping decisions, which could mean separate environments per agency.
- The hosts’ ask: A unified, CIRCIA-style scoping guide across agencies.
Transcript
FAR CUI Could Reopen CMMC’s Scoping Problems
Jacob: All right, folks. It’s November 2026, and defense contractors have spent years debating what belongs inside their NIST SP 800-171 compliance boundaries. The CMMC program eventually introduced detailed scoping rules to address those exact questions. But the upcoming FAR CUI rule relies on NIST SP 800-171 guidance without incorporating the CMMC assessment scoping framework. So two contractors implementing the same NIST security requirements could be operating under very different scoping guidance, and that’s coming pretty soon. That’s what we’re going to talk about today.
Daniel, scoping is easily the most common category of questions we’ve gotten over the years. It’s the number one bucket by far, and for good reason. It’s the single best way to save money while you comply with these requirements, but it’s also the most complicated rabbit hole in this space.
Daniel: We’ve been doing the CUI Hotline for over a hundred episodes, with thousands of questions. I’ve talked to somewhere between 8,000 and 9,000 defense contractors, and question number one, every single time, is: how do I keep things out of scope? How do I save money? How do I change my data flow to support a smaller boundary? When the FAR CUI rule came out in proposed form, and now as it makes its way toward final publication and interagency review, one key ingredient was missing: scoping.
NIST 800-171 Rev 3 is pretty binary on scoping. It’s a CUI asset or it’s not. There’s some language identifying what could be called a security protection asset, but what’s nice about the CMMC scoping guidance is that it’s very clear on which controls apply to which kinds of assets. When you start talking about SPAs and specialized assets, those really mean something. So it’s going to be detrimental without that secret sauce. And everyone thought the scoping guidance maybe wasn’t enough. I think it should actually be more detailed in its examples, to give people more clarity on which controls to apply to what.
Jacob: The NIST scoping guidance is a single sentence. It’s been a single sentence since 2018, in Revision 1, and for three years before that, since it came out in 2015, there really wasn’t any scoping guidance whatsoever. CMMC gave us a 16-page scoping guide with a bunch of asset categories. I agree with you: there needs to be more information, more examples, more categories, and more options for helping people limit their scope, spend, cost, burden, and impact. But that’s not the tone we’ve heard with the ongoing CMMC review, and none of it exists in the FAR CUI rule. That’s a big problem. Federal contractors who will be experiencing the joy of NIST SP 800-171 for the first time have no context for what the defense sector has said scoping rules and categories could be. And defense contractors have a different problem: you’ve got CMMC scoping guidance, but will other agencies and customers accept it on the same system? We don’t know. That goes beyond the problem we’ve discussed before, of defense contractors having to meet one revision while federal contracts require a separate one. But first, let’s talk about what 800-171 says, then what CMMC added, and then some of the classic problems exposed by the gap between the two.
What NIST SP 800-171 Actually Says About Scope
Daniel: NIST SP 800-171’s applicability language covers system components that process, store, or transmit CUI, or provide security protection for those components. That’s all they really give us.
Jacob: Right. The document says organizations can isolate their CUI systems to limit the scope of implementation, but that’s all it says about separate processing domains. NIST doesn’t provide a comprehensive taxonomy or categorization of assets, or detailed rules for assessing the different types of assets that might exist, whether they process, store, and transmit, provide protection, or neither. It doesn’t tell you how to classify your endpoints, network devices, security tools, specialized systems, or external providers. None of that is explicitly covered in 800-171, but it’s all very relevant. The bottom line is that NIST establishes general applicability but doesn’t provide CMMC-style assessment scoping methodologies, and that creates a lot of problems.
Daniel: The one thing the FAR CUI rule does bring to the table is a single out-of-scope asset classification: VDI.
Jacob: Right, and we’ll talk about that shortly. But that’s what the FAR rule says, not what NIST SP 800-171 says. If you’re like most companies and you pick up the NIST requirements without reading the corresponding rule, you won’t know that. And will GSA include that in a scoping guide, or will they just say “comply with the NIST requirements”?
What CMMC Added: Asset Categories and VDI
Jacob: Let’s talk about what CMMC added. NIST has had this very general, very broad applicability language that hasn’t really changed in about eight years. It’s basically been the same sentence or two the entire time. The CMMC program regulation has five asset categories: CUI assets, security protection assets, contractor risk-managed assets, specialized assets, and out-of-scope assets. It gives you rules for how those categories are treated during an assessment, whether that’s a third-party assessment or a self-assessment. It’s the same scoping guidance and asset categories regardless of the method. CMMC also has specific treatment for situations like restricted VDI clients. Daniel, this is the thing you’ve been spiking the football on since the CMMC program rule came out. What was the world like before the VDI guidance, and what’s it like after?
Daniel: It was so crazy. Before the VDI guidance, it was such a tossup. Some assessors would say it’s out of scope. Some would say no, it’s in scope. Some would look at how the Army deployed VDI and say, “If the Army is doing it, it’s good for defense contractors, who are using VDI on non-managed systems.” There just wasn’t much clarity. Is the network traffic over HTTPS in scope? Is the physical endpoint in scope? What level of control is acceptable for disabling redirection? What can be allowed and what can’t? What solutions can you even use if the endpoints are in scope? Some people said all Level 2 requirements need to be on that asset. Some said only selective ones, because it’s a security protection asset. Some said it’s fully out of scope. Until the rule came out and the scoping guidance supplemented it, VDI was a tossup. Could I use it and be compliant? It depended on which assessor you picked and what requirements they saw.
Jacob: Whether other agencies under the FAR CUI rule will require third-party assessment remains to be seen. But do you have defensible logic behind your decisions if you end up with a False Claims Act matter, an insurance issue, a DIBCAC audit as a defense contractor, or some other audit the other agencies come up with? Without concrete guidance, you get a lot of flexibility. But over the years, people get very uncomfortable with that flexibility, because they don’t want to make the decision on their own. They want to be told what the rule is. If you only have the FAR CUI rule to go on, you don’t have much of that. You don’t have documentation expectations, or anything about asset inventories, system security plans, or network diagrams and how they relate to the asset categories. NIST sort of assumes you’ll know how to do that, but it doesn’t really explain it.
Three Scoping Problems Federal Contractors Will Face
Jacob: Let’s look at three classic problems that will be relevant under the FAR CUI rule.
First, personal devices and remote access. If someone views CUI through a managed application, does the entire phone or laptop fall under the NIST SP 800-171 requirements? CMMC gives us more explicit assessment treatment for certain architectures, particularly restricted VDI clients. It doesn’t say that in SP 800-171. So I think when federal contractors read that document, this question will come up. Even though the FAR CUI rule talks about it, people don’t read the rules. They read the NIST document. We’ll be right back in the same situation, which raises the bigger issue: can you go to your other federal customer and say “the DoD says this is okay”? They may say, “That’s nice that the DoD does that, but over here we do it this way.” Nobody knows whether they’ll reciprocate that guidance.
Daniel: And here’s the beautiful part: we got ODPs as part of FAR CUI for Rev 3. That’s a big win for a lot of people. Prescribe me what to configure, what the parameters are, all of that. Some enterprises actually hate it, because they don’t want you dictating how to implement a specific control. But small businesses are all about ODPs. Just give me the recipe. The one piece we’re missing is asset classifications, and when to apply those controls. Without scoping guidance, what’s in scope and what’s out? Are endpoints in scope? If you don’t read the FAR CUI clause and you’re accessing VDI, you can make an assumption: if it’s on my screen, it should be a CUI asset.
Jacob: The second super common problem, which still comes up today, is specialized systems. What happens when a CNC machine, a laboratory instrument, or a developmental system can’t reasonably implement all the requirements in NIST SP 800-171? NIST talks about enduring exceptions documented in the SSP, but that’s a whole other can of worms. Who grants the enduring exception? For how long? How are you managing it? Is it on the POA&M or not? Are you keeping up with your SSP? Do you even have one? CMMC adds the specialized asset category and an associated assessment treatment for it. The 32 CFR program rule even acknowledges that the department is accepting more risk by allowing the specialized asset category and the contractor risk-managed asset category, with this additional flexibility on what applies when, where, and how. Beyond the very general NIST guidance, there’s nothing beyond “enduring exception.” This wouldn’t have been one of the most common issues over the years if the enduring exception guidance in SP 800-171 made sense to people.
Daniel: People think their corporate IT infrastructure is expensive to make compliant, but specialized assets gave manufacturers so much slack. That’s back on the table with FAR CUI, and that’s the friction point, because FAR sits above DFARS. For the DoD, maybe my assets aren’t in scope for all the controls. For FAR CUI, with the lack of scoping guidance, and here’s the thing, no agency is going to whip out scoping guidance on day one once FAR CUI is published, it just ain’t going to happen. So you’re going to sit in purgatory for a long, long time, and the assumption is you’re putting controls on those assets.
Jacob: Last but not least, security protection systems. This is the famous secondary clause in NIST’s scope language: systems that provide protection for components that store, process, or transmit CUI. What about firewalls, identity providers, monitoring tools, managed service providers, and infrastructure that protects CUI but doesn’t itself store, process, or transmit it, just monitors the environment? It’s a nebulous gray area. The applicability statement includes these protective components, but CMMC scoping guidance provides explicit security protection asset categories, and explains what to do about external providers and cloud providers. None of that exists in the NIST document, so you’re right back to asking what “provides protection for” means.
Daniel: We saw this happen all the time with DFARS 7012. Even to this day, I get people calling to say, “I implemented the 110.” I ask, “Where did you do it?” “Commercial clouds.” That’s a problem immediately, day one. We’ll see the same thing with FAR CUI. People will hear NIST and look at the Rev 3 publication. I hope they look at the ODPs, but unless you read the FAR CUI clause, you won’t even know those exist. That’s another hurdle people will probably miss. And there’s no ESP guidance, for external service providers and MSPs. There’s no language on relevant or applicable controls for those assets, and no shared responsibility matrix. If the agencies aren’t going to write their own scoping guidance or agree on a unified one, which is what I’d hope they’d do in the final rule, we’ll see, there’s going to be a huge problem for a lot of organizations.
The Agency Reciprocity and Harmonization Problem
Jacob: Or the frustration of going through the CMMC process, getting a third-party certification, and then another agency says, “Well, that’s not the guidance we would have come up with.” Then you end up in a harmonization issue, which we all know and love.
To summarize why the FAR CUI rule is such an issue, and we’ve done many episodes on this: the proposed approach would bring NIST SP 800-171 requirements and obligations into all federal contracts, beyond the DoD and defense contractors. Those contractors will not, at this point, inherit CMMC’s five asset categories, assessment treatments, or the extra detailed guidance in those 16 pages beyond NIST’s sentence and a half. None of that is in the FAR CUI rule. That doesn’t necessarily mean people complying with the FAR CUI rule have a larger compliance boundary. But less prescriptive guidance for defining and defending that boundary opens you up to spending more money, more liability, and more gray areas. It makes it harder to know what’s going on, easier to overspend, and the burden bigger, and it makes things take longer. A very outcome-oriented scoping sentence instead of a detailed scoping guide makes everything worse.
Daniel: So organizations may need to rely more heavily on things they’re bad at: documented architecture, CUI data flow documentation, system security plan documentation, and individual agency interpretations of your contract requirements. That’s a lot of overhead to manage, and it’s coming for federal contractors.
Jacob: The defense space spent years developing CMMC-specific answers to questions posed or left open by NIST guidance, or by a lack of specific NIST guidance. The FAR CUI rule is going to force us to answer all of those questions again without the CMMC rule book, and we don’t know how that’s going to work.
Daniel: It’s going to be a disaster, quite honestly. I’m trying to be somewhat optimistic, but people aren’t going to read the ODPs. People aren’t going to read that VDI is out of scope. They’re just going to look at 171, ignore FedRAMP requirements and FAR CUI, and we’re going to see the emergence of multiple different environments per agency to meet their specific scoping requirements. Maybe some will do reciprocity. Maybe some will say, “If you’re doing CMMC, we’re good with that,” assuming CMMC jumps to Rev 3 at some point. But because there’s no unification, we need the CIRCIA equivalent of a scoping guide, to actually lessen the burden on federal contractors. If we don’t, the burden’s going to go through the roof.
Jacob: Absolutely.
Why Federal Contractors May Have to Start Over
Jacob: Wrapping up: NIST SP 800-171 tells you in general which components the requirements apply to. CMMC tells you much more about how different types of assets are treated during an assessment of those requirements. The FAR CUI rule is going to expose a problem that CMMC mostly resolved but that NIST by itself never fully addressed. For contractors outside the defense industrial base, this will be their first encounter with the ambiguity the defense space has struggled with for years and years. We’re going to repeat history in a lot of situations, and it will probably be more confusing than clarifying, based on our experience in this space.
Like and subscribe, because we put out content multiple times a week on issues just like this. As Daniel said, we have the live Hotline every Friday, where we’ve answered thousands of questions, most often about scoping. That’s going to be everybody’s biggest problem very soon. So like, subscribe, tell your friends, read the scoping guide, and hope everybody reciprocates. We’ll see you next week.
Daniel: See y’all.
Contact
Speak With Our Team
Our team of compliance and cybersecurity experts are on standby and ready to help. We’ll walk you through what you need and what to expect.
