Quantcast StorefrontBacktalk » Blog Archive » What Should You Do After The Breach?
advertisement
advertisement

What Should You Do After The Breach?

Written by Evan Schuman
October 28th, 2009
Like this story? Share it
To share this story with people in your social network, please click on the network icons below.

There is no shortage of advice on ways to try and prevent a data breach. But if it happens to you, do you have a plan of precisely what to do after the fact? Very few retailers do. Lots of complicating factors exist, such as the probability that the breach will be discovered many months after it ended, plus the fact that the bad guys will almost certainly have radically altered the logs. But the essential issue is that you have an urgent need to do several things immediately.

First, you have two competing Number One priorities: Stop the current attack (if it’s still going on) and prevent a new one; and keep systems fully functional so that sales are in no way impacted. Those two priorities don’t play well with each other, and that’s what we’re exploring in our Guest Column this week on the new McAfee security blog. Conflicts aside, there is a logical sequence of events that retailers need to follow the instant a breach is discovered.


advertisement

Leave a Reply

Newsletter

Quickly catch-up on the latest in E-Commerce and Retail Tech with our free weekly newsletter, with urgent bulletins as news merits.
advertisement

Most Recent Comments

Kill All The Passwords

This article does mention, but does not give enough attention to, the fact that the attacks discussed are only feasible when the encrypted password file can be copied and subjected to an offline attack. The trick is to have authentication performed on a separate, much more strongly secured host - such as an Active Directory Domain Controller, or a Kerberos server, or a NIS+ server, or even using something as banal as an LDAP-over-SSL authentication dialog. In these environments, the odds of the "password file" being stolen and subjected to an offline attack go to near zero, and only online attacks may be carried out by the attacker. With sensible exponential backoff between failed password attempts, lockout after a modest number of failed attempts on a single account, and pattern detection, that minimum 7 character password is quite secure enough. Passwords aren't dead yet for security purposes, and they will be with us for a very long while to come for practical purposes. The trick is to employ them correctly. Read more...
The possibilities you describe are years away from being implemented at best, so for the moment passwords are an ugly reality. Luckily, password managers can easily manage hundreds of passwords of any length. The only thing a user needs to remember is the master password. It seems like an easier task to educate users on how to use password managers rather than implement complex security technology on a global basis. Read more...