WEBVTT

00:00:00.230 --> 00:00:00.900
[Autogenerated] now, Jacob.

00:00:00.910 --> 00:00:04.290
Requirement 12.8 service providers.

00:00:04.610 --> 00:00:11.170
The one that causes no end of grief of the planned on it should be quite simple.

00:00:11.740 --> 00:00:16.800
So we've just been through the theory of it practically as a QoS Azure.

00:00:16.810 --> 00:00:18.170
You're walking on site.

00:00:18.640 --> 00:00:20.990
What are you looking for?

00:00:20.990 --> 00:00:21.580
We're gonna ask.

00:00:21.580 --> 00:00:22.270
Well, first.

00:00:22.280 --> 00:00:24.330
So, in an ideal situation,

00:00:24.330 --> 00:00:28.230
I want to see these organization knows who all their service providers are.

00:00:28.240 --> 00:00:30.170
Okay, so we're looking for a list of them, right?

00:00:30.180 --> 00:00:32.619
And some sort of procedure from managing service providers.

00:00:32.619 --> 00:00:35.920
How they engage, how they how they maybe wrap up when they're done.

00:00:35.930 --> 00:00:38.300
And, you know,

00:00:38.300 --> 00:00:42.290
conceivably if there's some sort of network or or logical connectivity,

00:00:42.290 --> 00:00:44.410
how they establish it, how they make sure that that works.

00:00:44.420 --> 00:00:46.090
Okay, Right on, then.

00:00:46.090 --> 00:00:46.480
Ideally,

00:00:46.480 --> 00:00:51.490
the other thing I'm looking for them are the compliant ao CSS from

00:00:51.490 --> 00:00:53.970
those service providers that the client is collecting.

00:00:54.140 --> 00:00:56.070
Are you looking for a contract to be in place?

00:00:56.080 --> 00:00:57.860
There's a contract need to be in place.

00:00:57.870 --> 00:01:02.050
You know, I don't actually have a requirement for a contract.

00:01:02.440 --> 00:01:03.000
Right.

00:01:03.010 --> 00:01:04.220
Um you know,

00:01:04.220 --> 00:01:06.210
the peace IDE AD CS doesn't really get into sort of

00:01:06.210 --> 00:01:08.750
the brass tacks of contracting.

00:01:08.760 --> 00:01:09.940
It's just written agreement.

00:01:09.950 --> 00:01:11.390
Yeah, it does a written agreement.

00:01:11.400 --> 00:01:16.840
So whatever shape that takes, um and you know,

00:01:16.840 --> 00:01:19.990
whatever shape it takes where the I mean again.

00:01:19.990 --> 00:01:24.970
Ideally, the organization wants to demonstrate PC IT CSS compliance for,

00:01:25.740 --> 00:01:26.310
you know,

00:01:26.310 --> 00:01:32.790
are accepting PC responsibility for for the service providers that it's using.

00:01:32.800 --> 00:01:35.270
So you've got a list you're looking for a written

00:01:35.270 --> 00:01:37.150
agreement which could be a contractor.

00:01:37.150 --> 00:01:37.940
It could be a letter.

00:01:37.940 --> 00:01:41.320
It could be something, something or terms and conditions on on a public website,

00:01:41.330 --> 00:01:43.740
Right conceivably that you're taking off.

00:01:43.750 --> 00:01:48.520
And now you're looking for evidence off that third parties compliance.

00:01:48.530 --> 00:01:50.700
You're looking for a to attestation of compliance.

00:01:50.710 --> 00:01:54.230
That's that's really what you're you should be looking for, right?

00:01:54.240 --> 00:01:54.550
You know,

00:01:54.550 --> 00:01:56.940
based on some of the guidance documentation about

00:01:56.950 --> 00:01:58.780
interacting with third-party service providers,

00:01:58.780 --> 00:01:58.950
right,

00:01:58.960 --> 00:02:02.690
if they're providing some service where they're involved in in

00:02:02.700 --> 00:02:06.100
handling payment card data or affecting the security of that's

00:02:06.100 --> 00:02:07.440
what they should be doing right?

