WEBVTT

00:00:00.940 --> 00:00:03.350
[Autogenerated] now, having have that hard think Andi,

00:00:03.360 --> 00:00:06.280
Maybe posting questions to management that we probably need to

00:00:06.280 --> 00:00:09.930
come back to the next phase of the compliance journey is to

00:00:09.940 --> 00:00:13.340
understand what the current picture of payment card data

00:00:13.340 --> 00:00:15.750
processing is within the organization.

00:00:16.440 --> 00:00:19.250
The aim is to get a clear picture as possible of

00:00:19.250 --> 00:00:23.350
where cardholder data is stored, processed and transmitted in the organization.

00:00:23.780 --> 00:00:28.950
And, more importantly, why is being stored, processed or transmitted?

00:00:29.540 --> 00:00:30.400
It's very rather,

00:00:30.400 --> 00:00:33.350
an organization can give this clear picture without some

00:00:33.350 --> 00:00:35.850
serious business and technical analysis.

00:00:36.340 --> 00:00:40.990
What we need to do then is document what I call the cardholder data footprint,

00:00:41.180 --> 00:00:44.120
describing where the cardholder data is stored,

00:00:44.280 --> 00:00:45.600
processed and transmitted.

00:00:45.850 --> 00:00:48.180
So we need to understand what systems it's on.

00:00:48.370 --> 00:00:52.950
What networks it's transmitted over on what applications touch cardholder data.

00:00:53.640 --> 00:00:57.350
To do this successfully requires two parallel streams of work.

00:00:57.940 --> 00:01:03.310
The first maps of business processes on the second uses technical tools to

00:01:03.310 --> 00:01:07.200
discover where cardholder data is present within an organisation.

00:01:07.200 --> 00:01:08.050
Systems.

00:01:09.340 --> 00:01:11.490
Let's start with mapping business processes,

00:01:11.730 --> 00:01:14.550
and that means we need to understand our acceptance channels.

00:01:14.940 --> 00:01:17.120
If we have face to face retail environments,

00:01:17.170 --> 00:01:21.210
how do we process cards do we have any e commerce websites,

00:01:21.220 --> 00:01:23.450
and if so, how did they process cards?

00:01:23.840 --> 00:01:24.560
And finally,

00:01:24.870 --> 00:01:28.670
do we have any mail order or telephone or the capabilities on a

00:01:28.670 --> 00:01:32.880
word of advice here that you often find an organization does

00:01:32.880 --> 00:01:36.530
have a telephone order capability, even though it doesn't advertise it.

00:01:36.660 --> 00:01:38.760
He might be through the retail stores directly.

00:01:38.860 --> 00:01:40.860
Or there's a small team somewhere in customer

00:01:40.860 --> 00:01:42.730
service that you never knew existed.

00:01:42.860 --> 00:01:45.550
That takes telephone orders for special people.

00:01:46.240 --> 00:01:50.120
Having identified the acceptance channels that exist within an organization,

00:01:50.350 --> 00:01:53.180
there are three key questions you need to find the answers for.

00:01:53.420 --> 00:01:55.450
Firstly, where does the date ago?

00:01:55.840 --> 00:02:02.020
What applications, systems and network store process or transmit cardholder data?

00:02:02.220 --> 00:02:04.380
Secondly, what volume is there?

00:02:04.480 --> 00:02:05.560
How many transactions?

00:02:05.560 --> 00:02:06.750
A day of processed?

00:02:07.140 --> 00:02:07.730
It's cut.

00:02:07.730 --> 00:02:09.090
All the data is stored.

00:02:09.199 --> 00:02:11.840
How long has it kept for what data is stored?

00:02:11.980 --> 00:02:13.050
Why's it stored?

00:02:13.740 --> 00:02:16.270
And then, finally, who owns this business process?

00:02:16.450 --> 00:02:18.680
Because if you want to change the business process,

00:02:18.790 --> 00:02:23.050
say to remove cardholder data storage, who will need to agree to this?

