In this article and video, we will see how the Indicator Graph provides us a visual representation of how indicators map to hosts in our environment as well as CrowdStrike Intelligence data.
Accessing Falcon Indicator Graph
There are three different ways to access the Falcon Indicator Graph.
With Falcon X, quarantined files are automatically sent to the sandbox for analysis. For those detections, you can link directly to an indicator graph from the “Execution Details” under “Sandbox Analysis”. Clicking on the highlighted icon will present a pre-populated indicator graph based on the strict IOC’s associated with the analyzed file.
When you are researching a specific adversary or report, you will also see the option to open the related indicator graph as shown below.
Similarly, you can open the indicator graph from within the sandbox report.
Using the Falcon Indicator Graph Intelligence
The Falcon Indicator Graph allows you to visualize the connections between a given indicator, CrowdStrike’s Intelligence data, and hosts in your environment. This helps speed up investigations while providing valuable context about the potential adversary and larger campaign. On the graph, the indicators are shown in the middle with Intel data to the left and host information to the right.
When an indicator is linked to CrowdStrike Intelligence information, it can help you learn about and understand the methods and motivations of adversaries. By clicking on the Intel report icon in this example, you see the connecting lines highlighted. We are also presented with an overview of the report as well as an option to view the complete report. In this example, we learn that the file is attributed to Cobalt Spider.
Looking to the right side of the graph, clicking on the “hosts” icon will expand a list of hosts that have event data containing these particular indicators. Like with Intel, this will highlight the lines connecting that host to the indicators and Intel attributes. You also have the option to expand and see the specific host’s detailed information.
Building a Custom Falcon Indicator Graph
You can also start with any indicator(s) and build your own graph. Indicators can be IPs, domains or file hashes. You can access this option from the Indicators App under Intelligence.
By clicking on “Create indicator graph” you are prompted with the screen to add your own input.
You can also add indicators to an existing graph using the “+” icon outlined below.
Falcon Indicator Graph empowers analysts to quickly visualize incidents, enrich investigations, and take action to improve the organization’s overall security posture.
- 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
- 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.