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
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

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
 

Recommended Reading:

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!
News
Former CISA Director Chris Krebs Discusses Risk Management & Threat Intel
Kelly Sheridan, Staff Editor, Dark Reading,  2/23/2021
Edge-DRsplash-10-edge-articles
Security + Fraud Protection: Your One-Two Punch Against Cyberattacks
Joshua Goldfarb, Director of Product Management at F5,  2/23/2021
News
Cybercrime Groups More Prolific, Focus on Healthcare in 2020
Robert Lemos, Contributing Writer,  2/22/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
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
Building the SOC of the Future
Building the SOC of the Future
Digital transformation, cloud-focused attacks, and a worldwide pandemic. The past year has changed the way business works and the way security teams operate. There is no going back.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-4931
PUBLISHED: 2021-02-24
IBM MQ 9.1 LTS, 9.2 LTS, and 9.1 CD AMQP Channels could allow an authenticated user to cause a denial of service due to an issue processing messages. IBM X-Force ID: 191747.
CVE-2020-11987
PUBLISHED: 2021-02-24
Apache Batik 1.13 is vulnerable to server-side request forgery, caused by improper input validation by the NodePickerPanel. By using a specially-crafted argument, an attacker could exploit this vulnerability to cause the underlying server to make arbitrary GET requests.
CVE-2020-11988
PUBLISHED: 2021-02-24
Apache XmlGraphics Commons 2.4 is vulnerable to server-side request forgery, caused by improper input validation by the XMPParser. By using a specially-crafted argument, an attacker could exploit this vulnerability to cause the underlying server to make arbitrary GET requests.
CVE-2021-21974
PUBLISHED: 2021-02-24
OpenSLP as used in ESXi (7.0 before ESXi70U1c-17325551, 6.7 before ESXi670-202102401-SG, 6.5 before ESXi650-202102101-SG) has a heap-overflow vulnerability. A malicious actor residing within the same network segment as ESXi who has access to port 427 may be able to trigger the heap-overflow issue in...
CVE-2021-22667
PUBLISHED: 2021-02-24
BB-ESWGP506-2SFP-T versions 1.01.09 and prior is vulnerable due to the use of hard-coded credentials, which may allow an attacker to gain unauthorized access and permit the execution of arbitrary code on the BB-ESWGP506-2SFP-T (versions 1.01.01 and prior).