WEBVTT

00:00:00.000 --> 00:00:02.751
Now the one last thing that I want to show.

00:00:02.751 --> 00:00:06.199
We had said that this is the minimum that I would recommend people turn on,

00:00:06.200 --> 00:00:07.779
but there are a lot of other logs.

00:00:07.779 --> 00:00:11.623
And someone may not know exactly what they want to do,

00:00:11.623 --> 00:00:15.390
so there is one tool that will actually show that for you.

00:00:15.390 --> 00:00:19.894
So there's a tool called LOG-MD, so I'm just going to go to that.

00:00:19.895 --> 00:00:21.513
LOG-MD is a great tool.

00:00:21.514 --> 00:00:23.029
It can be used to actually analyze your logs,

00:00:23.029 --> 00:00:24.650
but we're going to use it a little bit differently.

00:00:24.650 --> 00:00:28.341
If you run it by default, and you don't have proper logging set on,

00:00:28.341 --> 00:00:29.450
it actually won't run,

00:00:29.450 --> 00:00:33.907
but it spits out an audit file that tells you what you need to turn on.

00:00:33.907 --> 00:00:40.569
So I don't have proper logging set up on this, so I'm going to run logmd.

00:00:40.569 --> 00:00:42.190
It's going to go and it's going to say hey,

00:00:42.190 --> 00:00:45.118
you don't have the right logs turned on.

00:00:45.119 --> 00:00:47.655
Look at this file, the Report_Audit_Settings file.

00:00:47.655 --> 00:00:49.285
So let me open that up.

00:00:49.285 --> 00:00:53.613
The log doctor is giving you his analysis of what's wrong with your stuff.

00:00:53.613 --> 00:00:56.733
And this is a free tool as well.

00:00:56.733 --> 00:01:02.070
So I'm going to open that up.

00:01:02.070 --> 00:01:05.297
And here, we see it telling us that we don't have the log sizes correctly,

00:01:05.297 --> 00:01:07.854
but here are the commands that you need in order to do that.

00:01:07.854 --> 00:01:11.220
So that what we had talked about before and the size of your logs as well.

00:01:11.220 --> 00:01:14.865
And right here is where it shows you here are the different

00:01:14.865 --> 00:01:17.640
types of logs that need to be turned on based off of the

00:01:17.640 --> 00:01:19.441
different best practices that are out there,

00:01:19.442 --> 00:01:21.275
and this is what your PC is set to.

00:01:21.276 --> 00:01:23.825
Is that Center for Information Security, the CIS standards?

00:01:23.825 --> 00:01:26.427
Yes, the CIS standards, and some Australian,

00:01:26.427 --> 00:01:29.102
and Great Britain, and just all of these different standards.

00:01:29.102 --> 00:01:33.166
So this is a great tool as well to go in and just see what you need to turn on.

00:01:33.167 --> 00:01:34.169
Yeah, I like this a lot.

00:01:34.169 --> 00:01:36.958
I can even see there's a way this could be pulled,

00:01:36.958 --> 00:01:41.862
ran remotely, and then pulled in, and then see if someone is changing your logs.

00:01:41.862 --> 00:01:42.641
It all runs locally.

00:01:42.642 --> 00:01:47.296
Yeah, you could deploy it, have a script run as a scheduled task,

00:01:47.296 --> 00:01:50.273
and then look to see where things have been changed.

00:01:50.274 --> 00:01:51.738
Yeah, because as an intelligent insider,

00:01:51.738 --> 00:01:55.538
I may know that you're logging stuff and kind of change stuff so you

00:01:55.538 --> 00:01:57.366
can't catch me doing things I'm not supposed to do,

00:01:57.366 --> 00:02:00.582
company policy violations, or whatever worse.

00:02:00.582 --> 00:02:03.582
That's really neat.
