WEBVTT

00:00:00.490 --> 00:00:03.740
[Autogenerated] Let's take one final look at the retail network and see

00:00:03.740 --> 00:00:06.660
every architect in a business process re architected.

00:00:06.660 --> 00:00:10.600
Some networks could also help to reduce the scope of PC idea cess.

00:00:11.170 --> 00:00:14.280
If we didn't want to do something like the point to point encryption solution,

00:00:15.340 --> 00:00:16.570
what we could do is,

00:00:16.570 --> 00:00:19.390
rather than a route the car Datar through the point of

00:00:19.390 --> 00:00:21.230
sale system into the store server.

00:00:21.540 --> 00:00:24.530
We could put the point of sale systems on a completely separate

00:00:24.530 --> 00:00:28.470
network and haven't talked directly to the acquirer segmenting

00:00:28.470 --> 00:00:31.490
the point of sale system in the store server from the network

00:00:31.490 --> 00:00:33.050
that carries cardholder data.

00:00:33.590 --> 00:00:36.300
The payment terminal could still send a truncated pan

00:00:36.300 --> 00:00:37.750
through to the point of sale system.

00:00:38.340 --> 00:00:38.870
And yes,

00:00:39.110 --> 00:00:42.200
that means we're not getting the information to the payment system to be

00:00:42.200 --> 00:00:44.350
able to produce the clearing file at the end of each day.

00:00:44.740 --> 00:00:47.340
But it will be really unusual if that could not be

00:00:47.340 --> 00:00:48.830
outsourced to a payment process.

00:00:48.830 --> 00:00:52.080
Auto in acquiring bank with a daily reconciliation file

00:00:52.080 --> 00:00:53.950
sent back into the payment system,

00:00:54.940 --> 00:00:58.950
it's actually really hard to discuss changes in scope and business

00:00:58.950 --> 00:01:02.830
processes because every organization is unique in how it processes

00:01:02.830 --> 00:01:05.880
payment cards and how it wants to conduct his business.

00:01:06.640 --> 00:01:08.800
There are some very common patterns that being

00:01:08.800 --> 00:01:10.380
established in the payment industry,

00:01:10.660 --> 00:01:13.750
and I've tried to show you some of those in the previous examples.

00:01:14.440 --> 00:01:15.250
Outsourcing.

00:01:15.440 --> 00:01:18.690
Replacing cardholder data with tokens or truncated pans and

00:01:18.690 --> 00:01:22.730
segmenting networks are the three most common techniques people

00:01:22.730 --> 00:01:25.040
will use to reduce the scope of their PC idea,

00:01:25.040 --> 00:01:26.120
says compliance.

00:01:27.040 --> 00:01:29.930
And this is one reason that I'm insistent.

00:01:30.110 --> 00:01:33.050
That PC idea says compliance isn't an I t.

00:01:33.050 --> 00:01:33.620
Problem,

00:01:33.780 --> 00:01:37.000
because working out how to reduce the footprint of Kartal today to

00:01:37.000 --> 00:01:39.750
across the organization is a business issue.

00:01:40.840 --> 00:01:42.190
There's one piece of advice,

00:01:42.320 --> 00:01:45.540
but I can't emphasize enough when you've decided

00:01:45.540 --> 00:01:47.290
what your new scope will look like.

00:01:47.350 --> 00:01:51.120
It's really important to validate this with your qualified security assessor,

00:01:51.360 --> 00:01:55.140
who will be independent from any supply you may be working with

00:01:56.140 --> 00:01:58.910
because you don't want to get to the stage of having made a large

00:01:58.910 --> 00:02:00.670
investment in the business process,

00:02:00.670 --> 00:02:04.100
re engineering or or outsourcing or network segmentation,

00:02:04.100 --> 00:02:05.590
ALS or a new technology,

00:02:05.790 --> 00:02:09.259
only to find that your assumption about how that would change your

00:02:09.259 --> 00:02:12.250
organization's PC idea so scope was incorrect.

00:02:13.740 --> 00:02:17.470
Scoping is a complicated thing in PC Idea says from a car.

00:02:17.480 --> 00:02:21.580
Emphasize enough how important it is to minimize the attack surface on

00:02:21.580 --> 00:02:24.580
the ongoing cost of compliance to make the footprint of cardinal the

00:02:24.580 --> 00:02:28.280
data a smallest possible in any organization.

00:02:28.540 --> 00:02:33.300
Now there is this really interesting guidance document from the PC I SSC,

00:02:33.470 --> 00:02:36.420
but talks about scoping it talks about shared services,

00:02:36.540 --> 00:02:41.040
and it shows some common patterns of ways that people may may reduce,

00:02:41.040 --> 00:02:44.650
scope or understand scope, so it's a really useful document to review.
