WEBVTT

00:00:00.040 --> 00:00:02.260
[Autogenerated] How frequently should you review the logs?

00:00:02.840 --> 00:00:06.560
So the requirement talks about daily review.

00:00:06.570 --> 00:00:07.070
Right?

00:00:07.080 --> 00:00:10.330
And in practice,

00:00:10.340 --> 00:00:17.170
I think what that means is you need to deal with your alerts on a daily basis.

00:00:17.180 --> 00:00:17.690
Right?

00:00:17.700 --> 00:00:18.090
Right.

00:00:18.100 --> 00:00:19.480
So, uh,

00:00:19.490 --> 00:00:26.220
if you've got whatever your criteria are to come up with interesting things,

00:00:26.220 --> 00:00:26.940
yeah, right.

00:00:26.950 --> 00:00:29.670
Go deal with those at least every day, right?

00:00:29.680 --> 00:00:32.540
I don't think that necessarily means that you've got to go scroll

00:00:32.540 --> 00:00:35.330
through a gig worth of log lines every day again.

00:00:35.340 --> 00:00:36.380
That that's not the point.

00:00:36.380 --> 00:00:40.550
But if you got to also make you to reviewing effectively reviewing the logs,

00:00:40.550 --> 00:00:43.890
consolidating, looking for something in producing alerts a song,

00:00:43.890 --> 00:00:45.670
they respond to those alerts every day.

00:00:45.740 --> 00:00:47.200
That makes the intent of the E.

00:00:47.200 --> 00:00:47.830
I think so.

00:00:47.840 --> 00:00:48.290
Yeah, it's not.

00:00:48.290 --> 00:00:50.040
You don't have to have a human doing it every day.

00:00:50.040 --> 00:00:51.500
It could be an ultimate do, right?

00:00:51.500 --> 00:00:56.920
Yeah, But again, the analysis is increasingly sort of machine based, right?

00:00:56.930 --> 00:01:00.720
And And the idea that that humans error really capable of doing the analysis?

00:01:00.730 --> 00:01:03.160
Um, is right.

00:01:03.160 --> 00:01:03.840
They never have.

00:01:03.840 --> 00:01:05.630
You just pretended right?

00:01:05.630 --> 00:01:07.120
And and so I mean, yeah.

00:01:07.120 --> 00:01:10.620
You want some humans doing the engineering of building

00:01:10.620 --> 00:01:13.670
that analysis set of tools right on.

00:01:13.670 --> 00:01:15.650
That's that's serious hard work, right?

00:01:15.650 --> 00:01:19.670
That's that's skilled, you know, a specialist information, security stuff.

00:01:20.040 --> 00:01:21.880
And and that's not easy.

00:01:21.890 --> 00:01:26.250
Um, but but I think that's how you get useful stuff out of your log data, right?

00:01:26.250 --> 00:01:29.750
I mean, I'm sure there was a log repository full of interesting data,

00:01:29.760 --> 00:01:32.370
you know, in insert security incident here.

00:01:32.370 --> 00:01:32.870
Absolutely.

00:01:32.880 --> 00:01:33.270
Right.

00:01:33.280 --> 00:01:34.170
And?

00:01:34.180 --> 00:01:36.580
And maybe they were getting alerts on the salient

00:01:36.580 --> 00:01:38.650
events and maybe they weren't right.

00:01:39.540 --> 00:01:43.330
Um, the standard split reviewing of logs into two.

00:01:43.330 --> 00:01:45.660
I think it was in version 3.1 of version 3.2,

00:01:45.670 --> 00:01:49.850
because you now got the requirement, you know,

00:01:50.340 --> 00:01:57.620
to review something's daily, and then other system components periodically,

00:01:57.630 --> 00:01:58.260
periodically.

00:01:58.840 --> 00:02:00.580
Well, what's periodic?

00:02:00.590 --> 00:02:01.520
I mean, you know what?

00:02:01.520 --> 00:02:04.250
What to you is that you say what is periodically mean.

00:02:04.260 --> 00:02:08.330
So So the notion behind that requirement is Go look at your

00:02:08.330 --> 00:02:11.730
kind of log data for your non CD or your non scope

00:02:11.730 --> 00:02:16.670
environment to make sure that there's not,

00:02:17.040 --> 00:02:18.790
you know, potentially adverse stuff.

00:02:18.790 --> 00:02:20.160
Kind of happening around the edges.

00:02:20.160 --> 00:02:20.540
Right?

00:02:20.550 --> 00:02:23.410
Okay, So maybe the bad guy isn't in your CD.

00:02:23.410 --> 00:02:25.040
Maybe isn't in your in scope environment.

00:02:25.040 --> 00:02:29.910
But if there's evidence in the log data for the adjacent

00:02:29.920 --> 00:02:33.390
systems that the bad guy is poking at the edges,

00:02:33.400 --> 00:02:36.140
I think you want to know that, all right,

00:02:36.140 --> 00:02:36.940
I think you want to know that.

00:02:36.940 --> 00:02:39.300
So, uh, you know what is the period?

00:02:39.300 --> 00:02:42.110
I think that's a little bit like 9.9 that we discussed previously.

00:02:42.120 --> 00:02:44.840
You gotta make some decisions about what is a good faith

00:02:44.840 --> 00:02:47.950
sort of justifiable period for that.

00:02:47.960 --> 00:02:49.240
Maybe that's not every day.

00:02:49.240 --> 00:02:50.550
Maybe that's every week or every month.

00:02:50.560 --> 00:02:53.700
I don't know, right, or it's going to be situation specific.

00:02:53.710 --> 00:02:54.380
Uh,

00:02:54.390 --> 00:02:57.750
but that's what you want to do is come up with your sort of rationale for that.
