WEBVTT

00:00:00.112 --> 00:00:01.178
So talking about these logs.

00:00:01.178 --> 00:00:02.622
I mean, it's great that we centralize them and everything,

00:00:02.622 --> 00:00:03.569
but which logs do we actually enable?

00:00:03.569 --> 00:00:05.649
Can you show me some of those and what that looks like?

00:00:05.649 --> 00:00:11.187
So let's jump on, and what I'm going to do is we have a Windows 7 system here,

00:00:11.187 --> 00:00:13.591
we're just going to go through and look at all the

00:00:13.591 --> 00:00:15.465
different logs that we can turn on.

00:00:15.466 --> 00:00:16.869
Well, let me rephrase that.

00:00:16.869 --> 00:00:19.055
We're not going to look at every log that we can turn on

00:00:19.055 --> 00:00:21.516
because that would take a little while.

00:00:21.516 --> 00:00:26.091
I highly recommend looking at the cheat sheets in order to determine that.

00:00:26.091 --> 00:00:27.945
If you're going to turn on specific logs,

00:00:27.946 --> 00:00:31.190
I'm going to show you the logs that you should at least at a minimum turn on.

00:00:31.190 --> 00:00:32.002
Okay, that's great.

00:00:32.002 --> 00:00:33.971
Like a good baseline log configuration.

00:00:33.971 --> 00:00:40.591
And would you possibly--- Why doesn't every log already come enabled?

00:00:40.591 --> 00:00:44.307
Why wouldn't we already have that as a baseline with Windows?

00:00:44.307 --> 00:00:48.848
Mostly because, well, probably because logs still take up space,

00:00:48.848 --> 00:00:53.854
and there is even a very, very minor performance hit.

00:00:53.855 --> 00:00:58.287
And Microsoft, I think, wants Windows to be customizable for everybody,

00:00:58.287 --> 00:01:00.904
and so not everybody may want this.

00:01:00.905 --> 00:01:03.712
They may not want to have all that extra disk space taken up.

00:01:03.712 --> 00:01:05.217
In fact, if you look at the cheat sheets,

00:01:05.217 --> 00:01:09.561
they recommend having it's something like 100 GB at

00:01:09.561 --> 00:01:14.107
least for your security logs, or something really large.

00:01:14.107 --> 00:01:15.489
Yeah, for it to archive into.

00:01:15.489 --> 00:01:18.254
Yeah, at least in towards the gigabyte range,

00:01:18.254 --> 00:01:21.144
maybe it's like 500 MB, but it's still very large,

00:01:21.144 --> 00:01:24.083
much bigger than what the defaults are.

00:01:24.084 --> 00:01:26.226
And that's a lot of space for some people,

00:01:26.226 --> 00:01:28.639
and they may not want to have that turned on.

00:01:28.640 --> 00:01:28.895
Yeah.

00:01:28.895 --> 00:01:31.247
And that speaks to, and I'm sure you'll show me,

00:01:31.247 --> 00:01:33.561
is when we're in the logs you can set them to archive,

00:01:33.561 --> 00:01:37.510
or you can set them to overwrite, and you can increase the size of the logs.

00:01:37.510 --> 00:01:41.872
But even the max size of the log is pretty small and doesn't,

00:01:41.873 --> 00:01:43.647
like if we're looking at something like a domain controller,

00:01:43.647 --> 00:01:44.907
will fill in.

00:01:44.907 --> 00:01:47.387
I've seen domain controller logs fill in 2 minutes.

00:01:47.388 --> 00:01:48.872
So if you're not archiving, then it's gone.

00:01:48.872 --> 00:01:49.109
Exactly.

00:01:49.109 --> 00:01:52.408
So one of the things that we're going to turn on is

00:01:52.408 --> 00:01:55.942
logging for process execution, and I just want to show you this beforehand.

00:01:55.942 --> 00:02:01.133
So I'm just going to clear the security logs here, and so now they're cleared.

00:02:01.134 --> 00:02:01.790
Just like an attacker.

