WEBVTT

00:00:00.223 --> 00:00:00.401
Yeah,

00:00:00.401 --> 00:00:03.435
and so I think we'll talk a little bit more about what's good

00:00:03.435 --> 00:00:05.435
versus bad coming up in some of the next module.

00:00:05.435 --> 00:00:07.991
We'll get some more experience with that.

00:00:07.992 --> 00:00:11.680
I know--- what types of things use these techniques?

00:00:11.681 --> 00:00:16.530
I know tools like PowerShell Empire I've used before for some threat emulation.

00:00:16.530 --> 00:00:18.512
I've loaded Meterpreter into memory and kind of done,

00:00:18.512 --> 00:00:21.301
and run Mimikatz using that and kind of looked at what that

00:00:21.301 --> 00:00:23.963
looks like from an attack perspective.

00:00:23.964 --> 00:00:25.995
What other tools do you know of that can use those?

00:00:25.995 --> 00:00:29.080
Because that's part of the issue with the prevalence is that

00:00:29.080 --> 00:00:30.973
you can just download something from GitHub.

00:00:30.973 --> 00:00:31.359
Yeah,

00:00:31.359 --> 00:00:34.687
a lot of these popular offensive frameworks have

00:00:34.687 --> 00:00:36.485
incorporated these techniques already.

00:00:36.485 --> 00:00:39.482
So like Empire that you mentioned and Metasploit,

00:00:39.482 --> 00:00:42.599
these already have those in there, Metasploit with Meterpreter.

00:00:42.600 --> 00:00:44.434
Meterpreter essentially sits in memory.

00:00:44.435 --> 00:00:50.041
So everything that it can do is a fileless attack in itself.

00:00:50.041 --> 00:00:52.015
Cobalt Strike, PowerSploit.

00:00:52.015 --> 00:00:57.018
There are just so many of these tools out there that you can,

00:00:57.018 --> 00:00:58.658
that anybody can download and use.

00:00:58.658 --> 00:01:00.718
And once you get on the system,

00:01:00.718 --> 00:01:04.898
you could use those to pivot and use these fileless malware techniques,

00:01:04.899 --> 00:01:10.636
and it's going to evade a lot of detections just by doing that.

00:01:10.637 --> 00:01:13.566
Yeah, and Cobalt Strike, that's just kind of the Gucci version of Armitage.

00:01:13.566 --> 00:01:15.943
It's just kind of like Kali Distro.

00:01:15.944 --> 00:01:17.233
So with that, I mean,

00:01:17.233 --> 00:01:20.729
that's--- I encourage people generally to go download these things we just

00:01:20.729 --> 00:01:24.244
talked about and then run then and in a safe environment,

00:01:24.244 --> 00:01:26.694
and then figure out whether you're catching that or not.

00:01:26.694 --> 00:01:27.580
Yeah, it is.

00:01:27.580 --> 00:01:29.352
That is really the best way.

00:01:29.353 --> 00:01:32.962
What it comes down to is, as defenders,

00:01:32.962 --> 00:01:37.089
in order for us to find these fileless malware attacks,

00:01:37.089 --> 00:01:41.933
the best thing for us to do is to go out and start looking for them.

00:01:41.934 --> 00:01:43.939
We can't rely on our tools, our antivirus,

00:01:43.939 --> 00:01:46.988
and our EDR, and everything else, to detect it for us.

00:01:46.988 --> 00:01:49.686
And when it detects it for us, that's awesome.

00:01:49.687 --> 00:01:50.980
It's great when that happens.

00:01:50.980 --> 00:01:52.526
But when it comes down to it,

00:01:52.526 --> 00:01:54.907
you still need to go out and start looking for these.

00:01:54.907 --> 00:01:59.096
And really, the way to do that is to set up proper logging on the systems,

00:01:59.097 --> 00:02:01.014
and once you have that proper logging on the systems,

00:02:01.014 --> 00:02:03.410
then you're going to be able to find these attacks.

00:02:03.411 --> 00:02:03.946
Yeah, absolutely,

00:02:03.946 --> 00:02:06.219
and that's all part of the maturity of your security

00:02:06.219 --> 00:02:08.696
operations team and your instance response.

00:02:08.696 --> 00:02:08.979
Awesome.

00:02:08.979 --> 00:02:10.395
And yeah, so moving forward,

00:02:10.395 --> 00:02:13.641
I think we're going to here soon take a look at some more examples and look at

00:02:13.641 --> 00:02:15.676
some good versus bad and some tools on how to catch this.

00:02:15.676 --> 00:02:15.887
Yeah,

00:02:15.887 --> 00:02:19.350
we're going to figure out what do we need to do in Windows systems in

00:02:19.350 --> 00:02:21.453
order to enhance that logging and find this stuff.

00:02:21.453 --> 00:02:24.303
Yeah, and then to the naysayers who say why do you always talk about Windows?

00:02:24.304 --> 00:02:27.582
It's well, because the world uses Windows, and that's what gets attacked.

00:02:27.583 --> 00:02:33.583
Yup, that's exactly what it is.
