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.

Database Security
Authentication
Mobile
Privacy
Compliance
Careers and People
Identity & Access Management
Security Monitoring
Advanced Threats
Insider Threats
Vulnerability Management
Comments
Michaels Data Breach Response: 7 Facts
Oldest First  |  Newest First  |  Threaded View
Robert McDougal
Robert McDougal,
 User Rank: Ninja
4/22/2014 | 9:49:05 PM
Should Michaels have done more?
The article quotes Gartner researcher Avivah Litan stating that it is not fair to expect retailers to have expert forensic teams on call at all times.  While I agree with that statement, (forensic teams, if not part of the in house security personnel should be on retainer for incident response) I do think there is a minimum due diligence to which they should be held accountable.  Did Michael's have a CISO in place, security staff, IDS/IPS, vulnerability management, etc?  Did they follow secure coding practices?  Were risk assessments routinely performed on the POS systems?  These are the questions I would like to see answered.

 
Marilyn Cohodas
Marilyn Cohodas,
 User Rank: Strategist
4/23/2014 | 8:44:49 AM
Re: Should Michaels have done more?
Great questions. I hope the answers will be brought to light overtime & help provide a blueprint for the future.. We know from the Target breach that were both ommissions and commissions of best security practices  (See Be Careful Beating Up Target). But the retail industry can learn a lot from the post mortems. 
Drew Conry-Murray
Drew Conry-Murray,
 User Rank: Ninja
4/23/2014 | 10:39:37 AM
Re: Should Michaels have done more?
Presumably Michael's was required to meet PCI standards, which means regular vulnerability assessments were conducted and IDS/IPS systems were in place. But as the article notes, we'll get more bang for the buck by overhauling the payment card system itself rather than trying to get thousands and thousands of retailers to run rock-solid security programs.
Duane T
Duane T,
 User Rank: Apprentice
4/23/2014 | 12:01:44 PM
Irony of sharing
While the point made about sharing is valid, the article also states that the malware had never been seen before. Unfortunately, you can't share what you don't know.

On the other hand, there was little information on any lessons about how the undetected malware was found or identified. The follow up on that is that once the malware was found, was that information shared, and how widely is that information available to help other firms avoid a similar breach.

 


Edge-DRsplash-10-edge-articles
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Everything You Need to Know About DNS Attacks
It's important to understand DNS, potential attacks against it, and the tools and techniques required to defend DNS infrastructure. This report answers all the questions you were afraid to ask. Domain Name Service (DNS) is a critical part of any organization's digital infrastructure, but it's also one of the least understood. DNS is designed to be invisible to business professionals, IT stakeholders, and many security professionals, but DNS's threat surface is large and widely targeted. Attackers are causing a great deal of damage with an array of attacks such as denial of service, DNS cache poisoning, DNS hijackin, DNS tunneling, and DNS dangling. They are using DNS infrastructure to take control of inbound and outbound communications and preventing users from accessing the applications they are looking for. To stop attacks on DNS, security teams need to shore up the organization's security hygiene around DNS infrastructure, implement controls such as DNSSEC, and monitor DNS traffic
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2023-33196
PUBLISHED: 2023-05-26
Craft is a CMS for creating custom digital experiences. Cross site scripting (XSS) can be triggered by review volumes. This issue has been fixed in version 4.4.7.
CVE-2023-33185
PUBLISHED: 2023-05-26
Django-SES is a drop-in mail backend for Django. The django_ses library implements a mail backend for Django using AWS Simple Email Service. The library exports the `SESEventWebhookView class` intended to receive signed requests from AWS to handle email bounces, subscriptions, etc. These requests ar...
CVE-2023-33187
PUBLISHED: 2023-05-26
Highlight is an open source, full-stack monitoring platform. Highlight may record passwords on customer deployments when a password html input is switched to `type="text"` via a javascript "Show Password" button. This differs from the expected behavior which always obfuscates `ty...
CVE-2023-33194
PUBLISHED: 2023-05-26
Craft is a CMS for creating custom digital experiences on the web.The platform does not filter input and encode output in Quick Post validation error message, which can deliver an XSS payload. Old CVE fixed the XSS in label HTML but didn’t fix it when clicking save. This issue was...
CVE-2023-2879
PUBLISHED: 2023-05-26
GDSDB infinite loop in Wireshark 4.0.0 to 4.0.5 and 3.6.0 to 3.6.13 allows denial of service via packet injection or crafted capture file