In this video and article, we will look at the integration available between CrowdStrike and Dragos – a CrowdStrike Store partner. The Dragos app enables CrowdStrike customers to analyze their existing Falcon agent data for any evidence of ICS and OT-focused adversaries operating in their IT environment.
Dragos is focused on protecting the world’s most critical infrastructure from adversaries. Their expertise around industrial security software and services adds a layer of knowledge to better arm CrowdStrike customers that support industrial operations. Because the CrowdStrike agent and event data is largely comprised of IT systems, this integration enables companies to be more proactive and effective in protecting their industrial operations from compromise.
Integration in the Dragos UI
The Overview page provides a visual representation of existing CrowdStrike event data through an Operational Technology lens. Dragos applies their specialized set of indicators to provide early warning of how and where activity groups focused on operational technology might be operating in the enterprise endpoint environment. That is critical as the adversary often targets IT systems as a pivot point to the more critical OT environments. The graph will illustrate any detected spikes in activity from Dragos known adversaries.
Dragos also provides additional details on the OT adversaries including capabilities, common targets, and mode of operations.
The event tab gives you the ability to see additional details for events where Dragos detecting adversary activity. The list includes the CrowdStrike event ID, event date, event type and device ID. Correlated with that are the specific indicator, related indicator type, confidence level, kill chain from Dragos.
Using the CrowdStrike event ID, customers can leverage the Event Search function of the Falcon UI to find the specific event in question. By pivoting to the process explorer view, all of the related processes and details are shown in a graphical, process tree view. This visual representation provides context to the single event by including all of the associated activities including the initial attack vector, parent processes, and command line details.
The Dragos app enables CrowdStrike customers to analyze their existing agent data for ICS- or OT-focused adversaries operating in their IT environment. Expanding visibility and leveraging the specialized IOCs and adversary information from Dragos allows companies to proactively protect their critical industrial operations, and reduce potential negative impacts on safety, reliability and productivity. Being able to apply that knowledge and then investigate and take action from the CrowdStrike UI helps customers minimize risks and stop breaches.
You can begin your trial of Dragos today directly in the CrowdStrike store.
- CrowdStrike 15-Day Free Trial
- CrowdStrike Tech Center
- Sign up for a weekly Falcon demo
- Request a 1:1 Demo
- Guide to AV Replacement
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.