The rule that writes NIST 800-171 into every federal contract is now the one lawyers expect first

Procurement attorneys tracking the FAR controlled-unclassified-information rule now put it as early as the end of this year, and no later than the end of the administration’s term. The more useful read is the comment record industry filed over the summer. Every significant ask is about the government’s side of the transaction — what it marks, who decides, which version applies, where you send the report. Nobody asked for the standard itself to come down.

The rule is FAR Case 2026-001, published as a proposed rule on June 23, 2026 at 91 FR 37550 inside the acquisition overhaul. This brief covered its contents when it appeared in August: it puts CUI safeguarding and NIST SP 800-171 into contracts across the civilian agencies rather than the Department of War alone, sets a 72-hour clock for reporting unauthorized access to CUI, and requires contractors to flow the obligation down and to oversee how subcontractors handle the data. The principal comment period closed July 23; the separate paperwork-burden comment period closed August 24. Since then, nothing — no final rule, no interim rule, no announced date.

What is new is that the people who read these dockets for a living have started putting a bracket around the timing. Reporting in early October collected the view from three government-contracts partners: the rule could land as soon as the end of 2026 and almost certainly before the administration’s term ends, with the open question being whether it arrives as a final rule or as an interim rule that takes effect on publication. One of them, Wiley Rein’s Trayce Howard, called it a sea change for many companies. Covington’s Ryan Burnette made the point that matters for planning: the current draft is far more similar to the January 2025 version than different from it, which means the shape of the obligation has now been stable across two drafts and a full comment cycle.

  • Jan 2025
    First standalone FAR CUI proposed rule. An eight-hour reporting window, triggered by suspected as well as confirmed incidents. Drew 93 respondents.
  • Jun 23, 2026
    Reissued inside the acquisition overhaul as FAR Case 2026-001. Reporting window widened to 72 hours, confirmed incidents only, deliberately aligned with the forthcoming CISA reporting rules.
  • Jul 23, 2026
    Comment period closes. Trade associations, universities and contractors file.
  • Aug 24, 2026
    Separate paperwork-burden comment period closes. The docket goes quiet.
  • End of 2026 at the earliest
    Practitioner consensus on timing, with no government-announced date. Final rule or interim rule both still live. An interim rule would take effect on publication.

Now the comment record, which is where the signal is. The Aerospace Industries Association asked the FAR Council to widen the 72-hour reporting window to 30 calendar days. The U.S. Chamber of Commerce objected that reporting still routes to agency-specific points of contact rather than one central hub, so a contractor working for several agencies inherits several reporting procedures. EDUCAUSE, writing for research universities, filed the most granular set: tie the standard for unmarked or mismarked CUI to objective indicators such as government markings or CUI metadata; state plainly on the agency CUI form that a contractor is not expected to infer CUI status without them; add a standard taxonomy to that form, because agencies have made mistakes identifying and marking CUI; fix the version of NIST SP 800-171 that applies at the moment of award rather than letting it float; and judge a plan of action and milestones by the credibility of the remediation plan rather than the size of the gap it discloses.

Put those side by side and the pattern is hard to miss. Industry is not arguing about whether 800-171 should apply. It is arguing about whether a contractor can reliably tell when it applies, which version of it applies, and who to call at three in the morning. That is a fight over the government’s inputs, not over the contractor’s obligations — and it is the same complaint the Department’s own reform review heard loudest, where improper CUI designation ranked among the most-cited frictions in the industry responses.

If your company has only ever held civilian contracts, read this paragraph twice: defense suppliers have lived under DFARS 252.204-7012 since its full-compliance deadline at the end of 2017, and they understand what it means for a cybersecurity representation to be attached to a payment. For a company whose entire history is with the civilian agencies, this rule is the first time NIST SP 800-171 compliance becomes a term of a federal contract — and therefore the first time a claim for payment can carry a cybersecurity representation behind it. That is the doorway through which False Claims Act exposure arrives, and the public record shows what it looks like in practice: a $507,144 settlement over a self-scored 110 that an assessment put at −170, and a $2 million settlement over a single non-compliant network. Neither began with an audit. One began with a former employee.
So what: two drafts and a comment cycle have left the core intact, which means you can build against it now without betting on a date. Three things are safe to start: a written inventory of which contracts and which systems hold CUI, a named individual who owns the incident call with a 72-hour runbook behind them, and a current gap assessment against 800-171. If you hold civilian-agency work, do this on the civilian side of the house too — that is the half of the market this rule is aimed at, and the half with the least muscle memory for it. An interim rule takes effect the day it publishes; there is no phase-in to plan around.

