WEBVTT

00:00:01.240 --> 00:00:04.090
[Autogenerated] The other thing we need to consider now is how well we

00:00:04.090 --> 00:00:07.120
currently measure up against the PC ideas s requirements.

00:00:07.540 --> 00:00:12.490
We need to look at our current processes and technology and see if bay me the

00:00:12.490 --> 00:00:15.670
particularly prescriptive requirements in the standard.

00:00:16.340 --> 00:00:19.240
I've called this a mini gap assessment because,

00:00:19.250 --> 00:00:22.810
as we're probably about to change some systems and processes is part

00:00:22.810 --> 00:00:27.090
about the scoping exercise is not worth doing a really detailed gap

00:00:27.090 --> 00:00:29.150
assessment against every requirement.

00:00:29.540 --> 00:00:34.040
But we do need to know if there are things that PC I D s s

00:00:34.050 --> 00:00:37.850
requires but we simply don't have or don't do.

00:00:38.440 --> 00:00:39.190
For example,

00:00:39.500 --> 00:00:43.580
we may have never used changed intentional fire integrity monitoring software.

00:00:43.860 --> 00:00:46.040
So this gap assessment would have shown that we need

00:00:46.040 --> 00:00:49.370
to procure and deploy that onda,

00:00:49.370 --> 00:00:54.210
although in the flow of things I've shown this happening before,

00:00:54.210 --> 00:00:56.760
the stuff in organization might do to reduce scope.

00:00:56.980 --> 00:00:59.850
It typically often happens at the same time,

00:01:00.990 --> 00:01:04.650
and that's because this is quite a hard thing for organizations to

00:01:04.650 --> 00:01:08.910
do until you've got a clear picture of what your final scope will

00:01:08.910 --> 00:01:10.890
look like and what you're complies.

00:01:10.890 --> 00:01:15.270
Target is you can't really assess with your existing security controls a

00:01:15.270 --> 00:01:18.540
sufficient or whether you'll need to deploy new policies.

00:01:18.540 --> 00:01:19.470
New processes.

00:01:19.560 --> 00:01:25.750
A new technology to meet PC Idea says his prescriptive requirements So you saw

00:01:25.760 --> 00:01:30.150
need a crystal ball to say What were the final state of PC?

00:01:30.150 --> 00:01:33.890
Idea says scope look like and then to a gap assessment against

00:01:33.890 --> 00:01:38.420
that final state before you actually created it on this Gap

00:01:38.420 --> 00:01:40.780
assessment should consider which PC I.

00:01:40.780 --> 00:01:41.100
D.

00:01:41.100 --> 00:01:43.180
S s requirements are in place.

00:01:43.840 --> 00:01:47.280
Whether there's any technical solutions that need to be born deployed

00:01:47.540 --> 00:01:50.900
on whether there are any business processes or policies that need to

00:01:50.900 --> 00:01:55.650
be changed on the results of this many gap assessment will probably

00:01:55.650 --> 00:02:00.520
BASSEM technology led projects and these technology leg projects will

00:02:00.520 --> 00:02:03.770
be able to run alongside the projects associative then into scoping

00:02:03.770 --> 00:02:04.580
initiatives.

00:02:05.740 --> 00:02:09.479
Having worked out what process re engineering re architecture dates,

00:02:09.479 --> 00:02:12.760
deletion outsourcing on new technical controls.

00:02:12.760 --> 00:02:15.720
You need the hard work of PC.

00:02:15.720 --> 00:02:17.950
Idea says Compliance really starts,

00:02:18.920 --> 00:02:22.220
and I've just shown this happening on this one slide.

00:02:22.420 --> 00:02:25.220
But I know this could be a war or a two or even a

00:02:25.220 --> 00:02:28.570
five year program has some stage.

00:02:28.810 --> 00:02:32.650
The program will come to an end the hard work will be over.

00:02:33.040 --> 00:02:34.600
You would have created a new card.

00:02:34.600 --> 00:02:37.620
All the data environment controlled What other systems and

00:02:37.620 --> 00:02:40.950
networks are connected to it by doing segmentation.

00:02:41.340 --> 00:02:45.040
And you may feel that you're ready for your first PC

00:02:45.040 --> 00:02:48.100
ideas s assessment and he might be right.

00:02:48.940 --> 00:02:52.550
But in my experience, you probably won't be ready quite yet.

00:02:53.270 --> 00:02:56.480
And so, in the compliance journey that we're following today,

00:02:56.750 --> 00:02:59.980
your assessor should come in and do a really accurate

00:02:59.980 --> 00:03:02.210
gap assessment to determine away.

00:03:02.210 --> 00:03:04.930
You are compliant on where you are not compliant

00:03:05.120 --> 00:03:07.670
with the requirements of PC I DSS,

00:03:07.810 --> 00:03:11.440
which can then often lead to a re mediation or fixing

00:03:11.440 --> 00:03:13.850
phase before the assessment proper.

00:03:14.940 --> 00:03:18.440
Now you might not need this remediation face, he says.

00:03:18.440 --> 00:03:21.650
I could come in and determine that you're pretty close to being ready

00:03:21.650 --> 00:03:23.980
for the production of your first reporting compliance,

00:03:24.230 --> 00:03:28.290
and they might change their gap assessment into a

00:03:28.470 --> 00:03:31.610
proper assessment in the first few days.

00:03:31.610 --> 00:03:33.250
Having looked at your organization,

00:03:33.380 --> 00:03:37.150
it's very hard to tell because all organizations are different.

00:03:37.540 --> 00:03:39.930
Well, there's typically depends on many variables,

00:03:39.930 --> 00:03:44.920
including how much PC idea says you've decided to do and how much change

00:03:44.920 --> 00:03:48.190
has been in the organization to get to where you are.

00:03:48.440 --> 00:03:51.450
So, as I said, this could be the start of the real assessment.

00:03:51.610 --> 00:03:56.180
Or it could be a pre assessment and remediation phase as

00:03:56.180 --> 00:03:58.830
we're now entering the assessment of faces of a compliance

00:03:58.830 --> 00:04:00.950
program in the next module,

00:04:01.050 --> 00:04:04.410
I'm going to take a fresh look at the testing procedures contained within the

00:04:04.410 --> 00:04:08.640
standard Onda The reporting documents the assessor will be completing as they

00:04:08.640 --> 00:04:13.070
perform the assessment and that so you can get an understanding of how

00:04:13.070 --> 00:04:15.450
rigorous the assessment process will be.

00:04:15.740 --> 00:04:17.950
I'm what the assessor is looking for.

00:04:18.740 --> 00:04:20.089
But before we do that,

00:04:20.290 --> 00:04:23.540
let's hear from Jacob again about how he manages scoping

00:04:23.540 --> 00:04:27.710
decisions in very large organizations and also discusses some

00:04:27.720 --> 00:04:30.640
examples of good and bad scope reduction.

00:04:30.790 --> 00:04:33.550
But he has encountered as an assessor
