DataBreaches.Net

Menu
  • About
  • Breach Notification Laws
  • Privacy Policy
  • Transparency Report
Menu

Privilege Under Fire: Protecting Forensic Reports in the Wake of a Data Breach

Posted on May 21, 2025 by Dissent

Alexander Koskey, Madison McMahan, and Matthew White of Baker Donelson write:

A recent decision from the Federal Court of Australia in McClure v.  Medibank Private Limited [2025] FCA 167 underscores just how easily privilege can be lost. While McClure was decided under Australian law, the court’s reasoning closely aligns with a series of U.S. cases that have steadily narrowed protections for forensic reports in recent years. The key takeaway from these decisions is clear: privilege doesn’t only depend on who commissioned the report – it hinges on why it was created, how it was used, and who saw it.

Forensic reports often reveal detailed technical findings and expose security vulnerabilities that could significantly influence the outcome of litigation. Protecting these reports under the attorney-client privilege or the work product doctrine isn’t just a best practice – it’s a critical step in managing legal risk after a breach. Left unprotected, a forensic report can serve as a roadmap for plaintiffs, outlining the very vulnerabilities and response gaps they’ll use to build their claims.

McClure v. Medibank

The case stems from a 2022 data breach that impacted millions of Medibank customers and prompted a class action lawsuit alleging failures in cybersecurity safeguards. As part of discovery, plaintiffs sought a range of materials prepared in response to the breach, including forensic reports from Deloitte and other third-party vendors. Medibank resisted production, claiming that the reports were protected by privilege because they were created to support litigation strategy and enable legal advice.

The court agreed in part, upholding privilege over reports commissioned by counsel for threat actor negotiations and legal strategy. However, it ordered the production of three Deloitte reports, finding that they were created for multiple purposes and that obtaining legal advice was not the dominant one.

The court’s analysis focused on several critical facts:

  • Public positioning: In press releases and ASX announcements, Medibank described Deloitte’s role as being related to customer protection, governance, and transparency – not legal advice.
  • Regulatory messaging: Medibank told regulators that Deloitte was engaged to avoid a separate investigation by the Australian Prudential Regulation Authority (APRA), further supporting a nonlegal purpose.
  • Board reporting: Deloitte reported directly to Medibank’s board and executive team, not to external counsel, which suggested the work was for operational oversight rather than legal strategy.
  • Public Statements: Medibank publicly referenced and implemented Deloitte’s recommendations, which the court said undercut any claim of confidentiality and waived privilege.

Ultimately, the court concluded that while legal advice was a purpose of the reports, it was not the dominant one required to sustain privilege. An appeal of this decision is likely.

Read more at JDSupra.

No related posts.

Category: Breach Incidents

Post navigation

← Hacker who breached communications app used by Trump aide stole data from across US government
Researchers Scrape 2 Billion Discord Messages and Publish Them Online →

Now more than ever

"Stand with Ukraine:" above raised hands. The illustration is in blue and yellow, the colors of Ukraine's flag.

Search

Browse by Categories

Recent Posts

  • National Health Care Fraud Takedown Results in 324 Defendants Charged in Connection with Over $14.6 Billion in Alleged Fraud
  • Swiss Health Foundation Radix Hit by Cyberattack Affecting Federal Data
  • Russian hackers get 7 and 5 years in prison for large-scale cyber attacks with ransomware, over 60 million euros in bitcoins seized
  • Bolton Walk-In Clinic patient data leak locked down (finally!)
  • 50 Customers of French Bank Hit by Insider SIM Swap Scam
  • Ontario health agency atHome ordered to inform 200,000 patients of March data breach
  • Fact-Checking Claims By Cybernews: The 16 Billion Record Data Breach That Wasn’t
  • Horizon Healthcare RCM discloses ransomware attack in December
  • Disgruntled IT Worker Jailed for Cyber Attack, Huddersfield
  • Hacker helped kill FBI sources, witnesses in El Chapo case, according to watchdog report

No, You Can’t Buy a Post or an Interview

This site does not accept sponsored posts or link-back arrangements. Inquiries about either are ignored.

And despite what some trolls may try to claim: DataBreaches has never accepted even one dime to interview or report on anyone. Nor will DataBreaches ever pay anyone for data or to interview them.

Want to Get Our RSS Feed?

Grab it here:

https://databreaches.net/feed/

RSS Recent Posts on PogoWasRight.org

  • The Trump administration is building a national citizenship data system
  • Supreme Court Decision on Age Verification Tramples Free Speech and Undermines Privacy
  • New Jersey Issues Draft Privacy Regulations: The New
  • Hacker helped kill FBI sources, witnesses in El Chapo case, according to watchdog report
  • Germany Wants Apple, Google to Remove DeepSeek From Their App Stores
  • Supreme Court upholds Texas law requiring age verification on porn sites
  • Justices nix Medicaid ‘right’ to choose doctor, defunding Planned Parenthood in South Carolina

Have a News Tip?

Email: Tips[at]DataBreaches.net

Signal: +1 516-776-7756

Contact Me

Email: info[at]databreaches.net

Mastodon: Infosec.Exchange/@PogoWasRight

Signal: +1 516-776-7756

DMCA Concern: dmca[at]databreaches.net
© 2009 – 2025 DataBreaches.net and DataBreaches LLC. All rights reserved.