WEBVTT

00:00:00.240 --> 00:00:02.720
[Autogenerated] That's really the sort of the people

00:00:02.730 --> 00:00:06.660
and policy orientated requirements, right?

00:00:07.140 --> 00:00:09.890
So thinking of thinking of all those together to 12 1

00:00:09.890 --> 00:00:15.530
right the right through to to 12.7, uh, coming back with set,

00:00:15.530 --> 00:00:17.460
You said the query e has to be done.

00:00:17.460 --> 00:00:20.230
You have to see it, but it doesn't have to be any good as an assessor.

00:00:20.240 --> 00:00:23.420
It's difficult to say it's difficult to apply anything

00:00:23.420 --> 00:00:26.230
from the text of the requirements to say,

00:00:26.240 --> 00:00:28.300
Yeah, you're doing it, but it's kind of terrible.

00:00:28.310 --> 00:00:31.530
Okay, The second year, I guess you've got exactly the same.

00:00:31.540 --> 00:00:35.450
Same constraints asl long as it's being done, it's being done right?

00:00:36.740 --> 00:00:38.770
Would you look for a new risk assessment in year two,

00:00:38.770 --> 00:00:40.490
or would you just keep accepting the same risk assess?

00:00:40.490 --> 00:00:42.880
I mean, I wouldn't want it says do an annual risk assessment.

00:00:42.890 --> 00:00:46.130
So So they changed the year on the front.

00:00:46.140 --> 00:00:49.180
If I mean so again,

00:00:49.180 --> 00:00:52.050
this is part of this is trying to get an understanding of

00:00:52.050 --> 00:00:53.710
what they actually did it literally.

00:00:53.710 --> 00:00:56.130
All they did was just update the year right,

00:00:56.140 --> 00:00:58.150
and they didn't actually do any risk assessment.

00:00:58.150 --> 00:01:02.480
They didn't actually evaluate anything right then know what you've

00:01:02.480 --> 00:01:05.060
done is is essentially falsified A document,

00:01:05.069 --> 00:01:05.580
right?

00:01:05.590 --> 00:01:07.990
And I'm pretty sure I've got terms and conditions that

00:01:07.990 --> 00:01:09.210
let me sort of walk away from this.

00:01:09.220 --> 00:01:10.170
You do that to me.

00:01:10.140 --> 00:01:11.070
Um,

00:01:11.040 --> 00:01:17.520
the if you do the risk assessment activities and you arrive

00:01:17.530 --> 00:01:20.760
at some very similar set of conclusions,

00:01:22.040 --> 00:01:23.460
you know, maybe so.

00:01:23.470 --> 00:01:24.000
Okay.

00:01:24.010 --> 00:01:27.770
Failures, failures of doing this leading to compromises.

00:01:27.780 --> 00:01:28.940
I mean, certainly might.

00:01:28.950 --> 00:01:32.000
The one I know best is about not screening employees, probably right.

00:01:32.000 --> 00:01:33.170
Not screening employees.

00:01:33.180 --> 00:01:39.810
Um, that's e mean, other other requirements don't necessarily lead to failures.

00:01:39.810 --> 00:01:44.790
I think maybe if you don't have, ironically,

00:01:44.790 --> 00:01:48.040
the stuff in 12.3 about acceptable use for something

00:01:48.040 --> 00:01:51.440
like remote access right then, then maybe somebody could do something ______.

00:01:51.450 --> 00:01:54.740
And actually, a lot of that is that this is about preventing mistake's,

00:01:54.740 --> 00:01:55.130
isn't it?

00:01:55.140 --> 00:01:57.970
Right rather than maliciousness, right?

00:01:58.440 --> 00:02:02.220
Those of the people in policy was pretty much wrapped up in the next module.

00:02:02.220 --> 00:02:06.750
We're gonna look at getting third parties to work with you who

00:02:06.750 --> 00:02:08.870
have responsibility for bits of your card,

00:02:08.870 --> 00:02:11.790
hold the data environment, or actually have your cardholder data
