Issues The Feed
Hello Contractor News

Johnson Controls pays $5M over cybersecurity rules in federal HVAC and building contracts

Johnson Controls will pay $5M to settle claims it skipped federal cybersecurity rules on HVAC and building contracts. What subs on federal jobs should check.

A Johnson Controls building. Photo: Corey Coyle via Wikimedia Commons, CC BY 3.0

Johnson Controls Inc. and two of its subsidiaries will pay $5 million to settle claims that they didn't follow required cybersecurity rules on federal contracts for HVAC and other building products and services, the Justice Department announced Nov. 13 (via U.S. Department of Justice). The case is a reminder that the paperwork side of a federal job, including how you protect the government's information, can carry real money.

The Milwaukee-based company settled along with Johnson Controls Fire Protection LP and Johnson Controls Security Solutions LLC. The deal resolves False Claims Act allegations tied to contracts and subcontracts with NASA and the Departments of Defense, Energy and Justice from January 2018 to August 2025.

According to the government, Johnson Controls didn't control access to protected information because it lacked enough information about, and control over, its own computer systems. On contracts that required it to meet the cybersecurity controls in National Institute of Standards and Technology Special Publication 800-171, including Defense Department work, the company allegedly didn't keep an adequate System Security Plan and didn't properly develop or carry out a plan of action and milestones.

Those two documents are basic building blocks under NIST 800-171. The security plan describes how a contractor's systems protect sensitive government information. The plan of action lists the gaps and how and when the contractor will fix them.

The settlement resolves two whistleblower lawsuits filed by former Johnson Controls employees, one in federal court in Atlanta and one in Washington, D.C. Whistleblower Kelly Vance will receive $850,000 from the settlement, according to the Justice Department. The U.S. Attorney's Office for the Northern District of Georgia, which worked the case, and Atlanta's WSB-TV also reported the settlement.

As is standard, the department noted that the claims are allegations only and there has been no determination of liability.

"Federal contractors must follow required cybersecurity standards to safeguard sensitive government information," said Jonathan Guynn, acting assistant attorney general for the department's Civil Division. Theodore S. Hertzberg, U.S. attorney for the Northern District of Georgia, said his office "will vigorously pursue contractors who fail to follow these requirements, particularly when those failures persist over several years."

"Cybersecurity requirements in federal contracts are not optional," said James Ives, director of the Defense Criminal Investigative Service, one of seven federal investigative offices involved.

The case lands while the Pentagon's own cybersecurity certification program, known as CMMC, is in a holding pattern. CMMC requirements began appearing in Defense contracts on Nov. 10, 2025, and the program covers information that flows down to subcontractors. But the department suspended the program's second phase in July, according to the Defense Department's CMMC page, and says it's paused in Phase 1. Self-assessments against NIST 800-171 are still required in the meantime, and the department says it will keep enforcing compliance through those self-assessments and some government-led reviews.

Why it matters for Contractors

Most small shops will never hold a NASA contract. But if you sub on a military base, a federal courthouse, a VA clinic or any other federal building job, the cybersecurity clauses in the prime contract can flow down to you. That's true whether you're installing HVAC, fire alarms or access control.

Read the clauses before you sign. If a subcontract references NIST 800-171, FAR 52.204-21 or the Defense cybersecurity clauses, ask the prime what you're expected to have in place, whether that's a security plan, a plan of action or a self-assessment score.

Don't check a compliance box you can't back up. The False Claims Act cases in this area turn on contractors claiming they met requirements they didn't. If you're not there yet, a written plan to get there is better than a certification you can't support.

And remember who brought this case: former employees. Whistleblowers can collect a share of what the government recovers, so gaps people inside your company know about are a real risk.