WEBVTT

00:00:00.110 --> 00:00:01.510
[Autogenerated] coming back to Year two.

00:00:01.520 --> 00:00:04.690
So business as usual organizations compliant.

00:00:04.690 --> 00:00:05.360
You're coming back.

00:00:05.740 --> 00:00:07.290
What do you do the second time around?

00:00:07.290 --> 00:00:09.800
What are you looking for in terms off seven.

00:00:09.810 --> 00:00:10.770
Requirement seven.

00:00:10.780 --> 00:00:13.690
Well, again seven and eight often travel together.

00:00:13.700 --> 00:00:14.690
So, uh,

00:00:14.700 --> 00:00:18.160
maybe a different sample of user accounts and making sure that

00:00:18.160 --> 00:00:20.310
they are assigned sort of the appropriate roles,

00:00:20.320 --> 00:00:23.670
uh, or or trying to see if things have changed,

00:00:23.670 --> 00:00:23.880
right?

00:00:23.890 --> 00:00:28.230
If if there are new systems, new repositories or things have gone away,

00:00:28.230 --> 00:00:32.860
maybe Or, you know, we we bought a new company and we threw it into the pot,

00:00:32.870 --> 00:00:34.530
or we got rid of some stuff.

00:00:34.690 --> 00:00:38.060
How does that change the groupings?

00:00:38.060 --> 00:00:41.300
That that's usually the interesting stuff in year two.

00:00:41.310 --> 00:00:45.650
Otherwise, if you've done it right in your one and it stays pretty constant,

00:00:45.660 --> 00:00:47.760
then yeah, stays pretty constant.

00:00:48.060 --> 00:00:49.860
Um, now,

00:00:49.860 --> 00:00:54.040
what about causes of compromise requirement seven major cause of compromise.

00:00:54.050 --> 00:00:58.480
Again, I think this goes into the pile of not the cause off,

00:00:58.490 --> 00:00:59.920
but the thing that makes it worse.

00:00:59.930 --> 00:01:00.220
I mean,

00:01:00.230 --> 00:01:03.510
the one thing I thinking back to when I read forensic reports

00:01:03.510 --> 00:01:05.570
the one thing I really concentrating on,

00:01:05.950 --> 00:01:06.930
something you said earlier.

00:01:07.230 --> 00:01:10.630
Too many administrators on one of those administrators

00:01:10.630 --> 00:01:12.590
has left and already noticed that left.

00:01:12.590 --> 00:01:15.390
And then the bad guy used the administrator because you have a lot

00:01:15.390 --> 00:01:17.260
of administrators hard to keep control of that.

00:01:17.380 --> 00:01:17.760
Yeah.

00:01:17.870 --> 00:01:19.030
Luckily, and requirement eight.

00:01:19.030 --> 00:01:21.430
Now, we have multi factor authentication for administrators,

00:01:21.570 --> 00:01:23.740
which we're gonna come onto in a few minutes,

00:01:23.940 --> 00:01:25.390
so that should hopefully take that away.

00:01:25.390 --> 00:01:27.880
But, you know, I've done security audits.

00:01:27.880 --> 00:01:31.640
Where you you run up the tool and you look at how many admits there are.

00:01:31.640 --> 00:01:32.160
You go.

00:01:32.640 --> 00:01:35.350
It's gonna be It's gonna be a long week.

00:01:35.360 --> 00:01:36.180
This is gonna get rough.

00:01:36.190 --> 00:01:36.870
Yeah.

00:01:36.880 --> 00:01:41.860
Um, I'm compensating controls and any common uses of compensating controls.

00:01:41.870 --> 00:01:44.120
I don't see a lot of compensating controls for requirements.

00:01:44.120 --> 00:01:44.470
Seven.

00:01:44.480 --> 00:01:46.870
Yeah, It's a little bread and butter, isn't it?

00:01:46.870 --> 00:01:47.430
Is right.

00:01:47.430 --> 00:01:50.100
Like I don't know what you would compensate like you either

00:01:50.100 --> 00:01:53.330
have access controls or everything's on.

00:01:53.340 --> 00:01:55.200
You know, yellow legal pads, I guess.

00:01:55.210 --> 00:01:57.330
Um so that seems pretty simple.

00:01:57.330 --> 00:01:58.210
Requirements seven.

00:01:58.220 --> 00:01:59.440
Short requirement.

00:01:59.450 --> 00:02:00.450
Business as usual.

00:02:00.450 --> 00:02:01.280
I t.

00:02:01.290 --> 00:02:05.650
And look after administrators on the number of administrators you have.

00:02:06.140 --> 00:02:07.620
It is about wrapping it up.

00:02:07.630 --> 00:02:08.280
It is.

00:02:08.280 --> 00:02:10.229
It's important but it's relatively straightforward.

00:02:10.240 --> 00:02:15.300
Okay, well, we'll finish requirements in their and then we'll look at,

00:02:15.300 --> 00:02:17.850
as you say, that in the next module is requirement,

00:02:17.860 --> 00:02:19.460
which is very closely aligned.

00:02:19.470 --> 00:02:23.620
But it's like how How do we get those users on boarded onto

00:02:23.620 --> 00:02:26.800
the network in into systems on How do we make sure that the

00:02:26.800 --> 00:02:28.650
right user a gzip in every time, right?