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!
6 Security Trends for 2018/2019
Curtis Franklin Jr., Senior Editor at Dark Reading,  10/15/2018
6 Reasons Why Employees Violate Security Policies
Ericka Chickowski, Contributing Writer, Dark Reading,  10/16/2018
Getting Up to Speed with "Always-On SSL"
Tim Callan, Senior Fellow, Comodo CA,  10/18/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Latest Comment: Too funny!
Current Issue
Flash Poll
The Risk Management Struggle
The Risk Management Struggle
The majority of organizations are struggling to implement a risk-based approach to security even though risk reduction has become the primary metric for measuring the effectiveness of enterprise security strategies. Read the report and get more details today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-10839
PUBLISHED: 2018-10-16
Qemu emulator <= 3.0.0 built with the NE2000 NIC emulation support is vulnerable to an integer overflow, which could lead to buffer overflow issue. It could occur when receiving packets over the network. A user inside guest could use this flaw to crash the Qemu process resulting in DoS.
CVE-2018-13399
PUBLISHED: 2018-10-16
The Microsoft Windows Installer for Atlassian Fisheye and Crucible before version 4.6.1 allows local attackers to escalate privileges because of weak permissions on the installation directory.
CVE-2018-18381
PUBLISHED: 2018-10-16
Z-BlogPHP 1.5.2.1935 (Zero) has a stored XSS Vulnerability in zb_system/function/c_system_admin.php via the Content-Type header during the uploading of image attachments.
CVE-2018-18382
PUBLISHED: 2018-10-16
Advanced HRM 1.6 allows Remote Code Execution via PHP code in a .php file to the user/update-user-avatar URI, which can be accessed through an "Update Profile" "Change Picture" (aka user/edit-profile) action.
CVE-2018-18374
PUBLISHED: 2018-10-16
XSS exists in the MetInfo 6.1.2 admin/index.php page via the anyid parameter.