00:02:24.340 --> 00:02:27.250
And you'll remember from the first module that there

00:02:27.250 --> 00:02:28.910
are a number of different functions.

00:02:28.910 --> 00:02:31.210
Associate with Kartal, the data processing.

00:02:31.680 --> 00:02:36.950
These are authorization clearing settlements on undoing transactions.

00:02:37.540 --> 00:02:39.160
In each of these functions,

00:02:39.280 --> 00:02:43.350
some cardholder data will be processed apart from settlement.

00:02:43.740 --> 00:02:45.920
And so when I mapping where carnal the day through,

00:02:45.920 --> 00:02:49.050
stored, processed or transmitted a map each one separately,

00:02:49.540 --> 00:02:52.100
for example, I go to the retail channel and,

00:02:52.100 --> 00:02:54.620
firstly, map out hone authorization happens.

00:02:54.760 --> 00:02:55.600
Then separately,

00:02:55.650 --> 00:02:58.730
I describe the process of sending clearing records at the end of the

00:02:58.730 --> 00:03:01.550
day because different systems may be involved.

00:03:02.140 --> 00:03:03.720
So for each acceptance channel,

00:03:03.910 --> 00:03:07.500
you need to map out which systems store process transmit Kartal the

00:03:07.500 --> 00:03:10.670
data for all of the appropriate payment of functions.

00:03:11.740 --> 00:03:11.950
So,

00:03:11.950 --> 00:03:13.730
for an example of mapping the payment flow of

00:03:13.730 --> 00:03:15.500
cardholder data in an organization,

00:03:15.770 --> 00:03:18.850
you might remember the retail network of the wired brain

00:03:18.850 --> 00:03:21.990
coffee company we met in the big picture cause it's a typical

00:03:21.990 --> 00:03:23.910
face to face retail environment.

00:03:24.720 --> 00:03:28.760
And here we've got a payment terminal on the point of sale system Ah,

00:03:28.760 --> 00:03:32.750
local server within the store which contacts the bank for authorization,

00:03:33.340 --> 00:03:35.390
some sort of connection through to head office,

00:03:35.560 --> 00:03:37.890
where there's a payment processing system which talked to

00:03:37.890 --> 00:03:40.880
the bank for clearing and then a database server that keeps

00:03:40.880 --> 00:03:42.510
a record of all transactions.

00:03:43.540 --> 00:03:46.180
No, again, taking this is an example.

00:03:46.180 --> 00:03:50.410
Let's take Take this system and catalogue where Kartal the data is stored,

00:03:50.630 --> 00:03:52.150
processed or transmitted.

00:03:53.140 --> 00:03:57.050
The payment terminal processes and transmits cardholder data,

00:03:57.840 --> 00:04:01.250
as does the point of sale system and in my experience is

00:04:01.250 --> 00:04:03.280
pretty typical for the point of sale.

00:04:03.280 --> 00:04:05.550
System will also store card hold the data,

00:04:05.940 --> 00:04:08.790
even though it probably doesn't need to the store

00:04:08.790 --> 00:04:11.180
server processes and transmit Stater.

00:04:11.270 --> 00:04:13.720
And again, in my experience, working in retail environments,

00:04:13.940 --> 00:04:17.579
it probably stores as well for a just in case the acquirer is off line.

00:04:17.579 --> 00:04:18.140
Anytime.

00:04:18.140 --> 00:04:18.610
Reason.

00:04:19.940 --> 00:04:23.400
The cardholder data is transmitted through the firewall to the bank and

00:04:23.400 --> 00:04:26.370
then also through the connection to head office into the fire or head

00:04:26.370 --> 00:04:30.280
office and then onto the payment system that will process and transmit

00:04:30.280 --> 00:04:31.660
the carnal the data as well.

00:04:31.930 --> 00:04:34.750
I guess it males the story we have to look to find out.

00:04:35.190 --> 00:04:39.350
And finally, the database server definitely does store cardholder data.

