WEBVTT

00:00:00.940 --> 00:00:01.830
[Autogenerated] in this module.

00:00:01.990 --> 00:00:05.920
We're just going to look at the two requirements that deal with third parties

00:00:05.980 --> 00:00:09.160
or as PC IDE CSS lights to call them service providers.

00:00:09.940 --> 00:00:12.370
Because there's organizations outsource more and more

00:00:12.370 --> 00:00:14.040
of their I t and their payments,

00:00:14.240 --> 00:00:17.200
they have less and less control over the security of

00:00:17.200 --> 00:00:19.450
those outsourced systems and services.

00:00:20.140 --> 00:00:22.760
But as far as PC IDE CSS is concerned,

00:00:22.950 --> 00:00:27.550
they always maintain responsibility for the security of cardholder data.

00:00:28.140 --> 00:00:33.040
The basic request of Requirement 12.8 is that organizations properly

00:00:33.040 --> 00:00:37.810
managed third-party service providers by having a set of policies and

00:00:37.810 --> 00:00:41.610
procedures to make sure there's a robust processes in place about how

00:00:41.610 --> 00:00:44.160
service providers error engaged on managed.

00:00:44.740 --> 00:00:47.850
I guess the first thing to understand is what PC IDE

00:00:47.850 --> 00:00:50.350
CSS defines a service provided to be.

00:00:51.040 --> 00:00:53.350
There are two classes of organizations.

00:00:53.840 --> 00:00:58.170
The first is organizations that receive cardholder data.

00:00:58.170 --> 00:01:02.450
So organizations I think it says that you share cardholder data with them.

00:01:02.450 --> 00:01:03.840
I don't like that word share,

00:01:03.840 --> 00:01:08.140
but organizations that receive cardholder data on the second is any

00:01:08.140 --> 00:01:11.670
organization that can affect the security of cardholder data,

00:01:11.780 --> 00:01:16.760
such as a hosting provider or or a manage security service provider or on

00:01:16.760 --> 00:01:21.610
outsourced I t provider on before we dive into what policies and procedures

00:01:21.610 --> 00:01:23.760
need to be in place to do with service providers.

00:01:24.140 --> 00:01:26.220
Here's something that's not really well defined,

00:01:26.220 --> 00:01:28.150
and it can catch non commercial.

00:01:28.150 --> 00:01:32.000
QoS is out because they take a too literal approach to this requirement,

00:01:32.010 --> 00:01:33.650
particularly that word share.

00:01:33.950 --> 00:01:38.030
So let's make sure we're clear about who is a service provider.

00:01:38.190 --> 00:01:42.420
And I can best describe this really simple picture because the best

00:01:42.430 --> 00:01:45.300
definition there is of a service provider is also simple.

00:01:45.510 --> 00:01:48.450
It's someone you pay to do something for you,

00:01:48.580 --> 00:01:52.090
something that's related to the security off cardholder data or

00:01:52.090 --> 00:01:55.050
related to the cardholder data you're responsible for.

00:01:55.740 --> 00:01:56.380
Actually,

00:01:56.380 --> 00:01:59.370
if you're in the EU and subject to the GDP are a service

00:01:59.370 --> 00:02:01.530
providers basic the same as a data process?

00:02:01.530 --> 00:02:02.720
Er, look at this picture.

00:02:02.830 --> 00:02:06.570
We've got the organization being assessed for compliance with PC IDE CSS.

00:02:06.800 --> 00:02:09.090
That's one in orange with the letter A,

00:02:09.370 --> 00:02:12.450
and they've bought a service from a second organization here.

00:02:12.450 --> 00:02:16.540
I've put it in Sion with the Letter B organization A is going to

00:02:16.540 --> 00:02:19.690
be the customer or purchaser on Organization B.

00:02:19.770 --> 00:02:23.840
Is the supplier or vendor typically organization a sense

00:02:23.840 --> 00:02:26.910
cardholder today still Organization B and ask them to do

00:02:26.910 --> 00:02:28.360
something with it on their behalf.

00:02:29.140 --> 00:02:33.100
Commercially organization be Will invoice organization A an

00:02:33.100 --> 00:02:39.300
organization A Will pay organization be so the the entity that sending

00:02:39.300 --> 00:02:42.450
an invoice and being paid is the service provider.