Four months before the pause, the government’s own auditors named three things that could break the program. All three are still open.

On March 12, 2026 — four months before the Phase 2 suspension — the Government Accountability Office published Defense Contractor Cybersecurity: DOD Should Address External Factors That Could Impede Program Implementation, report GAO-26-107955. The Senate Armed Services Committee had asked for it. The audit ran from December 2024 to March 2026, which means it closed its fieldwork roughly four months before the Department hit pause on the thing it was auditing. Read now, it is the most precise forecast on the public record of why the program stalled.

GAO scored the Department’s planning documents against seven key elements of a strategic plan. Six were addressed. One — identifying key external factors that could affect implementation — was only partially addressed, and that single gap produced the report’s single recommendation: the Chief Information Officer should assess and document those factors and develop approaches to address them. The Department concurred. Then GAO named the factors, and this is the part worth keeping.

External factorWhat GAO found in MarchWhere it stands now
Ecosystem capacityThe program depends on private assessors and certifiers to meet its own assessment projections. GAO counted 92 authorized assessment organizations as of December 2025, with 14 more assessed but not yet authorized.Reported at 117 authorized or accredited as of the September town hall, with the in-progress queue draining. More capacity, less demand for it.
Program demandCost and complexity could lead companies — especially small businesses, roughly three-quarters of a defense industrial base of about 200,000 firms — to stop doing business with the Department.This became the Department’s stated reason for the July 13 suspension. Unresolved by design: it is the reform review’s central question.
Evolving requirementsThe Department had not updated the program to Revision 3 of NIST SP 800-171, which NIST issued in May 2024.Still Revision 2. A transition plan exists and is held in abeyance; no rulemaking has published.

The candid moment in the report is the Department’s answer. Officials told GAO they had not assessed and documented these factors because the factors are outside the Department’s control — and that they had been unaware they needed to. GAO’s reply was that a factor being outside your control is not a reason to leave it undocumented, and that without doing so “DOD is increasing the risk that the program will not achieve its strategic goals.”

GAO also looked at the acquisition workforce that administers all of this, and found the training thin on the ground: 267 completions of the introductory cybersecurity course as of September 2025, and 18 of the senior-leader course, against a proposed goal of 70% completion within a year — roughly 113,000 people for the introductory course alone. The people writing the clause into your contract are learning this material at the same time you are.

The waiver, and the exception inside it: a January 2025 Department memorandum allows senior acquisition officials to waive CMMC assessment requirements. GAO’s assessment was blunt: waivers do not address the underlying challenges, and frequent use “could also undermine the long-term viability of the CMMC program.” The detail to carry away is the carve-out. The memorandum bars waivers for solicitations that require cleared defense contractors — so where classified work is in scope, subcontractors still have to meet the requirements even where assessment capacity is short. A waiver is also granted against a solicitation, not issued to a company. If someone in your supply chain has mentioned one, the only useful question is which solicitation it covers and whether your scope of work sits inside it.
So what: notice what GAO did not question. Not the 110 requirements, not the need for verification, not the standard. Every factor it named is about delivery — enough assessors, affordable for small firms, current with NIST. A finding that a program may be hard to deliver is not a finding that the underlying obligation is wrong, and the reform now in interagency coordination is an answer to GAO’s recommendation, not a repeal of the requirement. Practically: stop treating a waiver as portable, and check whether any solicitation you support requires cleared defense contractors, because that is the one case the waiver authority explicitly cannot reach.

The CUI executive agent already banned putting CUI into an uncontrolled AI system. The ban covers federal employees. It does not mention you.

The office that runs the CUI program government-wide is the Information Security Oversight Office at the National Archives. In September this brief covered two of its notices, 2026-07 and 2026-08, on the guidance agencies owe their contractors and on waivers. There is an earlier one from the same office that has had almost no attention in the defense industrial base, and it is the most direct statement any federal authority has made about controlled information and artificial intelligence.

