WEBVTT

00:00:01.040 --> 00:00:05.540
[Autogenerated] I used to describe piece GUID CSS Requirement 12 as right

00:00:05.540 --> 00:00:08.660
policies that no one else but your QoS a will ever read,

00:00:09.240 --> 00:00:11.620
which is perhaps a little unfair because,

00:00:11.620 --> 00:00:16.470
as the P CSS See always says, security is about technology,

00:00:16.670 --> 00:00:20.250
people on processes on Requirement 12 is the one that

00:00:20.250 --> 00:00:22.460
most deals with people and processes.

00:00:23.140 --> 00:00:27.380
It's a long requirement, but thankfully, most of it is self-explanatory.

00:00:27.610 --> 00:00:29.940
There are not many places where there's opportunity for

00:00:29.940 --> 00:00:32.080
misinterpreting what the standard want,

00:00:32.259 --> 00:00:36.160
although sometimes it does hide requirements in testing procedures.

00:00:36.640 --> 00:00:40.330
So the standard starts off with requirement for security policy,

00:00:40.550 --> 00:00:43.340
and then it requires an annual risk assessment.

00:00:43.620 --> 00:00:45.820
There's also a strangely written requirement,

00:00:45.910 --> 00:00:49.060
which basically asked for user orientated policies.

00:00:49.440 --> 00:00:52.560
Then a couple more requirements to make sure that responsibilities in the

00:00:52.560 --> 00:00:56.810
organization for implementing the Information Security Policy error assigned

00:00:56.810 --> 00:01:01.590
to people the final two people focused requirements are that there should be

00:01:01.590 --> 00:01:05.620
a general security awareness training on that people with access to

00:01:05.620 --> 00:01:10.150
cardholder data on the cardholder data environment or screamed or verified

00:01:10.270 --> 00:01:11.560
before they have access.

00:01:12.140 --> 00:01:14.910
We're going to cover the last couple of requirements is separate modules

00:01:15.000 --> 00:01:18.950
because they're not so much people focused but process focused.

00:01:19.100 --> 00:01:23.250
And these are how third parties or as PC IDE CSS

00:01:23.250 --> 00:01:25.110
likes to call them service providers.

00:01:25.110 --> 00:01:25.850
Error managed.

00:01:26.240 --> 00:01:29.450
How an organization response to an incident.

00:01:30.440 --> 00:01:31.420
Unsurprisingly,

00:01:31.420 --> 00:01:34.870
the people policy and process requirements apply to the

00:01:34.870 --> 00:01:36.990
whole of the cardholder data environment.

00:01:37.250 --> 00:01:38.940
And actually, I want to make a point here,

00:01:38.940 --> 00:01:42.290
which I may well repeat quite a few times in this module because

00:01:42.290 --> 00:01:46.670
it's quite important these sync everything in this requirement just

00:01:46.670 --> 00:01:51.520
applies to the people process and technology that's in scope of the

00:01:51.520 --> 00:01:53.450
PC IDE CSS requirements.

00:01:53.940 --> 00:01:54.900
That means, for example,

00:01:54.900 --> 00:01:59.520
if only 20 people out of your entire company have access to the cardholder data

00:01:59.520 --> 00:02:03.590
environment or can affect the security of the cardholder data environment is

00:02:03.590 --> 00:02:06.420
just those 20 people that the requirements apply to,

00:02:06.610 --> 00:02:08.669
not to your whole organization.

00:02:09.639 --> 00:02:13.570
The first requirement Van is to have a security policy which is published,

00:02:13.690 --> 00:02:15.970
managed on made available to everyone.

00:02:16.640 --> 00:02:21.110
And if you've been through the other 11 previous PC IDE CSS requirements,

00:02:21.340 --> 00:02:24.810
you'll know that the last sub requirement all of them was that you should have

00:02:24.810 --> 00:02:28.570
a security policy that mandated PC IDE CSS requirements,

00:02:28.850 --> 00:02:31.370
so this should almost already be in place.

00:02:31.940 --> 00:02:34.450
The QoS a will go through the whole policy to make sure

00:02:34.450 --> 00:02:35.960
it contains the relevant statements.

00:02:36.340 --> 00:02:37.340
Now, personally,

00:02:37.350 --> 00:02:40.170
I always make sure that I cross referenced 2D CSS

00:02:40.170 --> 00:02:43.020
requirement numbers in my security policies,

00:02:43.090 --> 00:02:45.190
which makes it much easier for the QoS A.

00:02:45.190 --> 00:02:48.140
To find their way around the policy on match My

00:02:48.140 --> 00:02:50.560
policy to the PC IDE CSS requirements.

00:02:51.240 --> 00:02:54.990
The assessor should also look to see that the policy is published on has

00:02:54.990 --> 00:02:57.570
been disseminated to everyone who needs to see it.

00:02:58.340 --> 00:03:01.730
The testing procedure doesn't say interview people,

00:03:01.890 --> 00:03:03.870
but I'm not sure how else the assessors going to

00:03:03.870 --> 00:03:06.260
determine if the policy is being circulated,

00:03:06.280 --> 00:03:07.970
so expect them to do this.

00:03:09.040 --> 00:03:10.570
There's one sub requirement,

00:03:10.660 --> 00:03:14.190
which is that the policy should be reviewed annually because although

00:03:14.190 --> 00:03:17.010
the PC is standard doesn't change that frequently.

00:03:17.210 --> 00:03:20.720
Your organization and the environment may change,

00:03:20.790 --> 00:03:22.540
so your policy should reflect this.

00:03:22.710 --> 00:03:23.480
For example,

00:03:23.640 --> 00:03:26.640
you may decide to upgrade your intruder detection

00:03:26.640 --> 00:03:29.380
system to an intruder protection system,

00:03:29.540 --> 00:03:32.290
which would therefore mean that your policy on how the ideas

00:03:32.290 --> 00:03:34.870
worked was implemented would need to be changed.

00:03:35.540 --> 00:03:38.960
To verify the policies reviewed and potentially updated annually,

00:03:39.160 --> 00:03:42.860
the QoS A will look at the policy on also speak with the relevant people
