The largest cybersecurity False Claims settlement reported to date landed last Tuesday. Every one of the five allegations is a missing document or an unchecked vendor.

On November 3 the Justice Department announced that ILC Dover and ILC Astrospace will pay $13 million to resolve allegations that they billed the Army, the Missile Defense Agency and NASA while knowing they had not complied with the cybersecurity requirements in those contracts. The conduct period runs from January 2018 to October 2024. The case began with the company’s own director of cybersecurity, and not one of the five alleged failures is a breach.

That last point is the one to sit with. Nobody alleges ILC was hacked. The government’s theory is that the company billed for work on contracts carrying cybersecurity obligations it had not met — and the obligations it is alleged to have missed are, almost without exception, pieces of paper and one unvetted vendor.

What the Department alleges was missingPeriod allegedWhat that is in your own file
A cloud provider holding CUI that the company never required or ensured met FedRAMP Moderate–equivalent securityFeb 2023 – Oct 2024Equivalency evidence for every cloud service touching controlled data, and the clause binding the provider.
A system security plan for each covered system, developed and periodically updatedJan 2018 – Mar 2022; Sep 2022 – Oct 2024One plan per system: boundaries, environment, how each requirement is implemented, connections out.
Full implementation of the NIST SP 800-171 and SP 800-53 controlsJan 2018 – Oct 2024Implementation, not description. The plan says what you do. This is whether you do it.
Plans of action and milestones to correct the deficienciesJan 2018 – May 2019; Jan 2022 – Sep 2024One entry per open requirement, with a corrective action, a named resource and a target date.
A current assessment reported to the Department — Astrospace filed none, Dover filed one out of dateNov 2020 – Oct 2024A current score, from a review of the plan under the Department’s own assessment methodology.

The case was brought under the whistleblower provisions of the False Claims Act by Philip Root, ILC’s former director of cybersecurity, who receives $2.35 million of the recovery; it is captioned United States ex rel. Root v. ILC Dover LP, No. 25-cv-70, in the District of Delaware. Six investigative bodies worked it, from the Defense Criminal Investigative Service and Army Criminal Investigation Division through to NASA’s and the General Services Administration’s inspectors general. Benjamin L. Wallace, the U.S. Attorney for Delaware, put the point plainly: “The best response to cyberattacks is to prevent them from happening in the first place.” NASA’s assistant inspector general for investigations, Robert Steinau, was blunter — “Strict compliance with federal cybersecurity standards is non-negotiable for any company doing business with NASA.” The claims resolved are allegations only, and there has been no determination of liability.

The part that should interest anyone buying or selling a company: Ingersoll Rand acquired ILC Dover in June 2024. Its spokesperson says the company became aware of the matter following that acquisition, acted promptly, and was in compliance by October 2024 — exactly where the alleged conduct period ends. Read the sequence: exposure created by a predecessor, found by an acquirer, fixed in about four months, and still $13 million two years later. Cybersecurity representations made to the government do not stay behind with the seller. On either side of a transaction involving controlled data, the security plan, the plan of action, the assessment history and the cloud inventory belong in diligence next to the financials.
So what: look at the dates in the last row: November 2020 to October 2024. That is the self-assessment-and-report duty, unmet for four years — and it is the duty that was never paused. Note what day it is, too. Today would have been the start of Phase 2 third-party certification, and it arrives with nothing attached to it; the largest number in the history of this kind of case arrived six days early, and it did not need Phase 2 to exist. So take the five rows above and run them this week against your files rather than your recollection. Four are answerable in an afternoon by somebody who knows where the documents live. The fifth — whether the controls are implemented rather than described — takes longer, which is precisely why it is the one most often assumed.

The first allegation is about somebody else’s computers. The clause makes it your problem anyway, and it uses two verbs.

In eleven issues this brief has never written about the sentence that produced the first row of that table, which is an omission worth correcting, because it is the single most commonly misread obligation in the whole framework. It sits in DFARS 252.204-7012 at paragraph (b)(2)(ii)(D), and it reads — in the clause version dated May 2024, untouched by July’s suspension — that if the contractor intends to use an external cloud service provider to store, process or transmit covered defense information, the contractor “shall require and ensure that the cloud service provider meets security requirements equivalent to those established” for the FedRAMP Moderate baseline, and “complies with requirements in paragraphs (c) through (g) of this clause for cyber incident reporting, malicious software, media preservation and protection,” and for “access to additional information and equipment necessary for forensic analysis, and cyber incident damage assessment.”

Two verbs. Require is contractual: your agreement with the provider has to say so. Ensure is evidentiary: you have to know it is true. Both duties sit on you, not on the provider, and a provider does not discharge them on your behalf by being large or well known.

Then notice what paragraphs (c) through (g) actually ask of a vendor, because they are not abstract: a cyber incident reported within 72 hours of discovery to the Department’s reporting portal, malicious software submitted to the Department’s cyber crime center, images and monitoring data preserved and protected for at least 90 days from the report, access to additional information or equipment for forensic analysis on request, and a damage assessment after. Every one of those is something a third party has to be contractually obliged and operationally willing to do, at two in the morning, on your behalf, for a system you do not own.

What equivalency is not: it is not a marketplace listing, and it is not an authorization — an equivalent offering has neither. It is not a SOC 2 report, an ISO 27001 certificate, a completed vendor questionnaire, or a reassuring page on a provider’s website. It is not a sentence in a master services agreement promising “compliance with applicable law.” And it is emphatically not the provider’s own say-so: the clause asks you to ensure, which is a word about what you can show. Equivalency is a file you hold about a system you do not operate.