00:02:42.840 --> 00:02:46.560
The one exception to this general rule is that if you're a merchant,

00:02:46.940 --> 00:02:49.810
your merchant or requiring bank is not a service provider,

00:02:49.910 --> 00:02:51.180
and this is confirmed in F a.

00:02:51.180 --> 00:02:54.680
Q 1284 That's of course,

00:02:54.680 --> 00:02:57.630
unless the acquirer or merchant bank is providing

00:02:57.640 --> 00:02:59.180
other services to the merchants,

00:02:59.180 --> 00:03:02.040
such as a payment gateway or car to organization,

00:03:02.250 --> 00:03:05.550
in which case there is service provider for those functions.

00:03:06.540 --> 00:03:08.660
There's also one error that I seek uses,

00:03:08.660 --> 00:03:11.740
and merchants and service providers get confused by because

00:03:11.740 --> 00:03:15.100
sometimes it's not unknown for the service provider to send

00:03:15.100 --> 00:03:16.750
cardholder data to emergent.

00:03:17.140 --> 00:03:17.770
For example,

00:03:17.840 --> 00:03:19.980
the merchant might have asked the service provided to

00:03:19.980 --> 00:03:22.990
collect the cardholder data on its behalf before it sends

00:03:22.990 --> 00:03:24.460
it to the merchant for processing.

00:03:24.840 --> 00:03:28.790
Now, some QoS is follow the flow of cardholder data on.

00:03:28.790 --> 00:03:30.530
They argue that in this example,

00:03:30.540 --> 00:03:34.860
organization bees sharing cardholder data with organization a they

00:03:34.860 --> 00:03:37.750
try to say that Azure service provided to be on.

00:03:37.750 --> 00:03:43.050
That's wrong because A is still contracting or buying a service from B Azure,

00:03:43.040 --> 00:03:45.860
ultimately responsible for the security of cardholder data.

00:03:46.340 --> 00:03:48.250
So if if you ever get stuck,

00:03:48.250 --> 00:03:51.440
working out who was service provider is my best advice,

00:03:51.440 --> 00:03:56.690
I get is again to always look a who pays who but isn't a

00:03:56.690 --> 00:03:59.320
specific testing procedure for 12.8 itself.

00:03:59.430 --> 00:04:01.610
It's one of those that refer to the testing requirements.

00:04:01.610 --> 00:04:05.720
But all the sub requirements and the general approach actually to all of 12.8,

00:04:05.720 --> 00:04:07.160
is to look at documentation.

00:04:08.340 --> 00:04:10.720
The first, some requirement, 12.8 point one,

00:04:10.720 --> 00:04:15.280
is pretty simple on once the organization to keep a list of service providers,

00:04:15.360 --> 00:04:18.360
which also includes a description of the service they provide.

00:04:18.839 --> 00:04:19.200
Now,

00:04:19.350 --> 00:04:22.660
I tend to advise people to also make sure they list the type in the

00:04:22.660 --> 00:04:25.390
volume of cardholder data the service provider receives or has

00:04:25.390 --> 00:04:29.310
access do on the contact details of the security and compliance

00:04:29.310 --> 00:04:30.780
contact with the service provider,

00:04:30.960 --> 00:04:34.050
and also when their PC IDE CSS compliance expires.

00:04:34.940 --> 00:04:36.490
The test for this is pretty simple.

00:04:36.760 --> 00:04:39.140
The QoS is just going to check the list and make sure it

00:04:39.140 --> 00:04:41.570
exists on has the information in it.

00:04:42.640 --> 00:04:47.940
The next of requirement is a very beautiful fudge because in a non ideal world,

00:04:47.950 --> 00:04:51.100
it would say have a contract with the service provider that

00:04:51.100 --> 00:04:53.460
compels them to comply with PC IDE CSS.

00:04:54.040 --> 00:04:54.760
But it doesn't.

00:04:55.140 --> 00:04:55.680
It saves.

00:04:55.680 --> 00:04:57.770
There needs to be a written agreement between the

00:04:57.770 --> 00:04:59.970
service provider on the merchants.

00:05:00.840 --> 00:05:05.140
This written agreement, which may or may not be a contract,

00:05:05.260 --> 00:05:08.460
needs to include an acknowledgement from the service provider that

