Cybersecurity Vulnerabilities: When Knowing Too Much Gets You Fired

August 27, 2026

by M&S Staff

Whistleblowing Matters: A Newsletter from Mehri & Skalet, PLLC – FindJustice.com

By: Richard Condit and Cleveland Lawrence III

When William Barlow became IBM’s Vice President of Threat Intelligence in 2017, he expected to protect one of the world’s most powerful technology companies from cyberattacks. Instead, he says he found that attacks were already well underway — and that IBM’s leadership knew but chose to say nothing.

According to a federal lawsuit unsealed this spring, an internal IBM investigation found 56,215 potential intrusions by Chinese government-linked hackers between 2013 and 2016 — but could not investigate further because IBM had kept no logs of who accessed its network or when. A subsequent internal investigation found that attackers had compromised nearly 400 accounts and almost 200 systems and servers across every IBM business unit in 18 countries, with hostile activity occurring on a nearly daily basis. A separate breach penetrated Truven Health Analytics, an IBM subsidiary that held a $7 billion federal Medicare and Medicaid contract — and on one occasion gave hackers real-time control over patient medication dosing in a neonatal intensive care unit.

Barlow says that when he raised alarms, senior IBM executives told him to “tone down” his reports and directed him to redact breach information from documents prepared for IBM’s internal cybersecurity council. One executive told him that then-CEO Virginia Rometty knew about the breaches but did not want to affect the company’s stock price. In May 2019, IBM’s Chief Information Security Officer warned Barlow that he “needed to be careful” and that his disclosures were “upsetting powerful people.” Barlow resigned that August, after it became clear IBM would not make required disclosures to government regulators. He also filed the whistleblower lawsuit, which alleged that IBM and AT&T — which jointly operated the compromised network — never disclosed the breaches to their federal government customers either, in violation of the False Claims Act.

Halfway around the world, another cybersecurity specialist was facing a remarkably similar problem. Marselles Jefferson was a fifteen-year veteran in defense contractor IT, who was hired by Science Applications International Corp. (SAIC) to support cybersecurity for the U.S. Air Force in Germany. Beginning in late 2021, Jefferson began reporting that SAIC was failing to properly scan military networks for vulnerabilities, that conflicts of interest had compromised the integrity of cybersecurity oversight, and that millions of dollars in government equipment was sitting unused. Each time Jefferson escalated his concerns — in emails, in meetings, and ultimately in a notice that he intended to file a complaint with the Inspector General — SAIC responded not with fixes, but with retaliation. Jefferson was demoted, stripped of teleworking rights he needed to care of his disabled spouse, placed on unpaid leave, removed from the contract, and fired soon after. After his termination, his employer told a security clearance investigator not to trust him — because he had “disagreed with the directives he was being given.” Jefferson also sued, alleging whistleblower retaliation under both the False Claims Act and the Defense Contractor Whistleblower Protection Act (10 U.S.C. § 4701) — which protects employees of government contractors from retaliation when they report waste, fraud, abuse, illegality, or gross mismanagement related to a DoD or NASA contract. His case is also currently pending in federal court; Mehri & Skalet represents him. On August 26, 2026, the Court denied SAIC’s motion for summary judgment on Jefferson’s Defense Contractor Whistleblower Protection Act claim. His case is proceeding to trial.

The False Claims Act: Sword and Shield

The False Claims Act (FCA) — which William Barlow invoked against IBM and AT&T — has become the federal government’s primary tool for holding tech companies accountable when they lie about cybersecurity compliance on government contracts. The law allows private individuals with non-public knowledge of fraud to file suit on the government’s behalf and collect a share of any recovery — up to 30%. On October 6, 2021, the Department of Justice formalized this approach by launching the Civil Cyber-Fraud Initiative, explicitly targeting contractors and grant recipients that misrepresent their cybersecurity practices. The Trump administration has not used that name, but it has continued — and accelerated — the same enforcement through the False Claims Act.

The Initiative has produced a steady stream of significant settlements:

  • In July 2022, Aerojet Rocketdyne paid $9 million to resolve allegations that it misrepresented its compliance with cybersecurity requirements in contracts with the Defense Department and NASA; the whistleblower received a $2.61 reward.
  • In March 2025, MORSECORP paid $4.6 million after its own Head of Security filed a qui tam complaint alleging the company’s senior executives knew of “chronic failures” to meet DFARS cybersecurity requirements but chose not to fix them; the whistleblower received $851,000.
  • In February 2025, Health Net Federal Services and Centene Corporation paid $11.25 million for falsely certifying cybersecurity compliance in their TRICARE contract, which provides health benefits to military families.
  • In May 2025, Raytheon, RTX, and Nightwing Group paid $8.4 million for failing to implement required security controls across 29 DoD contracts; a former Raytheon director of engineering received a $1.5 million whistleblower reward.

All told, in fiscal year 2025 DOJ recovered more than $52 million through nine cybersecurity-related FCA settlements — and five of the eight settlements that were specifically tied to the Civil Cyber-Fraud Initiative were qui tam cases brought by insiders. Last year, DOJ’s FCA recoveries exceeded $6.8 billion — the highest total in the statute’s history.

