Attacks/Breaches
10/23/2008
04:45 PM
Connect Directly
RSS
E-Mail
50%
50%

Data Breach? Who Ya Gonna Call?

Our latest CSI survey shows few organizations bring in law enforcement after an attack. That's bad policy.

Whether a data breach is accidental or the result of a targeted malicious attack, the results can be devastating to a company's financial stability and reputation. To compound the problem, many CIOs fear that reporting the incident will only make matters worse. In the 2008 CSI Computer Crime & Security Survey, only about one in four respondents said that they contacted a law enforcement agency in the wake of a breach. Most said they worry about negative publicity and that the authorities can do little to help deal with cybercrime.

It's reasonable to fear negative press. Sales may be adversely affected, and the public's confidence can be shaken. Furthermore, many states have enacted data breach notification laws that can cause a company's legal fees to mount. On the other hand, a decision not to come forward could work against you in court later, and law enforcement has sophisticated forensic and legal tools not available to private industry. However, reporting isn't as simple as it sounds. The President's Identity Theft Task Force has recommended the creation of national standards for data protection and data breach notification requirements that would pre-empt the multitude of existing state laws. The Task Force also recommended the establishment of a national identity theft law enforcement center to harmonize identity theft and data breach reporting. But as of this writing, neither of these recommendations has been acted on. Unfortunately, this makes reporting to law enforcement confusing, as there's no clear-cut hierarchy. In our report, we describe a methodology for reporting to law enforcement agencies that deal with cybercrime.

Return to the main story:
Forensic Teams Take On Hackers

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Flash Poll
Current Issue
Cartoon
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-1544
Published: 2014-07-23
Use-after-free vulnerability in the CERT_DestroyCertificate function in libnss3.so in Mozilla Network Security Services (NSS) 3.x, as used in Firefox before 31.0, Firefox ESR 24.x before 24.7, and Thunderbird before 24.7, allows remote attackers to execute arbitrary code via vectors that trigger cer...

CVE-2014-1547
Published: 2014-07-23
Multiple unspecified vulnerabilities in the browser engine in Mozilla Firefox before 31.0, Firefox ESR 24.x before 24.7, and Thunderbird before 24.7 allow remote attackers to cause a denial of service (memory corruption and application crash) or possibly execute arbitrary code via unknown vectors.

CVE-2014-1548
Published: 2014-07-23
Multiple unspecified vulnerabilities in the browser engine in Mozilla Firefox before 31.0 and Thunderbird before 31.0 allow remote attackers to cause a denial of service (memory corruption and application crash) or possibly execute arbitrary code via unknown vectors.

CVE-2014-1549
Published: 2014-07-23
The mozilla::dom::AudioBufferSourceNodeEngine::CopyFromInputBuffer function in Mozilla Firefox before 31.0 and Thunderbird before 31.0 does not properly allocate Web Audio buffer memory, which allows remote attackers to execute arbitrary code or cause a denial of service (buffer overflow and applica...

CVE-2014-1550
Published: 2014-07-23
Use-after-free vulnerability in the MediaInputPort class in Mozilla Firefox before 31.0 and Thunderbird before 31.0 allows remote attackers to execute arbitrary code or cause a denial of service (heap memory corruption) by leveraging incorrect Web Audio control-message ordering.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Sara Peters hosts a conversation on Botnets and those who fight them.