FirstAlerts
Regulators & Courts

Honeywell Aerospace to Pay $2,042,518 to Settle Cybersecurity Claims

The settlement resolves allegations that a business unit failed to meet cybersecurity requirements on a Department of Defense contract.

2 reports on this incident · first at Sep 8, 2026, 2:17 p.m. ET

By AI ReporterWritten Sep 8, 2026, 2:24 p.m. ET
Honeywell Aerospace Inc. has agreed to pay $2,042,518 to resolve allegations that a business unit submitted claims for payment while failing to comply with cybersecurity requirements specified in NIST SP 800-171, according to the National Law Review. The , reported by the National Law Review, resolves a case brought by the Department of Justice in the U.S. District Court for the Western District of North Carolina ( Action No. 3:22-cv-129). The allegations cover conduct from April 2020 through December 2023. The company to the without admitting liability, the National Law Review reported. The specific allocation of the payment—whether it constitutes penalties, disgorgement, or redress—was not detailed in the report.

Earlier reports

  1. Sep 8, 2026, 2:17 p.m. ETFirst report

    Honeywell Aerospace to Pay $2 Million to Settle Cybersecurity Claims

    Honeywell Aerospace Inc. has agreed to pay $2,042,518 to resolve allegations that a business unit failed to comply with cybersecurity requirements on a Department of Defense contract, according to the National Law Review.

    The civil settlement, filed in the U.S. District Court for the Western District of North Carolina (Civil Action No. 3:22-cv-129), stems from allegations that from April 2020 through December 2023, the unit submitted claims for payment while not meeting cybersecurity specifications in NIST SP 800-171 for one of its networks. The case was brought by the Department of Justice.

    The company consented to the settlement, which resolves the allegations without a finding of liability.

Was this report accurate and useful?

Sources

Revision history

  1. Version 18 Sept 2026, 18:17current

    First published.

  2. Version 18 Sept 2026, 18:24current

    First published.

How we work

This site models an investigative reporter rather than a wire desk. The aim is the most complete, accurate and timely account we can assemble — all three, not a trade between them. Reports go out within minutes of the coverage they are built from, carrying context a newsroom would otherwise need a day and a records request to gather: what has happened at this place before, what the operator’s record is, which aircraft it actually was.

Reports are built from primary sources — accident and court records, official registries, weather observations, agency statements — and from reputable news organisations, each named where their reporting is used. Facts are extracted before anything is written, and every one must be supported by a quotation found in the source itself; the model that writes the report is given only those verified facts and never sees the article, so it cannot introduce a detail no source stated.

Where sources disagree we publish the disagreement, attributed, rather than picking a figure. Where a fact comes from a record rather than a reporter, we say so, and the language matches: an instrument reading is never described as something anyone confirmed. Some things are deliberately withheld — a suspect is not named until an agency names them on the record, victims until families or officials release them — and corrections appear as visible revisions, never as silent edits.

None of that makes a report true. A quotation check proves a source said something, not that it was right, and an automated system can be confidently wrong in ways the checks do not catch. If something here is wrong, the feedback above is how it gets found. The full methodology, including what we refuse to publish.