An HVAC supplier just paid $5 million over cybersecurity. Twenty-five awards were named, and most of them are subcontracts.

On Friday, November 13, the Justice Department announced that Johnson Controls, Inc. and two of its subsidiaries will pay $5 million to resolve False Claims Act allegations that they did not meet the cybersecurity requirements in their federal contracts. The customers were NASA and the Departments of Defense, Energy and Justice. The conduct period runs from January 2018 to August 2025. And the company that paid sells heating, ventilation and air conditioning.

Start with that last fact, because it is the whole lesson. Johnson Controls is not a defense IT integrator or a cloud provider. It supplies building products and services. The settlement agreement lists its awards in an exhibit, and there are twenty-five of them — fire protection work, security systems, HVAC at launch facilities, orders placed against schedule contracts. The great majority are not prime contracts at all. They are subcontracts, held under somebody else’s award.

The Department alleges three failures. The first is the one worth reading twice: that the company did not control access to protected information because it did not have sufficient information about its own information systems, or sufficient control over them. The second and third are familiar by now — that on the contracts requiring compliance with NIST SP 800-171, including its Defense Department contracts, it did not maintain a system security plan meeting the contract’s requirements, and did not adequately document, fully develop or fully implement a plan of action and milestones to correct deficiencies in its systems.

Read in order, those three are a sequence rather than a list. You cannot write an accurate security plan for systems you have not inventoried, and you cannot build a credible plan of action against a plan that was never accurate. The paperwork failures downstream are what the first failure looks like once somebody asks for documents.

  • Dec 31, 2017
    The date written into the Defense Department’s own solicitation provision: the deadline by which an offeror represents it will have implemented the 800-171 requirements. The settlement agreement says the requirements applied to this company by not later than that date.
  • Jan 1, 2018
    The covered conduct period begins — the day after the deadline.
  • Jun 7, 2024
    A former employee, Kelly Vance, files a sealed whistleblower suit in the Northern District of Georgia.
  • Aug 1, 2025
    The covered conduct period ends, seven and a half years after it started.
  • Feb 11, 2026
    A second whistleblower, David Thomas, files separately in the District of Columbia — twenty months after the first, and neither knew of the other.
  • Sep 14, 2026
    The two relators agree how to divide a share neither has yet been awarded.
  • Nov 13, 2026
    The settlement is announced, with an agreement dated the previous month. Nine years, start to finish.

Vance receives $850,000 of the recovery. Seven investigative bodies worked the file across six departments: the Defense Criminal Investigative Service, the Naval Criminal Investigative Service, the Air Force Office of Special Investigations, and the inspectors general of NASA, Energy, Justice and the General Services Administration. James Ives, who directs the Defense Criminal Investigative Service, summarized the Department’s position in four words — cybersecurity requirements in federal contracts “are not optional.” Theodore S. Hertzberg, the U.S. Attorney in Atlanta, was equally direct: “My office will vigorously pursue contractors who fail to follow these requirements.” The claims resolved are allegations only, and there has been no determination of liability.

The bill does not stop at five million. Of the $5 million, $2,428,565.80 is restitution, and interest runs at five percent a year from June 2026 until payment. On top of the settlement sum the company pays $135,000 and $163,750 to the two relators’ lawyers. And within ninety days of the agreement taking effect it must identify and repay the unallowable costs it had already included in earlier requests for payment — which is to say, the government also wants back whatever it was billed for compliance work that the Department alleges was not done. Budget the remediation twice: once to fix the gap, once to give back what the gap was funded with.
So what: the exposure here did not arrive through a cybersecurity contract. It arrived through subcontracts for building services, and it attached to a company whose leadership had every reason to think none of this was aimed at them. That is the part to act on. Pull the list of every award on which you are a subcontractor, not just the primes in your pipeline, and find the protected-information clause in each one — because the clause travels with the work regardless of what the work is. Then start where the Department started: not with the security plan, but with the inventory of systems the plan is supposed to describe. An inaccurate inventory is not a documentation problem. It is the first allegation.

Paying the settlement does not close the file. The agreement says so, in two paragraphs most people never read.

A False Claims Act settlement reads like an ending. It is narrower than that, and the Johnson Controls agreement is a clean example of exactly how narrow. What the government releases is civil and administrative monetary claims for the covered conduct — under the False Claims Act, under the Program Fraud Civil Remedies Act, and under the common-law theories of breach of contract, payment by mistake, unjust enrichment and fraud. That release is conditioned on the money actually arriving.

Everything else is kept. And in the next paragraph the company agrees to give up two constitutional defenses — double jeopardy and excessive fines — against any later criminal or administrative action arising from the same conduct. That is not an unusual term. It is a standard reservation in agreements of this kind, which is precisely why it is worth knowing that it is there.

What the civil release does not cover: criminal liability. Administrative liability and remedies, suspension and debarment included. Liability for any conduct other than the conduct described in the agreement — which here ends on August 1, 2025, leaving everything after that date untouched. The liability of individuals, which a corporate settlement does not resolve. Tax liability. And claims about warranties, defective products, or failure to deliver. The civil number is the part of the exposure that could be converted into a figure and closed. It is not the whole exposure.

What has changed in 2026 is the apparatus standing behind the piece that was reserved. A White House task force on fraud was established by executive order in March; the Acting Attorney General created a National Fraud Enforcement Division by memorandum on April 7; and a final rule published at 91 Fed. Reg. 53,357 on August 18, effective August 24, formally established it, adding a new subpart to the Department’s organizational regulations. The jurisdiction that rule assigns the new division includes, in its own words, “criminal proceedings involving monies owed to or paid by the United States.” That is procurement, described in the broadest available terms. The rule’s preamble says the division works “using advanced, data-driven investigative techniques” and by “developing systems and processes that ensure efficient identification and investigation of fraud.”