00:05:08.460 --> 00:05:12.020
the service provider has responsibility for the security of the

00:05:12.020 --> 00:05:15.460
cardholder data they process on your behalf or that they can affect

00:05:15.460 --> 00:05:17.050
the security of cardholder data.

00:05:17.640 --> 00:05:21.510
Now how this responsibility is word it is completely up to

00:05:21.510 --> 00:05:23.850
you or more probably up to your lawyer.

00:05:24.240 --> 00:05:27.530
What's important is that you have something in writing that shows

00:05:27.530 --> 00:05:30.660
the service provider has confirmed that they know those

00:05:30.660 --> 00:05:32.760
cardholder data involved in this service.

00:05:33.640 --> 00:05:36.990
PC IDE CSS isn't any more specific than this.

00:05:37.180 --> 00:05:42.140
It isn't looking to specify Contract clauses is not looking to

00:05:42.140 --> 00:05:45.400
specify specific conduct from the service provider,

00:05:45.430 --> 00:05:48.520
and it isn't looking to pass liability in the event of a

00:05:48.520 --> 00:05:50.170
data breach of the service provider,

00:05:50.640 --> 00:05:53.770
although I hope your lawyers do all of these things.

00:05:53.970 --> 00:05:55.270
But PC Idea says,

00:05:55.270 --> 00:05:58.610
Just wants to make sure that the service provider has acknowledged its

00:05:58.610 --> 00:06:03.370
responsibility for the security of cardholder data on the QoS.

00:06:03.370 --> 00:06:03.510
A.

00:06:03.510 --> 00:06:06.570
Will want to check that written agreement now,

00:06:06.640 --> 00:06:07.800
given this written agreements,

00:06:07.800 --> 00:06:11.270
often buried somewhere in a long and quite commercially sensitive contract,

00:06:11.270 --> 00:06:13.990
Sometimes it's worth getting this information together

00:06:13.990 --> 00:06:15.660
before an assessor wants to see it.

00:06:16.310 --> 00:06:17.060
Personally,

00:06:17.300 --> 00:06:20.790
I keep copies of the relevant pages of the contract with this

00:06:20.790 --> 00:06:24.670
acknowledgment of responsibility with my list of service providers.

00:06:25.240 --> 00:06:28.020
The next service provider sub requirement is that the

00:06:28.020 --> 00:06:30.480
organization must have a due diligence process.

00:06:30.480 --> 00:06:33.740
It follows when engaging a service provider and,

00:06:33.740 --> 00:06:37.170
as the guidance says, this will typically include a risk analysis,

00:06:37.320 --> 00:06:41.070
some understanding of how the service provided demonstrates

00:06:41.070 --> 00:06:44.180
its compliance with the PC IDE CSS requirements and how the

00:06:44.180 --> 00:06:46.360
service provider managers incidents.

00:06:46.840 --> 00:06:50.800
The use A will want to see the policies or procedures that specify

00:06:50.800 --> 00:06:54.040
what type of due diligence the organization has determined is

00:06:54.040 --> 00:06:56.540
required to be undertaken before a service.

00:06:56.540 --> 00:06:59.810
Providers engaged and the QoS a will also want to see the

00:06:59.810 --> 00:07:01.900
evidence that these procedures were followed,

00:07:01.900 --> 00:07:05.380
that the due diligence happened for the service providers that are

00:07:05.380 --> 00:07:09.250
listed in requirement 12.8 point one requirement,

00:07:09.250 --> 00:07:12.330
12.8 point four is pretty simple and wants to make sure

00:07:12.330 --> 00:07:14.880
that the organization checks the compliance status of

00:07:14.880 --> 00:07:16.360
each service provider annually.

00:07:16.840 --> 00:07:19.880
So that's typically by getting a new version of the service

00:07:19.880 --> 00:07:24.380
providers at a station of PC IDE CSS compliance on also making

00:07:24.380 --> 00:07:27.890
sure that it still applies to the services that are provided to

00:07:27.890 --> 00:07:30.030
the organization and QoS.

00:07:30.030 --> 00:07:35.070
A will look to see that this is a policy, but also that is carried out no.

00:07:35.440 --> 00:07:39.220
Before we get to the last sub requirement dealing with service providers,

00:07:39.470 --> 00:07:43.570
I guess I need to answer the question that you're probably asking yourself,

