PowerShell visibility is a necessity when investigating today’s threats. CrowdStrike provides the most comprehensive solution to detect, discover, and investigate PowerShell activity in your organization.
To detect PowerShell using CrowdStrike Falcon all you need is a system with the Falcon Sensor installed and PowerShell activity.
Different Levels of Visibility
PowerShell is versatile and can be used in a lot of different ways. A key to detecting both benign and malicious PowerShell activity is the ability to monitor it no matter how it’s used. Different ways PowerShell can be run is from a script, from a command prompt both clear text and encoded, and from an interactive user session.
Falcon PowerShell Visibility
3 Different Ways to Investigate PowerShell Activity
Many vendors claim they can identify details when PowerShell is used in an attack, and that’s very important, but it is also limiting. Because malicious PowerShell use often looks like legitimate, CrowdStrike doesn’t limit the amount of visibility when it comes to PowerShell. Below are three examples of the many ways that CrowdStrike can help you identify and understand PowerShell activity in your environment.
Events Search Page
Navigate to the Investigate App then Events Search. In this case I can search for all commands typed on a host by searching the command history
Another option is to use the Host search option that lists the activity, including PowerShell Activity, in a single window. The Host search can be located inside a detection, from the host app, or directly from a detection. The most direct approach is to open the Investigate App, then open the Host Search page.
PowerShell in a Detection
Another location where PowerShell information is displayed is directly in a detection. Even if the command itself isn’t malicious, the use of PowerShell will be visible inside the detection and the command used will be displayed.
In this instance we can see that another application actually launched PowerShell then used PowerShell as a tool to download a malicious payload. All that information is displayed in the alert.
CrowdStrike knows that detecting malicious binaries is important but it’s not always enough. Today’s attacks often leverage benign tools to carry out their malicious intent. With the visibility in Falcon, CrowdStrike customers have what they need to hunt, detect and stop threats, regardless of the tools they use.
- CrowdStrike 15-Day Free Trial
- Sign up for a weekly Falcon demo
- Request a 1:1 Demo
- Guide to AV Replacement
- CrowdStrike Products
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.