00:02:01.790 --> 00:02:03.220
Just like an attacker.

00:02:03.221 --> 00:02:11.834
I'm going to launch a Command Prompt, and I'm just going to run Notepad,

00:02:11.834 --> 00:02:16.317
and we'll run it with, let's see if I can find a file to open up here,

00:02:16.317 --> 00:02:18.980
actually, we'll just run it with Notepad.

00:02:18.980 --> 00:02:21.457
And if we go in here into the security logs,

00:02:21.457 --> 00:02:26.580
refresh it, you see nothing showed up.

00:02:26.580 --> 00:02:30.658
There was no indication that I launched a Command

00:02:30.658 --> 00:02:34.641
Prompt or I launched the Notepad.

00:02:34.642 --> 00:02:37.201
So we're going to go in, and we're going to turn those on.

00:02:37.202 --> 00:02:38.910
And that's not just a Notepad thing.

00:02:38.910 --> 00:02:41.389
That's anything we'd launch.

00:02:41.389 --> 00:02:43.506
Windows is doing tons of stuff in the background right now.

00:02:43.506 --> 00:02:45.776
None of that's being logged.

00:02:45.776 --> 00:02:48.097
So the best way to do it is to go into Group Policy.

00:02:48.097 --> 00:02:53.463
We're going to want to edit the Group Policy on the local system.

00:02:53.463 --> 00:02:54.642
This can also be done remotely.

00:02:54.643 --> 00:02:56.587
This can also be done remotely with Active Director,

00:02:56.587 --> 00:02:58.613
pushing out of Group Policy, and so on.

00:02:58.613 --> 00:03:01.847
And in fact, if you're in an organization, this is how you would do it.

00:03:01.848 --> 00:03:04.190
You wouldn't go around to every single system.

00:03:04.190 --> 00:03:12.377
So what you want to do is go to the Computer Configuration to Windows Settings,

00:03:12.377 --> 00:03:17.168
let me open that up, Security Settings,

00:03:17.168 --> 00:03:20.206
and then down here under Advanced Audit Policy Configuration,

00:03:20.206 --> 00:03:22.915
you'll see System Audit Policies,

00:03:22.915 --> 00:03:27.003
and these are all the different logs that you can turn on.

00:03:27.004 --> 00:03:31.793
Now these are all of the category, on the right-hand side here,

00:03:31.793 --> 00:03:35.245
we're seeing all of the different categories of logs that you can turn on.

00:03:35.246 --> 00:03:37.253
I see they all say Not configured.

00:03:37.253 --> 00:03:41.580
This is a default install, so nothing is configured by default.

00:03:41.581 --> 00:03:44.555
So here, when I go to Detailed Tracking,

00:03:44.556 --> 00:03:45.374
I'm going to drill down,

00:03:45.374 --> 00:03:48.764
we can see a number of different logs that we can turn on or off.

00:03:48.764 --> 00:03:52.589
And the ones that we really want to turn on are the Audit

00:03:52.589 --> 00:03:55.234
Process Creation and Audit Process Termination.

00:03:55.235 --> 00:03:58.303
So I'm just going to double-click on those and then Configure.

00:03:58.303 --> 00:04:00.971
I want to see both Success and Fail events.

00:04:00.971 --> 00:04:04.106
Yeah, and that's a good point too, success versus failure.

00:04:04.106 --> 00:04:05.031
It's really good to see first.

00:04:05.031 --> 00:04:07.094
You need to know when it fails also.

00:04:07.094 --> 00:04:08.635
And then I'm also going to turn on Audit Process

00:04:08.635 --> 00:04:12.985
Termination just so as an investigator, it's often useful for me to know,

00:04:12.985 --> 00:04:15.489
not only when a process started, but also,

00:04:15.489 --> 00:04:16.947
when it stopped.

00:04:16.947 --> 00:04:18.273
So if we stopped right here,

00:04:18.273 --> 00:04:21.963
we would be logging Process Creation and Process

