WEBVTT

00:00:00.040 --> 00:00:02.560
[Autogenerated] the car brands have listings of service providers.

00:00:02.570 --> 00:00:03.090
Yes.

00:00:03.640 --> 00:00:07.580
Does the service provider has to be listed listed on that car brand listing?

00:00:07.590 --> 00:00:08.520
Not necessarily.

00:00:08.530 --> 00:00:09.240
Uh,

00:00:09.250 --> 00:00:12.820
and And I've have a lot of service provider clients that

00:00:12.820 --> 00:00:15.560
don't seek that card brand listing.

00:00:15.570 --> 00:00:16.320
Uh,

00:00:16.329 --> 00:00:19.220
there are some other steps that you have to go through with the payment

00:00:19.220 --> 00:00:24.430
brands to get on the list beyond just having a compliant AOC.

00:00:24.440 --> 00:00:25.620
And, you know,

00:00:25.620 --> 00:00:29.000
many a lot of service provide a lot of entities who are essentially service

00:00:29.000 --> 00:00:32.280
providers because their clients want them to be right.

00:00:32.290 --> 00:00:35.190
They're not connected to the payments directly there providing,

00:00:35.200 --> 00:00:37.790
you know, infrastructure as a service or they're providing,

00:00:37.790 --> 00:00:39.090
you know, some other technology service,

00:00:39.100 --> 00:00:39.430
right?

00:00:39.430 --> 00:00:42.100
Like the payment is incidental to them.

00:00:42.110 --> 00:00:42.550
Right?

00:00:42.640 --> 00:00:45.000
But their clients want them to be PC IDE.

00:00:45.000 --> 00:00:45.280
SSH.

00:00:45.280 --> 00:00:45.840
Compliance.

00:00:45.850 --> 00:00:46.440
Right.

00:00:46.450 --> 00:00:47.170
And so they don't.

00:00:47.540 --> 00:00:47.920
I mean,

00:00:47.920 --> 00:00:49.660
you just even going through those agent

00:00:49.660 --> 00:00:51.330
registrations steps would be a real hurdle.

00:00:51.340 --> 00:00:51.930
It's a pain.

00:00:51.940 --> 00:00:52.570
Yes.

00:00:52.580 --> 00:00:55.390
If somebody is registered and listed on the car brand site,

00:00:55.400 --> 00:00:56.700
do you need to bother getting the error?

00:00:56.700 --> 00:00:57.280
You see,

00:00:57.290 --> 00:01:00.840
you still need to You still need to get that precisely because the car

00:01:00.840 --> 00:01:05.269
brand websites are sort of conspicuously absent of a lot of the detail

00:01:05.239 --> 00:01:07.830
of what their compliance effort entailed.

00:01:07.860 --> 00:01:09.830
And the AOC, you know,

00:01:09.830 --> 00:01:12.480
particularly after version three of peace AD DS s has a

00:01:12.480 --> 00:01:17.650
lot of substance and a lot more than it used to about what

00:01:17.650 --> 00:01:19.770
was done in the assessment.

00:01:19.780 --> 00:01:21.940
And you need to know that you can match that up with

00:01:21.940 --> 00:01:23.140
what you're expecting them to cover.

00:01:23.150 --> 00:01:24.720
Or, more importantly, what was not done in the U.

00:01:24.730 --> 00:01:24.960
S.

00:01:24.960 --> 00:01:28.760
Also that you know, if you're looking at a zoo you saw in the theory course,

00:01:28.760 --> 00:01:33.480
if you look at an AOC and it's got not applicable in lots of requirements,

00:01:33.480 --> 00:01:35.870
you need to be asking, why wasn't that applicable?

00:01:35.880 --> 00:01:38.360
Because if I'm thinking about how you architect that type

00:01:38.360 --> 00:01:40.080
of service that would be applicable, right?

00:01:40.080 --> 00:01:43.950
Or or it does that matter to what I'm using them for, right?

00:01:44.140 --> 00:01:44.430
Yeah,

00:01:44.430 --> 00:01:46.960
I'm expecting them to store cardholder data and they're saying a bunch

00:01:46.960 --> 00:01:49.200
of things in requirement three or not applicable.

00:01:49.210 --> 00:01:51.370
You know, it doesn't sound right
