Attacks/Breaches
3/9/2010
07:27 PM
Connect Directly
Google+
Twitter
RSS
E-Mail
50%
50%
Repost This

Voluntary Breach Disclosure Rare But Valuable

Most organizations won't go public about an attack unless they have to, but security experts say there are ways to collaborate without being stigmatized

Google's and Adobe's disclosure in January that they had been hit by the same wave of targeted attacks were rare voluntary revelations, the likes of which may never be seen again: Most companies won't disclose an attack unless required to by law or regulations. But security experts and forensics investigators say the best way to defend against targeted attacks and help unmask who's behind them is to gather and correlate attack information among various victims.

There's no common way today for victim firms to safely and confidentially share data about attacks they suffer, nor is there necessarily much incentive to do so. The so-called Aurora attacks out of China that hit Google, Adobe, Intel, and an unknown number of other organizations in the U.S. have reignited a debate about voluntary breach disclosure. Google's discovery of the attacks demonstrated how victims can benefit from collaboration with one another and law enforcement.

Aside from the obvious privacy concerns and worries about damage to their public images in the event of a publicly disclosed hack, many firms have reservations about sharing their breach information with law enforcement because it's often more of a one-way street than an information-sharing arrangement: They supply their attack information to the authorities and often don't hear back.

But that soon could change. FBI director Robert Mueller last week in a keynote address at the RSA Conference 2010 said while today it's the exception rather than the rule for organizations to report cyberattacks to the bureau, he promised some big changes that could allay privacy concerns. "We will minimize the disruption to your business. We will safeguard your privacy and your data. Where necessary, we will seek protective orders to preserve trade secrets and business confidentiality. And we will share with you what we can, as quickly as we can, about the means and methods of attack," Mueller told attendees.

Kevin Mandia, CEO of forensics firm Mandiant, says one approach would be for vertical markets to set up their own disclosure vehicles. They could then take that anonymized information and offer it to the FBI or other authorities. "I would send the raw information, malware, and intelligence to the government, but not through my organization," Mandia says. Doing so would provide a more confidential conduit of disclosure, plus different industries have different IT security requirements, he says.

But the reality is that unless they are bound by disclosure laws or regulations, most organizations just keep quiet about attacks on their networks. "It's a lonely life as a victim," he says. "How do they merge their data without repercussions? And [many times] they don't get any intelligence out of [sharing the information]."

Verizon Business, meanwhile, last week released to the public its framework for gathering and analyzing forensics data from a data breach that serves as the basis for its comprehensive annual data breach reports. The hope is the framework will facilitate more cooperation and data-sharing among breach victim organizations.

Half of all breaches that Verizon has investigated during the past two years have been related in some way. But in many other cases, breaches aren't correlated to look for connections, says Wade Baker, director of risk intelligence for Verizon Business. "Something I would love to see is [determining] connections among attacks," he says.

National cybersecurity coordinator Howard Schmidt said last week in an RSA town hall meeting discussion that he's looking at incident response issues. Schmidt said private industry hasn't had a central point of contact for reporting attacks, and they want to know who to call and how to protect their intellectual property.

Meanwhile, there has been plenty of speculation about Google's own business reasons for revealing the targeted attacks out of China, but all the search giant has said is it did so because of the security implications, human rights issues, and freedom of speech. Adobe also had its reasons for coming forward: "For us, it was about transparency. Our software is widely distributed," said Gary Terrell, CISO for Adobe Systems.

The CSO Council-Bay Area, of which Adobe is a founding member and Terrell the chair, also serves as an informal venue for some organizations to share breach information under nondisclosure. "We are able to share information confidentially" in the council, says Leslie Lambert, the former CISO for Sun Microsystems. Lambert notes that law enforcement typically wants "to pull from us [enterprises]" without necessarily reciprocating with any information about attacks or investigations.

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 Senior Editor at DarkReading.com. 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 Magazine, ... View Full Bio

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2012-3946
Published: 2014-04-24
Cisco IOS before 15.3(2)S allows remote attackers to bypass interface ACL restrictions in opportunistic circumstances by sending IPv6 packets in an unspecified scenario in which expected packet drops do not occur for "a small percentage" of the packets, aka Bug ID CSCty73682.

CVE-2012-5723
Published: 2014-04-24
Cisco ASR 1000 devices with software before 3.8S, when BDI routing is enabled, allow remote attackers to cause a denial of service (device reload) via crafted (1) broadcast or (2) multicast ICMP packets with fragmentation, aka Bug ID CSCub55948.

CVE-2013-6738
Published: 2014-04-24
Cross-site scripting (XSS) vulnerability in IBM SmartCloud Analytics Log Analysis 1.1 and 1.2 before 1.2.0.0-CSI-SCALA-IF0003 allows remote attackers to inject arbitrary web script or HTML via an invalid query parameter in a response from an OAuth authorization endpoint.

CVE-2014-0188
Published: 2014-04-24
The openshift-origin-broker in Red Hat OpenShift Enterprise 2.0.5, 1.2.7, and earlier does not properly handle authentication requests from the remote-user auth plugin, which allows remote attackers to bypass authentication and impersonate arbitrary users via the X-Remote-User header in a request to...

CVE-2014-2391
Published: 2014-04-24
The password recovery service in Open-Xchange AppSuite before 7.2.2-rev20, 7.4.1 before 7.4.1-rev11, and 7.4.2 before 7.4.2-rev13 makes an improper decision about the sensitivity of a string representing a previously used but currently invalid password, which allows remote attackers to obtain potent...

Best of the Web