WEBVTT

00:00:00.054 --> 00:00:02.270
We talked about persistence and the file has to exist somewhere.

00:00:02.270 --> 00:00:02.586
Generally,

00:00:02.586 --> 00:00:05.208
that's the registry or maybe there's a temp directory or

00:00:05.208 --> 00:00:07.689
a temp file that's created temporarily as things are

00:00:07.689 --> 00:00:10.081
moving through and into memory.

00:00:10.081 --> 00:00:12.579
But I think when I was reading through kind of the

00:00:12.579 --> 00:00:13.472
stuff we were going to talk about,

00:00:13.473 --> 00:00:16.607
another question I have is what if they're not worried about persistence?

00:00:16.607 --> 00:00:19.458
Is there any artifact at all left over?

00:00:19.458 --> 00:00:22.980
If an attacker decides that they're not worried about persistence,

00:00:22.980 --> 00:00:26.695
and I have seen attacks like this before from some pretty

00:00:26.695 --> 00:00:28.665
advanced attackers where they get on the system,

00:00:28.665 --> 00:00:33.015
they load their malware into memory, and then they don't set up persistence,

00:00:33.015 --> 00:00:36.116
there could be very little to nothing left behind.

00:00:36.117 --> 00:00:40.802
I mean, you may get a couple log messages indicating that something happened.

00:00:40.802 --> 00:00:43.481
But beyond that, if the attacker is good enough,

00:00:43.481 --> 00:00:45.630
and like you said, they don't care about persistence,

00:00:45.630 --> 00:00:49.652
because persistence is going to leave some artifact behind,

00:00:49.653 --> 00:00:52.806
it could be very difficult to detect them.

00:00:52.807 --> 00:00:53.686
Or if you do detect them,

00:00:53.686 --> 00:00:57.572
it could be very difficult to almost impossible to

00:00:57.572 --> 00:01:00.312
recover anything related to what they did.

00:01:00.313 --> 00:01:04.911
Let's take the situation of an attacker gets on a system,

00:01:04.911 --> 00:01:06.723
they compromise it,

00:01:06.723 --> 00:01:09.338
they use fileless malware techniques so their tools

00:01:09.338 --> 00:01:13.382
are loaded directly into memory, they've been injected directly into memory,

00:01:13.382 --> 00:01:16.827
and they don't set up persistence so there's no artifacts in there.

00:01:16.827 --> 00:01:17.821
They do what they want to do,

00:01:17.821 --> 00:01:21.632
and then they cause the system to reboot so you don't have that memory

00:01:21.632 --> 00:01:25.616
that you can grab anymore that has that tool in place.

00:01:25.617 --> 00:01:28.986
After the reboot, you're struck.

00:01:28.987 --> 00:01:31.566
As a defender, there is really not much you can do.

00:01:31.566 --> 00:01:34.677
You can kind of hope that maybe something got written to the

00:01:34.677 --> 00:01:39.200
page file that you can maybe pull out, maybe--- If you get there in time.

00:01:39.200 --> 00:01:41.310
---if you get there in time,

00:01:41.310 --> 00:01:44.506
maybe you will get lucky and there was some network traffic if you

00:01:44.506 --> 00:01:46.993
were recording network traffic that you can use.

00:01:46.993 --> 00:01:50.018
But beyond that, you're kind of stuck.

00:01:50.018 --> 00:01:53.048
And I've seen attacks like this before, and I've seen this happen.

00:01:53.048 --> 00:01:55.052
And from the defender side,

00:01:55.052 --> 00:01:58.406
there is not much you can do at that point except

00:01:58.406 --> 00:02:00.854
for try to infer what they did.

00:02:00.855 --> 00:02:01.014
Yeah.

00:02:01.014 --> 00:02:02.820
So you definitely have to be watching for this if

00:02:02.820 --> 00:02:04.878
this is something you want to catch,

00:02:04.878 --> 00:02:08.601
and it also kind of speaks to it's not just malware.

00:02:08.601 --> 00:02:10.889
This isn't just kind of broad.

00:02:10.889 --> 00:02:13.357
I want to spread out some malware for ransomware and to get

00:02:13.357 --> 00:02:15.209
somebody to pay me some Bitcoin or something.

00:02:15.209 --> 00:02:17.662
We're also talking about individual targeted attacks where you

00:02:17.662 --> 00:02:19.775
can load not just the exploit in the memory,

00:02:19.775 --> 00:02:22.937
but you can load tools that can be actively used.

00:02:22.938 --> 00:02:24.795
You bring up a good point as well.

00:02:24.796 --> 00:02:29.294
This isn't, these techniques are becoming more and more common,

00:02:29.294 --> 00:02:34.134
so you are seeing them with commodity malware.

00:02:34.134 --> 00:02:38.136
You are seeing them start to happen with the attacker whose

00:02:38.136 --> 00:02:42.021
goal is to install Bitcoin miners on a system.

00:02:42.022 --> 00:02:44.070
So those would definitely leave things behind.

00:02:44.071 --> 00:02:48.217
You install a coin miner on there, it's going to spike the CPU,

00:02:48.217 --> 00:02:51.353
you're going to leave files behind, and all that.

00:02:51.354 --> 00:02:54.154
But the root cause of how it happened, which is,

00:02:54.154 --> 00:02:57.679
as an investigator, that's one of the things that I want to try to find,

00:02:57.680 --> 00:02:59.200
that may not be there.

00:02:59.200 --> 00:03:03.590
And so those techniques are being used just by those advanced attackers,

00:03:03.590 --> 00:03:06.130
at the APT A very targeted.

00:03:06.130 --> 00:03:06.967
---a very targeted,

00:03:06.967 --> 00:03:14.051
as well as the commodity hackers who are just trying to make money essentially.

00:03:14.051 --> 00:03:16.451
Yeah right.