00:04:40.740 --> 00:04:43.530
Now, looking at the White Break Coffee e commerce system,

00:04:43.810 --> 00:04:46.020
we ever use a shopping on her computer at home,

00:04:46.380 --> 00:04:50.410
a connection through to the Merchants Web server located within in DMC,

00:04:50.840 --> 00:04:52.450
the Payment Processing System,

00:04:52.450 --> 00:04:54.720
which talked to the bank for authorization and clearing,

00:04:54.970 --> 00:04:58.950
and finally, that database server that keeps a record of all transactions.

00:04:59.440 --> 00:05:02.510
And again, if we catalogue where cardholder data is stored,

00:05:02.510 --> 00:05:03.720
processed or transmitted,

00:05:03.950 --> 00:05:08.410
we start off with cardholder data transmitted from the user's browser

00:05:08.620 --> 00:05:11.290
through the perimeter firewall and onto the Web server,

00:05:11.290 --> 00:05:12.150
where it be processed.

00:05:12.150 --> 00:05:13.210
In transmitted onwards,

00:05:13.420 --> 00:05:16.220
you'll often find that badly configured Web service also

00:05:16.220 --> 00:05:19.790
store cardholder data in case payment processing systems are

00:05:19.790 --> 00:05:21.750
unavailable from the Web server.

00:05:21.750 --> 00:05:24.140
The card Tetris was transmitted through the D M Z

00:05:24.140 --> 00:05:28.050
firewall to the payment system, where it's processed and transmitted to the bank.

00:05:28.740 --> 00:05:32.600
And, of course, the payment system may well store a copy of the cardholder data.

00:05:32.780 --> 00:05:33.620
And then, finally,

00:05:33.720 --> 00:05:38.550
the cardholder data is stored on the database server in

00:05:38.550 --> 00:05:39.900
parallel to the business process.

00:05:39.900 --> 00:05:43.840
Analysis on organization should also use technical tools to

00:05:43.840 --> 00:05:46.210
look for cardholder data stored in IT systems.

00:05:46.740 --> 00:05:49.050
Persistently called data discovery,

00:05:49.840 --> 00:05:53.410
the organization needs to select a data discovery tool designed to

00:05:53.410 --> 00:05:56.310
find cardholder data on there are lots available.

00:05:56.510 --> 00:05:59.360
They will search through every system and discover where

00:05:59.360 --> 00:06:03.530
cardholder data is stored in databases in flat files on

00:06:03.540 --> 00:06:05.430
every single server and workstation,

00:06:05.430 --> 00:06:10.150
the organization on every website the organization has on in every log

00:06:10.150 --> 00:06:12.690
file that's being produced and saved by the organization.

00:06:12.940 --> 00:06:16.120
And this needs to be done across the entire organization,

00:06:16.310 --> 00:06:19.800
in production systems, in test systems and development systems.

00:06:19.980 --> 00:06:24.450
In staging systems, you have to look everywhere on every single system.

00:06:25.140 --> 00:06:27.200
And if you've never done this exercise before,

00:06:27.410 --> 00:06:30.950
you'll find cardholder data in places you just did not expect.

00:06:31.440 --> 00:06:34.090
Backups that people took before they did a system upgrade

00:06:34.340 --> 00:06:37.990
testing development systems that belong to no one systems

00:06:37.990 --> 00:06:40.260
that people stopped using years ago.

00:06:40.470 --> 00:06:42.350
But they have never been decommissioned.

00:06:42.900 --> 00:06:45.470
And as you come across cardholder data that you don't need,

00:06:45.690 --> 00:06:48.920
you should delete it because this will instantly reduce the amount of

00:06:48.920 --> 00:06:51.520
card old ization that could be stolen by an attacker.

00:06:51.820 --> 00:06:52.750
And that's a good thing.

00:06:53.840 --> 00:06:57.200
The other major business discovery exercise you need to do is to

