This document and video will demonstrate Falcon X and the benefits of automating threat intelligence.
- Subscription: Falcon Prevent, Falcon X
Automated File Submission
Falcon X is designed to automatically provide detailed malware analysis that is integrated as part of the alert to help analysts save time and make effective security decisions.
Below, we see a Falcon prevention event that also resulted in a quarantined file.
As we scroll down in the details pane, we see that the quarantined file was also sent to the sandbox for analysis. That happened automatically with no intervention from the administrator.
We immediately see useful context from the Falcon X analysis directly in the UI. In addition to the summary risk assessment, you have the option to download both strict and broad Indicators of Compromise (IOCs). You can also open the complete sandbox report. It provides additional analysis details including the threat level and score. There are three options to drill further into the report: Report Summary, Network Activity, and Advanced Analysis.
Under Report Summary, you can view the more details risk assessment and get information on related malware in the “Malquery” section. This information comes from CrowdStrike’s extensive malware database and can help you understand if this attack is part of a larger initiative. You can understand if you have been the target of similar attacks in the past. If not, you can use that information to get proactive in protecting against those other files in the future.
From the Falcon UI, you have the option to download IOC’s related to the analyzed malware. Those could include things like known bad domains or IP addresses. That information can be used with other security tools to block access to known bad sites via firewalls, web content filters or IPS devices.
For malware with actor attribution, there is the option to open the complete actor profile and better understand who is attacking your organization. The actor profile contains additional IOC’s for the actor including known Command and Control servers and IPs. In many cases, you will also see a list of commonly exploited vulnerabilities. This information can help you ensure your environment is patched and protected from a targeted bad actor attack.
Falcon X fully automates the analysis process, incorporates threat intelligence, and yields actionable intelligence information. It provides greater context so that security analysts can be faster and more effective as they learn from attacks and strive to protect the larger organization.
- 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.