00:02:07.440 --> 00:02:09.449
And this is this is where all the grief happens.

00:02:09.639 --> 00:02:11.640
So there, too, after stations of compliance,

00:02:11.650 --> 00:02:14.290
one that comes with a self assessment questionnaire,

00:02:14.300 --> 00:02:17.810
one that is a result of an on site assessment by qualified security.

00:02:17.810 --> 00:02:20.190
Assessor uh, do you care what you get?

00:02:20.200 --> 00:02:20.830
Yes.

00:02:20.840 --> 00:02:21.220
Okay.

00:02:21.230 --> 00:02:21.740
Yes.

00:02:21.750 --> 00:02:23.190
So, uh,

00:02:23.200 --> 00:02:27.550
the self assessment questionnaire is just that it's

00:02:27.550 --> 00:02:29.650
the organization assessing itself.

00:02:29.640 --> 00:02:30.270
Yeah, right.

00:02:30.240 --> 00:02:30.840
Uh oh.

00:02:30.840 --> 00:02:34.130
And maybe they're doing so correctly.

00:02:34.140 --> 00:02:35.450
Maybe not.

00:02:35.460 --> 00:02:35.860
Right.

00:02:35.870 --> 00:02:38.590
But the point of the self assessment questionnaire was

00:02:38.600 --> 00:02:42.420
essentially a risk decision by the payment brands by the PC IT

00:02:42.420 --> 00:02:45.320
council by the acquiring institutions to say,

00:02:45.330 --> 00:02:51.140
there's this category of institution that the the sort of useful risk

00:02:51.140 --> 00:02:54.350
decision for us is to have them assess themselves rather than compel

00:02:54.350 --> 00:02:56.890
them to obtained services of nested.

00:02:56.900 --> 00:02:57.170
Right.

00:02:57.180 --> 00:03:00.170
But if that entity is a service provider,

00:03:00.540 --> 00:03:04.230
right, providing services to other kinds of organizations,

00:03:04.240 --> 00:03:08.760
right and consequently affecting their security,

00:03:10.140 --> 00:03:10.420
right?

00:03:10.420 --> 00:03:12.570
The idea that they can self assess.

00:03:12.580 --> 00:03:15.250
Yeah, it is pretty silly.

00:03:15.260 --> 00:03:16.380
Okay, but what if you don't?

00:03:16.390 --> 00:03:17.730
What if that's all you get?

00:03:17.740 --> 00:03:20.460
You telling your client that they can't use that service provider?

00:03:20.840 --> 00:03:24.370
Uh, it could be the case then, that if that client,

00:03:24.380 --> 00:03:29.310
if my client has only that from the service provider,

00:03:29.320 --> 00:03:31.010
that I would then go to the service provider and say,

00:03:31.010 --> 00:03:31.270
Well,

00:03:31.270 --> 00:03:37.500
I'm I'm willing to essentially incorporate your stuff into my

00:03:37.500 --> 00:03:41.940
assessment of my client or go get an assessor,

00:03:41.950 --> 00:03:42.410
right?

00:03:42.420 --> 00:03:44.300
S o e.

00:03:44.300 --> 00:03:47.660
I mean, that that's that's a sort of hard sort of bargain to Docker, right?

00:03:47.670 --> 00:03:49.870
But that's I mean, otherwise, what assurances do you have?

00:03:49.870 --> 00:03:50.060
I mean,

00:03:50.060 --> 00:03:56.440
I don't I don't take my clients assurances we completed this questionnaire.

00:03:56.440 --> 00:03:59.220
You don't need to ask us about patching right on.

00:03:59.220 --> 00:04:02.290
This third-party is part of that environment, right?

00:04:02.300 --> 00:04:05.340
So why would I take their self A to AD DS station?

00:04:05.340 --> 00:04:08.470
Their self assessment saying, Yeah, you don't have to ask us any questions.

00:04:08.470 --> 00:04:11.890
We take all these boxes for you because they're gonna be held

00:04:11.890 --> 00:04:13.970
contractually liable if they're if they're telling a fib.

