WEBVTT

00:00:00.940 --> 00:00:01.600
[Autogenerated] requirement,

00:00:01.600 --> 00:00:06.160
12.7 calls for all personnel to be screened before they're hired.

00:00:06.640 --> 00:00:07.400
This requirements,

00:00:07.400 --> 00:00:11.500
designed to reduce the possibility off insider threat by making

00:00:11.500 --> 00:00:15.070
sure that people with access to cardholder data or people who can

00:00:15.070 --> 00:00:18.240
affect the security of the cardholder data environment are not the

00:00:18.240 --> 00:00:22.190
type of people to steal cardholder data or facilitate other

00:00:22.190 --> 00:00:23.650
steaming cardholder data.

00:00:24.440 --> 00:00:26.220
There's a few things, actually,

00:00:26.220 --> 00:00:28.550
it's quite important to consider with this requirement.

00:00:29.540 --> 00:00:33.350
The first is the standard doesn't say what type of screening you should do.

00:00:33.620 --> 00:00:36.130
So this needs to be based on your risk assessment.

00:00:36.140 --> 00:00:37.970
And it could be that you have different levels of

00:00:37.970 --> 00:00:40.070
screening based on people's role.

00:00:40.840 --> 00:00:43.600
The next thing to be aware of is the note in the requirement

00:00:43.610 --> 00:00:45.400
that echoes the exception requirement.

00:00:45.410 --> 00:00:48.780
Ate the people who just process a single card at a time.

00:00:48.950 --> 00:00:51.770
So people such as people in retail stores who serve your

00:00:51.770 --> 00:00:54.660
customers who just processing a single transaction at once

00:00:54.940 --> 00:00:59.200
and for these type of personnel, this requirement isn't mandatory.

00:00:59.330 --> 00:01:00.760
It's just recommended.

00:01:01.740 --> 00:01:05.900
The final thing I'd like to remember is that who and how

00:01:05.900 --> 00:01:08.670
you screen personnel is often a subject to local

00:01:08.670 --> 00:01:10.550
employment and data protection laws.

00:01:11.240 --> 00:01:15.310
And remember that PC IDE CSS doesn't override those laws.

00:01:15.530 --> 00:01:17.970
So if you can't do this type of screening because of

00:01:17.970 --> 00:01:20.510
local laws or works council arrangements,

00:01:20.590 --> 00:01:22.670
you can still comply with the standard.

00:01:23.440 --> 00:01:25.720
The testing procedure is for the QoS SATA.

00:01:25.720 --> 00:01:29.260
Go and talk with the HR department to find out what screening is done.

00:01:29.740 --> 00:01:31.370
Personally, I was the use.

00:01:31.370 --> 00:01:31.630
A.

00:01:31.630 --> 00:01:35.350
I'd also look for policies and risk assessments to support this process.

00:01:36.240 --> 00:01:38.760
We're going to pause going through Requirement 12 here

00:01:38.850 --> 00:01:41.440
because we've covered lots of general policy and procedure

00:01:41.440 --> 00:01:43.710
requirements on people requirements.

00:01:43.860 --> 00:01:46.980
So it's a good time to join the conversation with Jacob Ansari

00:01:47.070 --> 00:01:50.870
where I discuss with him the practical issues of implementing on

00:01:50.870 --> 00:01:52.730
assessing some of these requirements.

00:01:53.440 --> 00:01:57.250
We're then going to look at the remaining two sections in Requirement 12,

00:01:57.400 --> 00:01:59.450
which deal with third-party service providers.

00:01:59.450 --> 00:02:02.260
An incident response in the next two modules
