DataBreaches.Net

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

Wow: Boar’s Head provides a master class in incident response and transparency

Posted on September 14, 2024September 14, 2024 by Dissent

How often have you seen DataBreaches heap praise on an entity for its incident response or transparency? Not too often, right? But DataBreaches is super-impressed by how Boar’s Head has responded to a food safety incident. No, this wasn’t any data security breach or privacy data breach, but it was an incident that had harmed the health of some of consumers, could have harmed more, and definitely could have significantly harmed consumer trust and their reputation. But they handled it all magnificently.

Seriously — I do not have enough words of praise for their handling of a situation. They responded quickly, they responded prudently with the best interest of consumers in mind, and they responded transparently — admitting publicly to their problems. Here is just a portion of their recall notice:

First and foremost, our investigation has identified the root cause of the contamination as a specific production process that only existed at the Jarratt facility and was used only for liverwurst. With this discovery, we have decided to permanently discontinue liverwurst.

In response to the inspection records and noncompliance reports at the Jarratt plant, we will not make excuses. In the spirit of complete transparency, we are sharing with you the July 31, 2024 USDA Notice of Suspension received by our Jarratt facility here.

Given the seriousness of the outbreak, and the fact that it originated at Jarratt, we have made the difficult decision to indefinitely close this location, which has not been operational since late July 2024. It pains us to impact the livelihoods of hundreds of hard-working employees. We do not take lightly our responsibility as one of the area’s largest employers. But, under these circumstances, we feel that a plant closure is the most prudent course. We will work to assist each of our employees in the transition process.

This is a dark moment in our company’s history, but we intend to use this as an opportunity to enhance food safety programs not just for our company, but for the entire industry.

They then detail other changes and protections they have put into place.

If there’s a way to inspire more confidence in a product following a safety issue like listeria contamination, then Boar’s Head has achieved that with their response and their transparency. As a consumer, I have absolutely no hesitation in purchasing their products again.

Read their entire recall notice to see more examples of how they handled their response and transparency brilliantly.

Now let’s see more data breach victims stand up and be as responsive and transparent in responding to data breaches.

h/t, @Viss for making us aware of the company’s great response.

 


Related:

  • ModMed revealed they were victims of a cyberattack in July. Then some data showed up for sale.
  • Confidence in ransomware recovery is high but actual success rates remain low
  • Protected health information of 462,000 members of Blue Cross Blue Shield of Montana involved in Conduent data breach
  • Resource: NY DFS Issues New Cybersecurity Guidance to Address Risks Associated with the Use of Third-Party Service Providers
  • Bombay High Court Orders Department of Telecommunications to Block Medusa Accounts After Generali Insurance Data Breach
  • Cyber-Attack On Bectu’s Parent Union Sparks UK National Security Concerns
Category: Commentaries and AnalysesMiscellaneous

Post navigation

← Multiple attacks forces CISA to order agencies to upgrade or remove end-of-life Ivanti appliance
The US is Preparing Criminal Charges in Iran Hack Targeting Trump, AP Sources Say →

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

  • District of Massachusetts Allows Higher-Ed Student Data Breach Claims to Survive
  • End of the game for cybercrime infrastructure: 1025 servers taken down
  • Doctor Alliance Data Breach: 353GB of Patient Files Allegedly Compromised, Ransom Demanded
  • St. Thomas Brushed Off Red Flags Before Dark-Web Data Dump Rocks Houston
  • A Wiltshire police breach posed possible safety concerns for violent crime victims as well as prison officers
  • Amendment 13 is gamechanger on data security enforcement in Israel
  • Almost two years later, Alpha Omega Winery notifies those affected by a data breach.
  • Court of Appeal reaffirms MFSA liability in data leak case, orders regulator to shoulder costs
  • A jailed hacking kingpin reveals all about the gang that left a trail of destruction
  • Army gynecologist took secret videos of patients during intimate exams, lawsuit says

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

  • As shoplifting surges, British retailers roll out ‘invasive’ facial recognition tools
  • Data broker Kochava agrees to change business practices to settle lawsuit
  • Amendment 13 is gamechanger on data security enforcement in Israel
  • Changes in the Rules for Disclosure for Substance Use Disorder Treatment Records: 42 CFR Part 2: What Changed, Why It Matters, and How It Aligns with HIPAAs
  • Always watching: How ICE’s plan to monitor social media 24/7 threatens privacy and civic participation

Have a News Tip?

Email: Tips[at]DataBreaches.net

Signal: +1 516-776-7756

Contact Me

Email: info[at]databreaches.net
Security Issue: security[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.