00:04:21.963 --> 00:04:23.533
Termination events within the log.

00:04:23.534 --> 00:04:25.906
As soon as you click OK, it's doing it on the system,

00:04:25.906 --> 00:04:28.060
which is great; however,

00:04:28.061 --> 00:04:31.085
we're going to enhance it a little bit more because we want to

00:04:31.085 --> 00:04:32.699
see everything that that process is doing.

00:04:32.699 --> 00:04:39.306
And so what I'm going to do is I'm going to go back up here to the Group Policy.

00:04:39.306 --> 00:04:43.780
I'm going to go, let me minimize this,

00:04:43.780 --> 00:04:46.954
I'm going to go down from the Computer Configuration,

00:04:46.954 --> 00:04:53.656
to Administrative Templates, to System, and then up here,

00:04:53.656 --> 00:04:54.599
Audit Process Creation.

00:04:54.600 --> 00:04:57.280
And you can see there's one item in here called Include

00:04:57.280 --> 00:04:59.457
command line in process creation events.

00:04:59.457 --> 00:05:02.223
And what this will do when we enable it is,

00:05:02.223 --> 00:05:05.790
not only is it going to show us when a process starts,

00:05:05.791 --> 00:05:07.664
it's going to show us the entire command line.

00:05:07.665 --> 00:05:13.331
So think back to our demo with the PowerShell and the EncodedCommand.

00:05:13.331 --> 00:05:16.825
If we had not turned this on, we would just see that PowerShell started up,

00:05:16.825 --> 00:05:17.474
which is great.

00:05:17.475 --> 00:05:19.489
It's great to know that PowerShell would start up.

00:05:19.489 --> 00:05:20.820
However, by turning this on,

00:05:20.820 --> 00:05:23.598
we're also going to see PowerShell -Encoded and

00:05:23.598 --> 00:05:25.409
then that base-64-encoded string.

00:05:25.409 --> 00:05:29.068
So it makes logging much more powerful for us to detect this,

00:05:29.068 --> 00:05:32.924
and we'll look at a couple tools later on that will actually use this

00:05:32.924 --> 00:05:35.475
information to detect these attacks automatically for us.

00:05:35.476 --> 00:05:35.719
Awesome.

00:05:35.719 --> 00:05:40.377
So this is an enabling capability for other tools to be able to detect it.

00:05:40.377 --> 00:05:44.117
So I'm just clicking Enabled, OK, and then I am good to go.

00:05:44.117 --> 00:05:45.590
I'm just to minimize this.

00:05:45.590 --> 00:05:47.065
If we refresh here,

00:05:47.065 --> 00:05:50.962
we can already see that there a number of logs that have already been created.

00:05:50.962 --> 00:05:56.592
The ones that you want to focus on for process creation are 4688 events.

00:05:56.592 --> 00:05:58.596
And let me do this, so I'm going to go back here,

00:05:58.596 --> 00:06:01.952
I'm going to launch Notepad, and I'm going to give it a file to open up.

00:06:01.953 --> 00:06:02.265
Okay.

00:06:02.265 --> 00:06:04.449
I'm giving it something on command line.

00:06:04.449 --> 00:06:07.984
So when I hit Enter, it opens that up.

00:06:07.985 --> 00:06:09.300
Great.

00:06:09.300 --> 00:06:13.246
Let me refresh.

00:06:13.246 --> 00:06:18.157
And here, if we open up and go into this,

00:06:18.158 --> 00:06:21.950
we can see not only do we show that Notepad was open,

00:06:21.950 --> 00:06:25.264
but we can see the command line, and we see exactly what it opened up,

00:06:25.265 --> 00:06:27.260
what was giving it to it on the command line.

00:06:27.260 --> 00:06:28.385
Go back to the PowerShell thing,

00:06:28.385 --> 00:06:32.089
we would see PowerShell alt -Encoded and so on right here in our logs.

00:06:32.090 --> 00:06:34.437
And we were essentially logging these, we would have that as well.