00:04:14.140 --> 00:04:16.260
A conceivably.

00:04:16.640 --> 00:04:23.230
Um, if if the service provider is telling a fib or is just miss taken right,

00:04:23.240 --> 00:04:25.420
let's give them the benefit of you know,

00:04:25.420 --> 00:04:28.810
our our, uh and my client gets breached,

00:04:28.820 --> 00:04:29.050
right?

00:04:29.050 --> 00:04:33.180
My client is holding the bag with respect to the payment

00:04:33.180 --> 00:04:36.140
brands or the acquiring banks or what have you,

00:04:36.150 --> 00:04:36.620
Right?

00:04:36.630 --> 00:04:42.790
Um, and if they have any recourse against that service provider,

00:04:42.800 --> 00:04:43.030
right,

00:04:43.040 --> 00:04:45.630
its's them basically bringing legal action against the

00:04:45.640 --> 00:04:47.530
party based on whatever is in the contract,

00:04:47.540 --> 00:04:51.970
which, you know, may or may not have any meaningful substance.

00:04:52.940 --> 00:04:54.020
You're not like us.

00:04:54.030 --> 00:04:54.980
You're not gonna get into that.

00:04:54.980 --> 00:04:56.110
Well, do you have enough liability?

00:04:56.120 --> 00:04:59.960
Yeah, I'm not an attorney, and I'm not going to pretend to be one.

00:04:59.970 --> 00:05:00.580
Right.

00:05:00.590 --> 00:05:04.340
And so saying, do you have any legal recourse against this entity?

00:05:04.350 --> 00:05:06.730
E don't know, right?

00:05:06.740 --> 00:05:08.140
Somebody else's job to find that out.

00:05:08.150 --> 00:05:08.510
Okay,

00:05:08.520 --> 00:05:13.030
so we've got a list we've got written agreements were gathering

00:05:13.030 --> 00:05:18.310
after stations of compliance done by an on site is nested all you're

00:05:18.310 --> 00:05:19.960
going out on assessing the third-party.

00:05:19.960 --> 00:05:21.750
Is part of this part of it, right?

00:05:22.440 --> 00:05:22.950
Um,

00:05:23.840 --> 00:05:29.580
on that guess is to the end and you pass the the only other piece I would say

00:05:29.580 --> 00:05:32.010
is when you're gathering those adaptations of compliance,

00:05:32.020 --> 00:05:32.450
right?

00:05:32.460 --> 00:05:35.570
This is where you want the client to have some meaningful process to do that

00:05:35.580 --> 00:05:40.640
because I want to say they want to make sure Does my third-party Are they

00:05:40.640 --> 00:05:44.060
getting assessed for the relevant requirements to me?

00:05:44.070 --> 00:05:44.690
Right.

00:05:44.690 --> 00:05:46.790
So maybe the easiest examples, if you have,

00:05:46.790 --> 00:05:48.730
like, a managed services provider, right,

00:05:48.740 --> 00:05:50.200
That's providing, like,

00:05:50.200 --> 00:05:52.590
managed operating systems error managed networking devices,

00:05:52.590 --> 00:05:52.940
right?

00:05:52.950 --> 00:05:57.590
Did they just get assessed for the physical security of their co location space?

00:05:57.590 --> 00:06:00.050
Or did they get their manage services assessed Also?

00:06:00.240 --> 00:06:08.080
And if their coverage isn't equivalent to your service use,

00:06:08.090 --> 00:06:09.100
then you got a problem.

00:06:09.110 --> 00:06:15.050
My reflection on that is many people buy services optimistically, right?

00:06:15.060 --> 00:06:17.380
They get the AOC and do brilliant.

00:06:17.380 --> 00:06:17.860
I've got the O.

00:06:17.860 --> 00:06:18.050
C.

00:06:18.050 --> 00:06:19.240
Don't look at it right,

00:06:19.250 --> 00:06:24.890
And it's actually really important because many times vendors make I'm

00:06:24.890 --> 00:06:29.250
gonna give him the benefit of the doubt a mist ake on sending an AOC for

