If you’re like us you have a hard time remembering the point of sale (PoS) breaches that have occurred over the years. In an effort to simplify past public breaches, we have created a timeline that describes 59 distinct PoS-related breaches where the following were (or are believed to be) true:
The incidents were found through a combination of “intense Googling”, referencing various news outlets, such as KrebsOnSecurity and ThreatPost, and several breach databases including the VCDB VERIS Community Database and the OSF DataLossDB.
Looking at the data provided some interesting talking points.
For example, based on our research, the Fudruckers breach in 2002 may have been the first reported PoS malware-related breach. Also, out of all of the breaches we observed, the only businesses that went out of business as a direct result of a PoS malware infection were two Spicy Pickle restaurants in Kalamazoo, MI. (Readers, please correct us if we’re wrong…)
You can view the full timeline by clicking on the timeline image below:
This is not the complete list of PoS breaches to date. According to the 2014 Verizon Data Breach Investigations Report (DBIR), 198 total incidents were reported related to PoS intrusions. Unfortunately for us, Verizon doesn’t name victims in the report nor do they divulge client-specific information on any breaches handled by any of the DBIR contributors.
The DBIR team did, however, report that RAM scrapers have passed keyloggers as the most common malware associated with POS intrusions and that compromises take seconds or minutes (87 percent combined) to happen in POS attacks – with exfiltration happening within minutes of a compromise in 88 percent of breaches. Attackers, meanwhile, have free reign for weeks, in 85 percent of breaches before they are discovered.
Verizon also said that “Regardless of how large the victim organization was or which methods were used to steal payment card information, there is another commonality shared in 99% of the cases: someone else told the victim they had suffered a breach.”
We plan on treating this breach timeline as a living document. As such, if you have any additions or corrections, please let us know ASAP and we’ll update the data. Also, if you think a breach-to-variant comparison for the malware employed in each case would be of value, please drop us a line.
What should enterprises do when faced with ransomware? The answer is, it depends.
As a follow up to our previous post, the agenda for the S4 Incident Responder and Researcher Conference, being held at OpenDNS HQ on September 18th, 2014, is now finalized.
|8:00||Breakfast and coffee (first talk 9AM SHARP!)||n/a|
|9:00 – 11:00||Malware Analysis for Incident Responders||Lenny Zeltser, The SANS Institute|
|11:00 – 13:00||Using Bro*||Anthony Kasza, OpenDNS|
|13:00 – 15:00||Using Moloch||Scott Floyd, Salesforce|
|15:00 – 17:00||IR 2.0 : Elastic Search, Logstash, Kibana (ELK)||The folks at Elastic Search|
Note: Lunch will be provided and available during the Bro session.
|17:00 – 17:20||Measuring the IQ of your Threat Intelligence Feeds||Alex Pinto, MLSec Project|
|17:30 – 17:50||FastResponder: New Open Source weapon to detect and understand a large scale compromise||Sébastien Larinier, Guillaume Arcas, and Olivier Zheng, Sekoia|
|18:00 – 18:20||Threat intelligence for Incident Responders||Sam Liles, Cyberforensics Laboratory at Purdue|
|18:30 – 18:50||Building Your Own DFIR Sidekick||Scott J Roberts, GitHub|
|19:00 – 19:20||GRR and Rekall: State of the Union||Elizabeth Schweinsberg and Kristinn Gudjonsson, Google|
|19:30 – 22:00||Networking, drinks, and conversation||n/a|
Who: Incident Responders, Security Researchers, Security Analysts
What: S4 (San Francisco Security Series): Incident Responder and Researcher Conference
When: September 18, 2014 (registration starts at 8:30 AM. First training at 9:00AM)
Where: OpenDNS HQ, 135 Bluxome St., San Francisco, CA 94107
Food and Drinks: Provided
Free and reliable WiFi: Provided
Event Hashtag: #s4con
OpenDNS Twitter Account: twitter.com/OpenDNS
Please reserve soon as space is limited. Again, the registration link can be found here: https://irespond.eventbrite.com.
We look forward to seeing you!
The post S4 Incident Responder and Researcher Conference: Agenda appeared first on OpenDNS Security Labs.