The 2015 CUI proposal planned a single FAR clause for contractors; in November 2026 it was still a proposal

On May 8, 2015, the National Archives proposed one rule for how agencies label and protect sensitive unclassified data. It called the rule part of a three-part plan with a single FAR clause. FAR proposals followed in 2025 and 2026; none was final.

Looking Back revisits past weeks one at a time, up to the most recent, and asks what it meant for the banks, health systems and public agencies we serve. The series was written in 2026, with the benefit of hindsight, and each article says which week it looks back on.

Two-minute summaryThe dek and the first sentence of each section, quoted from the article

On May 8, 2015, the National Archives proposed one rule for how agencies label and protect sensitive unclassified data. It called the rule part of a three-part plan with a single FAR clause. FAR proposals followed in 2025 and 2026; none was final.

  1. The week The order behind it described the problem in strong terms.
  2. The categories: what counted, and who decided That design came from the order.
  3. The markings: labels, banners and legacy The proposal made the registry’s markings the only ones allowed.
  4. The systems: moderate by default The proposal set a baseline for federal systems.
  5. The contracts: how the rule was meant to reach outsiders For other outside entities, the proposal used softer terms.
  6. How the proposal reached different organizations Defense contractors faced the defense supplement’s rules from August 2015. [3] Those rules used NIST SP 800-171 and a 72-hour reporting window. [3] In our reading, a contractor that also served civilian agencies would carry two sets of contract terms for similar data.
  7. Objections, and where the argument stops The proposal’s scope was agencies. [1] It said it applied to agency practices involving outside recipients by extension. [1] Its own regulatory analysis discussed contractors and small businesses at length, because its effect on them was the main economic question. [1] In our reading, a rule whose economic analysis centers on contractors cannot be read as internal to agencies.
  8. With hindsight The final rule’s preamble described the proposal as published on May 5, 2015, at 80 FR 26501. [4] The Federal Register issue that carries 80 FR 26501 is dated May 8, 2015. [1] We use the issue date.

The week

On May 8, 2015, the Federal Register published a proposed rule from the National Archives and Records Administration titled “Controlled Unclassified Information.” [1] The head of the agency had signed it on April 27, 2015. [1] Comments were due on or before July 7, 2015. [1] The rule would add a new Part 2002 to Title 32 of the Code of Federal Regulations. [1]

The proposal came from the Information Security Oversight Office, a component of the agency. [1] Executive Order 13556, dated November 4, 2010, had made the agency the executive agent for a program to manage unclassified information that needs protection. [2] The agency had delegated that authority to the office’s Director. [1] The proposal said it would set policy for agencies on designating, safeguarding, disseminating, marking, decontrolling and disposing of such information. [1]

The order behind it described the problem in strong terms. It said agencies used ad hoc, agency-specific policies, procedures and markings for this kind of information. [2] It called the result an “inefficient, confusing patchwork” that had led to inconsistent marking and unclear or unnecessarily restrictive dissemination. [2] The proposal added a count: before the order, more than 100 different markings for such information existed across the executive branch. [1]

The order had set its own clocks. Agency heads were to review their categories and markings and submit a catalog to the executive agent “within 180 days of the date of this order.” [2] The executive agent was to set up a public registry of approved categories “within 1 year of the date of this order.” [2] It was to publish a report on agency implementation in each of the first 5 years, and biennially after that. [2] In our reading, the May 2015 proposal was the binding rule the order’s design needed.

The proposal explained why the agency chose a regulation. It said there was no viable alternative to a rule for meeting the order’s mandate to set consistent standards across the government. [1] It said a regulation binds agencies throughout the executive branch to apply the program’s safeguards, markings and decontrol requirements uniformly. [1] It said the agency had built the program with agencies and industry through working groups, surveys and rounds of comment on drafts. [1]

The proposal also set out a plan that went beyond its own text. It said the agency had partnered with the National Institute of Standards and Technology on a special publication for applying security requirements in contractor environments. [1] That publication, NIST SP 800-171, had gone through one round of public comment and was in a second round until May 12, 2015. [1] The proposal said it expected NIST to finalize it in June 2015. [1]