00:06:29.250 --> 00:06:32.370
a service that actually that you're not buying where they don't have a

00:06:32.370 --> 00:06:34.230
NAOC for the service you are buying.

00:06:34.240 --> 00:06:38.960
I've seen it so many times that it's such a common mistake's that sometimes

00:06:38.940 --> 00:06:41.610
sometimes I doubt the integrity of people who were doing that.

00:06:41.620 --> 00:06:42.600
That does happen.

00:06:42.600 --> 00:06:44.610
So I'm gonna be, you know, being really honest.

00:06:44.610 --> 00:06:47.230
You have to check, but what you're buying.

00:06:47.240 --> 00:06:51.570
But iOS covers my favorite about that was actually finding.

00:06:51.570 --> 00:06:54.870
I think this was a It was a version 3.0 a.

00:06:54.870 --> 00:06:54.960
O.

00:06:54.960 --> 00:06:55.780
C.

00:06:55.790 --> 00:06:58.380
After 3.0 had ended right,

00:06:58.390 --> 00:07:03.410
and the date on the AOC was after the sunset of 3.13

00:07:03.410 --> 00:07:06.550
point one was supposed to be used, but they're just hopeful,

00:07:06.560 --> 00:07:06.880
you know?

00:07:06.890 --> 00:07:09.110
Well, you know are essentially daring you like.

00:07:09.110 --> 00:07:09.660
What are you gonna do?

00:07:09.660 --> 00:07:10.860
Fail me for that?

00:07:11.240 --> 00:07:11.570
Thanks.

00:07:12.040 --> 00:07:14.550
Do we really need to throw down, right?

00:07:14.560 --> 00:07:15.250
Really?

00:07:16.540 --> 00:07:18.770
Also, in terms of service providers,

00:07:18.780 --> 00:07:21.040
there is some people are not service providers.

00:07:21.040 --> 00:07:21.400
For instance,

00:07:21.400 --> 00:07:24.000
you're acquiring bank is not a service provided to You

00:07:24.000 --> 00:07:26.720
don't need to ask your acquiring bank for their AOC

00:07:26.730 --> 00:07:28.050
because they're probably laughing.

00:07:28.050 --> 00:07:32.270
But it might be fun if you try, but other, you won't get success.

00:07:32.270 --> 00:07:34.880
I have seen those listed in section 12.8 on many

00:07:34.880 --> 00:07:38.150
occasions where the QoS adjust says, Well,

00:07:38.150 --> 00:07:39.830
you you give the Dodgers the acquiring bank,

00:07:39.830 --> 00:07:42.680
so we have to list all we have to list them on if they're listening.

00:07:42.680 --> 00:07:46.060
12 8, you need you need evidence and compliance, don't you?

00:07:47.140 --> 00:07:50.350
Yeah, I've seen that happen, right?

00:07:50.360 --> 00:07:53.530
And and there is a section in the summary part of the rock where that says,

00:07:53.530 --> 00:07:56.620
who are the entities that you are, you know,

00:07:56.630 --> 00:07:59.430
sending payment card data to where you should list all the

00:07:59.430 --> 00:08:01.040
acquiring institutions error payment process,

00:08:01.040 --> 00:08:02.500
but that's not the same thing is 12.8.

00:08:02.510 --> 00:08:05.360
But the problem is that section in the rock at the bottom says

00:08:05.360 --> 00:08:07.860
these people will be listed in 12.8 IE6.

00:08:07.860 --> 00:08:08.650
A bit of bad.

00:08:08.660 --> 00:08:10.070
It's bad type Power BI.

00:08:10.080 --> 00:08:11.710
There's a little bit of that.

00:08:11.720 --> 00:08:12.560
I actually have one.

00:08:12.560 --> 00:08:16.090
Where we were employing a service provider who sent

00:08:16.090 --> 00:08:19.500
the card data to us that you get.

00:08:19.510 --> 00:08:21.580
You get odd situations like that,

00:08:21.590 --> 00:08:25.290
or or sometimes you have a situation where there is an entity

