Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

News

5/13/2016
10:55 AM
Sean Martin
Sean Martin
Slideshows
Connect Directly
LinkedIn
RSS
E-Mail
50%
50%

Happy Blame Someone Else Day

In cybersecurity, each day a company experiences a data breach, it appears to be #BlameSomeoneElseDay
Previous
1 of 14
Next

Today is an unusual day, for sure. It’s most likely a holiday most of us have missed. Even though it takes place on Friday the 13th, it’s not about being superstitious. It’s actually about blaming someone else.

So, here’s to you—Happy Blame Somebody Else Day!

What is this holiday, you ask? National Blame Someone Else Day is an “unofficial” national holiday always celebrated on the first Friday the 13th of the year. It was invented due to an alarm clock failing to go off, hence creating a domino effect of bad luck events throughout the day.

According to the National Day Calendar, the way to celebrate is self-explanatory in the name, and not much more needs to be said. If you don’t want to blame someone, you can choose to place the blame on something.

Speaking of blame, “accountability in security” is an ongoing issue. It seems that internal teams at organizations are always trying to point the finger elsewhere if something bad occurs—especially if the organization is a victim of an attack. This brings to mind the old adage “When You Point a Finger at Someone, There Are Three More Pointing Back at You” —Unknown.

The actual visual would be a room full of people pointing at each other, no one accepting responsibility.

In cybersecurity, the day a company experiences a data breach appears to be their very own #BlameSomeoneElseDay:

  • Blame Poor or Missing Risk Assessments
  • Blame a Lack of Funding
  • Blame the Tools
  • Blame Bad Behavior
  • Blame a Lack of Communication
  • Blame a Poor Reporting Structure
  • Blame the Lack of Awareness
  • Blame the Bad Decision(-Maker)
  • Blame the Short-Term Fix
  • Blame a Lack of Metrics
  • Blame the Third-Party Vendor
  • Blame Everybody Else
  • Blame a Magician

The team at imsmartin would like to thank the experts from the following companies that helped to make this “lucky 13” slideshow possible: Armor, Citrix, Palo Alto Networks, Rook Security, and WhiteHat Security.

Each expert shared their thoughts on where blame occurs and why blaming someone or something else is a bad idea …. even if it happens to be on Blame Someone Else Day.

In case you were wondering, the official hashtag for this holiday is #BlameSomeoneElseDay.

 

Sean Martin is an information security veteran of nearly 25 years and a four-term CISSP with articles published globally covering security management, cloud computing, enterprise mobility, governance, risk, and compliance—with a focus on specialized industries such as ... View Full Bio

Previous
1 of 14
Next
Comment  | 
Print  | 
More Insights
Comments
Threaded  |  Newest First  |  Oldest First
COVID-19: Latest Security News & Commentary
Dark Reading Staff 8/10/2020
Pen Testers Who Got Arrested Doing Their Jobs Tell All
Kelly Jackson Higgins, Executive Editor at Dark Reading,  8/5/2020
Researcher Finds New Office Macro Attacks for MacOS
Curtis Franklin Jr., Senior Editor at Dark Reading,  8/7/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Special Report: Computing's New Normal, a Dark Reading Perspective
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
The Changing Face of Threat Intelligence
The Changing Face of Threat Intelligence
This special report takes a look at how enterprises are using threat intelligence, as well as emerging best practices for integrating threat intel into security operations and incident response. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-8913
PUBLISHED: 2020-08-12
A local, arbitrary code execution vulnerability exists in the SplitCompat.install endpoint in Android's Play Core Library versions prior to 1.7.2. A malicious attacker could create an apk which targets a specific application, and if a victim were to install this apk, the attacker could perform a dir...
CVE-2020-7029
PUBLISHED: 2020-08-11
A Cross-Site Request Forgery (CSRF) vulnerability was discovered in the System Management Interface Web component of Avaya Aura Communication Manager and Avaya Aura Messaging. This vulnerability could allow an unauthenticated remote attacker to perform Web administration actions with the privileged ...
CVE-2020-17489
PUBLISHED: 2020-08-11
An issue was discovered in certain configurations of GNOME gnome-shell through 3.36.4. When logging out of an account, the password box from the login dialog reappears with the password still visible. If the user had decided to have the password shown in cleartext at login time, it is then visible f...
CVE-2020-17495
PUBLISHED: 2020-08-11
django-celery-results through 1.2.1 stores task results in the database. Among the data it stores are the variables passed into the tasks. The variables may contain sensitive cleartext information that does not belong unencrypted in the database.
CVE-2020-0260
PUBLISHED: 2020-08-11
There is a possible out of bounds read due to an incorrect bounds check.Product: AndroidVersions: Android SoCAndroid ID: A-152225183