The third part was a contract clause. The proposal said the executive agent was planning a single Federal Acquisition Regulation clause that would apply the rule’s requirements to contractors. [1] It described the whole as a “three-part plan (rule, NIST publication, standard FAR clause).” [1] It said businesses would receive streamlined and uniform requirements through that plan. [1]

The proposal was frank about what it did not know. The agency certified that the rule would not have a significant adverse economic impact on small entities. [1] It also said information on how many small contractors had not yet implemented the needed system standards was unreported and difficult to collect. [1] It said there may still be a significant impact on small businesses that had to bring themselves into compliance with existing standards. [1] It opened that question for comment. [1]

So, in the week of May 4, 2015, agencies and their contractors had a proposed rule, a draft NIST guide in its second comment round, and a promised contract clause. In our reading, only the first of the three was in their hands that week as a formal proposal.

NARA’s May 2015 proposal is easy to read as a records-management rule about stamps on documents. [1] It was more ambitious than that. It tried to replace more than 100 agency-specific markings with one program, one registry and one set of handling standards. [1] For a chief data officer, it was a proposal to classify a whole category of government data by one scheme.

The proposal also depended on two documents it did not contain. NIST was to describe security for contractor systems, and a single FAR clause was to carry the rule into contracts. [1] NIST finished its part in June 2015, as the final rule later shows. [4] The FAR Council published a proposed rule with a provision and two clauses on January 15, 2025. [5] On June 23, 2026, it re-proposed the controlled unclassified information terms, as one provision and one clause, inside a broader FAR proposal. [7]

Our argument is that the 2015 proposal settled how the government would name and label this data, but left the contractor’s obligations to a contract clause that did not arrive. In our reading, the Department of Defense filled the gap for its own contracts in August 2015, with its own clause. [3] That is the opposite of the uniformity the program promised.

We take the proposal in four parts, which follow the life of a piece of controlled data:

  1. The categories: what counted as controlled unclassified information, and who decided.
  2. The markings: how the data was labeled, and what happened to older labels.
  3. The systems: what security applied where the data was stored and processed.
  4. The contracts: how the requirements reached contractors and other outside holders.

The parts do not overlap. The first is the definition, the second the label, the third the technical protection and the fourth the legal channel to outsiders. After them we look at how the proposal reached different organizations, take the objections, and end with checks a data or security leader could run.

The categories: what counted, and who decided

A definition tied to existing law

The proposal defined controlled unclassified information as information that laws, regulations or government-wide policies require to have safeguarding or dissemination controls. [1] Classified information was excluded. [1] The definition did not let an agency create a new category by its own policy. [1]

That design came from the order. The order made the CUI categories and subcategories the exclusive designations for such information throughout the executive branch. [2] It said that if there is significant doubt about whether information should be designated, it shall not be so designated. [2] In our reading, that rule pushed agencies to show a legal basis before they controlled anything.

The registry as the source of truth

The proposal made an online registry the center of the program. It described the CUI Registry as the online repository for all information, guidance, policy and requirements on handling CUI, other than the rule itself. [1] It said the registry would be publicly accessible. [1] It said the registry would cite the laws, regulations or government-wide policies behind each category and note any sanctions for misuse. [1]

For a data governance team, this is a familiar structure. A registry is a controlled vocabulary with a citation for each term. The proposal said agencies and authorized holders must follow the requirements in the registry. [1] In our reading, a category list that changes in a registry, outside the rule text, means an agency’s data catalog has to track an external source that can change without a new rulemaking.

Basic and Specified

The proposal set two levels of handling. CUI Basic was the default, uniform set of standards for all categories. [1] CUI Specified applied where the underlying law, regulation or policy spells out its own handling standards. [1] The proposal said Specified standards may be more stringent than, or simply differ from, the Basic ones. [1]

