This document and video will demonstrate how Falcon Spotlight provides a one-click solution to prioritized patching.
Patch deployment is often scheduled as part of a regular maintenance window. However, there may be occasions where patching can’t wait, such as a newly disclosed vulnerability with known exploits that, if left unpatched, would expose the organization to significant risk.
With the Falcon platform, security practitioners now have the ability to identify critical vulnerabilities, and also address those vulnerabilities with one-off patch deployment. Spotlight users can now take advantage of a 1-click action to deploy Windows Update patches to specific hosts.
In the Falcon Console, on the Spotlight dashboard we can get a quick overview of vulnerabilities currently in our organization. Not only can we easily filter on the dashboard it also provides for easy visualization of vulnerabilities. There is also a section that provides top recommendation, the KB associated and the number of vulnerabilities this patch would cover.
After selecting a specific host or recommended patch will provide additional details and access to the “Install Patch” button. Clicking the ‘Install Patch’, the host’s local Windows Update service will attempt to download and install the patch. A success message indicates that the process has started, not that it has completed; depending on the size of the patch, this could take some time.
When the patching process is complete, there are two ways to confirm that the patch was successfully installed. The “Installed Patches” Falcon console link will take you to a page within Spotlight, where you can check to see if the patch was successfully installed on that host. Because it may take some time for the sensor to report a newly installed patch, clicking the “Connect to Host” button will allow us to use RTR to check the patch status quickly.
In conjunction with the emergency patching feature, Real Time Response has also added the “Update” command which provides patching functionality via the RTR console. By typing “help update” we see the options available. To find out if my recent patch installation attempt was successful, I can use ‘update query’ to see if a patch was recently installed.
The output includes additional details such as the patch title and description. The ‘update history’ command can be used to view recent updates and their status. We could also use the ‘update query’ command in conjunction with a KB number to get more details about that specific KB. If we see that there are no longer updates available for that host, that would indicate that the patch installation was successful.
When there’s a trending vulnerability that cannot be addressed quickly enough through the normal patch process, Spotlight’s “patch now” feature enables users to easily and surgically remediate vulnerabilities, reduce their attack surface, and proactively decrease chances of being breached due to unpatched vulnerabilities.
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.