WEBVTT

00:00:01.200 --> 00:00:02.060
[Autogenerated] in this module,

00:00:02.190 --> 00:00:04.360
we would be looking at what is probably going to be the

00:00:04.360 --> 00:00:08.710
longest phase of your PC ideas s journey to compliance In

00:00:08.710 --> 00:00:11.560
scoping segmentation of scope production,

00:00:11.760 --> 00:00:13.840
we're thinking about how many systems,

00:00:13.840 --> 00:00:18.350
networks and applications will need to comply with the PC ideas s requirements.

00:00:19.640 --> 00:00:22.410
And although I've split this journey up into these faces,

00:00:22.640 --> 00:00:26.950
it's quite possible now that the way you approach your compliance

00:00:26.950 --> 00:00:30.170
journey may combine some of the activities that I've actually put

00:00:30.170 --> 00:00:33.140
into separate faces in this module.

00:00:33.290 --> 00:00:36.320
We start off with the as his picture we worked out

00:00:36.320 --> 00:00:37.540
at the end of the last module.

00:00:37.670 --> 00:00:38.190
Remember,

00:00:38.330 --> 00:00:41.620
that's are accurate picture of the way that our organization

00:00:41.620 --> 00:00:46.370
currently processes payment cards with then go to do a couple more

00:00:46.370 --> 00:00:49.930
bits of thinking where we decide how large an environment we want to

00:00:49.930 --> 00:00:53.960
make comply with PC idea cess and also make an initial assessment of

00:00:53.960 --> 00:00:55.170
the technical controls,

00:00:55.330 --> 00:00:59.250
policies and procedures that may be missing in our organization.

00:00:59.740 --> 00:01:03.780
That's going to give us a big work plan where we re engineer and re architect.

00:01:03.780 --> 00:01:07.580
Our systems deleted wanted data and maybe outsourcing business

00:01:07.580 --> 00:01:10.710
activities had the end of all that work.

00:01:10.790 --> 00:01:13.350
While which may take a number of years of a PC,

00:01:13.350 --> 00:01:14.120
I program,

00:01:14.480 --> 00:01:17.710
we end up with our new picture of the way we store

00:01:17.870 --> 00:01:20.290
process and transmit cardholder data,

00:01:20.550 --> 00:01:24.350
which gives us a new scope for RPC ideas s compliance assessment.

00:01:25.740 --> 00:01:29.750
And that is typically time to get an external assessment of that new scope.

00:01:29.900 --> 00:01:32.850
To see how far away we are from meeting PC idea

00:01:32.850 --> 00:01:35.210
assesses prescriptive requirements.

00:01:35.940 --> 00:01:40.060
This exercise will generally lead to another face of work where we re

00:01:40.060 --> 00:01:42.750
mediate problems found in that initial assessments.

00:01:43.240 --> 00:01:50.800
Then we really ready for our first formal PC ideas s assessment in this module.

00:01:50.900 --> 00:01:53.370
I'm going to use the word scope quite a lot,

00:01:53.600 --> 00:01:56.890
and you'll often hear people talking about scoping and scope

00:01:56.890 --> 00:01:59.550
reduction when they talk about PC idea sets.

00:02:00.240 --> 00:02:04.390
One quite annoying thing is that scope is often used to

00:02:04.390 --> 00:02:06.700
mean different things to different people.

00:02:07.540 --> 00:02:09.940
Sometimes when people use the word scope,

00:02:10.150 --> 00:02:13.130
they mean we need to consider whether the system application

00:02:13.130 --> 00:02:15.910
that work or person has anything to do with PC.

00:02:15.910 --> 00:02:22.410
Idea says it's in scope of consideration and is part of any assessment on

00:02:22.410 --> 00:02:26.020
Assessor will look at the entire organization who want to know your

00:02:26.020 --> 00:02:30.360
justification for saying some parts of the organization are outside the scope

00:02:30.360 --> 00:02:33.750
of PC idea set where others are within the scope of PC.

00:02:33.750 --> 00:02:34.520
Idea says.

00:02:35.340 --> 00:02:39.430
The second way that scope is used is to say that a particular system,

