WEBVTT

00:00:00.130 --> 00:00:00.870
[Autogenerated] now, then, Jacob.

00:00:00.880 --> 00:00:01.840
Requirement 12.

00:00:01.850 --> 00:00:07.630
We're almost at the end of PC IDE s almost and I know,

00:00:07.640 --> 00:00:12.570
having worked for many years, people feel this when they get to requirement 12.

00:00:12.570 --> 00:00:15.970
It's like we're almost there is like running a marathon so close

00:00:15.970 --> 00:00:18.020
you can see the finish line on the great thing.

00:00:18.020 --> 00:00:20.070
Requirement 12 is You can do it really badly and

00:00:20.070 --> 00:00:21.250
quickly and just get away with it.

00:00:21.250 --> 00:00:22.750
Can't you generally?

00:00:22.750 --> 00:00:25.230
Yes, because it's about documentation.

00:00:25.240 --> 00:00:27.050
So I'm gonna take requirement 12 going to.

00:00:27.050 --> 00:00:28.790
Take it in three modules way.

00:00:28.790 --> 00:00:29.610
Got this first modules.

00:00:29.610 --> 00:00:31.010
Going to, look at all the documentation.

00:00:31.010 --> 00:00:32.830
Right The way up till we get service providers.

00:00:32.840 --> 00:00:38.860
Uh, eso a za necessity if you don't require 12 before you've been on site.

00:00:38.860 --> 00:00:41.630
If you ask for all the documentation first I ask for

00:00:41.630 --> 00:00:43.290
all the documentation all the time.

00:00:43.290 --> 00:00:46.240
And sometimes I even get some of this really sometimes.

00:00:46.250 --> 00:00:47.560
Okay, hope springs eternal.

00:00:48.140 --> 00:00:49.180
Otherwise, what are you doing?

00:00:49.190 --> 00:00:50.910
You're looking for a security policy looking for a

00:00:50.910 --> 00:00:52.550
risk assessment to begin with, right?

00:00:52.940 --> 00:00:54.140
What was an assessor?

00:00:54.140 --> 00:00:55.410
What are you looking for in there?

00:00:55.420 --> 00:01:02.520
Because Well, so in a security policy, I wanted to see something that describes,

00:01:02.640 --> 00:01:05.140
at least at a top level, right?

00:01:05.140 --> 00:01:07.590
Some of the information security practices of the organization.

00:01:07.590 --> 00:01:07.770
Right.

00:01:07.770 --> 00:01:12.150
And then maybe that links into other documentation for,

00:01:12.160 --> 00:01:14.150
you know, other of the requirements, right?

00:01:14.150 --> 00:01:16.950
Going back to even the policy stuff we talked about in requirement one.

00:01:16.960 --> 00:01:20.450
Um, and I want to see who's sort of responsible for this.

00:01:20.450 --> 00:01:23.570
I want to see how they how they disseminate this information,

00:01:23.580 --> 00:01:25.210
how they organize it.

00:01:25.220 --> 00:01:27.490
Who does what?

00:01:27.500 --> 00:01:27.950
Right.

00:01:27.960 --> 00:01:32.960
At least which job role does what if maybe not the individual person's name.

00:01:32.960 --> 00:01:34.850
So you're looking for responsibilities in the policy?

00:01:34.860 --> 00:01:37.120
Yeah, ex wives that is responsible for this.

00:01:37.120 --> 00:01:37.360
Yeah.

00:01:37.370 --> 00:01:37.570
Yeah.

00:01:37.570 --> 00:01:40.650
These people, these roles needed to cover these these tasks,

00:01:40.650 --> 00:01:43.870
these functions, uh, you know, these these things,

00:01:43.880 --> 00:01:44.220
right?

00:01:44.230 --> 00:01:48.210
And then the risk assessment risk assessment is maybe the requirement.

00:01:48.210 --> 00:01:52.250
I find the most frustrating in 12.2 because I think

00:01:52.250 --> 00:01:54.970
it it gives a lot of potential, right?

00:01:54.980 --> 00:01:56.440
Do some risk assessment.

00:01:56.440 --> 00:01:56.660
Right.