00:06:34.438 --> 00:06:35.216
That's awesome.

00:06:35.216 --> 00:06:39.199
And so with that, if I just double-click say an icon,

00:06:39.200 --> 00:06:42.285
does that show, it'll show up and say no command line?

00:06:42.285 --> 00:06:42.853
It will.

00:06:42.853 --> 00:06:44.813
You may either have no command line,

00:06:44.813 --> 00:06:48.526
or if that icon it actually has a command line in the

00:06:48.526 --> 00:06:51.097
background within the launch for that program,

00:06:51.097 --> 00:06:53.143
then it would show up here as well.

00:06:53.143 --> 00:06:56.857
So if the shortcut runs a command line to open the program,

00:06:56.857 --> 00:06:58.575
then it will show up.

00:06:58.576 --> 00:07:00.696
Which is great because generally the attack is not

00:07:00.696 --> 00:07:02.608
running around clicking stuff, like that's not,

00:07:02.608 --> 00:07:03.831
but the users are.

00:07:03.832 --> 00:07:05.355
So you can look at things that don't have command lines

00:07:05.355 --> 00:07:08.332
and kind of discard those as well, they're just opening up Word.

00:07:08.333 --> 00:07:09.091
That's not a big deal.

00:07:09.092 --> 00:07:14.062
But if Word was open via command line, then that's a little more interesting.

00:07:14.062 --> 00:07:16.079
So we turned on process creation,

00:07:16.080 --> 00:07:18.395
which is definitely something that's you'll want to do.

00:07:18.395 --> 00:07:20.659
Let's also talk about PowerShell.

00:07:20.660 --> 00:07:25.141
PowerShell is used for a lot of attacks like we've already seen.

00:07:25.141 --> 00:07:27.517
Beyond just what we saw, the little snippet that we saw,

00:07:27.517 --> 00:07:30.364
there can be a lot more that's going on that PowerShell can do,

00:07:30.364 --> 00:07:33.464
and so you definitely want to turn on even more logging.

00:07:33.465 --> 00:07:40.122
So what we'll do in order to do that is we'll jump back to Group Policy.

00:07:40.122 --> 00:07:42.890
The great thing is all of this stuff can be configured in Group Policy.

00:07:42.890 --> 00:07:46.963
You can configure it centrally, and so you're good to go.

00:07:46.964 --> 00:07:49.400
The way that I'm going to configure it is for PowerShell 5,

00:07:49.400 --> 00:07:51.658
and we'll talk a little bit about how you can do this

00:07:51.658 --> 00:07:54.588
for PowerShell 2 through 4 as well.

00:07:54.588 --> 00:07:58.881
But for PowerShell 5, you go to the Computer Configuration.

00:07:58.881 --> 00:08:01.642
We're going to go back down to Administrative Templates,

00:08:01.643 --> 00:08:06.484
to Windows Components, and then somewhere in here,

00:08:06.484 --> 00:08:09.162
there should be a Windows PowerShell.

00:08:09.163 --> 00:08:09.920
There it is.

00:08:09.920 --> 00:08:11.435
So here, we've got Windows PowerShell.

00:08:11.435 --> 00:08:15.268
And Windows PowerShell has a number of different logs that you can turn on.

00:08:15.269 --> 00:08:17.427
We're not going to turn on every single one of these

00:08:17.427 --> 00:08:19.777
because some of them can be very verbose,

00:08:19.777 --> 00:08:22.688
and they can just add to the noise.

00:08:22.689 --> 00:08:24.759
So we're only going to look at, turn on a couple.

00:08:24.759 --> 00:08:28.254
the first thing that we're going to do is we're going to turn on Module Logging.

00:08:28.255 --> 00:08:30.069
Module Logging,

00:08:30.069 --> 00:08:35.420
whenever a module within PowerShell gets started up like a program,

00:08:35.419 --> 00:08:37.224
or if it loads a library, or things like that,