Importantly, the False Claims Act not only allows whistleblowers like William Barlow to sue on behalf of the government to recover stolen taxpayer money and protects whistleblowers from retaliation. Essentially, any effort to redress or to prevent an FCA violation is protected.

The SEC Enters the Picture

In recent years, the U.S. Security Exchange Commission (SEC) has increasingly treated cybersecurity failures not just as operational problems, but as investor disclosure violations, which has opened an additional avenue for whistleblowers. For workers at publicly traded tech companies, the SEC’s whistleblower program provides additional options and protections — that work alongside the government contractor statutes discussed above. Since many publicly-traded tech companies are also major federal contractors, their employees may have recourse under multiple regimes.

Notably, in October 2024 the SEC settled charges against four companies — Unisys, Avaya, Check Point Software Technologies, and Mimecast — for downplaying the impact of the SolarWinds cyberattack on their own systems. Each had discovered that hackers accessed its networks through the compromised SolarWinds software but disclosed only vague, hypothetical risks to investors. Unisys paid $4 million; Avaya paid $1 million; Check Point paid $995,000; and Mimecast paid $990,000 — approximately $7 million combined.

For tech workers at public companies, the SEC whistleblower program, like the False Claims Act, offers both financial rewards and legal protections: tips that lead to successful enforcement actions over $1 million can generate awards of 10 to 30 percent of sanctions collected, and employees are protected from retaliation for reporting to the SEC even if their tip does not result in an award.

Which Laws Protect Tech Workers Who Speak Up?

The legal landscape for cybersecurity whistleblowers has expanded considerably in recent years, though significant gaps remain. Employees of Department of Defense contractors are covered by the Defense Contractor Whistleblower Protection Act, mentioned above. Employees of civilian agency contractors — companies with federal contracts outside the DoD — have parallel protections under the Contractor Employee Whistleblower Protection Act (41 U.S.C. § 4712), enacted in 2013 and made permanent in 2016. Both statutes prohibit retaliation against employees who report gross mismanagement, waste, fraud, abuse of authority, or violations of law in connection with a federal contract, and both provide reinstatement, back pay, and compensatory damages. Many tech companies hold contracts with both DoD and civilian agencies, and their employees may be covered by both statutes simultaneously.

Employees of publicly traded companies can turn to the Sarbanes-Oxley Act (18 U.S.C. § 1514A), which protects workers who report conduct they reasonably believe constitutes securities fraud or related violations. Courts have read SOX’s anti-retaliation provisions broadly, prohibiting threats, harassment, and demotion — not just termination. The Dodd-Frank Act extends further protection and financial reward to anyone who provides original information to the SEC about violations of the securities laws, regardless of whether they are a company employee. Government contractors aware of cybersecurity fraud on federal contracts may also have standing as qui tam relators under the False Claims Act, with retaliation protections and a share of any recovery.

Beyond federal law, state whistleblower statutes offer an important and often underused layer of protection for tech workers.

The picture is less clear for workers at purely private companies, and especially for those raising concerns about artificial intelligence. In 2024, current and former employees of OpenAI and Google DeepMind publicly argued that AI workers lack adequate legal protection to report safety concerns, pointing to restrictive non-disclosure agreements (NDAs) as a barrier. Senator Chuck Grassley sent a letter to OpenAI raising concerns about its NDA practices, and legal scholars have called for AI-specific whistleblower legislation. Proposed federal legislation aims to close these gaps, but as of August 2026 no comprehensive AI-specific whistleblower statute has been enacted.

Although tech companies routinely require broad NDAs that appear to prohibit disclosure of any company information, whistleblower protections under federal and state law generally take precedence over NDAs when an employee reports to a regulator or to law enforcement. An NDA cannot lawfully prevent a worker from filing a complaint with the SEC, DOJ, or OSHA, or from reporting fraud on a federal contract. Workers who have signed NDAs should not assume silence is legally required — but should consult counsel before disclosing to understand exactly what their NDA covers and where the law overrides it.

What To Know Before Reporting Wrongdoing

Any tech worker contemplating a whistleblower disclosure should contact experienced attorneys to help them navigate the complex landscape before taking action. Attorneys can advise you about how to best document concerns in writing through official channels to create a contemporaneous record, preserve evidence lawfully. Cybersecurity workers face one additional risk worth naming: the surveillance tools and techniques they understand professionally may be deployed against them by an employer once they are perceived as a threat. Company devices, email systems, and access logs can be monitored, and internal reporting activity may be tracked in real time. Keeping consultations and disclosures off company systems is basic preparation.

This newsletter is for informational purposes and does not contain or constitute legal advice. Your facts and circumstances may differ from a subject referenced in this newsletter. Consult with an attorney with any questions or for legal advice on your specific circumstances. You should also be aware that the statute of limitations (the legally imposed deadline to bring a lawsuit) may severely limit the time remaining for you to file any potential claims you may have.