Be precise about what this is and is not. The rule does not mention the False Claims Act, and civil false-claims work stays where it has always been, in the Civil Division — Friday’s settlement was a Civil Division matter, announced by the Civil Division’s acting head. The new division is a criminal litigating component. But the Johnson Controls announcement closes with a paragraph on that task force and that division, which tells you which banner these cases are now being announced under, and the second half of the rule’s stated method is the half that matters for anyone who has been relying on the arithmetic of detection. Both whistleblowers in this case were insiders. A department that is building systems to identify fraud from its own data is a department that will not always need one.

So what: this changes where a discovered gap gets escalated. When somebody in your organization finds that the security plan does not match the systems, or that an assessment on file is out of date, the question is no longer only what the fix costs and how long it takes. It is also what the mandatory-disclosure obligation in your business-ethics clause requires, who makes that call, and how fast. Decide that sequence now, in writing, while nothing is wrong — because the version of this conversation that happens after a subpoena arrives is a much worse conversation. And make sure the route for raising it internally is one a cautious employee would actually use. In this case two of them chose the courthouse instead, twenty months apart.

The sentence that makes these cases possible is in a solicitation provision — and you agreed to it when you bid.

Trace any of these settlements back far enough and you arrive at the same place, which is not a clause in a signed contract. It is DFARS 252.204-7008, Compliance with Safeguarding Covered Defense Information Controls, in a version dated October 2016. The Johnson Controls agreement names it alongside the better-known 7012. It is a solicitation provision, not a contract clause — which means it governs the proposal and then does not appear in the awarded contract’s clause list at all. That is a large part of why nobody reads it.

Its operative paragraph is short. By submitting its offer, the provision says, the offeror represents that it will implement the NIST SP 800-171 security requirements in effect when the solicitation was issued — not later than December 31, 2017, or as the contracting officer authorizes. That is the hinge the whole enforcement program turns on. A statement of present intent, made at the moment of offer, about a standard with a date attached. The False Claims Act does not need a breach or an audit finding to work with a sentence like that; it needs only a representation and a subsequent request for payment. Which is why the covered conduct in Friday’s settlement begins on January 1, 2018 — the day after the date the provision names.

The provision has a second half that gets even less attention, and it is the genuinely useful one. If an offeror proposes to vary from any 800-171 requirement, the provision tells it to submit a written explanation to the contracting officer, for consideration by the Defense Department’s chief information officer, of either why a requirement is not applicable or how an alternative but equally effective security measure compensates for not implementing it. An authorized representative of the chief information officer then adjudicates that request in writing before award — and anything accepted is incorporated into the resulting contract.

A plan of action and an adjudicated variance are not the same document. A plan of action is your own record of something you have not done yet, written by you, held by you, and — as three settlements now demonstrate — readable later as evidence of a known gap. An adjudicated variance is the government’s written agreement that a requirement does not apply to you or is satisfied another way, signed off before award and carried into the contract. One is a promise to yourself. The other is a term of the deal. Only the second was ever the government’s idea for handling a control you genuinely cannot implement, and almost nobody uses it.
So what: before the next proposal leaves the building, have somebody confirm that the 800-171 representation inside it is true on the day it is submitted rather than true in plan. If a requirement does not apply to your environment, or is met by a different control, that is a case to make in writing to the contracting officer for the chief information officer’s representative — not an open line left sitting in a plan of action for four years. And do not let the 2016 date on the provision suggest it has gone quiet. Old provisions do not expire; the suspended piece of the program this year was the third-party certification gate, not the representation underneath it. That sentence is still in every solicitation you answer, and it was still enough to produce a $5 million number on Friday.

What to do this week

Three things, in the order the Department found them.

  • Inventory before you document. Reconcile the list of systems in your security plan against the systems that actually exist and actually touch protected information. The first allegation on Friday was not knowing.
  • Pull every award where you are a subcontractor and find the protected-information clause in each. The clause follows the work, not the industry you think you are in.
  • Settle your internal escalation route in writing. Who decides what gets disclosed when a gap is found, on what clock — and whether an employee would use that route rather than a lawyer.

Quick hits

  • Nov 13
    Four protected-information regimes appear in one settlement, and only two of them are DFARS clauses.
    The agreement cites the two Defense Department clauses you would expect, 252.204-7008 and 252.204-7012 — and then NASA’s own security requirement for unclassified information technology at NFS 1852.204-76, a Department of Energy Official Use Only requirement, and the Justice Department’s own information-technology security requirements. The information at issue is described as including both controlled unclassified information and Official Use Only information, which are separate categories with separate handling rules. If your clause matrix was built around 7012 and the certification program, it will not show you the other three, and three of the four customers in this case were not the Defense Department.
  • Nov 13
    One of the seven inspectors general on this case was the General Services Administration’s, and schedule orders were among the awards named.
    Alongside the defense and NASA investigators, the inspectors general of Energy, Justice and the General Services Administration all worked the file, and the special agent in charge of the administration’s Southeast and Caribbean investigations division is quoted in the announcement. Several of the twenty-five awards in the exhibit are orders placed against schedule contracts. The practical point for anyone holding a schedule alongside defense work: the oversight body that comes asking about your cybersecurity representations may not be the one you have been preparing for, and it will be asking about the same documents.

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