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

Image Source: imsmartin

Image Source: imsmartin

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
Newest First  |  Oldest First  |  Threaded View
DevSecOps: The Answer to the Cloud Security Skills Gap
Lamont Orange, Chief Information Security Officer at Netskope,  11/15/2019
Attackers' Costs Increasing as Businesses Focus on Security
Robert Lemos, Contributing Writer,  11/15/2019
TPM-Fail: What It Means & What to Do About It
Ari Singer, CTO at TrustPhi,  11/19/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: -when I told you that our cyber-defense was from another age
Current Issue
Navigating the Deluge of Security Data
In this Tech Digest, Dark Reading shares the experiences of some top security practitioners as they navigate volumes of security data. We examine some examples of how enterprises can cull this data to find the clues they need.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-18858
PUBLISHED: 2019-11-20
CODESYS 3 web server before 3.5.15.20, as distributed with CODESYS Control runtime systems, has a Buffer Overflow.
CVE-2019-3466
PUBLISHED: 2019-11-20
The pg_ctlcluster script in postgresql-common in versions prior to 210 didn't drop privileges when creating socket/statistics temporary directories, which could result in local privilege escalation.
CVE-2010-4659
PUBLISHED: 2019-11-20
Cross-site scripting (XSS) vulnerability in statusnet through 2010 in error message contents.
CVE-2019-4530
PUBLISHED: 2019-11-20
IBM Maximo Asset Management 7.6, 7.6.1, and 7.6.1.1 could allow an authenticated user to delete a record that they should not normally be able to. IBM X-Force ID: 165586.
CVE-2019-4561
PUBLISHED: 2019-11-20
IBM Security Identity Manager 6.0.0 could allow a remote attacker to execute arbitrary code on the system, caused by the deserialization of untrusted data. By persuading a victim to visit a specially crafted Web site, an attacker could exploit this vulnerability to execute arbitrary code on the syst...