The FAR controlled unclassified information (CUI) rule and where it stands, explained

The governmentwide contract rule for controlled unclassified information is still proposed. Its January 2025 version was folded into the June 2026 FAR overhaul proposal for a new FAR part 40, which moved incident reporting from 8 to 72 hours and pointed to NIST SP 800-171 Revision 3.

Federal agencies have handled controlled unclassified information (CUI) under one set of executive branch rules since the National Archives and Records Administration (NARA) codified them at 32 CFR part 2002 [1]. To apply those policies to contractors, the 2025 proposal said, the CUI Program must be incorporated into the acquisition process [1]. This explainer covers the 2025 proposal that would supply one, how the 2026 overhaul of the Federal Acquisition Regulation (FAR) reshaped it, what changed between the two drafts, and what is in force today.

The 2025 proposal: FAR Case 2017-016

The Department of Defense, the General Services Administration and NASA published the proposed rule, FAR Case 2017-016, on January 15, 2025, at 90 FR 4278 [1]. It would amend the FAR to implement NARA’s CUI Program as it relates to federal contracts [1]. Comments were due by March 17, 2025 [1].

The central device was a new form, the Standard Form XXX, Controlled Unclassified Information (CUI) Requirements [1]. The proposal explained that laws, regulations and governmentwide policies already require CUI protections, but that there was no standard way to identify those requirements and share them with contractors [1]. The SF XXX would be included in solicitations and contracts that may involve CUI and would define the handling requirements in line with 32 CFR part 2002 [1].

The 2025 draft would have added a provision, 52.204-WW, and two clauses: 52.204-XX, Controlled Unclassified Information, and 52.204-YY, Identifying and Reporting Information That Is Potentially Controlled Unclassified Information [1]. Identifying CUI on the SF XXX would trigger the compliance requirements in 52.204-XX, such as the security requirements in NIST SP 800-171 Revision 2 or the controls in NIST SP 800-53, depending on the type of information system involved [1]. Contractor employees handling CUI would have had to complete training specified on the form [1]. Contractors would have had to report suspected or confirmed CUI incidents within 8 hours, unless a different period applied to a specific category of CUI or to a federally controlled facility [1].

The 2026 overhaul: a new FAR part 40

The case did not go final on its own [2] [3]. On June 23, 2026, the FAR Council published a proposed rule under the Revolutionary FAR Overhaul revising FAR parts 1, 2, 4, 33, 39, 40 and 53, at 91 FR 37550, as FAR Case 2026-001 [2]. The rule implements Executive Order 14275, Restoring Common Sense to Federal Procurement, and is one of twelve proposed rules that together would rewrite the FAR [2]. Comments were due by July 23, 2026 [2].

That proposal consolidates security requirements, prohibitions and exclusions into FAR part 40, and adds requirements for handling CUI there [2]. It lists FAR Case 2017-016 among the earlier cases it draws on, and says the FAR Council received comments on the 2025 proposal and changed the text in response [2]. The CUI requirements would sit in a new provision, 52.240-6, Notice of Controlled Unclassified Information Requirements, and a new clause, 52.240-7, Controlled Unclassified Information, prescribed at FAR 40.304-6 [2]. The term CUI would be defined in FAR 2.101 because more than one FAR part would use it [2].

What changed between the two drafts

The 2026 proposal lists its changes from the 2025 text [2]:

  • Reporting window. CUI incidents would be reported within 72 hours from discovery, instead of 8 hours, which the Council says aligns with DFARS 252.204-7012 and the Cyber Incident Reporting for Critical Infrastructure Act of 2022 [2].
  • Where to report. Defense contracts would report at the DoD’s DIBNet site and other contracts to CISA, with a notice to the contracting officer; an incident at a FedRAMP-authorized cloud provider that is reported under FedRAMP’s procedures needs no separate report [2].
  • Narrower incident definition. A CUI incident would cover unauthorized disclosure, improper modification or improper destruction of CUI, or unauthorized access to the system where it resides; unmarked or mismarked CUI would not be an incident unless it led to one of those results [2].
  • One clause removed. The clause on identifying and reporting information that is potentially CUI is deleted [2].
  • Training and liability. The specific training requirement and the language on contractor liability for CUI incidents are removed [2].
  • Contractor information. Information a contractor creates or holds is excepted from the CUI definition unless a law, regulation or governmentwide policy specifically requires the contractor to apply safeguarding or dissemination controls to it [2].

The technical baseline moved too. The 2026 form would list the organization-defined parameters for NIST SP 800-171 Revision 3, aligned to the values that will be codified in 32 CFR part 170 through DoD rulemaking, so that contractors follow one standard across agencies [2]. Enhanced requirements from NIST SP 800-172 would apply only when an agency identifies them for a critical program or high-value asset [2]. A new paragraph would require a contractor to notify the contracting officer within 72 hours of determining that another law or regulation prevents it from meeting a requirement in the clause [2].

What is in force today

Both documents are proposed rules. The 2026 proposal describes its changes as what the rule would do “if finalized” [2]. As checked on November 14, 2026, a Federal Register search for FAR Case 2017-016 returns the 2025 and 2026 proposals and regulatory agendas, and no final rule [3]. No date for a final rule has been published, so none is given here.

Defense contractors already work under DFARS 252.204-7012, which defines “rapidly report” as within 72 hours of discovery of any cyber incident [4] and which the 2026 proposal cites in aligning its 72-hour window [2]. Across agencies, the gap the 2025 proposal described remains: no standard way to identify CUI requirements and share them with contractors [1].

For data and records teams, the drafts point to the same practical questions. Where does CUI live in contractor systems, which category does each data set belong to, and could the organization report an incident within 72 hours of discovery with the data elements available at that point [2]? Those are good practice for readiness, not requirements yet.

This explainer describes proposed rules; it is not legal advice, and organizations should confirm with counsel and their contracting officers how CUI terms apply to their contracts.

Moraph’s teams help organizations with work like this. See our solutions.

Spotted an error? Tell us and we will check it and correct the explainer where needed.

  • FAR
  • controlled unclassified information
  • CUI
  • FAR Case 2017-016
  • FAR part 40
  • Revolutionary FAR Overhaul
  • NIST SP 800-171
  • 32 CFR part 2002
  • incident reporting