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.

Attacks/Breaches

3/30/2010
03:14 PM
Connect Directly
Google+
Twitter
RSS
E-Mail
50%
50%

Organizations Rarely Report Breaches to Law Enforcement

Meanwhile, FBI says it's making the process more private and more of a two-way street

Most organizations hit by breaches that don't require public disclosure don't call in law enforcement -- they consider it an exposure risk, with little chance of their gaining any intelligence from investigators about the attack, anyway.

FBI director Robert Mueller has acknowledged this dilemma facing organizations that get hacked, noting in a speech at the RSA Conference last month that disclosing breaches to the FBI is the exception and not the rule today. But the FBI will protect victim organization's privacy, data, and will share what information it can from its investigation, he said, rather than continue with the mostly one-way sharing that organizations traditionally have experienced when dealing with the FBI.

Gary Terrell, president of the Bay Area CSO Council and CISO at Adobe, says different companies have their own rules about reporting to law enforcement. "[Many] won't talk to law enforcement without an NDA [non-disclosure agreement]," says Terrell, who was speaking on behalf of the Council. "The FBI has a hard time signing it. That hasn't been successful so far, so sharing with the FBI has been minimal."

He says the feds have their own communications "protocol" for sharing classified information, but they don't have a standard and confidential way to work with the private sector on breach investigations. And until the feds can work with NDAs, there won't be much back-and-forth between companies and these agencies about breaches, he predicts.

Acting deputy assistant director for the FBI's Cyber Division Jeffrey Troy says it helps the attackers if companies aren't disclosing breaches to the FBI or law enforcement. "We are most concerned with gathering that information and sharing it with everyone else [affected] so we can harden the systems," Troy says. "If you are not telling us you have been penetrated ... that [may be] another attack vector we can't protect everyone else from.

"It's to the advantage of the bad guys if you don't share that information. We're trying to get people to understand that."

Troy says the bureau has had breach cases where it collected evidence of attackers getting into hundreds of companies. "They [the victims] hadn't come to us and told us, but we found the evidence because we caught the hacker that did it. You may not come to me, but it's likely I'm going to come to you."

Security experts and forensics investigators say the best way to defend against targeted attacks as well as other breaches and help unmask who's behind them is to gather and correlate attack information among various victims. Connecting the dots also helps companies defend against similar types of attacks. The unprecedented voluntary disclosure earlier this year by Google, Adobe, and later, Intel, that they were victims of targeted attacks out of China demonstrated how victims can benefit from collaboration with one another and law enforcement. But security experts say Google and Adobe's disclosures were an anomaly rather than a trend.

Companies hit by breaches where customer information or credit and debit card numbers weren't exposed aren't necessarily required by law to go public about the hacks. So rather than suffer bad PR or stock market ramifications, they merely keep quiet. JC Penney, for instance, reportedly fought but ultimately lost its bid to keep its name secret in the recent trail of convicted Heartland Payment Systems hacker Albert Gonzalez. While JC Penney's computer system had been breached, prosecutors said the government didn't have evidence that any payment card numbers were taken. Wet Seal was another retailer also hit by the attackers, but there was no evidence card numbers were taken from its system, either.

Those companies that do voluntarily report attacks to law enforcement sometimes suffer productivity issues as well as worries of bad publicity. Some that have voluntarily tried to work with law enforcement have had their data centers confiscated, hampering their day-to-day operations while the FBI finishes its investigation.

"We've seen where the FBI has gone in and cleaned out data centers. How do these companies recover?" says Patricia Titus, chief information security officer for Unisys Federal Systems and former CISO for the Transportation Security Administration (TSA). "They need to get back up and running versus protecting forensics data" for the FBI, she says.

"Where's the incentive" for reporting to the FBI? Titus says. "Companies are in business to make money and stay up and functioning."

Page 2: What The FBI Will Share 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

Previous
1 of 2
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
6 Emerging Cyber Threats That Enterprises Face in 2020
This Tech Digest gives an in-depth look at six emerging cyber threats that enterprises could face in 2020. Download your copy today!
Flash Poll
State of Cybersecurity Incident Response
State of Cybersecurity Incident Response
Data breaches and regulations have forced organizations to pay closer attention to the security incident response function. However, security leaders may be overestimating their ability to detect and respond to security incidents. Read this report to find out more.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-11619
PUBLISHED: 2020-04-07
FasterXML jackson-databind 2.x before 2.9.10.4 mishandles the interaction between serialization gadgets and typing, related to org.springframework.aop.config.MethodLocatingFactoryBean (aka spring-aop).
CVE-2020-11620
PUBLISHED: 2020-04-07
FasterXML jackson-databind 2.x before 2.9.10.4 mishandles the interaction between serialization gadgets and typing, related to org.apache.commons.jelly.impl.Embedded (aka commons-jelly).
CVE-2020-11509
PUBLISHED: 2020-04-07
An XSS vulnerability in the WP Lead Plus X plugin through 0.98 for WordPress allows remote attackers to upload page templates containing arbitrary JavaScript via the c37_wpl_import_template admin-post action (which will execute in an administrator's browser if the template is used to create a page).
CVE-2020-6647
PUBLISHED: 2020-04-07
An improper neutralization of input vulnerability in the dashboard of FortiADC may allow an authenticated attacker to perform a cross site scripting attack (XSS) via the name parameter.
CVE-2020-9286
PUBLISHED: 2020-04-07
An improper authorization vulnerability in FortiADC may allow a remote authenticated user with low privileges to perform certain actions such as rebooting the system.