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

CrowdStrike Launches Free Toolkit For Incident Response

New, free CrowdResponse platform will be Swiss army knife for incident response, CrowdStrike says

CrowdStrike Wednesday released a new, free incident response toolkit designed to help enterprises collect the data they need to analyze sophisticated attacks.

In a blog posted on its website, CrowdStrike unveiled a community software platform called CrowdResponse, which can be downloaded for free.

"This is a toolkit that will help incident responders collect the data that they need, manipulate and analyze the data, and then sort it and tie it into the tools they already have," says George Kurtz, CEO and co-founder of CrowdStrike, a threat intelligence firm that also offers incident response and analysis services. "It's a slimmed-down version of the toolset that we use internally when we are called in to do incident response."

CrowdResponse is a community-based platform that may eventually support as many as 25 software modules, each serving a different aspect of the incident response process, Kurtz says. This week's release includes three modules: @dirtlist, @pslist, and @yara.

The @dirtlist tool offers a way to do directory listings, which enables responders to verify and display digital signature information and filter files and paths to speed incident analysis.

The @pslist module lets incident responders list out all active running processes, speeding the task of analyzing executable files and identifying those that might be associated with a sophisticated attack.

The @yara module is an enhanced version of the popular, community-based YARA malware analysis tool, which helps users identify and classify malware samples, speeding the process of sorting targeted attacks from random attacks.

"The @yara module is the one I'm most excited about," Kurtz says. "It greatly speeds the scan time and aids a responder in quickly pinpointing adversary activity on a suspect system."

The new platform will make it easier for enterprises to collect incident response data and compare it to threat intelligence "indicators" that are associated with particular groups of attackers, Kurtz says. When CrowdStrike identifies a new group of threat actors -- it already is following about 60 of them -- enterprises can use CrowdResponse to determine whether those threat actors might be at work in their own environments.

"The toolkit also contains a community aspect that will allow users to share information about what they are seeing with [CrowdStrike] and with each other," Kurtz says. "This will help with the intelligence-gathering process -- the more eyes that are on the attackers, the faster we will be able to identify what they are doing and put a stop to it."

CrowdResponse can be downloaded here.

Have a comment on this story? Please click "Add a Comment" below. If you'd like to contact Dark Reading's editors directly, send us a message. Tim Wilson is Editor in Chief and co-founder of Dark Reading.com, UBM Tech's online community for information security professionals. He is responsible for managing the site, assigning and editing content, and writing breaking news stories. Wilson has been recognized as one ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Edge-DRsplash-10-edge-articles
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
The State of Cybersecurity Incident Response
In this report learn how enterprises are building their incident response teams and processes, how they research potential compromises, how they respond to new breaches, and what tools and processes they use to remediate problems and improve their cyber defenses for the future.
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-3539
PUBLISHED: 2021-08-04
EspoCRM 6.1.6 and prior suffers from a persistent (type II) cross-site scripting (XSS) vulnerability in processing user-supplied avatar images. This issue was fixed in version 6.1.7 of the product.
CVE-2021-36801
PUBLISHED: 2021-08-04
Akaunting version 2.1.12 and earlier suffers from an authentication bypass issue in the user-controllable field, companies[0]. This issue was fixed in version 2.1.13 of the product.
CVE-2021-36802
PUBLISHED: 2021-08-04
Akaunting version 2.1.12 and earlier suffers from a denial-of-service issue that is triggered by setting a malformed 'locale' variable and sending it in an otherwise normal HTTP POST request. This issue was fixed in version 2.1.13 of the product.
CVE-2021-36803
PUBLISHED: 2021-08-04
Akaunting version 2.1.12 and earlier suffers from a persistent (type II) cross-site scripting (XSS) vulnerability in processing user-supplied avatar images. This issue was fixed in version 2.1.13 of the product.
CVE-2021-36804
PUBLISHED: 2021-08-04
Akaunting version 2.1.12 and earlier suffers from a password reset spoofing vulnerability, wherein an attacker can proxy password reset requests through a running Akaunting instance, if that attacker knows the target's e-mail address. This issue was fixed in version 2.1.13 of the product. Please not...