WEBVTT

00:00:00.041 --> 00:00:02.059
So we're going to be talking about fileless malware,

00:00:02.059 --> 00:00:06.591
and really, the first question is is what is fileless malware beyond a buzzword?

00:00:06.592 --> 00:00:10.754
So fileless malware is a really a class of malware or attacker

00:00:10.754 --> 00:00:14.203
techniques that use operating system commands that are already

00:00:14.204 --> 00:00:15.816
installed in the operating system.

00:00:15.816 --> 00:00:17.973
The attackers live off the land.

00:00:17.974 --> 00:00:23.774
And while fileless malware sounds like it doesn't leave behind any files at all,

00:00:23.774 --> 00:00:25.313
that's really a misnomer.

00:00:25.314 --> 00:00:28.222
There are often files that are left behind by the

00:00:28.222 --> 00:00:29.923
malware or used in the attacks.

00:00:29.923 --> 00:00:35.883
There are very few attackers or malware that leave no files left behind at all.

00:00:35.883 --> 00:00:38.630
Yeah, so there's not much that doesn't leave some sort of artifact,

00:00:38.630 --> 00:00:42.989
and that's how we can hunt for it.

00:00:42.989 --> 00:00:47.342
They're going to use the tools that are installed in the system like PowerShell,

00:00:47.343 --> 00:00:49.267
the C# Compiler, living in the registry,

00:00:49.268 --> 00:00:51.946
and other techniques like that to maintain persistence on the

00:00:51.946 --> 00:00:54.126
system and really just hide from the defenders.

00:00:54.126 --> 00:00:58.255
So these are tools that have to be enabled or are already enabled so

00:00:58.255 --> 00:01:00.754
you can make system administration a little easier.

00:01:00.755 --> 00:01:03.542
I know I used PowerShell all the time when I was in my

00:01:03.542 --> 00:01:05.442
comeuppance in system administration and automation,

00:01:05.441 --> 00:01:09.028
and you can't really disable that and still be able to manage your environment,

00:01:09.029 --> 00:01:10.894
but then the attacker can also use that.

00:01:10.894 --> 00:01:11.162
Exactly.

00:01:11.162 --> 00:01:13.747
You know, all of the tools, like PowerShell,

00:01:13.747 --> 00:01:14.235
WMI,

00:01:14.235 --> 00:01:17.708
that the systems administrators use to manage all

00:01:17.708 --> 00:01:19.466
the systems within an enterprise,

00:01:19.466 --> 00:01:21.496
the attackers are using those to their advantage.

00:01:21.497 --> 00:01:26.240
So it becomes very difficult for the defenders to both find that activity out

00:01:26.240 --> 00:01:29.637
of all of the noise that's happening from the normal systems administration

00:01:29.637 --> 00:01:33.495
and hone in on what the malicious activity is.

00:01:33.495 --> 00:01:36.134
Talking about that, maybe give me an example.

00:01:36.135 --> 00:01:36.487
Sure.

00:01:36.487 --> 00:01:39.474
So the classic example is a user surfing the web,

00:01:39.474 --> 00:01:42.423
and they click on the wrong link and go to a malicious site that

00:01:42.423 --> 00:01:46.327
loads up let's say a malicious flash file.

00:01:46.328 --> 00:01:47.133
It's always flash.

00:01:47.133 --> 00:01:51.033
And instead of the flash file downloading additional malware where it

00:01:51.033 --> 00:01:54.466
would be actually downloading a file onto the system.

00:01:54.466 --> 00:01:58.225
Instead, it runs, let's say, a PowerShell command.

00:01:58.225 --> 00:02:00.623
And that PowerShell command in turn goes out,

00:02:00.623 --> 00:02:03.752
downloads something from the internet from another malicious site,

00:02:03.752 --> 00:02:05.661
but instead of dropping it to the disk,

00:02:05.661 --> 00:02:08.342
it actually just loads it directly into memory,

00:02:08.342 --> 00:02:11.230
and so the malware is now running in-memory.

00:02:11.231 --> 00:02:13.545
It's never touched the disk,

00:02:13.546 --> 00:02:16.723
and that malware that's running in-memory may store

00:02:16.723 --> 00:02:18.658
itself directly in the registry.

00:02:18.658 --> 00:02:23.366
And yeah, the ones who really know what's going on are going to say well,

00:02:23.367 --> 00:02:29.452
the internet cache has files in it, the registry is technically a file,

00:02:29.452 --> 00:02:33.780
but the malware itself has never really touched the disk.

00:02:33.780 --> 00:02:36.806
That's where the fileless malware name comes from.

00:02:36.806 --> 00:02:38.257
Yeah, that's what the moniker fileless malware is.

00:02:38.257 --> 00:02:41.378
It's not that there are no files involved or there's no artifacts involved.

00:02:41.378 --> 00:02:44.481
It's that the stuff streams directly in-memory and that the

