WEBVTT

00:00:01.240 --> 00:00:03.150
[Autogenerated] Here's the wide brain coffee retail.

00:00:03.150 --> 00:00:04.450
Know what we looked earlier?

00:00:05.240 --> 00:00:06.010
Let's go through it.

00:00:06.120 --> 00:00:09.040
Looking at where cardholder data is stored and ask

00:00:09.040 --> 00:00:10.460
you whether it can be deleted.

00:00:11.540 --> 00:00:13.440
We discovered that date was store on the point of

00:00:13.440 --> 00:00:15.710
sale system and on the store server.

00:00:16.340 --> 00:00:21.460
What we need to do now is to look at how much data stored on why now.

00:00:21.630 --> 00:00:25.510
The reason that data stored here is in case they acquire is off line in the

00:00:25.510 --> 00:00:28.650
merchant isn't able to obtain authorization the time of sale.

00:00:29.340 --> 00:00:31.240
That's a valuable commercial feature.

00:00:31.450 --> 00:00:34.070
And so we probably can't stop the data storage here.

00:00:34.330 --> 00:00:37.510
But perhaps we can restrict stories just to the store server,

00:00:37.720 --> 00:00:40.350
and so there's no data stored on the point cell system.

00:00:41.340 --> 00:00:45.060
We'll also want to check that data is deleted once the authorizations

00:00:45.060 --> 00:00:48.680
received so we can minimize the date of storage in these areas and

00:00:48.680 --> 00:00:51.000
therefore reduce the impact of a data breach.

00:00:51.240 --> 00:00:54.090
Even though we can't completely reduce the scope of our PC.

00:00:54.090 --> 00:00:55.250
Idea, says compliance.

00:00:55.360 --> 00:00:57.380
We're not taking these things out of scope because they're

00:00:57.380 --> 00:00:59.250
still gonna be processing and transmitting.

00:00:59.440 --> 00:01:01.600
We can regis storage, reducing risk.

00:01:02.540 --> 00:01:06.980
The same is probably true of the payment system is required to store data.

00:01:07.070 --> 00:01:10.380
So compresses the clearing file at the end of the day on again,

00:01:10.620 --> 00:01:14.240
or we can probably do here is make sure the date is deleted as soon as

00:01:14.240 --> 00:01:16.790
it's no longer required keeping the amount stored.

00:01:16.790 --> 00:01:18.750
Cardholder data smallest possible.

00:01:19.740 --> 00:01:22.990
And now we come to a database service storing the card details for

00:01:23.000 --> 00:01:27.240
every transaction but y break office ever made on.

00:01:27.240 --> 00:01:29.150
We need to find out why that is.

00:01:30.340 --> 00:01:32.280
Typically, in my experience,

00:01:32.420 --> 00:01:36.220
there are a number of reasons why card all the data is stored in databases.

00:01:36.870 --> 00:01:41.240
The first is to be able to track customers spending across multiple wired

00:01:41.240 --> 00:01:44.810
brain coffee branches and use it for analytics and loyalty.

00:01:45.540 --> 00:01:48.700
The second is that somebody thought this was a good idea,

00:01:48.700 --> 00:01:51.150
usually for accounting purposes at one stage.

00:01:51.360 --> 00:01:53.950
But actually nothing is done with the data,

00:01:54.540 --> 00:01:57.660
so we need to find out why the data is stored and ask.

00:01:57.660 --> 00:02:03.430
The question is that another way of doing this on one option could just be to

00:02:03.430 --> 00:02:06.330
store the 1st 6 and last four digits of the card number,

00:02:06.430 --> 00:02:09.680
along with the cardholder's name and a transaction reference

00:02:09.830 --> 00:02:12.190
rather storing the actual whole card number.

00:02:12.470 --> 00:02:14.750
This would probably give enough uniqueness for our loyalty

00:02:14.750 --> 00:02:17.720
program and also be sufficient for accounts when they wanted

00:02:17.720 --> 00:02:19.790
to check refunds or prevent fraud.

00:02:20.540 --> 00:02:23.420
As we know from PC ideas s requirement three,

00:02:23.710 --> 00:02:26.460
The 1st 6 and last four digits of a card number alone

00:02:26.580 --> 00:02:28.550
are not classified as cardholder data.

00:02:28.940 --> 00:02:32.610
So by making this change, the database server no longer stores,

00:02:32.880 --> 00:02:36.130
processes or transmits cardholder data and so now

00:02:36.250 --> 00:02:38.000
doesn't form part of our cardholder.

00:02:38.000 --> 00:02:38.360
Data.

00:02:38.360 --> 00:02:42.970
Environments, however, is still connected to the cardholder data environment,

00:02:43.120 --> 00:02:46.010
so some PC idea says requirements will still apply.

00:02:47.200 --> 00:02:50.940
If we wanted to totally remove the database of From the Scope of PC,

00:02:50.940 --> 00:02:51.630
Idea says,

00:02:51.870 --> 00:02:54.950
we would also have to install a firewall between the payment

