WEBVTT

00:00:00.040 --> 00:00:02.920
[Autogenerated] I mean, that wraps up 12 10, and that wraps up 12.

00:00:02.930 --> 00:00:04.360
Unless, of course, your service provider.

00:00:04.360 --> 00:00:08.160
Unless you're services on, there's a new weird requirement 2011,

00:00:08.170 --> 00:00:12.870
which is this requirement that service providers have to what they have to.

00:00:12.870 --> 00:00:13.550
What does it mean?

00:00:13.550 --> 00:00:14.960
What's this requirement mean?

00:00:14.970 --> 00:00:16.860
It's a policy and procedure thing, isn't it?

00:00:16.870 --> 00:00:17.410
It is.

00:00:17.420 --> 00:00:21.950
It is well, and I want to see some, like process artifact from that.

00:00:21.960 --> 00:00:26.120
But the goal is is that you're testing kind of your security procedures to

00:00:26.120 --> 00:00:29.070
make sure that they're working the way you expect them to.

00:00:29.340 --> 00:00:32.509
You know, here is it's kind of like 10.8.

00:00:32.520 --> 00:00:34.950
But for people, okay, right, right.

00:00:34.960 --> 00:00:38.520
It's our people doing what they're supposed to do Now,

00:00:38.520 --> 00:00:40.510
I would expect some of the findings to shake out from this.

00:00:40.510 --> 00:00:43.910
Maybe, uh, this person needs more training, right?

00:00:43.920 --> 00:00:45.780
They just didn't know how to deal with the situation.

00:00:45.790 --> 00:00:46.030
Right?

00:00:46.040 --> 00:00:49.820
Or this task is too big for this one person to do so.

00:00:49.820 --> 00:00:52.650
We need more bodies or we need more automation, right?

00:00:52.660 --> 00:00:53.890
Or, you know,

00:00:53.900 --> 00:00:56.710
maybe this person did what they were supposed to do and produced

00:00:56.710 --> 00:00:58.850
some piece of information that was useful,

00:00:58.860 --> 00:01:02.020
but it didn't get handed off to whoever needed to do to have you

00:01:02.020 --> 00:01:03.580
actually start assessing against this one.

00:01:03.590 --> 00:01:05.209
You actually doing the physical assessment?

00:01:05.209 --> 00:01:05.670
CSS?

00:01:06.040 --> 00:01:09.050
How's that going with the organizations with a bit like,

00:01:09.060 --> 00:01:09.940
I don't know what to do.

00:01:09.950 --> 00:01:12.730
I I think I think we had a lot of these kinds of conversations, right.

00:01:12.730 --> 00:01:13.840
What are you looking for?

00:01:13.840 --> 00:01:15.550
What are you expecting us to do?

00:01:15.550 --> 00:01:18.020
And you know, whenever there's a new requirement,

00:01:18.030 --> 00:01:19.760
uh, in PC IDE s s,

00:01:19.760 --> 00:01:23.420
there's this pressure to make it as much of a paper chase is possible,

00:01:23.430 --> 00:01:24.070
right?

00:01:24.240 --> 00:01:28.770
And then assessors have to sort of exert the opposite pressure to

00:01:28.770 --> 00:01:33.280
make it an actual thing that does something useful right on dso

00:01:33.290 --> 00:01:37.570
that's still in contention right now, right where you know,

00:01:37.570 --> 00:01:39.880
there's a lot of pressure to make it a paper chase,

00:01:39.880 --> 00:01:43.520
right to just, you know, make it an extra paragraph in the security policy,

00:01:43.530 --> 00:01:43.710
right?

00:01:43.710 --> 00:01:45.360
That nobody ever looks that nobody ever does anything

00:01:45.360 --> 00:01:47.720
about it is the very final requirement.

00:01:47.720 --> 00:01:51.360
So people's, you know, patience and tolerance for CSS has probably run out.

00:01:51.370 --> 00:01:55.790
Absolutely crashed at this point in time, which I actually hope yours hasn't.

00:01:55.790 --> 00:01:57.330
And I hope you actually found this.

00:01:57.330 --> 00:02:01.940
This this course of theory and practical experience for the last three

00:02:01.940 --> 00:02:04.530
requirements of CSS has sort of brought it to life.

00:02:04.530 --> 00:02:06.150
But the last three requirements, you know,

00:02:06.150 --> 00:02:08.050
they're not joined up in the same way as the rest of

00:02:08.050 --> 00:02:10.360
the standard way started off with,

00:02:10.340 --> 00:02:15.290
with effectively logging and monitoring on finding Attackers in our networks.

00:02:15.290 --> 00:02:21.040
We then looked at how we tested and tested our defenses with both ___________,

00:02:21.040 --> 00:02:23.230
testing and vulnerability scanning on.

00:02:23.230 --> 00:02:25.260
Then there's this whole thing in Section 12,

00:02:25.260 --> 00:02:28.750
which is basically e used to describe it as Let's keep lots of

00:02:28.750 --> 00:02:31.150
paperwork with nobody that the assessor ever reads,

00:02:31.340 --> 00:02:33.480
which which can be the low bar.

00:02:33.480 --> 00:02:36.510
But actually some of the stuff in 12 we've talked about with Jacob

00:02:36.510 --> 00:02:40.230
there with certainly 12 12 to on the risk assessment,

00:02:40.230 --> 00:02:43.250
and the Incident Response plan has a real benefit to the

00:02:43.250 --> 00:02:45.320
organization of doing secure security.

00:02:45.320 --> 00:02:46.960
Well, that's the end of this.

00:02:46.970 --> 00:02:52.420
This this final look at the PC IDE CSS standards and hope you found it useful
