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

10/23/2008
04:45 PM
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
Comments
Newest First  |  Oldest First  |  Threaded View
News
Inside the Ransomware Campaigns Targeting Exchange Servers
Kelly Sheridan, Staff Editor, Dark Reading,  4/2/2021
Commentary
Beyond MITRE ATT&CK: The Case for a New Cyber Kill Chain
Rik Turner, Principal Analyst, Infrastructure Solutions, Omdia,  3/30/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-29370
PUBLISHED: 2021-04-13
A UXSS was discovered in the Thanos-Soft Cheetah Browser in Android 1.2.0 due to the inadequate filter of the intent scheme. This resulted in Cross-site scripting on the cheetah browser in any website.
CVE-2021-3460
PUBLISHED: 2021-04-13
The Motorola MH702x devices, prior to version 2.0.0.301, do not properly verify the server certificate during communication with the support server which could lead to the communication channel being accessible by an attacker.
CVE-2021-3462
PUBLISHED: 2021-04-13
A privilege escalation vulnerability in Lenovo Power Management Driver for Windows 10, prior to version 1.67.17.54, that could allow unauthorized access to the driver's device object.
CVE-2021-3463
PUBLISHED: 2021-04-13
A null pointer dereference vulnerability in Lenovo Power Management Driver for Windows 10, prior to version 1.67.17.54, that could cause systems to experience a blue screen error.
CVE-2021-3471
PUBLISHED: 2021-04-13
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Notes: none.