In this video and article, we will look at the integration available between CrowdStrike and TrueFort – a CrowdStrike Store partner. TrueFort can leverage the existing CrowdStrike agent and event data to provide application visibility and security..
TrueFort’s real time application mapping gives security, application, and operations teams unparalleled visibility to understand the environment in the context of applications and identify unusual behaviors. The value of TrueFort’s solution can be immediately realized given the CrowdStrike agent is installed and collecting the necessary event data.
Integration in the TrueFort UI
Based on the CrowdStrike event data, TrueFort’s UI can provide a real time visual representation of how applications are communicating in your environment. In this example, we see three applications communicating.
From this view, you can drill down on a specific application to see the details behind both external and internal communications.
In this application view, the middle section illustrates a three tier application. There are web servers, application servers, and database servers. The lines indicate expected communication between the backup servers and the database server. In addition, the web server primarily communications with the app server while the app server connects to the database server.
There is also the option to drill down to look at a specific server to understand what processes are actively running and how they are communicating.
TrueFort provides an illustration of the exact processes responsible for each network connection along with information about the destination. TrueFort’s machine learning and profiling capabilities help establish baselines so that unusual and potentially suspect activity can be identified.
In this example, we saw rogue communication of a workstation connecting directly to a database server which may indicate data exfiltration. Having the visibility to identify this is kind of unusual behavior is critical to helping us identify process and security gaps. We can use the hostname from the TrueFort alert and search for that managed system in the CrowdStrike UI. Even without a CrowdStrike detection event, we can take action to network contain the system and use real time response to investigate further.
Combining the power of CrowdStrike’s event data with TrueFort’s application visibility tools yields immediate value to your organization. TrueFort’s machine learning can use the existing telemetry data to determine baseline behaviors, offer visibility into how applications are communicating, and highlight unusual activity.
You can begin your trial of TrueFort 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
- 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.