WEBVTT

00:00:00.000 --> 00:00:03.405
So we've kind of established the baseline I want to follow,

00:00:03.405 --> 00:00:05.227
fileless malware is going to be.

00:00:05.227 --> 00:00:05.976
But really,

00:00:05.976 --> 00:00:08.893
knowing that we have to shift from signature analysis to behavior

00:00:08.893 --> 00:00:11.575
analysis to be able to catch this kind of stuff.

00:00:11.575 --> 00:00:14.349
And the first step in that is find out how it works.

00:00:14.349 --> 00:00:14.740
Exactly.

00:00:14.740 --> 00:00:17.364
It's really important to understand how,

00:00:17.364 --> 00:00:20.807
what these techniques are because there are multiple

00:00:20.807 --> 00:00:23.131
techniques that the attackers are going to use in their

00:00:23.132 --> 00:00:25.599
fileless attacks and the fileless malware.

00:00:25.599 --> 00:00:28.622
And by looking and understanding at least what the patterns

00:00:28.622 --> 00:00:30.676
of those are or what they may look like,

00:00:30.676 --> 00:00:34.430
then you're going to be able to look at a system

00:00:34.430 --> 00:00:36.546
and recognize when that occurred.

00:00:36.546 --> 00:00:37.726
So you mentioned PowerShell.

00:00:37.727 --> 00:00:39.627
That was one that came up, and that's probably a biggie.

00:00:39.627 --> 00:00:42.346
Can you explain a little more about what that would look like and how it's used?

00:00:42.347 --> 00:00:42.725
Yeah.

00:00:42.725 --> 00:00:46.862
PowerShell has been on Windows systems since I think Windows 7.

00:00:46.862 --> 00:00:49.838
It's been available before that, but it's been standard since Windows 7.

00:00:49.838 --> 00:00:53.886
Yeah, v2 in Windows 7 made remoting a lot easier and things.

00:00:53.886 --> 00:00:56.448
And PowerShell is just like it sounds.

00:00:56.448 --> 00:00:57.598
I mean, it's extremely powerful.

00:00:57.599 --> 00:01:00.608
Let's face it, it can pretty much do anything.

00:01:00.609 --> 00:01:03.064
The security world has kind of embraced PowerShell,

00:01:03.064 --> 00:01:07.644
and so there are lots of PowerShell based attack toolkits out there.

00:01:07.645 --> 00:01:10.192
There are forensic toolkits based around PowerShell.

00:01:10.192 --> 00:01:13.339
It can pretty much do anything that you want to on the system,

00:01:13.339 --> 00:01:15.858
and even better, you can script everything out.

00:01:15.858 --> 00:01:18.827
So you don't have to be in front of a GUI anymore

00:01:18.827 --> 00:01:21.011
in order to administer a system.

00:01:21.012 --> 00:01:24.009
Well, attackers have realized this,

00:01:24.009 --> 00:01:29.058
and they use this to their advantage because PowerShell is ready to run on

00:01:29.058 --> 00:01:32.130
pretty much every Windows operating system that's out there,

00:01:32.130 --> 00:01:34.098
in an enterprise at least.

00:01:34.099 --> 00:01:36.137
They can use it to download additional malware.

00:01:36.137 --> 00:01:40.968
They can use it to inject into other processes to make themselves persist.

00:01:40.968 --> 00:01:42.753
There is just so much that can be done.

00:01:42.753 --> 00:01:44.973
It's pretty rare nowadays, I think,

00:01:44.973 --> 00:01:50.503
to see an attack that does not involve PowerShell.

00:01:50.504 --> 00:01:56.162
And so from a perspective of using batch scripts or VBS versus PowerShell,

00:01:56.163 --> 00:01:59.174
I imagine PowerShell has a lot more access to the underlying OS.

00:01:59.174 --> 00:02:00.283
Is that the advantage there?

00:02:00.283 --> 00:02:01.101
It is.