00:06:57.200 --> 00:07:00.140
work out who else has your cardholder data.

00:07:00.470 --> 00:07:04.750
So here we're looking for what PC idea says calls service providers.

00:07:05.340 --> 00:07:12.390
Third parties that store process transmit cardholder data for you or third

00:07:12.390 --> 00:07:16.250
parties that you outsource business processes or facilities or technology to

00:07:16.640 --> 00:07:19.200
who could affect the security of your cardholder.

00:07:19.200 --> 00:07:24.470
Data on a really good thing to discover when you talk to third parties is what

00:07:24.480 --> 00:07:27.050
other services they can provide to help you comply with PC,

00:07:27.050 --> 00:07:27.780
Idea says.

00:07:28.060 --> 00:07:31.780
If they're in the business off doing things with cardholder data,

00:07:32.000 --> 00:07:34.770
they most developed technical solutions to outsource

00:07:34.780 --> 00:07:36.670
other payment processing activities,

00:07:36.850 --> 00:07:39.120
which could help you reduce the footprint of card all

00:07:39.120 --> 00:07:40.750
the data within your organization.

00:07:40.940 --> 00:07:44.790
So understanding what's possible from supplies is really helpful

00:07:44.980 --> 00:07:47.150
when you're going through your scoping decisions.

00:07:47.740 --> 00:07:49.530
Once you've been through this exercise for every

00:07:49.530 --> 00:07:51.950
acceptance channel and every business process,

00:07:52.340 --> 00:07:55.160
and you've used a technology solution to discover where

00:07:55.160 --> 00:07:57.380
carnal the data is in your organization,

00:07:57.940 --> 00:08:00.030
you have an accurate picture of all the systems,

00:08:00.190 --> 00:08:05.050
networks and applications that store process or transmit cardholder data.

00:08:05.540 --> 00:08:08.350
Whether that's just the primary account number were also any

00:08:08.350 --> 00:08:12.510
sensitive authentication data such as the CVC to code this

00:08:12.510 --> 00:08:16.170
using e commerce transactions as well as understand the

00:08:16.170 --> 00:08:17.930
technical flow of card all the data.

00:08:18.190 --> 00:08:21.800
You should have a good view of the underlying business processes and also

00:08:21.800 --> 00:08:26.400
know who within your organization is responsible those business processes

00:08:26.660 --> 00:08:28.810
because you'll need to work with those people.

00:08:28.830 --> 00:08:30.790
If you want to change things on.

00:08:30.790 --> 00:08:33.260
The final part of the picture is that you'll know about

00:08:33.270 --> 00:08:36.000
all the third parties who store process.

00:08:36.010 --> 00:08:39.630
Transmit Kutteles of data for you and also way you outsource business.

00:08:39.630 --> 00:08:43.659
Process off all facilities to service providers that could affect the

00:08:43.659 --> 00:08:48.550
security of the cardholder data you're responsible for in the next module

00:08:48.730 --> 00:08:50.970
will take a good hard look at this picture.

00:08:51.100 --> 00:08:52.880
The safe that describes the environment.

00:08:52.880 --> 00:08:55.150
We want to make PC idea says compliance.

00:08:55.640 --> 00:09:00.160
Or, if you want to change some business processes old or at some technology,

00:09:00.360 --> 00:09:04.890
will change technology to make the compliance job much easier on.

00:09:04.890 --> 00:09:09.150
Remember, that's about ongoing compliance as much as anything else.

00:09:10.640 --> 00:09:13.300
But before that, let's join the conversation I had with Q.

00:09:13.300 --> 00:09:13.500
S.

00:09:13.500 --> 00:09:13.580
A.

00:09:13.580 --> 00:09:16.510
Jacob Ansari, where we discuss how you can use a cure,

00:09:16.510 --> 00:09:16.730
say,

00:09:16.730 --> 00:09:20.100
to help all the way through the compliance journey and also the

00:09:20.100 --> 00:09:22.250
different roles that cure saves can fulfill