00:02:39.540 --> 00:02:43.950
person or network is in scope of some or all of the requirements.

00:02:43.950 --> 00:02:47.700
That PC idea says demands if an organization stores,

00:02:47.840 --> 00:02:49.980
processes or transmits cardholder data,

00:02:50.270 --> 00:02:54.150
everything Enver organizations in scope of consideration.

00:02:54.540 --> 00:02:57.540
But not everything will need to comply with some or all

00:02:57.580 --> 00:02:59.750
of PC idea assesses requirements.

00:03:01.190 --> 00:03:05.620
Now you may remember this slide from the big picture course because it describes

00:03:05.760 --> 00:03:09.290
which systems are in scope of the PC ideas s requirements.

00:03:10.340 --> 00:03:13.850
We start off with the cardholder data environment or C d A,

00:03:14.290 --> 00:03:16.360
and that's defined as any technology,

00:03:16.540 --> 00:03:20.210
people or processes which store process transmit

00:03:20.210 --> 00:03:22.790
cardholder data on by technology.

00:03:22.790 --> 00:03:26.820
We basically mean networks, systems and applications.

00:03:27.540 --> 00:03:31.460
Once we define the CD, we've been need to determine the technology,

00:03:31.460 --> 00:03:31.930
the people,

00:03:31.930 --> 00:03:35.490
the processes that are also connected to the cardholder data

00:03:35.490 --> 00:03:39.050
environment or that could affect the security of the TV.

00:03:39.740 --> 00:03:43.640
Those two environments together described the scope that the PC I.

00:03:43.640 --> 00:03:47.240
D S s requirements will apply to One thing to be careful

00:03:47.240 --> 00:03:50.920
about is that some of the PC idea says requirements only

00:03:50.920 --> 00:03:53.540
apply to systems in the cartel, the data environment.

00:03:53.810 --> 00:03:56.710
And so when you look at a requirement when you're doing PC,

00:03:56.710 --> 00:03:59.880
Idea says it's important to see whether this requirements just be

00:03:59.880 --> 00:04:02.920
restricted to active in the carnal data environment or if it

00:04:02.920 --> 00:04:04.950
applies to connected to systems as well.

00:04:06.280 --> 00:04:11.400
Another way of thinking about PC idea says scoping, is to imagine three zones.

00:04:12.040 --> 00:04:14.820
The inside zone is the cardholder data environment,

00:04:14.910 --> 00:04:18.750
which contains the systems that store process or transmit cardholder data.

00:04:19.339 --> 00:04:22.000
The next zone is the connected to zone,

00:04:22.150 --> 00:04:25.190
which includes systems that are connected to the cardholder data

00:04:25.190 --> 00:04:28.730
environment or that can affect the security off the cardholder data

00:04:28.730 --> 00:04:31.280
environments and then in the final zone,

00:04:31.460 --> 00:04:34.250
the systems that are not connected to the CD at all.

00:04:35.140 --> 00:04:38.320
One really good way of determining whether a system is

00:04:38.320 --> 00:04:41.750
connected to or not connected to is to think what would

00:04:41.750 --> 00:04:43.750
happen if that system was compromised.

00:04:44.640 --> 00:04:49.460
But the way I like to think of it is that for systems connected to the CD,

00:04:49.630 --> 00:04:50.960
if they're compromised.

00:04:51.100 --> 00:04:53.260
The Attackers got a foothold into the cut.

00:04:53.260 --> 00:04:54.450
All the data environment.

00:04:54.940 --> 00:04:56.280
So I care about that.

00:04:57.340 --> 00:04:59.810
Where a systems that are not connected to the CD A.

00:05:00.090 --> 00:05:04.270
If an attacker compromises them, he might be bad for my organization.

00:05:04.450 --> 00:05:06.500
But I'm not worried about the security of cardholder.

00:05:06.500 --> 00:05:08.360
Data, in fact,

00:05:08.360 --> 00:05:14.150
gives us three logical scopes systems that in the cardholder data environment

00:05:14.640 --> 00:05:18.160
systems that are connected to the cardholder data environment always could

