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-0972
Published: 2014-08-01
The kgsl graphics driver for the Linux kernel 3.x, as used in Qualcomm Innovation Center (QuIC) Android contributions for MSM devices and other products, does not properly prevent write access to IOMMU context registers, which allows local users to select a custom page table, and consequently write ...

CVE-2014-2627
Published: 2014-08-01
Unspecified vulnerability in HP NonStop NetBatch G06.14 through G06.32.01, H06 through H06.28, and J06 through J06.17.01 allows remote authenticated users to gain privileges for NetBatch job execution via unknown vectors.

CVE-2014-3009
Published: 2014-08-01
The GDS component in IBM InfoSphere Master Data Management - Collaborative Edition 10.0 through 11.0 and InfoSphere Master Data Management Server for Product Information Management 9.0 and 9.1 does not properly handle FRAME elements, which makes it easier for remote authenticated users to conduct ph...

CVE-2014-3302
Published: 2014-08-01
user.php in Cisco WebEx Meetings Server 1.5(.1.131) and earlier does not properly implement the token timer for authenticated encryption, which allows remote attackers to obtain sensitive information via a crafted URL, aka Bug ID CSCuj81708.

CVE-2014-3534
Published: 2014-08-01
arch/s390/kernel/ptrace.c in the Linux kernel before 3.15.8 on the s390 platform does not properly restrict address-space control operations in PTRACE_POKEUSR_AREA requests, which allows local users to obtain read and write access to kernel memory locations, and consequently gain privileges, via a c...

Best of the Web
Dark Reading Radio