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.

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

  • McLaren provides written notice to 743,131 patients after ransomware attack in July 2024
  • A state forensics lab was leaking its files. Getting it locked down involved a number of people.
  • CoinMarketCap Hacked, Scrambles to Remove Malicious Wallet Verification Popup
  • Montana Attorney General launches investigation into Lee Enterprises data breach
  • AT&T gets preliminary approval for $177 million data breach settlement
  • Aflac notifies SEC of breach suspected to be work of Scattered Spider
  • Former JBLM soldier pleads guilty to attempting to share military secrets with China
  • No, the 16 billion credentials leak is not a new data breach — a wake-up call about fake news (Updated)
  • Tonga’s health system hit by cyberattack (1)
  • Russia Expert Falls Prey to Elite Hackers Disguised as US Officials

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 Markup caught 4 more states sharing personal health data with Big Tech
  • Privacy in the Big Sky State: Montana’s Consumer Privacy Law Gets Amended
  • UK Passes Data Use and Access Regulation Bill
  • Officials defend Liberal bill that would force hospitals, banks, hotels to hand over data
  • US Judge Invalidates Biden Rule Protecting Privacy for Abortions
  • DOJ’s Data Security Program: Key Compliance Considerations for Impacted Entities
  • 23andMe fined £2.31 million for failing to protect UK users’ genetic data

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.