DataBreaches.Net

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

The Bank of England reminds us why it is important to check recipients before sending an email

Posted on May 25, 2015 by Dissent

Steve Myers gives us a winner for email gaffe of the month:

The Bank of England has been the latest victim of the internet.

Well, no. They’re not a victim of the internet as much as they are a victim of their own human error, but read on….

They have taught all of us a very important lesson as far as email etiquette is concerned. Whenever you are sending an email, you need to ensure you are sending it to the correct person. And don’t forget to double check just before hitting send.

This issue was created when the bank accidentally sent an email to the Guardian which contained vital information on a project wherein the financial implications of the U.K. parting from the European Union were discussed. This email was supposed to be sent out to 4 senior executives from the bank and eve(n) contained plans on how the bank was going to avoid any questions from the press.

So basically, if you are thinking up of something and want to keep the media out of it then you need to ensure you don’t send them an email about it.

Read more on Benchmark Reporter.


Related:

  • Landmark civil penalty of AU$5.8 million issued under Australia’s Privacy Act
  • How many courts have had sealed and sensitive files exposed by one vendor's error?
  • Legal Aid Agency chief admits difficulties understanding impact of cyberattack
  • Revealed: Afghan data breach after MoD official left laptop open on train
  • Canada says hacktivists breached water and energy facilities
  • UK: FCA fines former employee of Virgin Media O2 for data protection breach
Category: ExposureFinancial SectorNon-U.S.

Post navigation

← North Dakota amends data breach notification law
CareFirst breach demonstrates how assumptions hurt healthcare →

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

  • Short-term renewal of cyber information sharing law appears in bill to end shutdown
  • Yanluowang ransomware IAB pleads guilty
  • Lawsuit Alleges Ex-Intel Employee Hid 18,000 Sensitive Documents Prior to Leaving the Company
  • HIPAA, but for non-Covered Entities?
  • Manassas City Public Schools close on Monday due to cyberattack
  • San Joaquin County Superior Court concludes sensitive info leaked in data breach
  • NCCIA arrests man over massive data breach involving millions of Pakistanis
  • Defense Contractors Are Silencing Their Cybersecurity Watchdogs
  • Fourth Circuit Weighs in on Standing in Data Breach Class Actions
  • ALT5 Sigma sues former consultant over alleged data breach

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

  • 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
  • Who’s watching the watchers? This Mozilla fellow, and her Surveillance Watch map
  • EPIC Publishes New Whitepaper Detailing Privacy Risks of Government Data Mining Programs
  • Modern cars are spying on you. Here’s what you can do about it.

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.