WEBVTT

00:00:00.140 --> 00:00:02.090
[Autogenerated] Where do people fail on this one?

00:00:02.540 --> 00:00:04.630
Uh, in a couple of places.

00:00:04.640 --> 00:00:05.450
Um,

00:00:06.840 --> 00:00:10.430
sometimes they can't show me all of the event data

00:00:10.430 --> 00:00:11.660
that they need to be gathering right.

00:00:11.660 --> 00:00:14.300
All of the event types, um,

00:00:14.310 --> 00:00:18.080
sometimes used to be the case that organizations had a

00:00:18.080 --> 00:00:20.110
hard time retaining all of the log data.

00:00:20.110 --> 00:00:23.360
But storage is increasingly sort of inexpensive and

00:00:23.360 --> 00:00:25.500
accessible so that that sort of fallen away.

00:00:25.510 --> 00:00:31.670
The biggest thing is some sort of meaningful analysis and response, right?

00:00:31.680 --> 00:00:33.380
I see a lot of organizations say, Oh, well,

00:00:33.380 --> 00:00:33.860
we you know,

00:00:33.860 --> 00:00:38.300
we use the sort of canned PC I reports right that that dig

00:00:38.300 --> 00:00:42.010
into this database and pull stuff out, and we don't know how they work on.

00:00:42.010 --> 00:00:43.670
We don't really know what they're telling us,

00:00:43.680 --> 00:00:47.090
and we certainly haven't taken any efforts to sort of

00:00:47.100 --> 00:00:49.150
tuned this to suit our environment.

00:00:49.240 --> 00:00:50.620
And so then are we looked at the alerts,

00:00:50.620 --> 00:00:53.200
and we're like, That's a false positive or I'll,

00:00:53.200 --> 00:00:54.130
that's immaterial.

00:00:54.130 --> 00:00:55.870
Or I'll That's garbage right?

00:00:55.880 --> 00:01:01.030
And we basically trained ourselves to cry wolf and and then ignore that

00:01:01.040 --> 00:01:07.450
its coverage of problem because obviously a lot of cloud by systems now

00:01:07.640 --> 00:01:09.530
this required the supply supplied by systems.

00:01:09.530 --> 00:01:10.190
Absolutely, isn't it?

00:01:10.200 --> 00:01:10.590
Of course.

00:01:10.600 --> 00:01:14.830
So if you're if you're procuring Cloud UNIX was needs to

00:01:14.840 --> 00:01:17.170
procure logging from that cloud environment.

00:01:17.180 --> 00:01:17.600
Right?

00:01:17.610 --> 00:01:18.870
That needs to be consolidated.

00:01:18.880 --> 00:01:21.350
Doesn't need to be consolidated with with local logs as well.

00:01:21.350 --> 00:01:23.560
So So this is this is a tricky thing.

00:01:23.570 --> 00:01:27.940
I think if you don't have a consolidated longer posit Torrey,

00:01:27.950 --> 00:01:32.270
you are blinding yourself to what's actually happening.

00:01:32.440 --> 00:01:36.090
Uh, that said the words like, consolidate your log.

00:01:36.090 --> 00:01:40.330
Repo doesn't they don't really exist in PC IDE s s.

00:01:40.340 --> 00:01:43.580
And there are cases where clients, for whatever reason,

00:01:43.590 --> 00:01:46.810
have maybe a couple of different silos of blog data

00:01:46.820 --> 00:01:49.440
that they can't or don't consolidate.

00:01:49.450 --> 00:01:52.760
And so can you fail somebody on that?

00:01:52.770 --> 00:01:54.450
I'm not sure you can write.

00:01:54.460 --> 00:01:57.900
Um, does it diminish its usefulness?

00:01:57.910 --> 00:01:59.220
I think significantly
