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.

Risk

8/11/2008
09:15 AM
Connect Directly
Google+
Twitter
RSS
E-Mail
50%
50%

What to Do After a Breach

Former FTC official gives Defcon attendees the lowdown on breach response and working with law enforcement

LAS VEGAS -- DefCon 16 -- There are plenty of breach disclosure laws and regulations for businesses to follow if they get hacked or suffer some sort of data leak, but there’s no requirement that they have an actual breach response plan, according to a former Federal Trade Commission official.

Don Blumenthal, an attorney and consultant specializing in data security and privacy as well as senior principal with Global Cyber Risk, LLC, and an adjunct professor at the University of Michigan, said in an interview that aside from some federal regulations guiding government breach response, private industry isn’t mandated to set up a game plan for the aftermath of an attack or leak. “I am not aware of any other statute or regulation that makes it mandatory or requires that companies have a breach response plan in place,” he says.

Still, Blumenthal says he sees some organizations taking the initiative themselves to set up post-breach plans given the epidemic of high-profile breaches today. He gave attendees at DefCon on Saturday a few key tips on what to do in the aftermath of a breach.

The first thing is to alert everyone in the company, with a need to know, about the breach. “Get them all in a room or on a conference call and have regular meetings,” Blumenthal says. This group of key individuals would include business, legal, and technical people to determine what to do next and "identify if outsiders need to be brought in, such as outside counsel with relative expertise in this area; outside communications firms, for ‘damage control’ and how to do notification; and forensics firms to do cross-checking to see what data is missing.”

It’s often difficult to determine what data is missing or compromised, so this process can take some time. “In the projects I see, notifications are generally being held until the company [hit by a breach] has a good handle on what happened,” he says.

The next major step is to notify law enforcement. “In general, the next step after convening everyone in house would be exploring law enforcement notification. And concurrent with all of this, you should get the data analysis going and plan how you’re doing to address it to the public,” Blumenthal says.

A healthy relationship with law enforcement can also help a breach notification situation go more smoothly. “I’m a firm believer in proactive dealings with law enforcement... Have law enforcement come talk to your company” about breach issues, he says. “Protect your rights above all, obey the law above all, but show respect and don’t play games [with law enforcement] because [nobody] wins doing that.”

Going public about a hack within your company obviously isn’t a natural reaction for most companies. “The biggest issue is trying to work through the understandable [instinct] in-house to want to keep it quiet,” Blumenthal says.

Have a comment on this story? Please click "Discuss" below. If you'd like to contact Dark Reading's editors directly, send us a message.

Kelly Jackson Higgins is the Executive Editor of Dark Reading. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise ... View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 8/3/2020
Pen Testers Who Got Arrested Doing Their Jobs Tell All
Kelly Jackson Higgins, Executive Editor at Dark Reading,  8/5/2020
'BootHole' Vulnerability Exposes Secure Boot Devices to Attack
Kelly Sheridan, Staff Editor, Dark Reading,  7/29/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Special Report: Computing's New Normal, a Dark Reading Perspective
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
The Changing Face of Threat Intelligence
The Changing Face of Threat Intelligence
This special report takes a look at how enterprises are using threat intelligence, as well as emerging best practices for integrating threat intel into security operations and incident response. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-16192
PUBLISHED: 2020-08-05
LimeSurvey 4.3.2 allows reflected XSS because application/controllers/LSBaseController.php lacks code to validate parameters.
CVE-2020-17364
PUBLISHED: 2020-08-05
USVN (aka User-friendly SVN) before 1.0.9 allows XSS via SVN logs.
CVE-2020-4481
PUBLISHED: 2020-08-05
IBM UrbanCode Deploy (UCD) 6.2.7.3, 6.2.7.4, 7.0.3.0, and 7.0.4.0 is vulnerable to an XML External Entity Injection (XXE) attack when processing XML data. A remote attacker could exploit this vulnerability to expose sensitive information or consume memory resources. IBM X-Force ID: 181848.
CVE-2020-5608
PUBLISHED: 2020-08-05
CAMS for HIS CENTUM CS 3000 (includes CENTUM CS 3000 Small) R3.08.10 to R3.09.50, CENTUM VP (includes CENTUM VP Small, Basic) R4.01.00 to R6.07.00, B/M9000CS R5.04.01 to R5.05.01, and B/M9000 VP R6.01.01 to R8.03.01 allows a remote unauthenticated attacker to bypass authentication and send altered c...
CVE-2020-5609
PUBLISHED: 2020-08-05
Directory traversal vulnerability in CAMS for HIS CENTUM CS 3000 (includes CENTUM CS 3000 Small) R3.08.10 to R3.09.50, CENTUM VP (includes CENTUM VP Small, Basic) R4.01.00 to R6.07.00, B/M9000CS R5.04.01 to R5.05.01, and B/M9000 VP R6.01.01 to R8.03.01 allows a remote unauthenticated attacker to cre...