00:02:54.950 --> 00:02:58.690
server on the database server with a strict set of rules that

00:02:58.700 --> 00:03:01.180
only allowed the payment served to, say,

00:03:01.280 --> 00:03:03.410
call a stored procedure on the database server.

00:03:03.650 --> 00:03:07.890
But that didn't allow any network connections at all to be initiated

00:03:07.890 --> 00:03:10.250
from the database service side of the firewall.

00:03:11.280 --> 00:03:14.700
Replacing the primary account number, or PAN by another.

00:03:14.700 --> 00:03:18.020
Value is a common technique that organizations used to

00:03:18.020 --> 00:03:19.950
limit the storage of cardholder data.

00:03:20.640 --> 00:03:24.750
There are three values that are typically used to replace the pan.

00:03:25.540 --> 00:03:26.850
The first is truncation,

00:03:27.440 --> 00:03:30.430
where the middle six digits of the card number were

00:03:30.430 --> 00:03:33.310
replaced by another character, typically an asterisk,

00:03:33.550 --> 00:03:36.850
leaving the 1st 6 on the last four digits of a card number.

00:03:37.440 --> 00:03:39.800
Actually, you don't require the 1st 6 digits,

00:03:39.800 --> 00:03:41.650
which is the bank identification number,

00:03:42.140 --> 00:03:46.350
then just keep the last four digits and truncate the remaining 12.

00:03:47.340 --> 00:03:48.550
The second is hashing,

00:03:48.940 --> 00:03:51.810
and this is where a cryptographic hash is creative

00:03:51.810 --> 00:03:53.650
the primary account number now.

00:03:54.040 --> 00:03:57.310
But downside of this technique is that the hash is going to be

00:03:57.310 --> 00:03:59.290
longer than the primary account number itself,

00:03:59.520 --> 00:04:02.290
which may require system changes because the field

00:04:02.290 --> 00:04:03.650
size is going to be different.

00:04:04.440 --> 00:04:07.790
Getting hashing right and secure is quite complicated.

00:04:08.060 --> 00:04:10.810
We talk about it when we discussed Requirement three

00:04:10.820 --> 00:04:13.550
earlier in the PC idea says Path Here, a Plural sites.

00:04:14.040 --> 00:04:18.060
If you want to use the hash to represent a primary account number in a system,

00:04:18.360 --> 00:04:20.519
then it's best to get advice from someone who is

00:04:20.519 --> 00:04:22.820
skilled at cryptographic operations.

00:04:23.740 --> 00:04:27.010
The third way of storing a different identify other

00:04:27.010 --> 00:04:28.330
than the primary account number.

00:04:28.430 --> 00:04:32.750
But being able to relate this to the primary account number is to use a Toko.

00:04:33.340 --> 00:04:36.240
There are commercial token ization systems available,

00:04:36.450 --> 00:04:39.610
which will create something that looks like a primary account number.

00:04:39.790 --> 00:04:41.820
But that isn't a primary account number.

00:04:41.820 --> 00:04:46.280
These air, called format preserving totalization systems token,

00:04:46.280 --> 00:04:48.130
is ations can be one way functions.

00:04:48.130 --> 00:04:51.650
So just like a hat, you could never get back to the primary account number.

00:04:52.340 --> 00:04:54.860
Some token ization systems could be two way,

00:04:55.150 --> 00:04:58.120
which means that at some stage you can turn the token back into the

00:04:58.120 --> 00:05:01.270
primary account number if you're going to do this.

00:05:01.740 --> 00:05:03.210
And personally, it's a technique.

00:05:03.220 --> 00:05:07.130
I've used lots to reduce the size of a cardholder data environment.

00:05:07.410 --> 00:05:10.570
It's quite complicated in terms of your PC ideas,

00:05:10.570 --> 00:05:13.340
a scope and where things are connected to and what can and

00:05:13.340 --> 00:05:16.050
can't turn tokens back into card numbers.

00:05:16.280 --> 00:05:19.750
So again, a recommend that you consult with people have done this before.

00:05:20.840 --> 00:05:21.500
Finally,

00:05:21.760 --> 00:05:25.200
it is really important to remember that all of Ou Bay have replaced

00:05:25.200 --> 00:05:27.150
the premier account number with another value,

00:05:27.600 --> 00:05:33.080
and so now a system does not store or process cardholder data unless you also

00:05:33.090 --> 00:05:35.800
isolate that system from the cardholder data environment,

00:05:36.000 --> 00:05:39.580
it will be still connected to the seedy and therefore in scope

00:05:39.580 --> 00:05:41.980
of some of PC Idea says his requirements.

00:05:43.340 --> 00:05:46.160
Having talked about hashing token ization truncation,

00:05:46.380 --> 00:05:49.960
I must remind you that an encrypted primary account number is still

00:05:49.960 --> 00:05:54.470
cardholder data and systems that store encrypted cardholder data are still

00:05:54.470 --> 00:05:57.590
in scope of all the relevant PC ideas s requirements.
