Three Things We Like About the FAR CUI Rule (and Two We Don’t)
Updated November 20, 2026
For years, protecting Controlled Unclassified Information (CUI) has been treated almost exclusively as a defense contractor problem. DoD contractors got DFARS 252.204-7012, NIST SP 800-171, and eventually CMMC. Contractors working for civilian agencies, on the other hand, got a patchwork of agency-specific requirements, inconsistent contract language, and often no clear rules at all.
The FAR CUI rule would end that split. If it’s finalized, the same baseline for safeguarding CUI and reporting incidents would apply across the entire federal supply chain, from the Department of War to the Department of Agriculture. In other words, thousands of companies that have never thought of themselves as part of the CUI conversation are about to join it.
We’ve followed the progress of this rule closely since it was first proposed, and on balance, we think it’s a step in the right direction. Here are three things we like about the FAR CUI rule and two we wish could be handled differently.
What is the FAR CUI rule, and what would it change?
The FAR CUI rule is a proposed change to the Federal Acquisition Regulation that would create one government-wide framework for how contractors identify, protect, and report incidents involving CUI.
With roots going back to 2010 (specifically, Executive Order 13556), the FAR CUI rule is hardly new. Defense contractors have had FAR-supplement requirements for years, but civilian contractors have been dealing with a patchwork of inconsistent, agency-specific requirements and no uniform FAR-level framework.
To address this inconsistent patchwork, the FAR Council first proposed the FAR CUI rule in January 2025. It came back in a significantly revised form in June 2026, as part of the Revolutionary FAR Overhaul, a government-wide initiative to rewrite the FAR in plain language and speed up federal buying. The new June 2026 version responds to the public comments on the earlier 2025 draft, and after one last comment period this summer, the industry is just waiting for it to be finalized.
If the FAR CUI rule goes ahead as proposed in the June 2026 version, here are the main things that would change for federal contractors handling CUI.
- Every contract would get a CUI determination.Contracting officers would complete a new Standard Form, the SF XXX, for every solicitation and contract. The form would state whether CUI is involved, where it will reside, what safeguarding and reporting requirements apply, and more.
- The requirements would flow down.Primes would pass CUI requirements through every subcontract tier where subcontractors handle CUI, including preparing and distributing an SF XXX to those subs.
- NIST SP 800-171 Revision 3 would become the standard.Contractors handling CUI would be required to implement 800-171 Rev. 3 and adopt the DoD’s organization-defined parameters (ODPs). For critical programs or high-value assets, contractors may also be required to implement NIST SP 800-172’s enhanced requirements.
- Incidents would have to be reported within 72 hours.That’s down from the 8-hour window in the original proposal, which public comments indicated would be a major burden on many companies. Contractors would also have to preserve information related to a CUI incident for at least 90 days.
- Almost no one would be exempt.The clauses apply to contracts for commercial products and services, with only a narrow exception for contracts solely for commercially available off-the-shelf items.
As for timing, current estimates put the final rule in spring 2027, but it could come as soon as next month. Either way, there’s no phase-in period once the rule is finalized, so contractors handling CUI will need to comply as soon as the new clauses appear in their contracts.
For defense companies already working under DFARS 252.204-7012, much of this will look familiar. For civilian contractors, it may be an unpleasant wakeup call. Luckily, many of the changes under the FAR CUI rule will promote better security and raise the standards for protecting sensitive information.
What the FAR CUI rule gets right
Adopting Rev. 3
The biggest change in the FAR CUI rule is also the one we’re happiest to see: Civilian contracts involving CUI would be held to NIST SP 800-171 Rev. 3. We’ve long argued that CMMC, which still points to Rev. 2, should make the same move. Rev. 3 is a more modern standard, it promotes operational resilience, it cleans up language that left too much room for interpretation, and it adds important emphasis on supply chain risk management.
The move may encourage CMMC to follow suit. Once most federal contractors are working with Revision 3 (and applying the DoD’s own ODPs), it will be much harder to justify keeping defense contractors on Revision 2. The FAR CUI rule could be just the push the DoD needs to finally make the switch.
A more reasonable reporting window
The January 2025 proposal gave contractors 8 hours to report a suspected CUI incident. The re-proposed rule extends that to 72 hours, which is the same timeframe that defense contractors use under DFARS 252.204-7012. There’s no reason why a contractor working under both FAR and DFARS clauses should be using two incident response playbooks with two different clocks, so the standardization is a good move.
Seventy-two hours is also more realistic for most businesses. Many small contractors have a single IT person who does everything, from identifying a data breach to troubleshooting the smart TV in the break room. Eight hours barely gives that employee time to confirm that something went wrong, let alone whether it qualifies as a CUI incident. Overall, the change will make reporting more accurate and complete for the government and less onerous and rushed for small businesses.
Agencies have to identify what’s CUI
One of the most persistent problems in protecting CUI is knowing what counts as CUI in the first place. Contractors regularly receive documents with no markings, inconsistent markings, or blanket CUI labels applied to everything as a precaution. When nobody is sure what needs protection, companies either over-protect at great expense or under-protect at great risk.
That problem came through clearly in this summer’s CMMC reform RFI. According to reporting by the Federal News Network, multiple industry groups told the CMMC Reform Task Force that inconsistent CUI identification and marking was one of the program’s main cost drivers, including unnecessary flowdown to subcontractors who may never actually handle CUI. The DoD’s own summary of the responses concluded that clearer CUI marking had the greatest potential of any RFI recommendation to narrow how much of the DIB is subject to NIST 800-171 and thereby reduce costs.
The FAR CUI rule addresses this issue head-on with the new SF XXX form that would require agencies to state whether CUI is involved, what kind, and where for each new contract. Contractors would still have to notify the contracting officer when CUI isn’t properly marked, but they would be starting from a much clearer place.
Where the FAR CUI rule falls short
Overall, our view is that the FAR CUI rule would raise the baseline for protecting sensitive government information across the entire federal supply chain, and that’s a great thing.
That said, a few of its provisions could create real problems for the contractors who have to live with them, and we hope to see those issues addressed when the finalized rule comes out.
A high bar for cloud providers
Under the proposed rule, any cloud service provider that a contractor uses to store, process, or transmit CUI identified in the SF XXX must meet security requirements equivalent to those the government set for the FedRAMP Moderate baseline.
Although this is an improvement over the January 2025 version that required cloud providers to be FedRAMP Moderate authorized with no equivalency option at all, it’s still a heavy lift for cloud providers. And it’s often impossible for the smaller, specialized SaaS vendors that small contractors rely on for ERP, engineering, quality management, and similar business tools. When those vendors can’t meet the bar, contractors are pushed into a short list of government cloud environments that cost more and can force them to rebuild how they work.
We already flagged this same requirement as onerous on the CMMC side in our response to the RFI this summer, and we weren’t alone. The Coalition for Common Sense in Government Procurement, for example, urged the Department to update the DFARS and align CMMC with the new FedRAMP program changes in its 2026 Consolidated Rules.
Changing the rules here would make it easier for contractors to access the cloud services they need at the costs they can afford.
Two standards for the same CUI
We said earlier that moving civilian contracts to Rev. 3 is the right call, and we stand by that. The problem is that both DFARS 252.204-7012 and CMMC still require Rev. 2, and the DoD hasn’t announced a timeline for transitioning to Rev. 3.
For contractors with both civilian and defense customers, that creates an awkward split. A company that supports the Department of Defense and the Department of Energy could end up needing two system security plans, two sets of documentation, and two assessment approaches to meet compliance with both standards. Large primes with dedicated compliance teams can absorb the extra work, but a 30-person machine shop with one defense contract and one civilian contract can’t do it nearly as easily.
Good for security, hard on small businesses
The FAR CUI rule gets a lot right. It moves civilian contracts to Rev. 3, sets a reasonable incident reporting window, and finally makes agencies identify CUI clearly. If it’s finalized in its current form, the federal supply chain will be more secure because of it.
Its timing will also pose a real challenge for small businesses, which make up a large portion of the federal supply chain. Once the FAR CUI rule is finalized and agencies begin including it in new contracts, there’s no phase-in period; contractors handling CUI will have to comply as soon as the new clauses appear in their contracts. Your average mom and pop business, and even many larger firms, will struggle with this timeline.
Small businesses are also likely to struggle with cost. When the FAR Council first proposed the rule in January 2025, it estimated first-year costs of $148,200 for small businesses and recurring annual costs of $98,800. Yet the rule comes with no grants, no cost-sharing, and no dedicated support to help small contractors get there.
We want the FAR CUI rule to succeed. But we hope the final version, as well as whatever comes out of the CMMC reform effort, looks closely at the realities of small businesses in the DIB. Reasonable phase-in periods, sensible cloud provider requirements, a well-timed move to Rev. 3, and real financial support would cost the government relatively little, and it would save a much higher cost in the long run: The risk of losing their large, diverse supplier base to compliance requirements that few contractors can fully meet.