00:08:37.224 --> 00:08:41.148
when we turn this on, it will start logging it,

00:08:41.148 --> 00:08:47.201
and so that will give us somewhat of a transcript of what

00:08:47.201 --> 00:08:51.025
the PowerShell was doing as it ran.

00:08:51.025 --> 00:08:51.333
Excellent.

00:08:51.333 --> 00:08:52.875
Yeah, it's just additional information.

00:08:52.875 --> 00:08:54.393
Transcript is a great word for it.

00:08:54.393 --> 00:08:59.109
It's the step by step of happened, and modules loading are part of that.

00:08:59.109 --> 00:09:01.182
So here, in order to enable that, I click on Enabled.

00:09:01.182 --> 00:09:03.622
And then down here, you could see Show icon,

00:09:03.622 --> 00:09:07.645
or the Show button, was turned on, so I click Show.

00:09:07.645 --> 00:09:07.927
And here,

00:09:07.927 --> 00:09:12.474
this is where you would list all of the module names that you want it to log.

00:09:12.474 --> 00:09:14.668
But what we're going to do is we're just going to put * in

00:09:14.668 --> 00:09:16.661
there because we want it to log everything.

00:09:16.661 --> 00:09:18.859
Thanks, asterisk.

00:09:18.859 --> 00:09:19.321
Exactly.

00:09:19.321 --> 00:09:19.447
Yeah,

00:09:19.447 --> 00:09:21.453
I was like I don't know that we're going to be able to put

00:09:21.453 --> 00:09:22.566
every single module we want in there.

00:09:22.566 --> 00:09:23.028
That's a lot.

00:09:23.028 --> 00:09:23.196
No.

00:09:23.196 --> 00:09:26.569
So you just, you tell it to log everything, and then it started to log.

00:09:26.569 --> 00:09:28.478
The next thing that we're going to do is we're going to

00:09:28.478 --> 00:09:30.436
turn on PowerShell Script Block Logging.

00:09:30.436 --> 00:09:33.400
This is pretty easy to do.

00:09:33.400 --> 00:09:36.454
This will log anytime, actually,

00:09:36.455 --> 00:09:40.401
this logs a lot of the commands and functions that get loaded into PowerShell.

00:09:40.401 --> 00:09:46.756
So you can almost pull out the exact code that the attacker is running.

00:09:46.756 --> 00:09:47.377
And sometimes,

00:09:47.377 --> 00:09:51.913
I know for using an invoke command or a remote command that's

00:09:51.914 --> 00:09:54.152
executing additional PowerShell somewhere else,

00:09:54.152 --> 00:09:58.212
sometimes the attack is called script block.

00:09:58.212 --> 00:10:03.994
So likely, without those turned on, we're not getting anything except for yeah,

00:10:03.995 --> 00:10:05.660
invoke command was ran, which is great,

00:10:05.661 --> 00:10:09.266
but we need to know what script was ran inside of there.

00:10:09.266 --> 00:10:10.247
And this is really easy to do.

00:10:10.248 --> 00:10:11.991
You just click Enabled.

00:10:11.992 --> 00:10:16.110
You do have an option of Log script block invocation start/stop events.

00:10:16.110 --> 00:10:16.875
I don't turn that on.

00:10:16.875 --> 00:10:19.065
I would not recommend turning that on because that's

00:10:19.065 --> 00:10:20.884
what generates a lot of noise.

00:10:20.884 --> 00:10:24.543
So but with just enabling this, it's more than sufficient for what we need.

00:10:24.544 --> 00:10:26.251
So that's the second thing that we're going to turn on.

00:10:26.251 --> 00:10:30.117
The third thing that we're going to turn on is actual PowerShell Transcription,

00:10:30.117 --> 00:10:34.752
and what this means is you can think of this as once we turn this on,

00:10:34.753 --> 00:10:37.845
it's almost like we are sitting behind the attacker looking over

00:10:37.845 --> 00:10:40.662
their shoulder as they're using PowerShell.

