The ILC Dover False Claims Act Cybersecurity Settlement Lists Five Alleged Failures, Starting With a Missing Plan
In the ILC Dover False Claims Act cybersecurity settlement, ILC Dover LP and ILC Astrospace LLC agreed to pay $13M. That is a settlement figure, not a contract value. It resolves False Claims Act allegations about cybersecurity on seven Army, Missile Defense Agency (MDA) and NASA contracts. DOJ announced it on Nov. 3, 2026. The United States alleges the companies sought payment from January 2018 to October 2024 while lacking, for stated periods, a system security plan, a current assessment posted for DoD, and a check that their cloud provider met FedRAMP Moderate equivalency. The claims are allegations only, and the companies admit no liability.
The revenue stake is existing-contract liability and DoD award-eligibility risk, limited to what the documents support. The United States framed ILC’s payment requests during the period as false for five stated reasons. If you hold a contract with DFARS 252.204-7012 or NASA’s clause 1852.204-76, that is the theory your own invoices could face. A missing or stale assessment also makes you ineligible to be considered for new DoD awards under DFARS 252.204-7019 and 252.204-7020, as the agreement’s recitals describe. No recompete date is tied to any named contract. This is currently an enforcement and requirements signal, not yet a validated federal contracting opportunity. The near-term commercial signal is compliance-services demand from firms that hold controlled unclassified information (CUI), not government spend.
| Field | Answer |
|---|---|
| Signal | $13M settlement of False Claims Act allegations on seven Army, MDA and NASA contracts; conduct period Jan. 1, 2018 to Oct. 30, 2024; no admission of liability |
| BD implication | Existing-contract liability and DoD award eligibility, not new business: a missing plan or stale assessment puts invoices and future eligibility at risk |
| Customer | Army, MDA and NASA, named as the payers of the allegedly false claims |
| Buyer | None identified; no agency is buying anything because of this settlement |
| Funding | Not applicable; $13M is a settlement amount, the contract values are not stated, and subcontract values do not appear as prime actions under ILC’s name |
| Vehicle / path | None identified; the agreement lists NASA contract NNJ16HD45D as received by ILC and, per its recital, subcontracts from prime contractors under the other six |
| Incumbents / ecosystem | ILC held NNJ16HD45D and, per the recital, subcontracts under the other six; the prime contractors are unnamed, and the agreement names no competitor |
| Access strategy | Protective: fix plan, assessment, and cloud evidence on contracts already held |
| Timing | ILC’s payment is due within 14 days of the agreement’s effective date; no recompete date is known |
| Confidence | High on the agreement’s terms; Low on contract values |
| Pursuit posture | DEFEND |
| Upgrade triggers | An agency suspension or debarment action tied to this conduct |
| Downgrade triggers | Contract values showing the exposure is small next to the $13M |
- ILC pays $13M plus 4.375% annual interest running from Sept. 24, 2026. Half, $6.5M, is designated restitution.
- The relator, ILC’s former Director of Cybersecurity, receives $2.35M from that recovery. ILC separately pays $288,000 in relator’s legal fees and $180,000 for claims outside the covered conduct.
- The release does not cover criminal liability, any agency’s suspension and debarment rights, or liability of individuals.
- ILC may not charge the payment or its negotiation costs to government contracts. It must repay any already billed within 90 days of the effective date.
Five Alleged Failures Cover the Cloud, the Plan, the Controls, the Fix List, and the Posting
The covered conduct in the ILC Dover False Claims Act cybersecurity settlement lists five failures. Each ties to a requirement that binds defense industrial base (DIB) and NASA contractors today, whatever the CMMC phase timing.
| Alleged failure | Period | Requirement cited |
|---|---|---|
| External cloud provider stored engineering, manufacturing and quality documents, including covered defense information (CDI), with no check for FedRAMP Moderate equivalency | Feb. 1, 2023 to Oct. 30, 2024 | DFARS 252.204-7012(b)(2)(ii)(D) and (c)-(g) |
| No system security plan (SSP) for each covered system | Jan. 1, 2018 to Mar. 10, 2022, and Sept. 1, 2022 to Oct. 30, 2024 | NIST SP 800-171 control 3.12.4; NASA clause 1852.204-76 |
| Not all NIST SP 800-171 and 800-53 controls implemented | Jan. 1, 2018 to Oct. 30, 2024 | NIST SP 800-171 and 800-53 |
| No plans of action and milestones (POA&Ms) | Jan. 1, 2018 to May 13, 2019, and Jan. 1, 2022 to Sept. 11, 2024 | NIST SP 800-171 and 800-53 |
| No current, plan-based assessment posted for DoD | Nov. 30, 2020 to Oct. 30, 2024 | DFARS 252.204-7019 and 252.204-7020 |
The no-plan allegation leaves out roughly six months, from Mar. 11 to Aug. 31, 2022. If you handle CUI, ask whether you hold a written plan for each system, whether it names the system boundary, and whether anyone updates it.
Without a Plan, the DoD Method Allows No Compliant Assessment
DFARS 252.204-7019 and 252.204-7020 require a current assessment for each covered system, no more than three years old. It must be posted in the Supplier Performance Risk System (SPRS) so DoD can see it. Scores run from -203 to 110. A self-assessed score must rest on the contractor’s review of its own system security plan and follow the DoD Assessment Methodology. As the agreement frames the DoD method, no assessment can be completed without a plan. The result is noncompliance with DFARS 252.204-7012.
The fifth allegation ties to posting. ILC Astrospace posted no assessment. ILC Dover posted none that was current, plan-based, and methodology-compliant. The United States says that made ILC ineligible to be considered for DoD contracts and subcontracts from Nov. 30, 2020 to Oct. 30, 2024, nearly four years. Ineligibility to be considered is an award condition, not a debarment. The agreement reserves each agency’s debarment rights separately.
A score you post must rest on a plan you hold. Subcontractors have one more check. Per the agreement’s recital, six of the seven named contracts were subcontracts under primes’ contracts. Ask your prime which clauses flowed down to you, and when.
Two Assessor Reports Stand Behind the Case, and Neither Became a Posted Score
The agreement says ILC’s third-party cybersecurity consultants assessed its systems in November 2018 and September 2024. They told ILC it had not implemented dozens of controls. Under the DoD method, those gaps would have produced scores of -59 and 21 if an SSP had existed. These are hypothetical scores from the agreement, not posted assessments. The United States says ILC reported neither to DoD.
The relator, ILC’s former Director of Cybersecurity, filed the qui tam suit on Jan. 17, 2025, about 21 months before DOJ announced the settlement.
Handle an assessor’s report in this order:
- Log the report’s date, scope, and every gap it lists.
- Compare its result with the assessment you have posted for DoD.
- Decide in writing, for each gap, whether to fix it, add it to a plan of action, or dispute the finding.
- Update your posted assessment if the report shows it is no longer accurate.
- Keep the decision record where your security staff and counsel can both reach it.
I would pull assessor reports first. The agreement lists ILC’s silence on two of them as part of the covered conduct. A managed service provider (MSP/MSSP) or governance, risk and compliance (GRC) vendor that produces scores for clients writes the client’s assessment record.
The Cloud Provider Allegation Rests on a Rule About Equivalency, Not a Breach
A DoD contractor that uses a cloud provider for covered defense information must “require and ensure” that the provider meets security requirements equivalent to the FedRAMP Moderate baseline. The same clause also reaches the provider on incident reporting, malware, media preservation, forensic access, and damage assessment. FedRAMP, the Federal Risk and Authorization Management Program, is the government’s cloud authorization program.
The allegation says ILC used an external provider for engineering, manufacturing, and quality documents for 21 months without requiring and ensuring that equivalence. The provider is unnamed, and the agreement alleges no breach, stolen file, or incident. I would call this a paperwork case: the alleged exposure came from the missing equivalency check.
- Name every external service that holds CUI, including email, file sharing, and quality-management tools.
- For each, hold the provider’s FedRAMP Moderate authorization or equivalence evidence, not a sales statement.
- Confirm each provider accepts the incident-reporting and forensic-access terms of the clause.
- Flow the same terms to any subcontractor that touches the data.
Competitive Landscape: No Rival Bidders, Three Groups Around the Same Controls
The agreement names no competitors for the seven contracts, and the settlement creates no solicitation. Three groups sit around the same controls:
- Other CUI-holding suppliers under the same clauses, who face the same exposure theory.
- MSPs, MSSPs, and GRC vendors, which sell the plans, assessments, and monitoring the covered conduct says were missing.
- Cloud and email providers, which must supply equivalence evidence to their defense customers.
This is contractor-internal compliance spending and private compliance-services demand. I would not size either as federal market. Army, MDA, and NASA appear in the agreement as the customers allegedly harmed, not as buyers. Suppliers should run the checklist below. Vendors should expect requests for equivalence evidence.
What Each Reader Does Before the Next Invoice
Check your own records against the five allegations, by segment:
- Small business DIB subcontractors: confirm in writing that your prime flowed down DFARS 252.204-7012. Hold an SSP for each system before you post or update an assessment.
- Mid-size suppliers with outside assessors: list every assessor report, compare each score with your posted assessment, and record the decision on every gap.
- Corporate acquirers and investors: the release extends to ILC’s current and former parents and successors. Treat a target with no SSP or no current assessment as carrying pre-closing exposure, and price it in diligence.
- MSP, MSSP, and GRC vendors: hold FedRAMP Moderate equivalence evidence for any service that stores client CUI.
- NASA contractors: confirm your IT security plan under clause 1852.204-76 exists and names the NIST controls your contract requires.
If you hold one of these contracts, I would treat this as DEFEND. Close the plan, assessment, and cloud-evidence gaps before the next invoice. The United States framed the claims as payment requests submitted during the period. Watch for any suspension or debarment action tied to this conduct. The release leaves those rights with each agency. If your contracts carry neither clause, drop this to IGNORE FOR NOW.
FAQ
What did ILC Dover allegedly do wrong, and what did it pay?
The United States alleges five failures between 2018 and 2024. They are a cloud provider with no equivalency check, no system security plan for most of the period, unimplemented controls, no plans of action, and no current assessment posted for DoD. ILC pays $13M plus interest, with $6.5M designated restitution.
Why does a missing system security plan make a score impossible?
The DoD Assessment Methodology scores a system against its plan. No plan means no assessment can be completed. The agreement says that outcome is itself noncompliance with DFARS 252.204-7012.
Does a cybersecurity False Claims Act case need a breach?
No. The agreement alleges no breach, stolen data, or incident. It alleges false claims for payment while requirements went unmet.
If an assessor tells me controls are missing, must I report the score?
The agreement lists ILC’s silence about two assessor scores as part of the covered conduct. It does not say every assessor report must be reported. Keep your posted assessment consistent with your latest assessor result. Record a decision on every gap.
Which agency’s rules apply, DoD’s or NASA’s?
Both appear. The agreement cites DoD’s DFARS clauses and NASA’s clause 1852.204-76 without assigning them to specific contracts. The NASA clause requires an IT security plan and, in some NASA contracts, NIST SP 800-53 controls.
Can the government still act against ILC beyond this payment?
Yes. The agreement reserves criminal liability, every agency’s suspension and debarment rights, and liability of individuals. The payment releases civil and administrative monetary claims for the covered conduct only.

