WEBVTT

00:00:00.040 --> 00:00:02.740
[Autogenerated] This is a requirement that's often outsourced.

00:00:02.750 --> 00:00:05.220
So there are a lot of managed security managed service

00:00:05.220 --> 00:00:08.750
providers manage security service providers that will put

00:00:08.750 --> 00:00:11.740
devices in that will collect your logs, consume them on,

00:00:11.740 --> 00:00:13.780
then put them into their managed service center.

00:00:13.790 --> 00:00:14.140
Right.

00:00:14.150 --> 00:00:15.560
Is that okay to CSS?

00:00:15.570 --> 00:00:16.610
It is right.

00:00:16.610 --> 00:00:19.640
And this is the thing that I think I've said on stage

00:00:19.650 --> 00:00:21.170
in speaking events or other places.

00:00:21.240 --> 00:00:24.000
Um, it's really, like 20%.

00:00:24.000 --> 00:00:24.240
What?

00:00:24.240 --> 00:00:27.150
The tool is a sort of 80% what you do with it.

00:00:27.160 --> 00:00:30.640
So whether you buy some expensive, you know,

00:00:30.640 --> 00:00:32.330
commercial log analysis package,

00:00:32.340 --> 00:00:35.770
whether you pay some third-party to do it right in the end,

00:00:36.540 --> 00:00:38.080
what that's going to do is it's going to take all that

00:00:38.080 --> 00:00:39.870
log data is gonna consume its going to, analyze it.

00:00:39.870 --> 00:00:41.030
However it does right.

00:00:41.040 --> 00:00:43.570
And the however it does is important, right?

00:00:43.570 --> 00:00:44.620
And you want to understand that,

00:00:44.620 --> 00:00:47.450
and you want to probably tune that to your environment,

00:00:47.460 --> 00:00:47.930
right?

00:00:47.940 --> 00:00:50.670
But setting aside the sort of complexity of that in the end,

00:00:50.670 --> 00:00:52.530
it's been going to yield some sort of alert.

00:00:52.540 --> 00:00:52.950
Right?

00:00:53.040 --> 00:00:54.940
I found something that looks suspicious,

00:00:54.940 --> 00:00:57.620
or I found something that meets some set of criteria,

00:00:57.630 --> 00:00:59.270
and I'm going to alert it on.

00:00:59.270 --> 00:01:02.840
So whether that's your own software that tells you hey,

00:01:02.840 --> 00:01:05.510
there's an alert or it's, um, third-party,

00:01:05.519 --> 00:01:06.160
you know,

00:01:06.160 --> 00:01:08.800
sending you some notification based on however you set up

00:01:08.800 --> 00:01:12.440
those notifications right then you as the organization

00:01:12.440 --> 00:01:16.750
ultimately get that back right, and then you have to go do something about right.

00:01:16.940 --> 00:01:20.510
And if it's just so, we pay a third-party and they sent us alert.

00:01:20.520 --> 00:01:22.480
Well, what happens when you get an alert?

00:01:22.490 --> 00:01:25.130
Because that that covers some of the requirement.

00:01:25.140 --> 00:01:27.770
But it doesn't cover the requirement off and do

00:01:27.770 --> 00:01:28.940
something and then do something about it,

00:01:28.950 --> 00:01:29.520
absolutely.

00:01:29.530 --> 00:01:31.300
But the important part, right?

00:01:31.310 --> 00:01:32.690
But some of the important parts,

00:01:32.690 --> 00:01:36.220
like one line isn't it was The unimportant part is like five pages.

00:01:36.230 --> 00:01:38.180
That is often the case
