Operations

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

6 Steps for Responding to a Disruptive Attack

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

1. Identify the nature of the attack.

It makes no sense to restore your environment before you understand the nature of the attack, how the attackers are accomplishing their objectives and ultimately contain the attack. If attackers are still in the environment and malware has not been contained systems will become compromised again, the attackers will encrypt your systems again, or data will be destroyed. More often than not, malware infiltrates a network when somebody opens up a malicious attachment.

Image Source: hackingmind.com

1. Identify the nature of the attack.

It makes no sense to restore your environment before you understand the nature of the attack, how the attackers are accomplishing their objectives and ultimately contain the attack. If attackers are still in the environment and malware has not been contained systems will become compromised again, the attackers will encrypt your systems again, or data will be destroyed. More often than not, malware infiltrates a network when somebody opens up a malicious attachment.

Image Source: hackingmind.com

2 of 7
Comment  | 
Print  | 
Comments
Newest First  |  Oldest First  |  Threaded View
More Than Half of Users Reuse Passwords
Curtis Franklin Jr., Senior Editor at Dark Reading,  5/24/2018
Is Threat Intelligence Garbage?
Chris McDaniels, Chief Information Security Officer of Mosaic451,  5/23/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-11505
PUBLISHED: 2018-05-26
The Werewolf Online application 0.8.8 for Android allows attackers to discover the Firebase token by reading logcat output.
CVE-2018-6409
PUBLISHED: 2018-05-26
An issue was discovered in Appnitro MachForm before 4.2.3. The module in charge of serving stored files gets the path from the database. Modifying the name of the file to serve on the corresponding ap_form table leads to a path traversal vulnerability via the download.php q parameter.
CVE-2018-6410
PUBLISHED: 2018-05-26
An issue was discovered in Appnitro MachForm before 4.2.3. There is a download.php SQL injection via the q parameter.
CVE-2018-6411
PUBLISHED: 2018-05-26
An issue was discovered in Appnitro MachForm before 4.2.3. When the form is set to filter a blacklist, it automatically adds dangerous extensions to the filters. If the filter is set to a whitelist, the dangerous extensions can be bypassed through ap_form_elements SQL Injection.
CVE-2018-11500
PUBLISHED: 2018-05-26
An issue was discovered in PublicCMS V4.0.20180210. There is a CSRF vulnerability in "admin/sysUser/save.do?callbackType=closeCurrent&navTabId=sysUser/list" that can add an admin account.