00:02:01.101 --> 00:02:02.739
That's the exact advantage.

00:02:02.740 --> 00:02:06.631
One of the advantages to attackers too is that depending on

00:02:06.631 --> 00:02:08.401
the version of PowerShell that you're using,

00:02:08.401 --> 00:02:11.187
there may be very little logging by default.

00:02:11.187 --> 00:02:16.489
With PowerShell 2, which is the standard version in Windows 7 by default,

00:02:16.489 --> 00:02:20.947
I think maybe even Windows 10 may come with PowerShell 2 by default,

00:02:20.948 --> 00:02:23.229
it has very little logging that occurs.

00:02:23.230 --> 00:02:26.347
As PowerShell has progressed from 3, to 4,

00:02:26.348 --> 00:02:30.542
to 5, you get more and more default logging and in PowerShell 5,

00:02:30.542 --> 00:02:31.465
you have a lot.

00:02:31.465 --> 00:02:35.248
and PowerShell 5 will even log suspicious things by default,

00:02:35.248 --> 00:02:38.004
suspicious activity that occurs in PowerShell by default.

00:02:38.004 --> 00:02:41.230
However, as a defender or as an investigator,

00:02:41.230 --> 00:02:43.590
you want to have it logging everything,

00:02:43.590 --> 00:02:49.035
and so there's additional things that you need to turn on in order to

00:02:49.036 --> 00:02:51.685
find this fileless malware that's using PowerShell.

00:02:51.685 --> 00:02:53.136
And in some environments,

00:02:53.136 --> 00:02:57.549
command line is kind of not allowed to be used by users,

00:02:57.550 --> 00:02:59.848
but then PowerShell is still available.

00:02:59.848 --> 00:03:00.613
It is.

00:03:00.614 --> 00:03:02.517
Some people of kind of caught on, Group Policy or whatever,

00:03:02.517 --> 00:03:04.917
to be able to able to lock down the command line to only admin users,

00:03:04.917 --> 00:03:08.325
but users still have full reign over PowerShell.

00:03:08.326 --> 00:03:10.388
It can still be executed.

00:03:10.389 --> 00:03:14.962
There are some restrictions that you can put into place to prevent scripts

00:03:14.962 --> 00:03:18.647
that are downloaded from being executed through PowerShell.

00:03:18.647 --> 00:03:20.049
Unsigned scripts.

00:03:20.049 --> 00:03:22.278
Exactly, but those are easily bypassed.

00:03:22.278 --> 00:03:23.971
Yeah, I think I've done that myself quite a bit.

00:03:23.972 --> 00:03:28.093
You just, even in the environments where command line is not available,

00:03:28.093 --> 00:03:30.688
you can still run batch scripts because batch scripts are apart of

00:03:30.688 --> 00:03:33.883
Windows and a lot of the scheduled tasks use those.

00:03:33.883 --> 00:03:34.676
And then you can just,

00:03:34.676 --> 00:03:38.099
it's literally an attack that says attack bypass execution policy,

00:03:38.099 --> 00:03:39.861
and then your policy doesn't matter.

00:03:39.861 --> 00:03:41.186
Yup, that's exactly it.

00:03:41.186 --> 00:03:44.564
It's so easy to bypass that it's really not a,

00:03:44.564 --> 00:03:47.556
nobody should be using that as a security protection.

00:03:47.557 --> 00:03:51.290
You just assume that the attacker is going to be able to get past that.

00:03:51.291 --> 00:03:53.020
I think that's a security protection from people

00:03:53.020 --> 00:03:54.017
who aren't trying to attack you.

00:03:54.017 --> 00:03:54.415
Exactly.

00:03:54.415 --> 00:03:58.992
One quick Google search and you will find out how to get around it.

00:03:58.992 --> 00:03:59.781
Thanks, Google.

00:03:59.781 --> 00:04:01.781
Yup, exactly.
