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

9/14/2016
03:00 PM
Kelly Sheridan
Kelly Sheridan
Slideshows
Connect Directly
Twitter
LinkedIn
Google+
RSS
E-Mail
50%
50%

5 Law Enforcement & Emergency Response Bodies IT Departments Should Know

It's smart for businesses to strengthen their relationships with law enforcement before a cyberattack takes place. Whom should they contact, and how will it help after a breach?
Previous
1 of 6
Next

Image Source: TzahiV/iStockphoto

Image Source: TzahiV/iStockphoto

If your business was the victim of a cyberattack tomorrow, whom would you call?

For many organizations, the immediate response following a breach is to contact law enforcement. Depending on the business and severity of the situation, this could mean calling a local law enforcement branch or reaching out to the FBI.

It's a wise decision made at the wrong time. By the time an attack has occurred, it's already too late to coordinate a rapid and effective response with law enforcement agencies.

"It is very important, prior to a breach, for a business to have a relationship with law enforcement," explains information security consultant Shane Shook. "Too often, there is no pre-existing relationship, no means of communication."

This communication gap can prove dangerous for victims of cybercrime.

If your organization's first contact with law enforcement takes place the day of a breach, you risk having the wrong responders arrive on site. It will take time to secure the right experts and provide them with the information they need, a delay that leaves businesses vulnerable.

This problem affects organizations of all sizes. Shook, who has worked on large breaches, including the Sony and Target attacks, explains how major organizations struggled in the critical response stages. It was a slow process to contact law enforcement and establish the communication and chains of command necessary to respond, he says.

Given the rampant increase in cybercrime, businesses should be building a rapport with law enforcement so they know whom to contact following a breach. These relationships should start at the local and regional levels of law enforcement, says Shook.

It's an important step in building a cybersecurity strategy, and most businesses fail to take it. Historically, most organizations are shy about partnering with the FBI and other law enforcement agencies because it might reveal sensitive information.

In this day and age, however, these relationships are critical amid the growing risk to businesses. Law enforcement agencies should be viewed as partners to assist in emergencies, says Shook, and more businesses should be open to their help.

Here, we take a closer look at the law enforcement agencies to know before a cyberattack takes place, and which to contact in the aftermath of a breach. Has your organization started to build a relationship with law enforcement? Do you intend to? Which agencies have you worked with?

 

Kelly Sheridan is the Staff Editor at Dark Reading, where she focuses on cybersecurity news and analysis. She is a business technology journalist who previously reported for InformationWeek, where she covered Microsoft, and Insurance & Technology, where she covered financial ... View Full Bio

Previous
1 of 6
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Whoopty
50%
50%
Whoopty,
User Rank: Ninja
9/16/2016 | 7:43:57 AM
Impressive
There's a lot more organisations geared towards cyber security than I realised, but I still don't have a lot of faith in federal authorities when it comes to digital security. It's getting better, but with the aged population in a lot of higher up positions, I get the vibe that most of them just don't understand its importance.
cyberpink
50%
50%
cyberpink,
User Rank: Strategist
9/15/2016 | 9:53:06 AM
Kudos
Great review of who to know before you are hacked next time.  Thanks!
Why Cyber-Risk Is a C-Suite Issue
Marc Wilczek, Digital Strategist & CIO Advisor,  11/12/2019
DevSecOps: The Answer to the Cloud Security Skills Gap
Lamont Orange, Chief Information Security Officer at Netskope,  11/15/2019
Attackers' Costs Increasing as Businesses Focus on Security
Robert Lemos, Contributing Writer,  11/15/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Navigating the Deluge of Security Data
In this Tech Digest, Dark Reading shares the experiences of some top security practitioners as they navigate volumes of security data. We examine some examples of how enterprises can cull this data to find the clues they need.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-19040
PUBLISHED: 2019-11-17
KairosDB through 1.2.2 has XSS in view.html because of showErrorMessage in js/graph.js, as demonstrated by view.html?q= with a '"sampling":{"value":"<script>' substring.
CVE-2019-19041
PUBLISHED: 2019-11-17
An issue was discovered in Xorux Lpar2RRD 6.11 and Stor2RRD 2.61, as distributed in Xorux 2.41. They do not correctly verify the integrity of an upgrade package before processing it. As a result, official upgrade packages can be modified to inject an arbitrary Bash script that will be executed by th...
CVE-2019-19012
PUBLISHED: 2019-11-17
An integer overflow in the search_in_range function in regexec.c in Oniguruma 6.x before 6.9.4_rc2 leads to an out-of-bounds read, in which the offset of this read is under the control of an attacker. (This only affects the 32-bit compiled version). Remote attackers can cause a denial-of-service or ...
CVE-2019-19022
PUBLISHED: 2019-11-17
iTerm2 through 3.3.6 has potentially insufficient documentation about the presence of search history in com.googlecode.iterm2.plist, which might allow remote attackers to obtain sensitive information, as demonstrated by searching for the NoSyncSearchHistory string in .plist files within public Git r...
CVE-2019-19035
PUBLISHED: 2019-11-17
jhead 3.03 is affected by: heap-based buffer over-read. The impact is: Denial of service. The component is: ReadJpegSections and process_SOFn in jpgfile.c. The attack vector is: Open a specially crafted JPEG file.