WEBVTT

00:00:00.140 --> 00:00:03.320
[Autogenerated] CCTV or whatever Access control is used

00:00:03.320 --> 00:00:04.850
because it doesn't say you have to have CCTV,

00:00:04.850 --> 00:00:07.200
does it CCTV or badge access?

00:00:07.210 --> 00:00:09.980
You know, sort of individually identifying access mechanism.

00:00:09.980 --> 00:00:10.520
Yeah.

00:00:10.530 --> 00:00:13.290
Um, obviously, in your app,

00:00:13.300 --> 00:00:15.820
there's quite strong privacy laws about recording

00:00:15.820 --> 00:00:17.420
people going in and out facilities.

00:00:17.430 --> 00:00:17.760
Right.

00:00:17.770 --> 00:00:24.190
So, uh, that's something that we need to talk about in in the in the assessment,

00:00:24.190 --> 00:00:25.240
which we don't often mention,

00:00:25.240 --> 00:00:29.240
which is this way don't do this requirement because of a legal constraints,

00:00:29.240 --> 00:00:29.590
right?

00:00:29.600 --> 00:00:31.760
This is probably the most common in Europe.

00:00:31.760 --> 00:00:33.960
This is probably the most common place I've seen that, right?

00:00:33.960 --> 00:00:34.240
Right.

00:00:34.240 --> 00:00:37.460
I see the legal constraints sort of show up either for

00:00:37.840 --> 00:00:40.610
privacy laws in your app about CCTV footage,

00:00:40.610 --> 00:00:43.040
retention or in other parts of the world about what

00:00:43.040 --> 00:00:44.410
you could do for background checks, right?

00:00:44.420 --> 00:00:44.810
Right.

00:00:45.280 --> 00:00:46.300
But yeah,

00:00:46.310 --> 00:00:49.930
and that's that's why there is that that feature in the aoc

00:00:49.930 --> 00:00:52.610
that that capability to say I didn't do this because the law

00:00:52.610 --> 00:00:53.860
prohibits me from doing so.

00:00:53.870 --> 00:00:56.160
And yes, local laws supersede PC IDE.

00:00:56.160 --> 00:00:56.550
SSH.

00:00:56.560 --> 00:00:57.410
Absolutely right.

00:00:57.630 --> 00:00:59.870
Despite what your QoS Azure might say to you,

00:00:59.940 --> 00:01:02.290
local laws always supersede PC ideas, right?

00:01:02.300 --> 00:01:03.530
It's written in the standard.

00:01:03.830 --> 00:01:05.830
And that's why there is that tick box well,

00:01:05.830 --> 00:01:07.530
and they tell us that in QoS a training.

00:01:07.530 --> 00:01:11.270
So if you're QoS, Azure is saying no PC IDE nested supersedes local laws.

00:01:12.380 --> 00:01:15.010
I've had QoS iOS app, CLI do says is the law,

00:01:15.260 --> 00:01:17.370
which, of course, it's not,

00:01:17.540 --> 00:01:21.170
although occasionally some laws sort of borrow some

00:01:21.170 --> 00:01:22.560
of the language from the CSS.

00:01:22.560 --> 00:01:23.860
But yeah, it's not okay.

00:01:24.640 --> 00:01:26.270
It is actually where we are today, isn't it?

00:01:26.280 --> 00:01:28.840
Because we're in Nevada and I think it's a state law in Nevada.

00:01:28.850 --> 00:01:29.520
It might be.

00:01:29.520 --> 00:01:30.360
I think it's a statement.

00:01:30.990 --> 00:01:34.230
There's certainly a few US states where it says if you handle cardholder data,

00:01:34.230 --> 00:01:35.880
you should comply with the right.

00:01:36.540 --> 00:01:39.560
So any tips and shortcuts and getting through through

00:01:39.570 --> 00:01:41.440
the physical bits of requirement nine.

00:01:41.540 --> 00:01:47.970
So if you are outsourcing any of your sort of physical

00:01:48.090 --> 00:01:49.930
security stuff to a co location,

00:01:49.930 --> 00:01:52.450
facility or cloud provider or something like that,

00:01:52.650 --> 00:01:58.260
look for some sort of responsibilities matrix,

00:01:58.260 --> 00:02:00.210
um, sort of division of responsibilities matrix,

00:02:00.210 --> 00:02:00.630
right?

00:02:00.640 --> 00:02:02.420
The provider does this stuff.

00:02:02.430 --> 00:02:04.500
The client does this other stuff,

00:02:04.500 --> 00:02:07.290
and here maybe the joint responsibilities and make sure

00:02:07.290 --> 00:02:10.039
that that aligns with what you expect right and make sure

00:02:10.039 --> 00:02:11.940
that that aligns with what?

00:02:11.950 --> 00:02:13.200
They're a O.

00:02:13.200 --> 00:02:13.950
C.

00:02:14.140 --> 00:02:16.960
Says they got tested right as part of their assessment.

00:02:17.150 --> 00:02:19.500
Eso you say all my stuff is in Colo's.

00:02:19.510 --> 00:02:21.220
I don't have any data centers.

00:02:21.320 --> 00:02:25.130
Um, I wouldn't call, you know, the big chunk of requirement nine not applicable.

00:02:25.140 --> 00:02:26.570
I would say it's in place,

00:02:26.670 --> 00:02:30.450
and here is the AOC that substantiate that my

00:02:30.450 --> 00:02:32.370
third-party is holding up their end.
