The Justice Department said on Nov. 13 that Johnson Controls Inc., the building-systems and HVAC supplier, and two of its subsidiaries have agreed to pay $5 million to resolve allegations that they did not meet the cybersecurity requirements in their federal contracts. The two subsidiaries are Johnson Controls Fire Protection LP and Johnson Controls Security Solutions LLC.

The announcement identifies no particular intrusion and no stolen data. According to the DOJ announcement, the government says the companies failed to control access to protected information and failed to keep the security documents their contracts required. Under the False Claims Act, taking federal money while not meeting the security terms you agreed to can lead to a fraud settlement even if no attacker is shown to have gotten in.

What the government alleged

According to the DOJ Office of Public Affairs, the allegations cover contracts and subcontracts with four agencies: NASA, the Department of Defense, the Department of Energy and the Department of Justice. The period at issue runs from January 2018 to August 2025. Lawyer Monthly reports that the settlement covers 25 federal contracts and subcontracts.

The government's allegations fall into two groups:

  • Access control. The companies allegedly failed to control access to protected government information, because of a lack of sufficient information about their information systems and a lack of sufficient control over them.
  • Required documents under NIST SP 800-171. On the contracts that required the NIST standard, including Defense Department contracts, the companies allegedly failed to maintain a System Security Plan that met the contractual requirements and failed to adequately document, fully develop or fully implement a plan of action and milestones.

The contract terms differed by agency. Lawyer Monthly says certain DoD agreements included DFARS clauses that point to NIST SP 800-171. NASA contracts had clauses covering unclassified electronic information. The DOE and DOJ contracts included provisions on who could access information.

The two documents at the center of the case

The allegations focus on paperwork and access control more than on any reported break-in. A security expert might see that as a small issue, but these two documents carry legal weight.

NIST SP 800-171 is the federal standard for protecting sensitive but unclassified government information held on contractors' own systems. It is a list of security requirements, and a contractor bound by it has to show how it meets each one.

A System Security Plan (SSP) is that showing. Lawyer Monthly describes it as a document covering the information system, its boundaries and operating environment, and how the contractor implements the required safeguards. Without an SSP, or with an SSP that doesn't match the real environment, a contractor has nothing that supports its claim to be compliant.

A plan of action and milestones (POA&M) covers what isn't done yet. It identifies deficiencies and the corrective work meant to reduce or eliminate vulnerabilities, and good practice is to give each item a fix and a date. The government alleges that Johnson Controls did not adequately document, fully develop or fully implement these plans. A POA&M that sits in a drawer and never gets worked doesn't help.

Whistleblowers brought the case

The settlement resolves two qui tam lawsuits. In these cases a private person sues on the government's behalf under the False Claims Act and can share in what the government recovers. DOJ lists the cases as United States ex rel. Kelly Vance v. Johnson Controls, Inc., No. 1:24-cv-2500, in the Northern District of Georgia, and United States ex rel. David Thomas v. Johnson Controls Int'l PLC, No. 1:26-cv-448, in the District of Columbia. Kelly Vance, a former Johnson Controls employee, will receive $850,000 of the settlement, according to DOJ and Court Cast.

DOJ's announcement included statements from Acting Assistant Attorney General Jonathan Guynn of the Civil Division and U.S. Attorney Theodore Hertzberg. It also included statements from the investigating agencies: the Defense Criminal Investigative Service, the Naval Criminal Investigative Service, NASA's Office of Inspector General and the General Services Administration's Office of Inspector General.

What the settlement does not show

The claims resolved by the settlement are allegations only, and DOJ says there has been no determination of liability. Lawyer Monthly notes that Johnson Controls has not admitted liability and that the settlement does not establish that the alleged violations occurred. Court Cast also reports that the settlement does not establish that government information was compromised, and says the announcement names no particular intrusion. As the sources describe it, this is a case about whether required security controls and documents were in place. It is not described as a breach case.

What It Means for Defenders

No patch or version fix applies here. The risk is in compliance work, and it falls on any organization that holds federal contracts or subcontracts with cybersecurity clauses. That includes DoD suppliers under DFARS clauses that reference NIST SP 800-171, and contractors for NASA, DOE and DOJ with information-handling or access terms. Johnson Controls makes HVAC, fire protection and security systems, so the case also shows that these rules can reach suppliers outside traditional IT. Facilities and building-services contractors with such clauses should take note.

Based on what the government alleged, here are the things to check:

  • Read your contracts and subcontracts. The 25 contracts and subcontracts in this case carried different security clauses from different agencies. Know which of your agreements cite NIST SP 800-171 and which have agency-specific information or access terms. Subcontracts were included here.
  • Confirm your System Security Plan exists and is accurate. It should describe the systems you actually run today, not the network you had three years ago. The government alleged a failure to maintain an SSP that met contract requirements; a stale SSP is an easy way to end up with that problem.
  • Treat your POA&M as a project plan. Each open item should have an owner, a fix and a date, and there should be evidence that work is happening. The government alleged that plans were not adequately documented, developed or implemented.
  • Check access controls for protected information. Access control was the first allegation in the case, tied to limited knowledge of and control over the company's own systems. Review who can reach government data, including staff, field technicians and third parties, and keep an accurate inventory of the systems involved.
  • Remember the timeline. The alleged conduct covered more than seven years. Compliance gaps can build up over the life of a contract, and records from years ago can come up in later litigation.
  • Take internal reports seriously. Both cases were whistleblower suits, and one relator, a former employee, receives $850,000. People inside your company who raise compliance problems should get a real response through internal channels.

For contractors working toward CMMC, the case adds a data point. It suggests that NIST SP 800-171 compliance, and the SSP and POA&M documents that support it, can draw False Claims Act scrutiny as well as ordinary contract review. A security claim made to the government needs current documentation behind it.

Sources