The proposal also set a rule for gaps. Where a Specified authority was silent on a requirement, agencies were to use CUI Basic for it, unless that would conflict with the Specified authority. [1] In our reading, that turns each Specified category into a merge of two rule sets. A records system or data loss prevention tool would need both to decide how to treat a file.

Limits on agencies

The proposal also limited what agencies could add. It said agency CUI policies do not apply to entities outside that agency unless the executive agent approves them and publishes them in the registry. [1] It said agencies may not include any CUI handling requirements other than those in the order, the rule or the registry when entering contracts, treaties or agreements. [1]

That limit mattered for outsiders. A contractor working for several agencies had faced, in the proposal’s words, differing requirements and conflicting guidance for the same types of information. [1] The proposal said a single standard would be simpler to execute and reduce costs. [1] The limit on agency-specific terms was how the proposal meant to deliver that.

Exclusive by design

The proposal closed the door on controls outside the program. It said agencies may not control any unclassified information outside of the CUI Program. [1] It said agencies must designate CUI only by use of a category or subcategory approved by the executive agent and published in the registry. [1]

For a data team, that sentence cuts both ways. It ends ad hoc labels such as an office’s own “sensitive” stamp. It also means a data set that an agency wants to protect, but that no law or government-wide policy covers, cannot be CUI. In our reading, such data would need ordinary access controls without a CUI label, or a new category approved through the executive agent.

Challenges and disputes

The proposal gave holders a way to question a designation. Authorized holders who believe in good faith that a designation is improper or incorrect should notify the designating agency. [1] Each CUI senior agency official had to create a process to accept and manage challenges. [1] The process had to acknowledge receipt, state an expected timetable, let the challenger explain, name the deciding official and protect challengers from retribution. [1]

Until a challenge is resolved, the information stays at the control level its markings show. [1] Disputes that the parties cannot resolve may go to the executive agent, which the proposal called the impartial arbiter. [1] Parties may appeal the executive agent’s decision through the Director of the Office of Management and Budget to the President. [1] In our reading, a contractor that thinks data was over-designated has a formal channel, but must keep protecting the data while using it.

Disclosure laws stay separate

The proposal kept CUI apart from disclosure decisions. It said the mere fact that information is designated as CUI has no bearing on determinations under any law requiring disclosure. [1] It said agencies must not cite the Freedom of Information Act as a CUI safeguarding or dissemination authority. [1] It said FOIA reviewers must use FOIA standards and exemptions, not CUI markings, to decide on release. [1]

The Privacy Act got similar treatment. The proposal said records subject to the Privacy Act do not have to be marked as CUI for that reason alone. [1] It added that information in Privacy Act systems of records may fall under other CUI categories and may need marking for that reason. [1] In our reading, a privacy office cannot assume that its system of records notice settles the CUI question either way.

What the category part asked of agencies

The categories part was a data inventory exercise. Each agency had already been told by the order to review its categories and markings and submit them with their legal basis. [2] The proposal said agency heads would designate a CUI senior agency official responsible for implementation. [1] It said that official would be the primary point of contact with the executive agent. [1]

In our reading, the work fell first on records officers, privacy officers and general counsel. They knew which statutes and regulations required protection. A chief data officer would then need to map those categories onto actual data sets and systems. The proposal did not set a date for that mapping; it left implementation deadlines to the executive agent’s later planning. [1]

The markings: labels, banners and legacy

One set of markings

The proposal made the registry’s markings the only ones allowed. It said CUI markings listed in the registry are the only control markings authorized to designate unclassified information requiring safeguarding or dissemination controls. [1] It said agencies must take active measures to discontinue use of any other markings. [1] It said agencies may not modify program markings to accommodate existing agency practices. [1]

For an agency, that meant retiring its own labels. Legacy labels might live in document templates, email classification tools, records schedules and system banners. In our reading, the proposal’s ban on other markings reached all of those places, paper and digital alike.

The banner

