BankInfoSecurity.com - Information Security News, Regulations, & Education

Banking Information Security Blogs

Comments (3)

Read All Posts (93)

Heartland's Lesson: How to Handle A Data Breach

February 10, 2009 - Linda McGlasson

Linda McGlasson
The fallout is still coming from the Heartland Payment Systems (HPY) data breach, and banks and credit unions are still dealing with the aftermath. At today's count there are more than 124 banks and credit unions affected by the breach, the number of cards affected topping 250,000.

The big question is: If your institution was hit with this kind of data breach that wasn't caused by your institution, would you be ready to respond? Heartland wasn't the first big data breach from outside service providers or retailers that institutions have had to respond to in the last three years. Those out there with short memories ... remember CardSystems Solutions, TJX or Hannaford? The TJX numbers hit more than 90 million credit card accounts. Some were already expired, but institutions still had to respond to the breach and talk to customers about it.

It's pretty much inevitable: At sometime, somewhere, you or one of the companies your institution depends on as a service provider will be the victim of a data breach. 

It's pretty much inevitable: At sometime, somewhere, you or one of the companies your institution depends on as a service provider will be the victim of a data breach. If those third-party service providers have your customers' sensitive data and they're breached, it means you have to also be ready to handle the fallout. Let's face the facts - the bad guys are really good at what they do and are now flexing their bad malware muscles, readying themselves to attack again and again to get at sensitive, lucrative data.

Take any good data breach incident response plan at any institution and look at it closely. What an institution (or any other entity for that matter) does in the first 24 hours after a breach (whether it occurs at your institution, or as in the case of Heartland, from an outside source) will decide if that institution can weather the storm that follows. Just looking at the national media attention that Heartland's announcement received shows anyone that what you say and do after something like this is closely scrutinized. (At current count on Google there were 860,000 results on the key words "Heartland breach")

In these hard economic times where customers' trust and confidence are at a premium, how an institution handles the news about a data breach and how it responds to its customers and the media can make the difference between keeping and losing those customers. Look at the findings of the Javelin Identity Fraud Report - it found that when a credit card fraud happens, "15 percent of all customers leave their credit card provider, 17 percent leave their current bank or credit union, and 40 percent of people defrauded through a debit card get a new relationship." So it is obvious what party pays the biggest price, even though they weren't directly responsible for a breach such as the one at Heartland - the institutions that issue the credit and debit cards. Your customer doesn't know who or what Heartland is, but they do know your institution and your brand, and they'll remember who they got the call from about the breach.

In the case of the Heartland breach, banks and credit unions around the country are beefing up their fraud monitoring and have initiated their communications response plan to reach out to their customers and members to let them know when their cards were included in the breach. Some called the customers, telling them the news that their card was being deactivated. Others sent out letters informing the customers affected that they were either having their card replaced, or closely monitored for signs of fraudulent activity. Over and over again, I've seen bank representatives saying the right things to their local reporters in the coverage of the breach and how they're handling it. Most are along the lines of: "It wasn't a breach in our systems, our systems are safe, and customers won't be liable for any fraud due to the breach." (See example of customer notification letter)

The real message for all institutions whether you have been affected in this latest breach or not is: Be prepared. It doesn't have to be a Heartland-sized data breach that would cause you to lose the trust, confidence and ultimately the business of your customers. You need an incident response plan ready to work with before, not after the breach is discovered. Your breach response plan needs to be well-thought out, with all players and tasks identified, and a set of standard operating procedures, with precision almost on a military level. Most importantly, and this can't be stressed enough, your data breach incident response plan needs to be tested, not just sit collecting dust on somebody's bookshelf or languishing on a manager's PC. It needs to be just as well-planned and tested like your disaster recovery and business continuity plans are.

In the end, it all is about staying in business and keeping the trust, confidence and business of your customers.


digg del.icio.us reddit
Share
Print Print

Post a Comment

Please login or register to post a comment
Username:  
Password:
Remember Username?
Comments
Very good points. I used to manage a portfolio of more than a million cards. Aside from your Response Plan being tested, you need to develop several contingencies depending on the type/level/size of the breach. The "knee jerk reaction" by most Tier 2 & 3 FIs is to block and re-issue, and many times this will push customers away who were never truly impacted, yet lost confidence in the Issuer and product. With Track 2 data and PIN block information as part of the compromise, obviously, drastic steps need to be taken. However, not all breaches are this severe.

Communication to the cardholder is key in order to maintain the cardholder's confidence in the product and the Issuer. My personal card was recently affected, and my "Top 10 Issuer" never told me that my card was going to be blocked and re-issued. I found out when my transaction was denied. Update your plans to leverage the development of technologies and processes. Not every communication has to go through the USPS. Card Systems and TJX were probably long before any FIs even thought about secure messaging in their online banking applications, SMS messaging or "warm blocks" that decline specific types of transactions and initiate cardholder alerts.

Additionally, FIs need to take a few minutes and dedicate some resources to analyze cards affected. Everyone knows not to re-issue a card that has already been closed/blocked. But many Issuers will mistakenly automatically re-issue a card in an open status...linked to an open DDA...that has not had an activity in the last 6 months. Not a good use of resources; this card could be "warm-blocked" with a communique to the cardholder.

Unfortunatley, what I see is that staffing has changed since the last compromise and "lessons learned" were not adequately documented. With two processor compromises this close together, now is the time to get the process on paper, re-visit, test and validate.
Posted by paag86 on February 27, 2009 @ 5:44 PM
-----------
I keep reading about breaches; is the PCI Compliance Requirement/Guideline/Don't blame us, a large part of the problem? Was everyone better off without it?
Posted by mcherry on February 11, 2009 @ 3:38 PM
-----------
All good advice. Thank you. The stats for affected issuers and cards are low by an order of magnitude, however. We are a small debit issuer (55,000 cards outstanding) and our CAMS alerts from Visa on this breach exceed 15,000 records (of which about 75% are open cards). This one will prove to be HUGE.

The elephant is the corner is that the issuers get to pick up the tab for notification, card re-issue, and fraud losses. So, "The real message" for sloppy processors and merchants is this: Get ready to write some big checks!!
Posted by Wadeg on February 11, 2009 @ 11:11 AM