00:01:56.660 --> 00:01:58.030
I would put this at the front of the PC.

00:01:58.030 --> 00:01:59.370
IDE s s right.

00:01:59.380 --> 00:02:02.490
Figure out where your risks are.

00:02:02.500 --> 00:02:05.430
Figure out something about your attack surface,

00:02:05.440 --> 00:02:07.600
the threats that you're dealing with.

00:02:07.610 --> 00:02:12.290
You know the vulnerabilities to your organization and then do something

00:02:12.290 --> 00:02:14.630
about it would be sort of how I would write this.

00:02:14.640 --> 00:02:17.150
Okay, I've people argue with me and say, Well, why?

00:02:17.160 --> 00:02:17.800
What should you do?

00:02:17.800 --> 00:02:18.490
A risk assessment.

00:02:18.490 --> 00:02:19.180
The council's done.

00:02:19.180 --> 00:02:20.880
The risk assessment is worked out.

00:02:20.880 --> 00:02:23.540
The controls we need to do they put it in PC ideas.

00:02:23.540 --> 00:02:25.380
That's why do I need to a separate risk assessment?

00:02:25.390 --> 00:02:26.560
Well, e,

00:02:26.560 --> 00:02:28.610
I think I think you want to do some separate risk

00:02:28.610 --> 00:02:30.370
assessment so that you understand.

00:02:30.940 --> 00:02:33.890
You know how that applies to your organization, right?

00:02:33.890 --> 00:02:37.810
I mean, the standard language has to be broadly app, clickable.

00:02:37.810 --> 00:02:40.820
It has to cover a lot of different kinds of entities, right?

00:02:40.830 --> 00:02:42.760
And And they're gonna be certain kinds of entities.

00:02:42.760 --> 00:02:45.410
Where you're gonna mark a lot of the requirements is not app, clickable.

00:02:45.410 --> 00:02:47.170
You're going to say that, you know, I don't store cardholder day,

00:02:47.170 --> 00:02:49.660
though, you know, a bunch of requiring S3 goes away on,

00:02:49.660 --> 00:02:53.520
so you're gonna have a different risk profile than you know,

00:02:53.520 --> 00:02:57.860
some other unlike kind of organization on looking at 12 1 12 to

00:02:57.860 --> 00:03:00.470
whether people usually fail In your experience,

00:03:00.480 --> 00:03:06.850
my experience is that there are a lot of really terrible sort

00:03:06.850 --> 00:03:11.010
of risk assessments out there that are, you know,

00:03:11.010 --> 00:03:12.990
I hesitate to criticize the medium right,

00:03:12.990 --> 00:03:15.640
But there's just a lot of, like, crummy spreadsheets where,

00:03:15.650 --> 00:03:17.080
you know, there's a lot of back slapping,

00:03:17.080 --> 00:03:18.600
and I don't think this is that big of a deal.

00:03:18.600 --> 00:03:20.500
That sort of de prioritize things right now.

00:03:20.510 --> 00:03:24.440
There's not much substance in the actual testing procedure, right?

00:03:24.450 --> 00:03:26.750
There's not, you know, any sort of linkage.

00:03:26.750 --> 00:03:28.660
Say it has to be any good or has to.

00:03:28.640 --> 00:03:31.380
It has to feed back into your strategic plan,

00:03:31.390 --> 00:03:33.470
or it has to help make your business decisions,

00:03:33.440 --> 00:03:35.540
or it needs to compel these other kinds of activities.

00:03:35.540 --> 00:03:39.170
It's just not in the statement in the testing procedure,

00:03:39.170 --> 00:03:40.650
and maybe it's implied right.

00:03:40.660 --> 00:03:43.010
But implication is usually sort of not enough.

00:03:43.020 --> 00:03:46.390
It's relatively rare that I fail somebody on this.

00:03:46.390 --> 00:03:49.360
I call it non compliant, but very often that I sort of shake my head at it.

00:03:49.370 --> 00:03:54.390
So famous Failure is pretty hard because the quality bar is not so.

00:03:54.400 --> 00:03:55.390
The bar is pretty low
