WEBVTT

00:00:00.940 --> 00:00:03.920
This final set of standards we're going to look at will primarily

00:00:03.920 --> 00:00:07.450
be used by financial institutions, so acquirers,

00:00:07.630 --> 00:00:10.960
issuers, and the card brands or schemes themselves.

00:00:12.540 --> 00:00:17.750
The 3D Core security standard specifies the security and the associated

00:00:17.750 --> 00:00:21.230
key management for all the servers that may be involved in

00:00:21.230 --> 00:00:24.750
authenticating a customer during a 3D secure session.

00:00:25.540 --> 00:00:31.100
There are typically 3 different servers involved in a 3DS

00:00:31.100 --> 00:00:34.580
authentication process, 1 at the acquirer,

00:00:34.760 --> 00:00:38.670
which is called the 3DS server and which starts the authentication

00:00:38.670 --> 00:00:43.930
process once that's been requested by the client, a directory server

00:00:44.090 --> 00:00:47.950
that knows how to route requests to issuers, and then the server run

00:00:47.950 --> 00:00:51.340
by the issuer that actually authenticates the cardholder and this is

00:00:51.340 --> 00:00:57.680
known as the access control server, or ACS. The 3DS standard consists

00:00:57.680 --> 00:01:01.130
of 2 parts, the baseline security requirements,

00:01:01.130 --> 00:01:04.769
which is a good overall security standard and it broadly

00:01:04.769 --> 00:01:09.870
equates to the same level of security as PCI DSS, and then

00:01:10.000 --> 00:01:12.720
the 3DS security requirements,

00:01:12.860 --> 00:01:16.550
which are focused on protecting the actual 3DS data and processes.

00:01:17.340 --> 00:01:20.670
You're probably asking yourself well why is the standard split like this?

00:01:20.870 --> 00:01:24.270
And it's because the general standard for all core participants,

00:01:24.420 --> 00:01:27.270
but then not all of them see the same type of data so they

00:01:27.270 --> 00:01:29.060
don't need to comply with both parts.

00:01:30.140 --> 00:01:33.620
The 3DS security requirements are particularly interesting

00:01:33.630 --> 00:01:37.180
because unlike PCI DSS, they also include requirements

00:01:37.180 --> 00:01:41.750
focused on system availability, as well as confidentiality and integrity.

00:01:42.540 --> 00:01:47.900
There is also a second 3DS standard, which is the 3DS software development kit,

00:01:48.030 --> 00:01:50.660
or 3DS SDK standard.

00:01:51.940 --> 00:01:54.790
This is for software development kit that is sold to

00:01:54.790 --> 00:01:59.380
third‑party developers to allow them to use the 3DS protocols

00:01:59.500 --> 00:02:01.560
as part of an app running on a device.

00:02:02.640 --> 00:02:06.430
The 3DS SDK standard has sections that apply to

00:02:06.430 --> 00:02:09.780
specific SDKs made by the company,

00:02:09.930 --> 00:02:14.580
but also to the company itself that develops the SDK and those include

00:02:14.580 --> 00:02:18.700
requirements around risk management and vulnerability management, so make

00:02:18.700 --> 00:02:21.420
sure that if vulnerabilities are found in the SDK,

00:02:21.520 --> 00:02:27.450
they're properly managed. Just as a 3DS standard will be only of

00:02:27.460 --> 00:02:31.280
interest to financial institutions, the same is true of the security

00:02:31.280 --> 00:02:33.350
requirements for a token service provider.

00:02:33.840 --> 00:02:38.450
Remember that a token service provider's job is to issue a token that looks

00:02:38.450 --> 00:02:42.960
just like a pan to a merchant or to a device and then keep a record of which

00:02:42.960 --> 00:02:46.860
tokens relate to which original or funding pans.

00:02:47.540 --> 00:02:53.510
The TSP standard requires PCI DSS as a baseline because, of course, the token

00:02:53.510 --> 00:02:57.350
service provider has both real pans, as well as tokens.

00:02:58.140 --> 00:03:02.000
The TSP standard then adds more stringent,

00:03:02.010 --> 00:03:05.790
remote, logical, and physical security requirements,

00:03:05.940 --> 00:03:08.400
along with requirements for cryptographic key

00:03:08.400 --> 00:03:11.060
management using hardware security modules.

00:03:13.240 --> 00:03:17.490
The final payment card industry standard we're going to meet is the card

00:03:17.500 --> 00:03:23.260
production standard, it's a set of logical and physical standards that describe

00:03:23.260 --> 00:03:29.100
the security around how cards are manufactured, personalized, and distributed

00:03:29.350 --> 00:03:32.660
and also how PINs are sent to cardholders.

00:03:33.340 --> 00:03:35.780
This standard is split into two documents,

00:03:36.010 --> 00:03:40.750
one for physical controls and the other for logical controls, and because

00:03:40.750 --> 00:03:43.730
it's concerned with looking after physical payment cards,

00:03:43.830 --> 00:03:45.030
often in bulk,

00:03:45.180 --> 00:03:48.460
there are actually a lot more physical security requirements than you

00:03:48.460 --> 00:03:50.960
normally see in an information security standard.

00:03:51.540 --> 00:03:54.820
It's a really interesting read if you normally just do logical

00:03:54.820 --> 00:03:58.000
security and you haven't had the experience of a whole lot of

00:03:58.000 --> 00:03:59.760
physical security requirements.

00:04:00.840 --> 00:04:06.110
So looking back at our example of how a card and a PIN is made for

00:04:06.110 --> 00:04:10.410
a consumer, the PCI card production standard will apply to

00:04:10.410 --> 00:04:13.470
manufacturers, the Personalization Bureau,

00:04:13.710 --> 00:04:17.860
how the Personalization Bureau receives data from the issuer, and how

00:04:17.860 --> 00:04:22.089
the card and the PIN are sent to the cardholder.

00:04:23.240 --> 00:04:27.230
If all the entities involved in card production comply with the standard,

00:04:27.400 --> 00:04:32.320
the idea is it will stop criminals from stealing blank cards or personalized

00:04:32.320 --> 00:04:36.080
cards and PINs from the manufacturing and distribution process,

00:04:36.250 --> 00:04:39.030
and that will be really damaging for the industry because the

00:04:39.030 --> 00:04:43.710
security of the issued card and its associated PIN are really

00:04:43.710 --> 00:04:46.060
fundamental to payment card security.
