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.

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
Creating an Effective Incident Response Plan
Security teams are realizing their organizations will experience a cyber incident at some point. An effective incident response plan that takes into account their specific requirements and has been tested is critical. This issue of Tech Insights also includes: -a look at the newly signed cyber-incident law, -how organizations can apply behavioral psychology to incident response, -and an overview of the Open Cybersecurity Schema Framework.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2022-43705
PUBLISHED: 2022-11-27
In Botan before 2.19.3, it is possible to forge OCSP responses due to a certificate verification error. This issue was introduced in Botan 1.11.34 (November 2016).
CVE-2022-45934
PUBLISHED: 2022-11-27
An issue was discovered in the Linux kernel through 6.0.10. l2cap_config_req in net/bluetooth/l2cap_core.c has an integer wraparound via L2CAP_CONF_REQ packets.
CVE-2022-45931
PUBLISHED: 2022-11-27
A SQL injection issue was discovered in AAA in OpenDaylight (ODL) before 0.16.5. The aaa-idm-store-h2/src/main/java/org/opendaylight/aaa/datastore/h2/UserStore.java deleteUser function is affected when the API interface /auth/v1/users/ is used.
CVE-2022-45932
PUBLISHED: 2022-11-27
A SQL injection issue was discovered in AAA in OpenDaylight (ODL) before 0.16.5. The aaa-idm-store-h2/src/main/java/org/opendaylight/aaa/datastore/h2/RoleStore.java deleteRole function is affected when the API interface /auth/v1/roles/ is used.
CVE-2022-45933
PUBLISHED: 2022-11-27
KubeView through 0.1.31 allows attackers to obtain control of a Kubernetes cluster because api/scrape/kube-system does not require authentication, and retrieves certificate files that can be used for authentication as kube-admin. NOTE: the vendor's position is that KubeView was a "fun side proj...