00:07:44.440 --> 00:07:48.080
which is whether a service provider needs to comply with PC IDE

00:07:48.080 --> 00:07:51.850
CSS because we've not actually explicitly had that stated in

00:07:51.850 --> 00:07:55.220
requirement 12.8 on the answer is, well,

00:07:55.230 --> 00:07:55.960
sort off.

00:07:56.840 --> 00:08:00.860
If an organization has an obligation to comply with PC IDE CSS,

00:08:01.240 --> 00:08:05.770
then even if it outsources things to one or more service providers,

00:08:06.140 --> 00:08:09.880
API GUID CSS still applies to the people processes and

00:08:09.880 --> 00:08:12.860
technology provided by the service providers,

00:08:13.440 --> 00:08:16.260
so the organization has a couple of options.

00:08:16.940 --> 00:08:21.110
The first is to ask the service provider to provide evidence of its own

00:08:21.110 --> 00:08:26.760
compliance with PC IDE CSS by providing its own at a station of PC IDE CSS

00:08:26.760 --> 00:08:31.060
compliance that will have Bean produced either by its internal assessor or

00:08:31.060 --> 00:08:33.809
by a qualified security assessor on.

00:08:33.809 --> 00:08:37.159
It's important that that at a station covers the services being

00:08:37.159 --> 00:08:42.250
provided to the organization OAuth the organization or,

00:08:42.250 --> 00:08:44.710
more normally, the organization's QoS Azure I can.

00:08:44.710 --> 00:08:48.340
GOAN ASSESS The service providers compliance with the PC IDE CSS

00:08:48.340 --> 00:08:51.000
requirements as part of its own assessment,

00:08:51.190 --> 00:08:54.730
So York Yusa would go to your service provider on

00:08:54.730 --> 00:08:57.230
assess or the requirements for in place.

00:08:57.840 --> 00:09:01.420
So the full answer to the question is that the people process

00:09:01.420 --> 00:09:05.160
and technology provided by the service provider do need to

00:09:05.160 --> 00:09:07.770
comply with the PC IDE CSS requirements.

00:09:08.340 --> 00:09:12.630
And that's what sub requirement 12.8 point five tries to make clear,

00:09:12.900 --> 00:09:17.420
because it demands that you define exactly what PC IDE AD FS requirements are

00:09:17.420 --> 00:09:20.780
the responsibility of the organization on which requirements of the

00:09:20.780 --> 00:09:25.250
responsibility of the service provider and the best way of doing This is to

00:09:25.250 --> 00:09:28.130
create what we all call a responsibility matrix,

00:09:28.310 --> 00:09:33.920
listing all 300 PC IDE CSS requirements and sub requirements and saying who,

00:09:34.030 --> 00:09:38.000
whether it's the organization or the service provider who does what

00:09:38.190 --> 00:09:41.700
for the services offered a typical responsibility.

00:09:41.700 --> 00:09:43.280
Matrix looks something like this.

00:09:43.550 --> 00:09:47.020
It's a spreadsheet with all the PC IDE CSS requirements listed down the

00:09:47.020 --> 00:09:50.380
left hand side and then columns showing whether requirement applies to the

00:09:50.380 --> 00:09:55.510
organization or the service provider or if it's a shared responsibility to

00:09:55.510 --> 00:09:57.390
validate this requirements in place,

00:09:57.530 --> 00:09:59.840
the QoS is going to want to see something that shows which

00:09:59.840 --> 00:10:01.900
requirements the responsibility of each party,

00:10:02.130 --> 00:10:06.650
which is why everyone uses something that looks like that responsibility matrix.

00:10:07.540 --> 00:10:09.580
That's the end of requirement 12.8,

00:10:09.770 --> 00:10:12.910
which details were organizations have to fulfill when

00:10:12.910 --> 00:10:14.470
they deal with service providers.

00:10:15.240 --> 00:10:18.190
The general guidance about how you deal with third-party

00:10:18.190 --> 00:10:21.420
service providers and how the organization must validate

00:10:21.490 --> 00:10:22.730
that the service providers,

00:10:22.730 --> 00:10:26.800
people processes and technologies comply with the PC IDE CSS requirements is

00:10:26.800 --> 00:10:31.170
actually in the standard is written at the start on page 12
