WEBVTT

00:00:00.000 --> 00:00:02.978
So we've talked a little bit about how these things work,

00:00:02.978 --> 00:00:06.414
these fileless malware attacks, and we gave an example in the last module,

00:00:06.414 --> 00:00:10.120
and then we've also talked kind of briefly about why attackers would

00:00:10.120 --> 00:00:12.924
use these because they can evade different things,

00:00:12.924 --> 00:00:15.863
but really, there's a bunch of ways to attack a system,

00:00:15.863 --> 00:00:19.751
or there's a bunch of different methods of exploits that malware uses.

00:00:19.751 --> 00:00:22.193
Why is this becoming so prevalent?

00:00:22.194 --> 00:00:27.765
Well, it really comes down to the fact that it's difficult to detect.

00:00:27.765 --> 00:00:31.866
The logging that is turned on on Windows systems by default,

00:00:31.866 --> 00:00:37.055
and unfortunately, most organizations, they don't turn logging on,

00:00:37.055 --> 00:00:40.047
or they don't enhance logging much past the defaults.

00:00:40.047 --> 00:00:42.699
And so a lot of this is not being logged,

00:00:42.699 --> 00:00:44.867
a lot of this activity is not being logged,

00:00:44.867 --> 00:00:49.133
and so these techniques become stealthy for the attackers.

00:00:49.134 --> 00:00:51.521
I mean, not only that, if you're living off the land,

00:00:51.521 --> 00:00:53.413
if you're using PowerShell, and you're using WMI,

00:00:53.413 --> 00:00:56.566
and you're using the tools that are already installed on the system,

00:00:56.566 --> 00:00:58.758
that means you don't have to download additional tools,

00:00:58.758 --> 00:01:02.288
which means you have less of a footprint on the system and on the network.

00:01:02.288 --> 00:01:05.449
It means that you know that the tools are already there.

00:01:05.450 --> 00:01:09.135
It's very easy for you to test because as an attacker,

00:01:09.135 --> 00:01:11.368
if I was going to attack an organization,

00:01:11.368 --> 00:01:13.144
I want to test my tools out beforehand,

00:01:13.144 --> 00:01:16.672
and if they have some custom Windows image,

00:01:16.672 --> 00:01:21.964
that means that my malware may not work like I expect it too.

00:01:21.965 --> 00:01:23.896
But if I use PowerShell,

00:01:23.896 --> 00:01:27.564
I know that the PowerShell on my computer is probably going to

00:01:27.564 --> 00:01:29.698
be the same PowerShell as on your computer.

00:01:29.698 --> 00:01:31.641
And so if I test it on my computer and it works,

00:01:31.641 --> 00:01:33.804
it's probably going to work on yours as well.

00:01:33.804 --> 00:01:34.990
Yeah, because it's part of the base OS.

00:01:34.990 --> 00:01:40.320
It's not like a third-party software that has to be enabled like a lot of the

00:01:40.320 --> 00:01:43.642
lower CVSS stuff that's coming out now that's like if this,

00:01:43.642 --> 00:01:47.813
and this, and this, then this exploit works whereas this is,

00:01:47.813 --> 00:01:52.036
yeah, it's on every single system and definitely going to be usable.

00:01:52.037 --> 00:01:55.037
Yeah, that's interesting.
