The CrowdStrike platform includes an extensive set of API’s for use by both customers and partners. In this video and article, we will look at one example of how those API’s can be leveraged by a specific partner product – IBM’s QRadar.
Before setting up and reviewing the integration options, there are a just a few prerequisite steps.
- Download the CrowdStrike app from the IBM X-Force App Exchange. This extension enables QRadar to ingest the CrowdStrike event data.
- Upload that app to your QRadar instance via the web browser.
- Collect the CrowdStrike API keys required for the desired level of integration.
- Endpoint – There are three API keys required to set up the data exchange and integration of your event data between CrowdStrike and QRadar. The Stream and Query API keys can be obtained from CrowdStrike support. An OAuth API key that allows read / write access to “Detections” and read / write access on “Hosts” can be configured in the Falcon UI.
- Intel – For Intel customers, the Intel API key is required to see correlated threat intelligence for the detections in the QRadar instance. That key can be obtained from CrowdStrike support.
Once the app is installed, the API information will be entered in the screens shown below. The first is for the endpoint API’s.
There is a separate configuration screen for the Intel integration.
How can customers use CrowdStrike event data within the QRadar interface?
Once the QRadar integrations are enabled, you will receive a feed of your CrowdStrike detections in the QRadar interface. They will be shown as “Offences” with a description that identifies then as CrowdStrike with additional details to reflect the event type.
For each type, you will see an event count and have the option to drill down for additional details. Here, we will look closer at the eight sensor based machine learning detection
From that view, you can then drill down again to a specific detection.
On the event information screen, you get all of the details associated with that detection. It includes the computer name, start time, containment status, and filename as well as any related CrowdStrike Intelligence reports.
What actions can customers take from the QRadar interface?
Using the “CrowdStrike Sensor ID” field, you can manage the containment status of the system.
You can choose to “Contain” a system, or “Lift Containment” as needed.
Looking to the “CrowdStrike Detect ID” you also have the ability to manage the detection status.
Options for detection status include “In Progress”, “True Positive”, “False Positive” and “Ignored”. This option gives you the ability to manage work flows while updating both the QRadar and CrowdStrike event status fields.
Open Detection Event
Using the “CrowdStrike Falcon Host Link” you can also open the specific detection in the CrowdStrike UI to view the entire process tree.
Crowdstrike understands that companies have existing security tools and SIEM products like IBM’s QRadar. Our API first approach makes it possible for you to leverage the CrowdStrike event data as needed to optimize your workflows and maximize the efforts of your overworked security staff.
- CrowdStrike 15-Day Free Trial
- CrowdStrike Tech Center
- Sign up for a weekly Falcon demo
- Request a 1:1 Demo
- Guide to AV Replacement
- CrowdStrike Products
- White Paper on Falcon OverWatch
How to Contain an Infected System
Hi, there. My name’s Peter Ingebrigtsen. And today, we’ve logged into the falcon.crowdstrike.com, or the Falcon User Interface.
And what we’re going to do is take a look at some of our systems and recognize that some of them are either currently under attack or recently been under attack, and may have been compromised. And we’d like to contain that system until we can further get to it, get our hands on it, and get a little bit more information out of it, or just prevent it from doing any more damage than it’s already done.
In order to do that, you need to be on your Detections app. You can do that by going to the radar here on the left-hand side. If you’re not already, or if your user interface doesn’t open that when you first log in, head there. And then just select the Recent Detections.
When that opens, you’ll notice that you can filter by any number of criteria, but we’re looking at some of the more recent events or situations that are going on. And you’ll notice that the same single machine has noticed a lot of different scenarios with privilege escalation or web exploits. And these severities are high to critical.
And we’d like to log in there, maybe do a little something, take a little closer look, and see if there’s something we should do. Obviously, we should do something. And as we start to dig through here, we see that there’s a lot of detection patterns, whether that be known malware, credential theft, or web exploits. We can see in the process tree a lot of different commands that were issued that look at that privilege escalation that we noticed earlier– or start to set that up.
So, we know that there’s something bad going on, and we’d like to take action right away. So, what we want to do is network contain this machine. But what I want to show you, as well, is that as we do this– I’m going to go to the machine itself. And I’d like to start a continuous ping so that you can watch the behavior and how long it takes to respond to this network containment.
Now, while we contain this– or take this machine off the network– we don’t kill the connection to the CrowdStrike Cloud. So, that as we get our hands on it– we clean it up, we feel comfortable putting it back on to the network– we can still operate or control that machine through the user interface that we have here.
The other thing I’d like to do is start a large download, so that we initiate with a single TCP connection– and there happens to be one in process– as opposed to the ping, where there may be multiple TCP resets or individual TCP threads going every time. So that you can see that as we contain this machine, it literally just knocks it off the network.
Forgive my screen, but I’ve changed the resolution for YouTube and for appearance purposes.
But as I come in here– and this will be right at the middle of the screen– this actually says Device Actions. And I’d like to contain it.
Now, as we do that, we have some options to make some notes. Contained by Peter. Multiple threats observed. Whatever notes you’d like to make– and then select Contain.
Now, the second we do this, on the left-hand side, you’ll see how quickly it takes for that to respond. So, immediately, almost in real time, you see a network failure on the download, and the ping test– or the continuous ping fail. So, we can close that.
Now, let’s say we’re a couple days later, this machine’s cleaned up, ready to go, and be put back in the network. You can go ahead and lift the network containment, again, from the user interface. We still have that connection to the machine, even though all the other network connections have been terminated.
So, as we do that, all good. Uncontain. And you’ll notice that almost immediately that ping starts to fire right back up again.
So, network containment is a powerful tool that we can use if we see something immediately taking action or if we see something recently in the past, and we’d like to get that machine off the network– almost quarantine it– so that it can’t do any more damage.
So, this has been network containment of network devices in the Falcon Sensor User Interface platform. Thanks again for watching.