00:02:44.481 --> 00:02:46.408
malicious part is deobfuscated memory,

00:02:46.408 --> 00:02:48.814
and then it is really difficult for things to detect.

00:02:48.814 --> 00:02:53.255
The malicious part never touches disk, and so some of the traditional tools,

00:02:53.255 --> 00:02:54.103
like antivirus,

00:02:54.103 --> 00:02:58.897
that may have a tougher time seeing things in-memory or seeing things that

00:02:58.897 --> 00:03:02.404
are getting injected into other processes on it within Windows are going

00:03:02.404 --> 00:03:04.811
to have more a difficult time to find that.

00:03:04.811 --> 00:03:07.334
And as analysts and investigators,

00:03:07.334 --> 00:03:12.184
when we go in to start looking to see why is this system acting weird,

00:03:12.184 --> 00:03:15.321
we typically look at timelines, and disk forensics,

00:03:15.321 --> 00:03:16.938
and things along those lines.

00:03:16.938 --> 00:03:20.279
That won't work in these cases because, like I said,

00:03:20.279 --> 00:03:22.275
there's no malware on the disk.

00:03:22.275 --> 00:03:25.430
It's all in-memory or it's all being hidden in the registry or other places,

00:03:25.430 --> 00:03:27.591
so we have to use different techniques.

00:03:27.592 --> 00:03:30.186
So you have to look for how it established persistence,

00:03:30.186 --> 00:03:31.899
if it established persistence,

00:03:31.899 --> 00:03:35.617
or use other tangential information to kind of identify

00:03:35.617 --> 00:03:37.335
something is going on weird with the system.

00:03:37.335 --> 00:03:37.665
Exactly.

00:03:37.665 --> 00:03:37.996
Exactly.

00:03:37.996 --> 00:03:39.272
I like that you said weird.

00:03:39.272 --> 00:03:41.212
So like that's kind of a common security operations

00:03:41.212 --> 00:03:44.079
incident response word that I like to use.

00:03:44.080 --> 00:03:47.295
It's not always a signature analysis or like a AV sig.

00:03:47.295 --> 00:03:48.713
It isn't always going to work.

00:03:48.713 --> 00:03:50.979
We need to look for things like what's weird is really,

00:03:50.979 --> 00:03:52.784
pretty much describes my job.

00:03:52.785 --> 00:03:53.271
Oh yeah.

00:03:53.271 --> 00:03:54.242
That is absolutely it.

00:03:54.243 --> 00:03:58.956
I mean, when we talk about hunting, hunting has been around for years and years.

00:03:58.957 --> 00:04:01.334
It's just kind of become that buzzword within the last couple years,

00:04:01.334 --> 00:04:04.475
but it all stems down to that analysist sitting there

00:04:04.475 --> 00:04:06.679
watching things that are going on and go hmm,

00:04:06.679 --> 00:04:08.488
that looks a little odd.

00:04:08.489 --> 00:04:09.807
Let me look into that a bit more.

00:04:09.807 --> 00:04:12.358
And that's what you really have to do in these cases.

00:04:12.358 --> 00:04:14.167
You have to look for those anomalies.

00:04:14.168 --> 00:04:15.763
You have to look at your tools.

00:04:15.763 --> 00:04:19.096
Antivirus does a--- antivirus is antivirus.

00:04:19.096 --> 00:04:21.673
It's going to do the best it can.

00:04:21.673 --> 00:04:24.262
ERD system, endpoint detection and response systems,

00:04:24.262 --> 00:04:27.316
tend to work a little bit better with detecting fileless malware

00:04:27.316 --> 00:04:30.369
just because they're looking for those anomalies.

00:04:30.369 --> 00:04:32.710
They're helping us find those anomalies that are

00:04:32.710 --> 00:04:34.578
occurring on the systems as they run.

00:04:34.579 --> 00:04:37.689
So we get a little bit into behavior analysis where we're essentially

00:04:37.689 --> 00:04:40.020
playing the one of these things is not like the other game.

00:04:40.020 --> 00:04:42.636
Establish the baseline and find what's weird.

00:04:42.637 --> 00:04:43.315
Exactly.

00:04:43.315 --> 00:04:43.993
Exactly.

00:04:43.993 --> 00:04:45.315
So are we going to, in this course,

00:04:45.315 --> 00:04:47.599
we're probably going to take a look at some examples?

00:04:47.600 --> 00:04:52.064
Yeah, we're going to look at how does fileless malware work.

00:04:52.065 --> 00:04:55.779
We'll show you a couple examples of how they work.

00:04:55.779 --> 00:04:58.033
I've got a couple systems here that I've already

00:04:58.033 --> 00:04:59.289
compromised with fileless malware,

00:04:59.289 --> 00:05:02.143
and so we'll go in and we'll look and see how we can

00:05:02.143 --> 00:05:04.199
detect it and what we need to do to Windows in order to

00:05:04.199 --> 00:05:09.374
actually find this type of thing.
