The Department of Justice (DOJ) continues to prioritize enforcement of federal contract cybersecurity requirements through the False Claims Act (FCA). In the past five months alone, DOJ announced resolutions with LOGZONE Inc. ($507,144), Honeywell Aerospace Inc. ($2.04 million), ILC Dover LP and ILC Astrospace LLC ($13 million), and Johnson Controls, Inc. and two subsidiaries ($5 million). Each resolution centered on alleged failures to implement the security requirements of Defense Federal Acquisition Regulation Supplement (DFARS) clause 252.204-7012 and National Institute of Standards and Technology (NIST) Special Publication (SP) 800-171, and in some cases related NASA, Department of Energy, and DOJ contract requirements, while the contractors continued to bill the government. Each resolution followed a common template: payment of roughly double the government's claimed damages, broad reservations of criminal and administrative remedies, and no admission of liability in most cases. Government contractors, particularly those who handle controlled unclassified information (CUI) under a contract or subcontract with the Department of Defense (DoD), must be more cautious than ever in implementing required security controls and should take internal reports of noncompliance seriously.
The False Claims Act
The FCA imposes civil liability on any person who knowingly presents, or causes to be presented, a false or fraudulent claim for payment to the government, or who knowingly makes a false record or statement material to such a claim. "Knowingly" includes actual knowledge, deliberate ignorance, and reckless disregard; specific intent to defraud is not required. Violators face treble damages plus inflation-adjusted, per-claim civil penalties for each false "claim" submitted to the government (e.g., a claim for payment while the contractor was out of compliance). The FCA's qui tam provisions permit private whistleblowers, known as "relators," to file suit on the government's behalf and to receive between 15 and 30 percent of any recovery. These whistleblowers are typically insiders who have raised issues that management did not remedy but can be any employee with non-public knowledge of the false claim, or even a third-party "data miner" or a competitor. In the cybersecurity context, the government's theory is typically that each invoice submitted while the contractor knew it was not meeting its contractual security obligations was a false claim.
The Cybersecurity Requirements That Have Led to FCA Settlements
DFARS 252.204-7012 requires defense contractors and subcontractors to implement the approximately 100 security safeguards in NIST SP 800-171 on systems that process, store, or transmit covered defense information (which is a type of CUI), and to ensure that any external cloud provider handling such information meets FedRAMP Moderate-equivalent standards. DFARS 252.204-7019 and 252.204-7020 require contractors to post a current assessment score of their NIST SP 800-171 compliance, ranging from -203 to 110, to the Supplier Performance Risk System (SPRS). DFARS 252.204-7012 also contains other requirements, such as for cyber incident reporting.
The recent settlements underscore the breadth and complexity of these cybersecurity requirements, creating compliance and FCA risk for contractors. According to the settlement agreement, LOGZONE posted a perfect self-assessment score of 110, but a later Defense Contract Management Agency assessment scored it at -170. DOJ alleged that Honeywell submitted false claims by seeking payment despite one of its units' networks not meeting NIST SP 800-171 standards. ILC allegedly lacked a system security plan (SSP) for most of a seven-year period, had no implemented plans of action and milestones (POA&Ms) to correct deficiencies, stored covered defense information with a noncompliant cloud provider, and never reported consultant findings that would have produced scores of -59 and 21. Johnson Controls allegedly failed to control access to protected information because it lacked sufficient information about and control over its own systems, and also lacked a compliant SSP and POA&Ms. The bottom line is that the DFARS, NIST, and other contractual requirements for handling sensitive government information are varied and offer many opportunities for lapses by even conscientious contractors.
Notably, in none of these matters did the DOJ publicly allege an actual breach or data loss; the alleged violations were failures to implement and document required controls. The message is clear: the U.S. government—including federal customers and law enforcement agencies—considers the risks posed by insecure contractor information systems more than sufficient basis to warrant FCA investigations. Whistleblowers know this and continue to assert cybersecurity deficiencies in qui tam actions, too.
The Resolutions
The four settlements include nearly identical terms and demonstrate the value of cooperation and a negotiated resolution. In each, approximately half the payment was designated as restitution, implying a damages multiplier of about 2. Each agreement released FCA and related common-law claims, but expressly reserved criminal liability, suspension and debarment, and claims against individuals. The cases also reflect the broad scope of federal agencies applying relevant cybersecurity requirements: LOGZONE involved two Navy contracts, while Johnson Controls, an HVAC and building-services supplier, resolved claims under 25 contracts and subcontracts with six agencies, including the Departments of Energy and Justice. While DFARS 252.204-7012 may be among the best-known cybersecurity clauses, contractors and subcontractors should bear in mind that other, non-DoD agencies maintain similar requirements for information that is unclassified but nevertheless sensitive and subject to special control measures.
Relators and the Government Drive These Cases
Three of the four matters began as qui tam suits by former employees. In ILC, the relator was the company's former director of cybersecurity, who will receive $2.35 million as the relator's share. Honeywell's relator, also a former employee, will receive approximately $376,000, and Johnson Controls' relator will receive $850,000. The employees responsible for cybersecurity are uniquely positioned to identify compliance gaps, and when internal escalations go unaddressed, the FCA offers them a significant financial incentive to report externally. The fourth case, LOGZONE, arose from the government's own assessment, a reminder that DoD assessors are an independent source of referrals to DOJ.
Contractors must also be mindful of retaliation risk. Section 3730(h) of the FCA separately prohibits discharging, demoting, harassing, or otherwise discriminating against an employee for lawful efforts to stop or report an FCA violation, and provides for reinstatement, double back pay, and special damages, including attorneys' fees. A retaliation claim can proceed even if the underlying fraud allegations fail. The Honeywell settlement expressly resolved the relator's FCA retaliation claim, and ILC paid separately to resolve its relator's claims outside the covered conduct, emphasizing that employment claims are now a routine part of these resolutions. Other whistleblower protection statutes apply to contractor employees, too. See, e.g., FAR Subpart 3.9 (implementing 41 U.S.C. § 4712); DFARS Subpart 203.9 (implementing 10 U.S.C. § 4701).
Conclusion
These settlements confirm that cybersecurity compliance remains a top enforcement priority, and the False Claims Act is often the government's tool of choice to enforce compliance. Highly incentivized whistleblowers and government assessors are actively surfacing violations. Contractors should review their compliance with contractual and NIST requirements (including a determination of which version of NIST SP 800-171 applies), confirm that their SSPs, POA&Ms, and SPRS scores reflect their actual security posture, and establish processes to investigate and resolve internal compliance concerns promptly and without reprisal. Venable's Investigations and White Collar Defense and Government Contracts teams have extensive experience helping contractors build compliance programs on the front end and navigating responses to whistleblower complaints, qui tam actions, and government investigations. Contact us for guidance on these issues and consider subscribing for future updates in this space.