The proposal required a banner marking on all CUI. [1] The banner could include up to three elements. [1] The CUI control marking was mandatory and could be the word “CONTROLLED” or the acronym “CUI.” [1] Category and subcategory markings were mandatory for CUI Specified. [1] Elements were to be separated by a single slash. [1]

A banner is metadata. In a document system, it can be a header, a property or a label. The proposal also allowed the CUI senior agency official to approve optional category markings for CUI Basic. [1] In our reading, that option meant two agencies could label the same type of Basic information differently, one with a category and one without.

Legacy material

The proposal defined legacy material as unclassified information marked or otherwise controlled before the program was implemented. [1] It said the program does not require agencies to redact or re-mark documents that bear legacy markings. [1] It said agencies must mark as CUI any information they derive from such documents and reuse in a new document, if it qualifies. [1]

That rule kept the cost of transition bounded. An agency did not have to relabel its archives. It did have to relabel information as it moved into new documents. In our reading, a data team would need a way to tell when content was derived from a legacy source. That is a lineage problem as much as a labeling one.

Waivers

The proposal allowed marking waivers. When marking is excessively burdensome, the CUI senior agency official may approve waivers of some or all marking requirements for CUI designated within that agency. [1] It said all CUI must still be marked when disseminated outside the agency. [1] A separate section let the agency head or senior official waive requirements in exigent circumstances, and required them to be reinstated when the circumstances end. [1]

In our reading, the outside-the-agency rule put the marking burden at the boundary. An agency could hold unmarked CUI internally under a waiver. It could not send it to a contractor that way. A data loss prevention control at the boundary would have to check for markings that internal systems might not carry.

A label cannot hide wrongdoing

The proposal set a limit on purpose. It said you must not mark information as CUI to conceal illegality, negligence, ineptitude or other disreputable circumstances embarrassing to any person or agency. [1] The order behind it had made the same point about openness, saying the program emphasizes the openness and uniformity of government-wide practice. [2]

In our reading, this limit is also a data quality rule. A category applied for the wrong reason is a wrong label, whatever the motive. A challenge process and a self-inspection program are the controls the proposal provided to find such labels. [1]

Decontrol

The proposal listed when agencies could decontrol CUI they had designated. The list included when the law no longer required control, when the agency released information to the public, and when a pre-determined event or date occurs. [1] It said decontrol could happen automatically or through an affirmative decision. [1] It said only personnel the agency authorizes may decontrol CUI. [1]

Decontrol is the end of the data life cycle. In our reading, automatic decontrol on an event or date is a rule a system could apply, if the event or date is recorded with the data. Without that record, decontrol becomes a manual review.

Records sent to the archives

The proposal also covered the last stop for many federal records. When feasible, agencies must decontrol records containing CUI before transferring them to NARA. [1] If they cannot, they must say on the transfer request that the records should stay controlled, and mark hard-copy containers. [1] If an agency does not note the CUI status on both the container and the transfer form, NARA may assume the information was decontrolled. [1]

In our reading, that rule makes the transfer form a control. A records officer who leaves the CUI field blank may, under the proposal’s terms, cause controlled data to be treated as decontrolled. Electronic transfers need the same discipline, because the proposal named NARA’s Electronic Records Archives as one of the transfer channels. [1]

The systems: moderate by default

Federal systems

The proposal set a baseline for federal systems. It said CUI is categorized at the moderate confidentiality impact level under FIPS Publication 199. [1] It said agencies must apply the appropriate security requirements and controls from FIPS Publication 200 and NIST SP 800-53, consistent with any risk-based tailoring decisions. [1] It said those standards were already required of federal agencies under the Federal Information Security Modernization Act of 2014. [1]

That baseline was not new for a federal system owner. What was new was the link between a data label and an impact level. In our reading, once data carries a CUI label, a system that stores it inherits at least a moderate confidentiality categorization.

A ceiling for outsiders

The proposal also set a ceiling. It said agencies may increase the confidentiality impact level above moderate and add controls only internally. [1] It said they may not require anyone outside the agency to use a higher impact level or more stringent requirements. [1]

