The news of the Epsilon data breach and the subsequent fallout and is getting a little stale at this point. I think anyone who cares understands by now that some company called Epsilon was breached and that their email address was compromised as a result. Let's examine what Epsilon did right, and what Epsilon did wrong, though, so we can perhaps avoid future breaches of this magnitude, and improve on network security and incident response processes.

To begin, let's look at what Epsilon did right. First of all, it detected that there was a breach. You have to award some bonus points for that one. According to a story , Epsilon had actually been warned late last year by ReturnPath--a company that provides monitoring and authentication services for companies like Epsilon--that there was an against email distributors.

Epsilon heeded that warning and installed additional protection designed to monitor traffic and alert Epsilon admins in the event any unusual activity or download patterns were detected. It was apparently this new system that let Epsilon discover the breach quickly, and contain the impact to only two percent of the Epsilon customer base.

Joris Evers, Director of Worldwide Public Relations at , commends Epsilon for recognizing and responding to the threat. "Return Path at least was right that cyber-attackers had email service providers in the cross hairs. In today's world organizations should always be at high alert for cyber-attacks, particularly when handling consumer information and even more so after a warning has been issued."

Lesson learned: pay attention to credible warning signs, and proactively implement the necessary security controls and defenses to reduce risk, and increase the probability that an attack will be discovered, and the damage minimized.