Contents
Contents
In the Raytheon and Nightwing cybersecurity settlement, the companies agreed to pay $8.4 million over allegations of missing security controls on an internal development system used for defense work. The whistleblower’s complaint went inside the business, describing instructions to certify compliance, unrestricted administrator access and a network allegedly left out of acquisition records. For someone who knows what a contractor’s systems actually do, those are the decisions behind the compliance statement.
The Justice Department announced the civil settlement on May 1, 2025. Raytheon, its parent RTX and Nightwing agreed to resolve allegations concerning conduct from 2015 through 2021. RTX sold its Cybersecurity, Intelligence, and Services business in March 2024, and that business became part of Nightwing. The alleged conduct preceded Nightwing’s acquisition.
The government alleged that Raytheon and its then-subsidiary Raytheon Cyber Solutions failed to develop and implement a system security plan for an internal development system. It also alleged that they failed to implement other required cybersecurity controls. The system supported unclassified work, but the government said it developed, used or stored covered defense information and federal contract information during work on 29 Defense Department contracts and subcontracts.
The government’s case put the security promise on the internal development system itself. We look at what that environment handled and what the contractor told its customer about protecting it.
The whistleblower’s amended complaint alleged that Raytheon personnel sought contract language exempting the company from cybersecurity requirements implementing NIST 800-171 in early February 2020. According to the complaint, the Defense Department refused the requested waiver, and an employee was then directed to sign the contract and certify compliance anyway. The filing quotes an instruction to assert compliance:
Insert that our IT system is compliant
The instruction also told the employee not to take an exception. The complaint alleged that Raytheon certified its ability to meet cybersecurity requirements when executing each contract’s statement of work, despite knowing or having reason to know that its systems could not comply.
We see the absurdity in that alleged response: the customer refused the waiver, so the answer was to write that the system complied. Problem solved, on paper.
The complaint identifies the development environment as DarkNet and describes research that sometimes involved deliberately activating viruses or malicious code for analysis. The whistleblower alleged that the sensitive work required separation from other systems, devices and the internet. Yet employees allegedly connected DarkNet to the internet, external devices or personal drives, with few documented rules and poor adherence to those that existed.
The complaint alleged that all employees using DarkNet had administrator privileges and that their activities were not monitored. It described engineers using those privileges to take over another employee’s account and impersonate her as a prank. We would expect a defense development network to keep intruders out, yet the complaint described employees using it to impersonate each other for a laugh.
The whistleblower also alleged that DarkNet lacked antivirus software and continuous monitoring. In a separate incident described in the complaint, an employee copied proprietary data onto a personal flash drive to take to a customer, then lost the drive. To the whistleblower’s knowledge, the incident went unreported to the government.
The complaint quoted a company letter stating that, based on an initial review, the company believed its development environment was noncompliant with federal safeguarding requirements. The letter also projected deployment of a replacement environment in September 2020:
Based on the current projections, Darknet 2.0 is expected to be deployed in September 2020.
According to the whistleblower, the replacement did not come online until March 2021, and Raytheon did not tell the Defense Department about the delay. The complaint further alleged that some work never moved off the original network. A temporary compliant environment covered only some of the work, and employees allegedly received authorization to return to the old system for a defense project while working from home.
For an insider, the important comparison is between the promised transition and the work actually moved. A new network on the calendar says nothing about which one was still doing the government’s work. We connect the migration history and remaining projects to the assurance the customer received.
The complaint alleged that in June 2020 the whistleblower learned DarkNet had been removed from Raytheon’s merger and acquisition information and was operating off the books. The complaint said people inside the business believed the omission was deliberate, allowing continued use of a system known to be noncompliant on defense contracts. That allegation concerns Raytheon’s earlier internal records.
For someone involved in a transaction, the system inventory and the government work running on it belong together. We would compare what the acquisition review described with the environments actually used, the contract assurances and the unresolved security work.
The complaint alleged that internal resistance to required controls included concern that engineers would leave if Raytheon had to comply. It also alleged that responsibility for compliance went to someone who had deliberately evaded requirements to reduce engineers’ work. Those allegations put management’s response to technical information alongside the controls themselves.
The 2026 University of California, Davis Law Review article Pathways to Protection: An Organization-Centered Approach to Whistleblowing Law argues that organizations can treat information from whistleblowers as a way to improve operations and prevent problems. Its framework distinguishes doing the minimum required from using internal knowledge to anticipate and address problems. That is a useful lens for this case: the employee who knows which system remains in use can explain a gap that the compliance statement leaves invisible.
For a cybersecurity case, useful evidence connects the actual system to the contract promise and the government money. The Raytheon complaint supplies concrete examples: the instruction to certify, statements of work, user privileges, a promised replacement date and work allegedly left on the old network. Connecting the system to the right contract, statement of work and payment request makes the employee’s technical knowledge useful to a defense contractor whistleblower claim.
An engineer may know the work stayed on the old environment. A security employee may know which protections were missing, while someone in contracts may know what assurance went to the customer. We bring those views together with what management knew and what the company disclosed.
MORSECORP’s civil settlement included admissions about an assessment score left uncorrected. The company reported 104, later received a consultant’s assessment of minus 142, and admitted that it did not correct the reported score until after a government subpoena. That history shows why the assessment behind a submitted score matters alongside what management learned afterward.
In the Georgia Tech case, the government alleged that an assessment described a fictitious or virtual environment, alongside missing protections at the actual lab. In Penn State’s settlement, the allegations included false promised remediation dates and failure to pursue remediation plans. Each comparison turns on something an insider can identify: the system assessed, the result reported or the fix promised.
Aero Turbine and Gallant Capital Partners supply another useful comparison. In their cybersecurity settlement, the Justice Department credited written self-disclosures, cooperation and prompt remedial action.
A former Raytheon Director of Engineering brought the qui tam case resolved by the settlement. The government joined the case for settlement, and the announcement provided for a whistleblower share of $1.5 million. The technical leadership role matters here because the complaint connected engineering work with contract assurances and decisions inside the business.
A whistleblower case under the False Claims Act can pay 15% to 30% of what the government recovers. We help insiders turn what they know about a system into that kind of case.
If you saw a compliance assurance that did not match the network, the access or the work left behind during a migration, speak to one of our Whistleblower Experts about what you saw. We build the case with you and bring in cybersecurity whistleblower lawyers who understand defense contracts and technical evidence. You bring the knowledge of what happened inside; we bring the judgment and partnership to pursue it with you.