The ceiling was the counterpart to the uniformity promise. A contractor serving several agencies would face one level, not several. In our reading, an agency that wanted more from a contractor for a particular data set would need it to be CUI Specified, with its own authority, rather than an agency preference.

Contractor systems and NIST SP 800-171

The proposal said many NIST controls are specific to government systems and had been difficult for contractors to implement on their own systems. [1] It said this had limited some businesses from competing for federal contracts. [1] It said NARA had partnered with NIST on a publication for applying the requirements in the contractor environment. [1]

That publication was NIST SP 800-171. The proposal said it was in its second comment round until May 12, 2015, and that NARA expected it to be finalized in June 2015. [1] The final rule later incorporated by reference NIST SP 800-171, dated June 2015, including updates as of January 14, 2016. [4]

Handling outside systems

The proposal also set physical and operational rules. Authorized holders needed controlled environments to protect CUI from unauthorized access or observation. [1] When discussing CUI, a holder had to reasonably ensure that unauthorized individuals could not overhear. [1] Outside a controlled environment, a holder had to keep CUI under direct control or behind at least one physical barrier. [1]

It addressed equipment too. When reproducing CUI on printers, copiers, scanners or fax machines, holders had to ensure the equipment did not retain data, or sanitize it under NIST SP 800-53. [1] Destruction had to make CUI unreadable, indecipherable and irrecoverable. [1] The proposal named NIST SP 800-88 among the guidance for destruction. [1] In our reading, these rules reached facilities, print services and device disposal contracts.

Evidence an assessor would ask for

The proposal did not list audit evidence. [1] In our reading, its terms point to records an inspector general or self-inspection team could ask to see. They include the system’s security categorization under FIPS 199, its selected controls under NIST SP 800-53, and the list of CUI categories it holds. They also include media sanitization records for copiers and printers, and destruction records.

The proposal required agencies to run a self-inspection program. [1] It said the program must include methods that evaluate program effectiveness, measure compliance and monitor implementation progress. [1] In our reading, a self-inspection that can show where each category lives, and how each location is protected, depends on the data inventory from the category part.

What the systems part asked of a security team

The systems part asked a security team to tie two inventories together. One is the inventory of data categories. The other is the inventory of systems and their security categorizations. In our reading, a system that held CUI at a lower categorization would need to be re-categorized or have the data moved.

For contractors, the systems part depended on a document not yet final that week. The proposal described the plan for NIST SP 800-171 but could not cite a final version. [1] A contractor’s security lead in May 2015 could read the draft and the proposal, and wait for both to be final.

The contracts: how the rule was meant to reach outsiders

A requirement in every contract

The proposal said agencies must include a requirement to comply with the order and the rule in all contracts that require a contractor to handle CUI for the agency. [1] It said the contractual requirement must be consistent with standards prescribed by the executive agent. [1] It did not itself write the clause. [1]

For other outside entities, the proposal used softer terms. When feasible, agencies should enter formal information-sharing agreements that require the other party to comply. [1] Where an agency had to share without an agreement, it must tell the recipient that the government strongly encourages protecting the CUI. [1] In our reading, a state agency or a university receiving CUI without an agreement had no binding obligation under the proposal.

What agreements had to say

The proposal set minimum terms for written agreements with non-executive branch entities. They had to say that CUI remains under the legal control of the federal government and that misuse is subject to penalties under applicable law. [1] They had to require the entity to handle CUI under the order, the rule and the registry. [1] They had to require the entity to report non-compliance to the disseminating agency’s CUI senior agency official. [1]

These are the terms a contracts office or grants office would need to add. In our reading, the reporting term carried the operational weight. It required the outside entity to know who the official was and to have a way to detect non-compliance.

A reasonable expectation before sharing

The proposal set a test for each outbound transfer. To disseminate CUI to a non-executive branch entity, a holder must have a reasonable expectation that the recipient will continue to control it under the order, the rule and the registry. [1] Before disseminating CUI, the holder must mark it under the executive agent’s guidance. [1]

