Home / Blog / CMMC & Cybersecurity

CMMC & Cybersecurity November 19, 2026 7 min read

The FAR CUI Rule Explained for Federal Contractors

Sentinel Blue
Sentinel Blue 7 min read
The FAR CUI Rule Explained for Federal Contractors

The FAR CUI Rule Explained for Federal Contractors

Updated November 19, 2026

For years, the rules for protecting Controlled Unclassified Information have lived mostly in defense contracts. A proposed federal rule would bring the same kind of requirements to civilian agencies. If your company handles CUI for any federal customer, this rule is worth understanding now.

Quick Answer

The FAR CUI rule is a proposed rule, published June 23, 2026, that would set one government-wide framework for protecting CUI and reporting CUI incidents. It would require systems that handle CUI to meet NIST SP 800-171 Revision 3, require incident reports within 72 hours, and flow those duties down to subcontractors. It is not final yet, and defense contractors remain under DFARS 252.204-7012.

What Is the FAR CUI Rule?

The FAR CUI rule is a proposal from the Federal Acquisition Regulatory Council, the group that writes the Federal Acquisition Regulation. The Council published it on June 23, 2026 at 91 FR 37550 as FAR Case 2026-001. It replaces an earlier proposal from January 2025 and forms part of the Revolutionary FAR Overhaul. The rule would place CUI requirements in an expanded FAR Part 40.

The public comment period closed on July 23, 2026. A final rule had not been issued in the sources we reviewed. Check the Federal Register for the current status before you plan around any date.

Who Would the Rule Cover?

The rule would reach contractors that handle CUI for civilian agencies, including contractors that sell commercial products and services. It leaves out commercially available off-the-shelf items. Law firm summaries from Mayer Brown describe it as extending requirements that have mostly applied to defense contractors to the civilian side of government.

Subcontractors fall inside the rule too. A prime contractor would pass the substance of the new clause to any subcontractor that receives CUI.

What Would Contractors Have to Do?

The proposal asks for six things, which Wiley and Mayer Brown both outline.

Area What the proposal says
Safeguarding Protect the CUI that the agency identifies on the new standard form. Treat information that arrives unmarked or mismarked as CUI until the contracting officer decides.
Security standard Systems that handle CUI meet NIST SP 800-171 Revision 3. Agencies may add NIST SP 800-172 controls for critical programs or high-value assets.
Cloud services Cloud services that handle CUI meet requirements equivalent to the FedRAMP Moderate baseline.
Incident reporting Report a CUI incident within 72 hours of discovery. Civilian reports go to a CISA web portal, and defense reports go to DIBNet. Notify the contracting officer when you file.
Incident response List the CUI involved, build a timeline of user activity, identify how the attacker got in, cooperate with the agency, and keep images of affected systems for at least 90 days.
Gaps at proposal time An offeror that cannot meet every requirement discloses the gaps and submits a plan of action and milestones.

What Are the New Clauses and the SF XXX Form?

The rule adds three pieces. FAR 52.240-6 is a solicitation provision that notifies offerors about CUI requirements. FAR 52.240-7 is the contract clause that sets the duties. SF XXX is a new Standard Form that the procuring agency completes for each contract involving CUI.

The form tells the contractor whether it will handle CUI, whether the CUI sits in federal or contractor facilities, who carries the marking duties, and whether NIST SP 800-172 applies. That makes the agency responsible for naming the CUI, which gives contractors a document to point to when they set scope.

How Does It Compare With DFARS 252.204-7012 and CMMC?

Defense contractors already work under DFARS 252.204-7012, and CMMC adds verification on top of it. The FAR proposal does not replace either one. Here is how the three line up.

Topic DFARS 252.204-7012 and CMMC Proposed FAR CUI rule
Who it covers Defense contractors Civilian-agency contractors
Status In force Proposed
NIST SP 800-171 version Revision 2 Revision 3, which has 17 control families instead of 14
Incident window 72 hours 72 hours
Reporting portal DIBNet CISA portal for civilian contracts, DIBNet for defense
Verification CMMC self-assessment and certification levels Disclosure of gaps with a plan of action at proposal time

