WEBVTT

00:00:01.040 --> 00:00:04.050
[Autogenerated] whenever I advise any organization about PC I.

00:00:04.050 --> 00:00:04.200
D.

00:00:04.200 --> 00:00:07.270
S s compliance have a really simple strategy,

00:00:07.430 --> 00:00:11.390
which is that I want the organization to do as little PC ideas us as

00:00:11.390 --> 00:00:15.670
possible unless the organization is in the business of storing,

00:00:15.850 --> 00:00:17.940
processing and transmitting payment card data.

00:00:17.950 --> 00:00:18.300
A.

00:00:18.430 --> 00:00:20.050
That's the way it makes its revenue.

00:00:20.840 --> 00:00:23.760
There are three reasons I take this approach personally.

00:00:24.060 --> 00:00:26.600
By reducing the footprint of systems that store

00:00:26.690 --> 00:00:28.560
process or transmit cardholder data,

00:00:28.680 --> 00:00:32.150
we automatically reduce the attack surface on the risk

00:00:32.540 --> 00:00:34.420
minimizing the number of systems,

00:00:34.420 --> 00:00:37.160
networks and applications that a criminal can attack to

00:00:37.160 --> 00:00:41.160
steal cardholder data increases our ability to protect

00:00:41.170 --> 00:00:42.550
them from such a hostile attack.

00:00:43.790 --> 00:00:47.740
Secondly, PC idea says compliance is really expensive to maintain,

00:00:47.960 --> 00:00:50.100
and this is what most organizations fail to

00:00:50.100 --> 00:00:52.570
understand where they start compliance.

00:00:52.570 --> 00:00:55.240
Journey Getting compliant is only half the battle.

00:00:55.520 --> 00:01:00.140
Maintaining compliance requires dedication personnel systems on

00:01:00.140 --> 00:01:04.590
proactive assessments and finally having a large Kartal.

00:01:04.590 --> 00:01:08.400
The data environment typically reduces an organization's ability to

00:01:08.400 --> 00:01:11.930
change quickly because every change the business is,

00:01:11.930 --> 00:01:14.160
it changed the cardholder data environment,

00:01:14.410 --> 00:01:17.550
which then becomes a mini PC I project on its own.

00:01:18.240 --> 00:01:20.300
So for these three key reasons.

00:01:20.490 --> 00:01:23.820
My approach to try to reduce the size of the cardinal,

00:01:23.820 --> 00:01:27.220
the data environment rather than trying to apply PC

00:01:27.220 --> 00:01:32.290
idea says to the as is systems, networks and applications.

00:01:33.520 --> 00:01:37.200
And when we talk about reducing the size of the cardholder data environments,

00:01:37.570 --> 00:01:39.530
there are typically four things that weaken.

00:01:39.530 --> 00:01:44.720
Do the first and most powerful is just delete cardholder

00:01:44.720 --> 00:01:46.850
data that doesn't need to be stored.

00:01:47.340 --> 00:01:50.750
Organizations typically used to keep lots of cardholder data,

00:01:50.980 --> 00:01:52.980
but nowadays often there's no need.

00:01:53.230 --> 00:01:54.980
If ever the real card numbers needed,

00:01:55.160 --> 00:01:58.480
it could be retreat from an acquirer or a payment service provider on

00:01:58.480 --> 00:02:01.550
refunds can usually be managed against transaction references.

00:02:01.940 --> 00:02:06.080
So my first strategy, once I found all the cardholder data in an organization,

00:02:06.220 --> 00:02:09.789
is to argue strongly that it should be deleted and then make people

00:02:09.789 --> 00:02:14.890
justify why it needs to be kept the second powerful technique in

00:02:14.890 --> 00:02:17.360
reducing the site of an organization's Kartal.

00:02:17.360 --> 00:02:20.780
The data environment is to pass the problem to somebody else

00:02:20.960 --> 00:02:23.650
that specializes in securing cardholder data,

00:02:24.340 --> 00:02:28.550
so work out what business processes can be outsourced to PC idea,

00:02:28.550 --> 00:02:30.300
says compliant service providers.

00:02:30.840 --> 00:02:31.400
Often,

00:02:31.520 --> 00:02:34.950
you'll also find a business benefit in this because the payment

00:02:34.950 --> 00:02:38.050
service provider is not only looking after security,

00:02:38.540 --> 00:02:41.460
but the payments of his brother's constantly innovating how

00:02:41.460 --> 00:02:43.710
payments can be accepted and process.

00:02:44.840 --> 00:02:48.950
The third option often complements the consideration of outsourcing,

00:02:49.340 --> 00:02:52.310
and that's to look at whether there's a better way of running

00:02:52.310 --> 00:02:55.930
a particular payment processing related business process that

00:02:55.930 --> 00:02:57.460
might be a business process.

00:02:57.460 --> 00:03:00.650
Change your technology chase that supports the business process Change.

00:03:01.640 --> 00:03:04.970
Finally, if there's no way of changing business processes,

00:03:04.970 --> 00:03:08.080
deleting cardholder data or outsourcing the problem,

00:03:08.250 --> 00:03:09.700
then it's time to work out.

00:03:09.710 --> 00:03:12.430
If it is possible to segmental re architect networks and

00:03:12.430 --> 00:03:18.040
systems to create an isolated cuddle, the data environment segmenting the card.

00:03:18.040 --> 00:03:20.560
All the data environment from other systems and networks

00:03:20.770 --> 00:03:24.150
means that the entire organizations, networks and no in scope.

00:03:24.940 --> 00:03:29.140
So you'd need to go back to the as is picture that describes the flow of

00:03:29.140 --> 00:03:32.120
payment card data between applications and across networks.

00:03:32.300 --> 00:03:35.280
Toe work out how the cardholder data environment could be

00:03:35.280 --> 00:03:38.170
segmented from the rest of the organizations networks.

00:03:38.940 --> 00:03:43.040
Typically, this is going to entail segmentation by creating networks,

00:03:43.040 --> 00:03:45.350
zones separated by firewalls.

00:03:46.490 --> 00:03:49.750
Let's look a couple of simple examples of scope reduction