The proposal also limited restrictions. Agencies may limit dissemination only through limited dissemination controls approved by the executive agent and published in the registry. [1] It said using those controls to restrict access unnecessarily is contrary to the program’s goals. [1] In our reading, the program pushed agencies to share, as long as the recipient could be expected to protect the data. That puts the weight on how an agency forms its expectation about a recipient.

The promised clause

The proposal’s plan rested on one clause for all agencies. It said the executive agent was planning a single FAR clause that would apply the rule to contractors and further promote standardization. [1] It said the clause would benefit small entities struggling with the current range of contract clauses. [1]

The FAR is the shared rulebook for executive agency contracts. A single clause there would have meant one text in every solicitation that involved CUI. Without it, the proposal’s contract requirement would be met by each agency’s own language, consistent with the executive agent’s standards. [1] In our reading, that is the patchwork the program was meant to end, moved from markings into contracts.

Defense moved first

The Department of Defense acted for its own contracts. On August 26, 2015, it issued an interim rule amending its acquisition supplement, effective that day. [3] The rule replaced a table of security controls based on NIST SP 800-53 with NIST SP 800-171 for covered defense information in contractor systems. [3] It defined rapid reporting of cyber incidents as reporting within 72 hours of discovery. [3]

In our reading, the defense rule did part of what the single FAR clause was meant to do, for one department. It adopted the NIST publication the NARA proposal had described. [1] [3] It also added a reporting duty and a new class of information, covered defense information, that sat inside the defense supplement rather than the government-wide program.

How the proposal reached different organizations

Federal agencies

For agencies, the proposal was binding once final. [1] It required a senior official, training, a self-inspection program and processes for challenges and misuse. [1] The proposal said agencies must train employees when they first begin working for the agency and “at least once every two years thereafter.” [1] Self-inspection was to include no less than annual review. [1]

Defense contractors

Defense contractors faced the defense supplement’s rules from August 2015. [3] Those rules used NIST SP 800-171 and a 72-hour reporting window. [3] In our reading, a contractor that also served civilian agencies would carry two sets of contract terms for similar data.

Civilian agency contractors

Civilian contractors faced each agency’s contract language. The proposal said agencies must include a requirement to comply in all contracts that require handling CUI. [1] Without the single clause, the text of that requirement was each agency’s to write, within the executive agent’s standards. [1]

State and local governments

The proposal said it would have no direct effects on state and local governments within the meaning of the federalism order. [1] It still reached them through information-sharing agreements, when feasible, and through the encouragement notice when not. [1] In our reading, a fusion center or state health agency would see CUI terms in its federal agreements.

Universities and research organizations

The proposal’s definition of non-executive branch entity covered persons and organizations outside the executive branch. [1] In our reading, a university that received CUI under a grant or contract was such an entity. The final rule later recorded a few comments, primarily from academic and research entities, calling the safeguarding requirements and NIST SP 800-171 too burdensome. [4] It declined to reduce the controls for information shared with outside entities. [4]

Health and financial organizations

The proposal said nothing specific about health systems or banks. In our reading, they would meet CUI when they received information from an agency under an agreement or contract. A health system in a federal research contract, or a bank handling program data for an agency, would be an outside holder. The proposal’s terms for agreements and contracts would apply through those documents. [1]

Cloud and IT service providers

A company that runs systems for an agency sat in a different position from one that only received CUI. The proposal’s systems section applied federal standards to CUI on federal information systems. [1] The final rule later said a system operated on behalf of an agency is subject to the rule as though it were the agency’s own. [4] In our reading, a hosting or managed service provider would need to know, contract by contract, which side of that line it was on.

Small businesses

The proposal’s own analysis singled out small contractors. NARA said it believed the impact would be minimal, if any, for businesses already meeting existing NIST and OMB standards. [1] It said reporting on non-compliance with those standards was limited. [1] It said that if any businesses were substantially out of compliance, the impact on them may be significant. [1]