00:08:25.290 --> 00:08:26.940
that's a merchant and a service provider.

00:08:26.950 --> 00:08:31.420
And sometimes you get these kind of, you know, tail wagging the dog situations.

00:08:31.430 --> 00:08:32.770
Yeah, but the end of the day,

00:08:32.770 --> 00:08:35.500
it's Whoever's got the contract with the payment brand is the person that's

00:08:35.500 --> 00:08:37.970
responsible for making sure that everyone else is compliant,

00:08:38.039 --> 00:08:38.419
right?

00:08:38.429 --> 00:08:38.760
Yeah.

00:08:40.440 --> 00:08:44.260
And then this needs to be an ongoing thing, doesn't it?

00:08:44.270 --> 00:08:46.750
So you're coming back from assessment in year two.

00:08:46.760 --> 00:08:49.680
You're not gonna accept the same bits of paper, are you?

00:08:49.690 --> 00:08:51.670
They should get new ones, right?

00:08:51.680 --> 00:08:54.950
You know, I have this situation where, uh,

00:08:55.440 --> 00:08:57.360
a lot of my clients, uh,

00:08:58.140 --> 00:09:03.050
host their stuff in co location facilities who are also our clients.

00:09:03.060 --> 00:09:07.150
Right and they get this sort of weird expectation that I'm just

00:09:07.150 --> 00:09:10.500
going to go bother my colleagues for the A.

00:09:10.500 --> 00:09:10.740
C.

00:09:10.740 --> 00:09:10.860
S.

00:09:10.860 --> 00:09:12.550
For those entities that seems reasonable.

00:09:12.560 --> 00:09:16.770
Well, e like the mechanics of that I don't care, right?

00:09:16.740 --> 00:09:17.650
Like Okay, fine.

00:09:17.650 --> 00:09:18.220
I'll go.

00:09:18.230 --> 00:09:20.250
You know, find it in our file share somewhere.

00:09:20.250 --> 00:09:21.230
That's fine, right?

00:09:21.240 --> 00:09:25.470
But the point is, you need to have some process to manage your service provider,

00:09:25.480 --> 00:09:25.970
right?

00:09:25.980 --> 00:09:28.550
And that process can't be bother, your assessor,

00:09:28.550 --> 00:09:30.120
because they also assess your services.

00:09:30.120 --> 00:09:32.700
Absolutely has to be where I've worked.

00:09:32.700 --> 00:09:36.820
You know, we create a calendar, and so we know when the AOC expires.

00:09:36.830 --> 00:09:39.240
So we go back like, two months on.

00:09:39.240 --> 00:09:42.350
There's a calendar reminder to contact the service provider and say

00:09:42.360 --> 00:09:44.520
you're gonna be out of compliance in two months time.

00:09:44.520 --> 00:09:46.530
What are you doing about it we're working at?

00:09:46.540 --> 00:09:49.000
Because that's often the real early warning We go.

00:09:49.000 --> 00:09:50.460
Yeah, we decided not to do it this year.

00:09:51.740 --> 00:09:53.030
And iPad, That's right.

00:09:53.040 --> 00:09:55.120
It's like you can't decide not to do it.

00:09:55.120 --> 00:09:57.170
It's written in our contract, for example.

00:09:57.180 --> 00:10:00.620
So find out early and then and then chase.

00:10:00.630 --> 00:10:02.510
But e mean in big companies,

00:10:02.510 --> 00:10:04.680
that's actually that's a full time job for someone is

00:10:04.690 --> 00:10:06.960
absolutely be a full time job with a large enough

00:10:06.960 --> 00:10:09.170
organization with enough service providers.

00:10:09.140 --> 00:10:09.360
Yeah,

00:10:09.360 --> 00:10:13.570
you could spend your whole time chasing AJAX and barking at people

00:10:13.570 --> 00:10:15.700
saying when you're gonna get your revalidation done.

00:10:15.930 --> 00:10:17.650
No, I mean yeah, literally.

00:10:18.340 --> 00:10:18.900
We do.

00:10:18.910 --> 00:10:21.250
I mean, I work places where you do that.
