WEBVTT

00:00:00.000 --> 00:00:03.030
And there are other ways that you can detect all of the other technique.

00:00:03.030 --> 00:00:07.328
We've kind of focused on PowerShell, but we talked about WMI.

00:00:07.329 --> 00:00:13.215
WMI is being used more and more by attackers, and so you can use Sysmon.

00:00:13.216 --> 00:00:18.649
Sysmon does really good at looking for WMI logs or logging WMI activity,

00:00:18.649 --> 00:00:22.843
and then you can go in and look at those WMI logs to see what activity that was,

00:00:22.843 --> 00:00:25.429
and again, baseline your systems.

00:00:25.430 --> 00:00:27.039
Look to see what the normal activity is,

00:00:27.039 --> 00:00:30.570
and then you can pull out the anomalous activity.

00:00:30.571 --> 00:00:34.119
If you wanted to look on systems for things like the event subscriptions

00:00:34.119 --> 00:00:37.567
through WMI that attackers are using for persistence,

00:00:37.568 --> 00:00:40.772
Autoruns is a great tool that will do that.

00:00:40.772 --> 00:00:42.687
Another Sysinternals tools.

00:00:42.688 --> 00:00:46.136
one of the things that it pulls out are all WMI subscriptions.

00:00:46.136 --> 00:00:52.379
The forensics PowerShell scripts Kansa.

00:00:52.379 --> 00:00:56.936
They will also, you can use those to pull out WMI event subscriptions as well.

00:00:56.936 --> 00:01:00.398
So let's say you didn't want to run Autoruns on all your systems,

00:01:00.398 --> 00:01:02.585
you could write a PowerShell script and deploy that everywhere,

00:01:02.585 --> 00:01:03.575
and just pull those out,

00:01:03.575 --> 00:01:06.853
and throw those into a database or an ELK stack and

00:01:06.853 --> 00:01:08.889
just kind of look at the anomalies.

00:01:08.890 --> 00:01:09.668
Like we said,

00:01:09.668 --> 00:01:14.637
when you look at all of the different systems across your organization,

00:01:14.638 --> 00:01:18.994
you should only have pretty much the same event subscriptions on all of them.

00:01:18.994 --> 00:01:23.635
So as you stack all of the ones that you pull back and list them,

00:01:23.635 --> 00:01:28.025
if one system has an event subscription that's not in the other system,

00:01:28.025 --> 00:01:31.875
you should definitely look at that to see why is that anomaly there.

00:01:31.875 --> 00:01:35.753
So you use the unique case as the indicator of compromise --- Right, yes.

00:01:35.753 --> 00:01:36.503
--- or likely.

00:01:36.503 --> 00:01:37.400
Right.

00:01:37.400 --> 00:01:37.921
Yeah, that's great.

00:01:37.921 --> 00:01:40.610
And I think what's really cool too is everything we've talked

00:01:40.610 --> 00:01:44.509
about for this kind of cutting edge detection stuff for

00:01:44.509 --> 00:01:46.308
instant response and investigation.

00:01:46.309 --> 00:01:47.810
We didn't really mention any commercial things,

00:01:47.810 --> 00:01:51.206
and I'm sure there is commercial stuff starting to catch up.

00:01:51.206 --> 00:01:53.482
But it seems that as attackers develop different methodologies,

00:01:53.482 --> 00:01:56.267
the first thing to catch up is going to be hey,

00:01:56.268 --> 00:01:58.615
you can write a PowerShell script to detect those.

00:01:58.616 --> 00:01:58.926
Exactly.

00:01:58.926 --> 00:02:00.792
And a lot of people have.

00:02:00.792 --> 00:02:03.842
There are some really brilliant security people out there,

00:02:03.842 --> 00:02:06.443
and they're using PowerShell to detect all of this,

00:02:06.444 --> 00:02:10.234
or they're releasing free tools in order to help you detect all of this.

00:02:10.235 --> 00:02:15.007
And I know a lot of organizations are maybe a little bit hesitant to

00:02:15.007 --> 00:02:17.007
use open-source tools or freely available tools,

00:02:17.008 --> 00:02:19.990
but if the commercial tool doesn't have it,

00:02:19.991 --> 00:02:21.839
you need to have something that does it.

00:02:21.840 --> 00:02:25.979
And if the tool is free with no cost, you can't beat that,

00:02:25.979 --> 00:02:28.517
and it works, and definitely go for it.

00:02:28.518 --> 00:02:32.122
If you encourage your people to use these open-source methodologies and tools,

00:02:32.123 --> 00:02:33.490
they're also going to be learning how things work

00:02:33.490 --> 00:02:35.185
because not all this stuff is like a nice,

00:02:35.185 --> 00:02:35.574
pretty GUI.

00:02:35.575 --> 00:02:38.850
You have to kind of know what you're looking for any why.

00:02:38.850 --> 00:02:39.290
Exactly.

00:02:39.290 --> 00:02:43.110
There is a difference between the skill of an analyst and the

00:02:43.110 --> 00:02:47.799
maturity of an organization when you have people that know to point

00:02:47.799 --> 00:02:51.030
and click in a GUI and get the results versus somebody who

00:02:51.030 --> 00:02:52.997
understands what's going on in the background.

00:02:52.997 --> 00:02:54.279
So when that GUI breaks,

00:02:54.279 --> 00:02:57.244
they can still get at that information and do that analysis,

00:02:57.244 --> 00:02:59.385
and that's really what sets apart the mature organizations

00:02:59.385 --> 00:03:01.733
from the ones that are just starting out.

00:03:01.733 --> 00:03:02.122
Yeah, excellent.

00:03:02.122 --> 00:03:04.191
And I think anyone watching can take even just some

00:03:04.191 --> 00:03:06.913
of the stuff you just did now, run that on some of your boxes,

00:03:06.913 --> 00:03:09.250
and see if there's some stuff that you don't know about.

00:03:09.250 --> 00:03:09.573
Exactly.

00:03:09.573 --> 00:03:11.902
And not only what we're talking about,

00:03:11.902 --> 00:03:14.749
there's obviously so much more regarding this,

00:03:14.749 --> 00:03:17.415
and throwing it back to us.

00:03:17.415 --> 00:03:19.550
Pluralsight has a lot of the training that will

00:03:19.550 --> 00:03:21.368
teach you all of this stuff as well.

00:03:21.369 --> 00:03:22.539
And so if nothing else,

00:03:22.539 --> 00:03:25.536
that is a huge resource to help mature your organization to

00:03:25.536 --> 00:03:27.555
get it to the point that it needs to be.

00:03:27.556 --> 00:03:30.733
And as you learn how maybe you go do some security for

00:03:30.733 --> 00:03:32.675
development stuff and you start learning like oh yeah,

00:03:32.675 --> 00:03:33.222
this is how.

00:03:33.442 --> 00:03:34.103
NET code works,

00:03:34.103 --> 00:03:36.699
and here is how I could search for that and what those strings would look like,

00:03:36.699 --> 00:03:40.569
maybe write your own DeepBlueCLI for your code compiling.

00:03:40.570 --> 00:03:44.587
The next generation of security people or analysts who are writing

00:03:44.587 --> 00:03:47.848
these tools are coming up in the environment now.

00:03:47.848 --> 00:03:50.918
And so having these tools to kind of use and base their

00:03:50.918 --> 00:03:53.914
stuff off of means that in 1 year, or 5 years,

00:03:53.914 --> 00:03:59.134
10 years from now, we're just going to be so much better off as an industry.