00:05:18.160 --> 00:05:23.670
affect the security of the CD and systems that we've looked at considered and

00:05:23.670 --> 00:05:27.850
decided that Law of the PC idea says requirements replicable because above

00:05:27.850 --> 00:05:29.510
their part of our organization,

00:05:29.700 --> 00:05:32.680
they don't fall into the other two scoping categories.

00:05:33.980 --> 00:05:37.100
Now we're at the stage where we have an accurate picture of the

00:05:37.100 --> 00:05:40.480
systems in our organization that store process,

00:05:40.490 --> 00:05:42.030
transmit carnal the data.

00:05:42.220 --> 00:05:46.400
Andi, If we mapped both authorization and clearing separately,

00:05:46.660 --> 00:05:49.820
we know which systems contain primary account numbers on which

00:05:49.820 --> 00:05:52.650
systems also contain sensitive authentication data,

00:05:53.690 --> 00:05:56.120
as well as knowing the technicalities of where cardholder

00:05:56.120 --> 00:05:58.150
data flows through the organization.

00:05:58.540 --> 00:06:01.370
We know the business processes which generate those Cardell

00:06:01.370 --> 00:06:03.920
the data flows and really importantly,

00:06:04.060 --> 00:06:07.950
we know who to go and talk to if we need to change those business processes,

00:06:08.640 --> 00:06:12.870
we've hopefully got an inventory of all the third party service providers

00:06:12.870 --> 00:06:17.090
that store process or transmit Kartal dilator on our behalf or who could

00:06:17.090 --> 00:06:19.250
affect the security of our cold hold of data.

00:06:19.740 --> 00:06:22.630
Which means we're now in a position to determine what our

00:06:22.630 --> 00:06:25.150
cardholder data environment would look like,

00:06:25.540 --> 00:06:29.050
what systems networks and what applications air in it.

00:06:29.470 --> 00:06:34.230
And then, more importantly, we can see how many systems are connected to our cut.

00:06:34.230 --> 00:06:35.980
All the data environment poor can affect the

00:06:35.980 --> 00:06:38.720
security of the CD eight and honestly,

00:06:39.010 --> 00:06:42.420
when most organizations first completeness exercise.

00:06:42.610 --> 00:06:45.760
But you realize that their entire organization is in scope,

00:06:45.920 --> 00:06:51.520
have all of the PC ideas s requirements applied to it and bat Liza very nicely

00:06:51.600 --> 00:06:54.850
to the next big thinking stage of the compliance journey.

00:06:55.340 --> 00:06:59.710
And the question we need to answer is how much PC idea says,

00:06:59.710 --> 00:07:01.650
Does your organization want to do?

00:07:02.240 --> 00:07:06.120
Do we want to apply all those prescriptive technical controls toe every

00:07:06.120 --> 00:07:09.750
system application and network in our organization?

00:07:10.580 --> 00:07:13.720
Other new things we want to do anyway and doing them at the same

00:07:13.720 --> 00:07:15.920
time as we consider the scope and size of RPC,

00:07:15.920 --> 00:07:16.450
Idea says.

00:07:16.450 --> 00:07:18.310
Environment is a sensible thing.

00:07:19.470 --> 00:07:20.860
Other business processes,

00:07:20.860 --> 00:07:24.850
particularly around how we accept and process payments that we want to change.

00:07:25.340 --> 00:07:25.530
Well,

00:07:25.530 --> 00:07:29.700
perhaps we want to use PCR DSS compliance as a catalyst to

00:07:29.700 --> 00:07:32.350
change the organization's security profile.

00:07:33.280 --> 00:07:37.230
We also have to realize that we might want to do lots of things,

00:07:37.280 --> 00:07:40.520
but the organization is under a constraint of being

00:07:40.520 --> 00:07:44.480
compliant by a certain date on the finally do we understand

00:07:44.480 --> 00:07:46.580
any cost constraints for the PC idea?

00:07:46.580 --> 00:07:47.650
Says compliance.

00:07:48.680 --> 00:07:49.680
In this notes clip,

00:07:49.810 --> 00:07:54.690
Jacob and I discuss how an organisation's culture can affect scoping decisions.