ISOO Notice 2026-01, Responsible Use of Classified National Security Information and Controlled Unclassified Information with Artificial Intelligence, was issued on March 30, 2026 and signed by ISOO Director Michael D. Thomas. It instructs agencies that Executive Orders 13526 and 13556 and their implementing regulations at 32 CFR 2001 and 2002 apply in full when classified information or CUI touches an AI system. Then it draws a line: agencies are to prohibit their personnel from entering classified information or CUI into any AI system that is internet-enabled, connected to infrastructure outside the agency’s control, or connected to an environment not accredited to the required standard. Before CUI is permitted onto such a system at all, the agency is to assess the system’s type and capabilities with its chief information officer, chief information security officer, CUI program manager and IT staff in the room — then fold the guidance into its own CUI policy and budget for the work.

The notice’s most useful contribution is a taxonomy. It distinguishes generative, open, closed, and asymmetric open-and-closed AI systems — the last being a system that draws on external data while keeping user inputs inside the session or inside an administrator-defined boundary, which the notice describes as common in regulated deployments. The operative question it sets up is not whether something is artificial intelligence. It is where the input goes.

What the notice does not do is the reason it belongs in this brief. It does not mention contractors. It does not mention non-federal systems. It sets no deadline, defines no approved-system list, and says nothing about how to mark output a model produced from CUI inputs. The executive agent for the entire CUI program has written down what it considers an unacceptable place to put controlled information, and then addressed it to the federal workforce only.

So what: treat the silence as a gap in the paperwork, not a gap in the exposure. Two things already carry this onto your systems without a new rule. ISOO Notice 2026-07 makes agencies give contractors written CUI guidance covering safeguarding and training, and the agency drafting yours is the one that just rewrote its own AI policy. And DFARS 252.204-7012 and the 110 requirements never cared which software was involved: an internet-enabled model outside your control is an external system, and you already owe requirements about those. Write the one-page rule yourself — permitted environment, prohibited ones, a line in your system security plan’s boundary description — and for every tool, answer the question the notice makes agencies answer: where does the input go?

What to do this week

The theme this issue: the obligations are stable, the dates are not. Build against the obligations.

  • Name who owns the 72-hour incident call, and write the runbook. Who decides it is reportable, who files, and where — civilian contracts included.
  • Write your one-page AI rule and reference it in your system security plan. Permitted environment, prohibited environments, and for each tool: where does the input go?
  • Ask whether any solicitation you support requires cleared defense contractors. The assessment-waiver authority cannot reach those, so flow-down stands.

Quick hits

  • Ongoing
    The no-cost help that actually exists, and the one list of it worth your time.
    The National Security Agency’s Cybersecurity Collaboration Center runs four services for defense industrial base companies at no charge, funded by the Department: protective DNS filtering; attack surface management, an adversarial look at your internet-facing assets returned as a prioritized report; threat intelligence collaboration over a secure channel carrying non-public, industrial-base-specific intelligence; and continuous autonomous penetration testing you run yourself. Eligibility is a low bar — an active Department contract at prime or subcontract level, or access to non-public Department information — and enrollment is a short form. These lower the cost of doing the work and produce artifacts an assessor will find useful. They do not lower the bar, and nobody at NSA signs your affirmation.
  • Oct 16, 2026
    The office holding the reform report added another senior technologist.
    Chief Information Officer Kirsten Davies named Jon Steinbach as strategic technical advisor on October 16, his remit covering emerging technology and, in his own framing, deeper collaboration across the defense industrial base. It follows August’s appointment of Sonu Shankar as principal deputy chief information officer, whose portfolio includes cybersecurity. Read it for institutional weight rather than policy: the office that controls both the reform recommendations and the Department’s forthcoming artificial-intelligence security framework keeps adding senior people. Programs being wound down do not get staffed up.

Not sure where your organization stands?

CUI Vault gives you a live, always-audit-ready picture of your CUI environment and NIST 800-171 posture — so headlines like today’s are a footnote, not a fire drill. Reach out to your NtelSec team to talk through your current gaps.

This briefing is a general-information summary of publicly reported CMMC and CUI developments. It is not legal advice; consult your compliance counsel before making contractual or certification decisions.
Talk to us about CUI Vault All issues