What belongs in that file is set out in the Department’s chief information officer’s December 21, 2023 memorandum on FedRAMP Moderate equivalency. We could not access the memorandum itself this week, so take the specifics as published practitioner readings rather than quoted text: those analyses agree that equivalency means the full FedRAMP Moderate control baseline with no open control findings at assessment, assessed by a FedRAMP-recognized third-party assessment organization rather than by the provider itself, producing a body of evidence — security plan, assessment plan, assessment report, plan of action — that is handed to you and producible to an assessor on request. The direction of travel is not in doubt either way: the forthcoming government-wide rule for controlled unclassified information carries the same FedRAMP Moderate requirement onto civilian contracts.

So what: make one list this week: every cloud service, hosted application and managed service that stores, processes or transmits controlled data. Against each line write two things — the document evidencing FedRAMP Moderate authorization or equivalency, and the provision in your agreement obliging that provider to incident reporting, malware submission, ninety-day media preservation, forensic access and damage assessment. A line with neither is the first allegation in last Tuesday’s settlement, written in your own hand. And include the services nobody thinks of as cloud: the file-transfer tool used for drawings, the e-signature platform, the CAD viewer, the helpdesk that screenshots a controlled document into a ticket.

There is a named federal official accountable for whether your data is CUI at all. Last Wednesday the Archives tightened the procedure for keeping track of who it is.

On November 4, the Information Security Oversight Office at the National Archives issued ISOO Notice 2027-01, signed by its director, Michael D. Thomas, and titled Procedures for Notification of an Appointment or Update to Controlled Unclassified Information Senior Agency Officials or Program Managers. It rescinds and replaces a memorandum from 2018. Its operative instruction is one sentence: agencies must complete and submit the attached change form whenever there is an appointment or update to their senior agency official or program manager for controlled unclassified information, sent to the Archives by email.

As administrative housekeeping goes, this looks like the least newsworthy document of the week. It is worth two minutes anyway, for the architecture it quietly maintains. It rests on 32 CFR 2002.8(b), under which an agency head must designate a CUI senior agency official and include that official in the agency’s contact listings; on 2002.8(c), under which that official designates a program manager; and on the definitions at 2002.4, under which both must be federal employees designated in writing, with the senior agency official serving as primary point of contact for official correspondence with the CUI Executive Agent.

Put plainly: at every agency you sell to, there is a named federal employee, designated in writing and listed in that agency’s contacts, who owns the question that small businesses cited most frequently in the response record to July’s reform review — whether your data should have been called controlled in the first place. That person exists by regulation, not by courtesy. And since September, under an earlier notice from the same office, agencies have owed contractors written CUI guidance across twelve categories, from how government-furnished CUI is identified through to the challenge process. The guidance has an author, and the author has a title and a name. Be clear about the limits, though: this notice does not mention contractors, sets no deadline, and creates no public roster — which is precisely why the question has to be asked rather than searched.

So what: send one email this week to your contracting officer with two requests in it: the contract’s written CUI guidance, and the name and office of the agency’s CUI senior agency official and program manager. Then route marking and designation questions to that named official in writing, rather than deciding them internally or firing them into a program mailbox. This changes nothing about what you owe — the obligation attaches to the character of the data, not to whether anybody answers your email. What it changes is the quality of your record. An unanswered question in a thread addressed to a named federal official is a very different document, two years and one whistleblower later, than a judgment call you made alone and never wrote down.

What to do this week

Three things, all answerable from files you either have or do not have.

  • Run the five allegations as a self-audit. A current plan per covered system, dated plans of action, a current assessment reported to the Department, and the controls implemented rather than described.
  • List every cloud and managed service touching controlled data, and name the equivalency evidence and the contract clause for each. Blanks are the first allegation.
  • Ask your contracting officer in writing for the agency’s CUI senior agency official and the contract’s written CUI guidance. Then address designation questions to a person.

Quick hits

  • Nov 2026
    Congress returns this week with no defense authorization act enacted, and the supply-chain provisions in the bill that passed are about who you buy from.
    The House passed its version on July 22 by 216 to 212; it reached the Senate on September 14, where a procedural vote on the companion bill failed in July and a compromise text is now expected in the lame-duck session. Government funding expires December 11. Four provisions in the House text are worth reading early: a bar on information-technology contracts with companies operating in China, Russia, Iran or North Korea unless they agree to disclose vulnerabilities to the Department first; exclusion orders from the Federal Acquisition Security Council reaching not only sources of concern but companies that use them; referral of additions to the Chinese military companies list to that council with a 270-day review; and a designated office for adversarial capital, including beneficial ownership of subcontractors. The much-discussed grant program for small-business assessment costs sits in the chamber that has passed nothing. The exclusion provisions are in the one that has.
  • Nov 2026
    The General Services Administration is adding a voluntary certificate whose own text names the False Claims Act as a remedy.
    The draft significant-changes attachment for the next schedule refresh introduces a domestic end product certificate at 552.238-130. Certification is voluntary — and paragraph (d) says a knowingly erroneous certification may bring remedies including those under the False Claims Act, though the agency notes it will not enforce the clause until an information-collection clearance is in place. The same refresh carries the clause on protecting government data inside large language model systems that this brief covered in October, with 90 days to accept the resulting mass modification. One correction: that refresh had been signaled for November 6 and has slipped, with the agency’s own attachment now saying only November 2026. Read the clauses before you accept the modification, not after.

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