WEBVTT

00:00:00.000 --> 00:00:03.435
Even with Event Log Explorer, it's pretty powerful.

00:00:03.435 --> 00:00:06.043
We could search through things pretty quickly.

00:00:06.044 --> 00:00:08.220
Well, what if we don't know what to look for.

00:00:08.220 --> 00:00:10.096
If we're a new analyst, if you're a junior analyst,

00:00:10.096 --> 00:00:12.019
you may not know what to look for,

00:00:12.020 --> 00:00:14.192
and so there are some tools there that will help you out.

00:00:14.192 --> 00:00:16.654
So I'm going to run one of those tools.

00:00:16.654 --> 00:00:21.064
Let me close this out, close all this out.

00:00:21.064 --> 00:00:24.149
And the tool I'm going to run is a PowerShell tool,

00:00:24.149 --> 00:00:24.606
and again,

00:00:24.606 --> 00:00:27.859
I'm running this as an administrator only because I want to make sure that my

00:00:27.859 --> 00:00:30.305
tool can see everything on the system and it's not restricted.

00:00:30.305 --> 00:00:34.129
You need admin rights to be able to see the security logs.

00:00:34.129 --> 00:00:36.501
So there's a tool here called DeepBlueCLI,

00:00:36.501 --> 00:00:40.135
and DeepBlue is a tool that is going to go in and it's going to scan

00:00:40.135 --> 00:00:42.631
your event logs in looking for anything anomalous.

00:00:42.632 --> 00:00:45.927
So we've already seen on the system what happened,

00:00:45.927 --> 00:00:50.268
what the attacker did, we have the encoded PowerShell and all that,

00:00:50.268 --> 00:00:51.549
but we had to search for it.

00:00:51.549 --> 00:00:56.085
So what I'm going to do is I'm going to run DeepBlue and hit Enter,

00:00:56.085 --> 00:01:00.447
and you can see that it went through,

00:01:00.447 --> 00:01:05.533
and not only did it find all of the stuff that we found,

00:01:05.534 --> 00:01:07.644
it actually tells us where it found it, when it occurred,

00:01:07.644 --> 00:01:10.014
and then it has why it flagged this.

00:01:10.014 --> 00:01:11.363
So in the case right here,

00:01:11.364 --> 00:01:14.866
we can see that it determined this was a suspicious command line

00:01:14.866 --> 00:01:19.383
because it found 500 plus consecutive Base64 characters,

00:01:19.383 --> 00:01:21.752
so a really long Base64 string,

00:01:21.753 --> 00:01:24.760
it sees the Base64 Encoded function being listed there,

00:01:24.760 --> 00:01:28.696
and then it also sees a download through the PowerShell.

00:01:28.697 --> 00:01:30.504
So it flagged it all for us.

00:01:30.504 --> 00:01:33.263
As an analyst, I may not think to look for all of this,

00:01:33.263 --> 00:01:36.812
or I may not even have the capability to look for all of this.

00:01:36.812 --> 00:01:37.799
And maybe some obscure endpoint.

00:01:37.799 --> 00:01:38.756
You're not looking,

00:01:38.756 --> 00:01:42.851
you're not mainly searching through every log of every endpoint all the time.

00:01:42.851 --> 00:01:43.225
Exactly.

00:01:43.225 --> 00:01:46.636
And tools like DeepBlue will help you do that.

00:01:46.636 --> 00:01:48.192
You can automate it.

00:01:48.192 --> 00:01:50.576
You could, if you're doing forensics,

00:01:50.576 --> 00:01:54.589
you can pull out the Windows event logs and tell DeepBlue to look for it,

00:01:54.589 --> 00:01:58.345
and it's a really great way to very quickly go in and triage a

00:01:58.345 --> 00:02:01.657
system to determine if it's been compromised or not.

00:02:01.657 --> 00:02:04.785
Yeah, so we've kind of gone from let's look for a specific ID,

00:02:04.785 --> 00:02:07.176
and we know Microsoft doing PowerShell is weird,

00:02:07.176 --> 00:02:09.895
but again, when we talked about getting lost in the noise,

00:02:09.895 --> 00:02:12.178
PowerShell is used for admin stuff all the time.

00:02:12.178 --> 00:02:15.567
So simply searching for a PowerShell string can really lead you

00:02:15.568 --> 00:02:19.456
astray depending on how active your admin guys are.

00:02:19.456 --> 00:02:20.490
On the system,

00:02:20.490 --> 00:02:24.012
I had cleared the logs before I ran it just so we

00:02:24.012 --> 00:02:25.700
could have something clean to look at.

00:02:25.700 --> 00:02:27.903
But if this was an organization's system that the

00:02:27.903 --> 00:02:29.055
administrators were using PowerShell,

00:02:29.055 --> 00:02:31.716
there would be probably literally thousands of logs that

00:02:31.716 --> 00:02:33.665
we would have had to gone through.

00:02:33.665 --> 00:02:38.095
And a tool like this very quickly will pull out the bad stuff for us.

00:02:38.096 --> 00:02:40.341
Yeah, so this just learned some of those bad things,

00:02:40.341 --> 00:02:44.229
here being the Base64 or even seeing entropy in

00:02:44.229 --> 00:02:46.656
strings that indicates it's encoded.

00:02:46.656 --> 00:02:50.713
So that really helps narrow you down, and then you can generate alerts from that.

00:02:50.713 --> 00:02:54.301
And it's even kind of written like an alert, like Base64 encoded function.

00:02:54.301 --> 00:03:01.051
That's the name of my alert.

00:03:01.051 --> 00:03:03.301
Yeah exactly.
