Operations

4/29/2016
12:30 PM
Steve Zurier
Steve Zurier
Slideshows
Connect Directly
Twitter
RSS
E-Mail
50%
50%

6 Steps for Responding to a Disruptive Attack

Today's threat landscape dictates that companies must have a workable incident response plan.
Previous
1 of 7
Next

Image Source: ddosattackprotection.org

Disruptive attacks have become a disturbing trend that IT departments must consider when analyzing the ongoing threat landscape.

In its M-Trends 2016 report, FireEye’s Mandiant Consulting says these disruptive attacks are very different and require a different response than the “low and slow” attacks in which threat actors gain access to the victim’s network and steal information on the network for days, weeks and months before launching a full attack.

Senior Vice President Jurgen Kutscher adds that the most common disruptive attacks are attempts to extract a ransom, destroying critical business systems or publishing sensitive data on the Internet to embarrass or blackmail the victimized company.

Kutscher says attacks that result in the public release of confidential data cause great embarrassment and reputational damage to companies. In some cases, companies even lose the ability to function as a business because mission-critical systems are taken down. Side effects include executive resignations, costly ransoms, and expensive system rebuilds. High profile cases run from the JP Morgan hack of two years ago to the recent wave of ransomware attacks on hospitals.

The following six slides were developed following interviews with FireEye’s Kutscher and Gunter Ollmann, CSO for Vectra Networks.

 

Steve Zurier has more than 30 years of journalism and publishing experience, most of the last 24 of which were spent covering networking and security technology. Steve is based in Columbia, Md. View Full Bio

Previous
1 of 7
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
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.