In our reading, the cost for a small firm was not the rule’s text but the gap between its systems and the standards the rule pointed to. The proposal expected NIST SP 800-171 to narrow that gap by describing requirements in terms a contractor’s systems could meet. [1] It expected the single FAR clause to make the terms the same across agencies. [1] The first of those arrived in June 2015. [4] The second did not arrive as a final rule in the period we checked. [6]

Agency program offices

The proposal put duties on agency heads and their CUI senior agency officials. [1] Program offices that create and share data would feel them in daily work: choosing categories, applying banners, and deciding whether a recipient can be expected to protect data. [1] In our reading, a program office that shares data with grantees or states would need the agreement terms before the first transfer, not after.

Objections, and where the argument stops

“The proposal was about agencies, not contractors”

The proposal’s scope was agencies. [1] It said it applied to agency practices involving outside recipients by extension. [1] Its own regulatory analysis discussed contractors and small businesses at length, because its effect on them was the main economic question. [1] In our reading, a rule whose economic analysis centers on contractors cannot be read as internal to agencies.

“Defense filled the gap, so the FAR clause did not matter”

The defense supplement covered defense contracts. [3] The FAR proposal said the Department of Defense had implemented the CUI program’s requirements in its own clause. [5] It said there was not a standard way requirements were identified and shared with contractors. [5] That is the FAR Council’s own description, in 2025, of the gap. [5]

“The FAR moves slowly, so the timing says nothing”

We have no source for a normal pace, and we do not compute one. The record shows a FAR case numbered 2017-016 in the regulatory agenda. [6] It shows a proposed rule on January 15, 2025, and a projected final rule date of December 2025 in the Spring 2025 agenda. [5] [6] It shows the case folded into a broader FAR proposal on June 23, 2026. [7] Whether that pace was normal is a judgment we leave aside.

“Uniform labels were the real goal”

Labels were a goal. The order also aimed at uniform safeguarding and dissemination. [2] The proposal tied handling to the label, and contract terms to handling. [1] In our reading, a uniform label with non-uniform contract terms delivers half the promise.

“A registry outside the rule weakens notice”

One could argue that placing categories and markings in a registry, rather than the rule, made the rules harder to follow. The proposal answered by making the registry publicly accessible and the sole authoritative repository besides the order and the rule. [1] It required each category to cite its legal basis. [1] In our reading, the registry gives notice, but an organization still has to watch it.

Where the argument stops

The argument does not claim that contractors were unprotected or that data was lost because of the missing clause. We have no source for that. It does not claim the 2025 or 2026 proposals will be finalized in any form. It claims only what the documents show: the plan had three parts, and the third came as proposals in 2025 and 2026. [1] [5] [7]

Checks for a data or security leader

If you are an agency

  • Map each registry category your agency handles to the data sets and systems that hold it.
  • Confirm that each system holding CUI is categorized at least moderate for confidentiality.
  • Check that legacy labels are retired in templates and tools, and that derived content gets current markings.
  • Put marking checks at the boundary where data leaves the agency, since waivers stop there.

If you are a contractor or grantee

  • List every contract and agreement that mentions CUI or covered defense information, and the clause each uses.
  • Record which NIST SP 800-171 version each contract names, since the 2025 FAR proposal named Revision 2. [5]
  • Identify the reporting window in each contract; the defense rule used 72 hours, the 2025 FAR proposal used 8 hours and the June 2026 FAR proposal used 72 hours. [3] [5] [7]
  • Ask your contracting officer which registry categories apply, rather than inferring them.

For both

  • Treat the registry as a dependency that can change, and assign someone to watch it.
  • Keep a record of why each data set is or is not CUI, citing the law behind it.

With hindsight

NARA published the final rule on September 14, 2016, effective November 14, 2016. [4] It established Part 2002 and applied to executive branch agencies that handle CUI. [4] It also described itself as affecting organizations that handle CUI or operate information systems on behalf of an agency. [4]