00:10:40.663 --> 00:10:46.966
We're going to get exact logs of everything that happened within PowerShell.

00:10:46.966 --> 00:10:49.036
So the way we do that is we have to enable it,

00:10:49.036 --> 00:10:52.533
and then we need to actually set up a directory to log it to.

00:10:52.534 --> 00:10:58.869
And so I'm just going to set up a directory here called transcripts.

00:10:58.870 --> 00:11:00.184
So you have to tell all the data where to go.

00:11:00.184 --> 00:11:02.543
Yeah, you have to tell the data where to go.

00:11:02.543 --> 00:11:04.788
I can see that being interesting for some tools to use too.

00:11:04.788 --> 00:11:08.185
That makes it a centralized location for all the information.

00:11:08.185 --> 00:11:08.560
Exactly.

00:11:08.560 --> 00:11:11.192
And yeah, you can absolutely do this.

00:11:11.193 --> 00:11:13.817
One of the recommendations that I've often seen is don't set

00:11:13.817 --> 00:11:16.246
this to be on the local directory itself.

00:11:16.246 --> 00:11:21.574
Set up a shared folder somewhere and have it logged to there instead.

00:11:21.575 --> 00:11:24.360
I'm not going to turn on Include invocation headers.

00:11:24.360 --> 00:11:27.168
It doesn't give you that much more information.

00:11:27.168 --> 00:11:29.312
What we have here is more than sufficient.

00:11:29.312 --> 00:11:32.618
So I'm going to click OK, and then PowerShell logging is turned on,

00:11:32.619 --> 00:11:33.808
and we are good to go.

00:11:33.808 --> 00:11:37.230
And we'll see what this looks like in that later on.

00:11:37.230 --> 00:11:39.755
And those cheat sheets that we looked at earlier will tell you

00:11:39.755 --> 00:11:43.451
as you turn these on what event number and IDs are correlated

00:11:43.452 --> 00:11:46.663
with these auditing policies.

00:11:46.663 --> 00:11:50.005
Now the catch to Windows PowerShell logging is that what we just

00:11:50.005 --> 00:11:53.187
did I believe is only available for PowerShell 5.

00:11:53.188 --> 00:11:57.283
When you want to log for PowerShell 2 through 4,

00:11:57.283 --> 00:11:59.887
there's something else that you have to do.

00:11:59.887 --> 00:12:05.739
So what you would do is, let me close out all this just so we're not seeing it,

00:12:05.739 --> 00:12:10.349
I'm going to run Notepad because we're going to create a file,

00:12:10.349 --> 00:12:13.755
and I'm actually going to run it as an administrator.

00:12:13.756 --> 00:12:16.222
And the reason I'm doing that is because we're going to

00:12:16.222 --> 00:12:18.888
save this file in a protected directory so we need to be

00:12:18.888 --> 00:12:20.903
an administrator to do this.

00:12:20.904 --> 00:12:22.379
But we're going to create a file,

00:12:22.379 --> 00:12:24.499
and we're going to put some commands in this file.

00:12:24.499 --> 00:12:27.562
So let me type in these commands.

00:12:27.562 --> 00:12:43.154
(Typing) Well, this is neat.

00:12:43.154 --> 00:12:44.798
I can kind of see what you're doing here.

00:12:44.798 --> 00:12:49.290
So this is PowerShell commands for PowerShell so this is going to on session,

00:12:49.290 --> 00:12:50.590
I'm assuming?

00:12:50.590 --> 00:12:50.658
Yes.

00:12:50.658 --> 00:12:51.315
Very cool.

00:12:51.315 --> 00:12:52.631
Hence the dollar sign.

00:12:52.631 --> 00:12:55.472
Dollar sign equals PowerShell in my mind.

00:12:55.472 --> 00:12:56.150
So these commands,

00:12:56.150 --> 00:12:58.966
these are going to turn on the module logging and the script block

00:12:58.967 --> 00:13:01.967
logging for us within PowerShell 2 through 4.