The 72-hour window lines up with DFARS on purpose. A contractor that has built a reporting process for defense work already has most of the pieces. Our post on what CUI is explains how the terms fit together, and our Revision 3 overview covers the standard in detail.

What Changed From the January 2025 Proposal?

The June 2026 version softened several points from the first draft.

  • The incident window grew from 8 hours to 72 hours.
  • The definition of a CUI incident now leaves out suspected incidents and improper handling that causes no actual disclosure, change, destruction, or unauthorized access.
  • Subcontractors report directly to the government, and also tell the contracting officer and the next higher-tier contractor.
  • The contractor liability language came out.
  • A flexible training approach replaced the fixed training requirement.
  • No extra reporting is needed when a FedRAMP-authorized cloud provider follows FedRAMP incident procedures.

What Should Contractors Do Now?

A final rule is not in place, but the direction is clear and the preparation work pays off under any outcome. These six steps cover the early work.

  1. Find your CUIList the contracts that involve CUI and the systems, people, and vendors that touch it.
  2. Compare your controls to Revision 3Map your current NIST SP 800-171 implementation to the Revision 3 requirements and note the differences.
  3. Review your cloud servicesConfirm that every cloud service handling CUI can show FedRAMP Moderate equivalence. Our page on GCC High covers one common option for government data.
  4. Build a 72-hour reporting processName who decides that an event is a CUI incident, who files the report, and how you preserve system images for 90 days.
  5. Plan for gapsWrite a plan of action and milestones for any requirement you cannot meet today, so you can disclose it at proposal time.
  6. Prepare your subcontractorsIdentify the subcontractors that will receive CUI and tell them what flow-down language to expect.

Detection is the hard part of a 72-hour clock, because the clock starts when you discover an incident. A monitored environment shortens that gap. Our security operations center service watches client environments around the clock, and our readiness assessment shows where your gaps sit.

A note on timing. In July 2026 the Department announced it was suspending the CMMC Phase II rollout. Phase I self-assessment requirements remain in place, and the DFARS 252.204-7012 obligations still apply. Self-assessments and select government-led assessments continue to enforce the Revision 2 requirements. See the Department announcement of July 13, 2026, 32 CFR Part 170, and DFARS 252.204-7025.

Frequently Asked Questions

What is the FAR CUI rule?+
The FAR CUI rule is a proposed Federal Acquisition Regulation rule that would set one government-wide framework for safeguarding Controlled Unclassified Information and reporting CUI incidents. The FAR Council published it on June 23, 2026 as FAR Case 2026-001.
Is the FAR CUI rule final?+
No. It was published as a proposed rule, and the public comment period closed on July 23, 2026. Until the FAR Council issues a final rule, the new clauses are not part of any contract. Check the Federal Register for the current status.
Does the FAR CUI rule apply to Department of Defense contractors?+
Defense contractors stay under DFARS 252.204-7012, which remains in effect. The FAR proposal extends similar requirements to civilian-agency contractors, and it routes defense incident reports to the DIBNet portal.
What is the SF XXX form?+
SF XXX is the proposed Standard Form for Controlled Unclassified Information Requirements. The agency that issues the contract completes it to show whether the contractor will handle CUI, where that CUI sits, who handles the markings, and whether NIST SP 800-172 applies.
How fast would contractors have to report a CUI incident?+
The proposal calls for a report within 72 hours of discovery. Civilian contracts report to a CISA web portal, and defense contracts report to DIBNet. The contractor also notifies the contracting officer and keeps images of affected systems for at least 90 days.
Does the proposed rule replace NIST SP 800-171 Revision 2 for CMMC?+
No. The proposed FAR rule names NIST SP 800-171 Revision 3 for civilian contracts, while DFARS 252.204-7012 and CMMC still refer to Revision 2. A separate DoD rulemaking would be the route to move defense contracts to Revision 3.

Handling CUI for federal customers?

Sentinel Blue monitors environments that hold CUI and helps contractors get ready for the requirements that apply to them.



Share: LinkedIn X / Twitter Email

Ready to get to work? So are we.

Our cyber adversaries aren't waiting and neither are we. Let's get the conversation started.

Contact Us Today