The final rule’s preamble described the proposal as published on May 5, 2015, at 80 FR 26501. [4] The Federal Register issue that carries 80 FR 26501 is dated May 8, 2015. [1] We use the issue date. The preamble said NARA received 29 written responses, totaling 245 individual comments. [4] It said comments came from contractors, businesses, academic and research organizations, state organizations, federal agencies and others. [4]

The final rule kept the core of the proposal and changed some parts. It incorporated by reference NIST SP 800-171, dated June 2015, with updates as of January 14, 2016. [4] It set out two types of systems that process CUI: federal information systems and non-federal information systems. [4] It said a system operated on behalf of an agency provides processing services the government might otherwise perform itself but has decided to outsource. [4] It said agencies may not treat non-federal systems as though they are agency systems, and must use NIST SP 800-171 when setting requirements for them. [4]

It also changed the treatment of legacy material. The final rule’s preamble said agencies must mark legacy information with new CUI markings if it qualifies. [4] It allowed an agency with a large amount of legacy material to waive re-marking while it stays within the agency, with protection by alternate means. [4] The proposal had said the program did not require re-marking legacy documents. [1]

The final rule repeated the contract plan. Its preamble said the executive agent was developing a FAR case through the normal FAR process, for agencies to use in contracts. [4] It said contracts and solicitations in which CUI will not be involved should not include CUI requirements, and that this would be handled through the FAR case and other contracting practices. [4]

The Department of Defense had already moved. Its interim rule of August 26, 2015 made NIST SP 800-171 the standard for covered defense information in contractor systems. [3] The 2025 FAR proposal described that defense clause, DFARS 252.204-7012, as the place where the Department had implemented the CUI program’s requirements. [5]

The FAR case appeared in the regulatory agenda as FAR Case 2017-016. [6] On January 15, 2025, the FAR Council published the proposed rule. [5] It would create a standard form, then numbered SF XXX, to identify the CUI in a contract and its handling requirements. [5] It would add a provision and two clauses to the FAR. [5] It would require contractors to report suspected or confirmed CUI incidents within 8 hours, unless a different period applies. [5] It named NIST SP 800-171, Revision 2, among the requirements a contract could trigger. [5] Comments were due on or before March 17, 2025. [5]

The Spring 2025 Unified Agenda entry listed the rule at the final rule stage. [6] It said the FAR Council had received public comments on the January 2025 proposal and was considering them in developing the final rule. [6] It projected a final rule in December 2025. [6] As checked on November 16, 2026, reginfo.gov listed Spring 2025 as the most recent Unified Agenda that carried RIN 9000-AN56. [8]

The case then moved into a larger rewrite. On June 23, 2026, the FAR Council published a proposed rule under FAR Case 2026-001, part of the Revolutionary FAR Overhaul, revising FAR parts that included Part 40. [7] It listed FAR Case 2017-016, the January 2025 proposal, among the cases it aimed to consolidate. [7] It said multiple respondents had commented on the 2025 proposal’s incident reporting timeline, and that the timeline had been updated to 72 hours from discovery. [7] It said the clause on identifying and reporting information that is potentially controlled unclassified information had been deleted, based on the comments. [7] It would add a provision at 52.240-6, Notice of Controlled Unclassified Information Requirements, and a clause at 52.240-7, Controlled Unclassified Information. [7] Comments were due on or before July 23, 2026. [7] As checked on November 16, 2026, we found no final FAR rule on controlled unclassified information in the Federal Register.

What held up from May 2015 is the structure. The registry, the Basic and Specified levels, the moderate baseline and the use of NIST SP 800-171 for contractor systems all survived into the final rule. [4] What did not hold up was the timing of the third part. The single clause the proposal planned was, as checked on November 16, 2026, still a proposal. [5] [6] [7]

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

  • controlled unclassified information
  • CUI
  • NARA
  • NIST SP 800-171
  • federal contractors
  • data classification