00:13:01.967 --> 00:13:04.371
So what I'm going to do is you just put these three commands,

00:13:04.371 --> 00:13:08.282
and this is all within the Malware Archaeology PowerShell cheat sheet,

00:13:08.282 --> 00:13:10.195
so you can just copy and paste it out.

00:13:10.195 --> 00:13:12.228
But what I'm going to do is I'm going to take these,

00:13:12.228 --> 00:13:20.468
and I'm going to save it into c:\windows\system32\windowspowershell\v1.

00:13:20.468 --> 00:13:26.735
0.

00:13:26.736 --> 00:13:29.010
It sounds like you're saving it for version 1.

00:13:29.010 --> 00:13:32.983
0, but actually, this is the directory that's used for all PowerShell.

00:13:32.983 --> 00:13:35.166
So regardless of version, it's always v1.

00:13:35.166 --> 00:13:35.790
0 directory.

00:13:35.790 --> 00:13:38.518
And then I'm going to call it profile.

00:13:38.518 --> 00:13:38.859
ps1.

00:13:38.859 --> 00:13:41.771
Let me just modify this.

00:13:41.772 --> 00:13:42.002
There.

00:13:42.002 --> 00:13:46.825
And so what that does is that created a profile for PowerShell that

00:13:46.825 --> 00:13:50.303
will get run every time a PowerShell script gets run.

00:13:50.304 --> 00:13:53.066
And so with these settings, it's going to log all that stuff for us.

00:13:53.067 --> 00:13:53.866
Oh, that's excellent.

00:13:53.866 --> 00:13:57.093
So is this able to be bypassed?

00:13:57.093 --> 00:13:59.393
Because I know you can choose a profile that's used

00:13:59.393 --> 00:14:01.740
occasionally when using remote commands and stuff.

00:14:01.740 --> 00:14:05.435
Is this something that can be bypassed as long as they know you're doing it?

00:14:05.435 --> 00:14:08.939
Yeah, an attacker, let's face it, an attacker once they get on a system,

00:14:08.940 --> 00:14:12.923
if they have enough knowledge, they're going to be able to bypass a lot of this.

00:14:12.923 --> 00:14:15.615
So yeah, there's always the chance that this is going to be bypassed,

00:14:15.616 --> 00:14:17.862
but that doesn't mean that you shouldn't turn it on.

00:14:17.862 --> 00:14:21.347
You should still turn on all of these things just so that you

00:14:21.347 --> 00:14:23.413
have it logging and you have things going.

00:14:23.413 --> 00:14:26.637
Yeah, you increase your likelihood of being able to catch something going on.

00:14:26.637 --> 00:14:27.089
Awesome.

00:14:27.089 --> 00:14:31.346
When these log, it's going to log into, under the Applications and Services Logs,

00:14:31.346 --> 00:14:33.802
you're going to see a Windows PowerShell section,

00:14:33.802 --> 00:14:35.912
that's where some of these are going to be logged.

00:14:35.912 --> 00:14:41.581
And then if you drill down into Microsoft and then Windows,

00:14:41.582 --> 00:14:43.985
there's an additional location.

00:14:43.985 --> 00:14:46.875
That's even better for putting stuff in different locations to

00:14:46.875 --> 00:14:48.899
make sure they don't get deleted as well.

00:14:48.899 --> 00:14:51.091
There's going to be a PowerShell Operational log,

00:14:51.091 --> 00:14:54.088
and that's where the majority of what we're going to

00:14:54.088 --> 00:14:55.906
look for is going to be located at.

00:14:55.906 --> 00:14:57.375
Okay, and that's always there,

00:14:57.375 --> 00:15:00.137
but it just doesn't always log all this stuff until we need it.

00:15:00.138 --> 00:15:04.955
Before we had turned all of this on, if we had gone in and looked at it,

00:15:04.956 --> 00:15:07.161
PowerShell is going to be logging some things,

00:15:07.161 --> 00:15:15.161
but we're not going to see a lot.
