WEBVTT

00:00:01.040 --> 00:00:04.440
[Autogenerated] you may be wondering if maintaining PC Idea says compliance

00:00:04.440 --> 00:00:11.070
is so hard but so important why the PC I SSC has not created requirements

00:00:11.070 --> 00:00:13.200
to maintain compliance within the standard?

00:00:13.940 --> 00:00:18.330
Well, if you turn to the back of the standard in Appendix A three,

00:00:18.440 --> 00:00:20.890
you will find those requirements in a section that's

00:00:20.890 --> 00:00:24.680
misleadingly called the designated entities Supplemental

00:00:24.680 --> 00:00:27.850
Validation or D E S V requirements.

00:00:28.480 --> 00:00:32.700
The DSV appeared as a separate document when PC Idea says

00:00:32.700 --> 00:00:36.650
Version three was released and it was incorporated into

00:00:36.650 --> 00:00:39.050
the standard in version 3.2.

00:00:40.140 --> 00:00:44.260
It would be better named Things Entities Must Do to maintain PC

00:00:44.260 --> 00:00:46.970
Idea says compliance between annual assessments.

00:00:47.740 --> 00:00:49.480
It's not part of the main standard,

00:00:49.640 --> 00:00:53.550
and entities who want to achieve PCR DSS compliance do not need

00:00:53.550 --> 00:00:56.250
to meet the requirements contained in the D.

00:00:56.250 --> 00:00:57.120
E S V.

00:00:58.240 --> 00:01:02.100
I suspect at some stage it was going to be part of PC, Idea says.

00:01:02.260 --> 00:01:04.980
But the car brands looked at that and decided all would be such a

00:01:04.980 --> 00:01:07.300
big change that they weren't going to make it.

00:01:07.490 --> 00:01:07.670
So.

00:01:07.680 --> 00:01:11.250
These requirements have been left is a separate or optional extra.

00:01:12.040 --> 00:01:15.870
So the beginning of the DSV it makes it clear that this

00:01:15.880 --> 00:01:20.250
appendix is only applicable to entities designated by payment

00:01:20.250 --> 00:01:24.540
brands or an acquirer is requiring additional validation of

00:01:24.540 --> 00:01:26.650
existing PC ideas s requirements,

00:01:27.440 --> 00:01:29.920
the type of entities that could be required to comply

00:01:29.920 --> 00:01:32.590
with the DSV there entity's processing,

00:01:32.590 --> 00:01:35.730
large volumes of card all the data or entities that have

00:01:35.730 --> 00:01:39.820
significant aggregation points of cardholder data or

00:01:39.970 --> 00:01:42.850
organizations that have previously been compromised.

00:01:42.850 --> 00:01:46.360
It had an account data compromise where criminals stole their count.

00:01:46.360 --> 00:01:47.150
All the data.

00:01:47.940 --> 00:01:49.720
If the requirements in the D.

00:01:49.720 --> 00:01:53.460
E S V apply to you, the car brands will tell you,

00:01:53.740 --> 00:01:56.310
you don't have to sort of guess that they might apply to you.

00:01:56.710 --> 00:01:57.950
And as far as I know,

00:01:58.440 --> 00:02:02.910
there are no card brands that have applied the requirements toe any

00:02:02.910 --> 00:02:08.539
organization to comply with the D S of a although I do know that if you

00:02:08.539 --> 00:02:11.980
decide to voluntarily comply with it is a service provider.

00:02:12.210 --> 00:02:15.950
One of the car brands will publicize this in their listing of service providers.

00:02:17.240 --> 00:02:21.550
Any organization can't decide that it would like to comply with the

00:02:21.550 --> 00:02:25.400
requirements in the DSV because they represent assessable.

00:02:25.400 --> 00:02:29.390
Good practice for rigorous business is usual compliance.

00:02:30.740 --> 00:02:34.640
The DSV includes requirements that are needed to properly maintain

00:02:34.910 --> 00:02:38.290
ongoing and continuous PC ideas as complies,

00:02:38.490 --> 00:02:41.090
is split into five separate requirements,

00:02:41.240 --> 00:02:45.410
which are to implement a formal compliance program to document and have

00:02:45.420 --> 00:02:48.690
ongoing validation of an organization's PC ideas.

00:02:48.690 --> 00:02:54.270
A scope to properly validate that PCR GSS is incorporated into business is usual

00:02:54.270 --> 00:02:59.370
activities to validate controls around logical access to cardholder data and

00:02:59.370 --> 00:03:02.520
finally to detect and respond to suspicious events.

00:03:03.940 --> 00:03:07.230
The DSP just looks like the rest of PC ideas s.

00:03:07.540 --> 00:03:08.700
There's a requirement,

00:03:08.930 --> 00:03:12.450
a testing procedure and guidance relating to the requirement.

00:03:13.090 --> 00:03:15.630
I'm not going to run through all the testing procedures,

00:03:15.850 --> 00:03:20.900
but let's take a quick look at all of the requirements I say a quick look.

00:03:20.910 --> 00:03:24.330
But I see the requirements are much more wordy than many of the

00:03:24.330 --> 00:03:27.050
standard PC idea says compliance requirements.

00:03:27.540 --> 00:03:29.810
I'm not going to just released requirement.

00:03:29.880 --> 00:03:34.000
I'm just going to summarize the key points on the first requirement.

00:03:34.010 --> 00:03:38.350
A 3.1 is to implement a PC idea, says compliance program.

00:03:38.790 --> 00:03:43.040
There are four sub requirements on the first of these is for management to

00:03:43.040 --> 00:03:46.930
define responsibility and accountability for both the protection of

00:03:46.930 --> 00:03:49.660
cardholder later on for the operation of the PC I.

00:03:49.660 --> 00:03:49.810
D.

00:03:49.810 --> 00:03:51.250
S s compliance program.

00:03:51.840 --> 00:03:56.870
This includes having a formal charter to maintain PC idea says compliance in

00:03:56.870 --> 00:04:01.880
the organization and then providing visibility of the state of compliance to

00:04:01.890 --> 00:04:04.450
executive management until the board of directors,

00:04:05.040 --> 00:04:07.890
the second sub requirement wants a formal compliance program.

00:04:08.000 --> 00:04:11.260
And this basically puts into place almost everything we've talked about

00:04:11.260 --> 00:04:14.480
in this module which your activities to effectively manage the

00:04:14.480 --> 00:04:20.279
requirements that level for movement level of maturity and to ensure

00:04:20.279 --> 00:04:24.050
that the schedule tests are completed and to analyse business change as

00:04:24.050 --> 00:04:25.650
it affects PC idea theft.

00:04:26.740 --> 00:04:28.190
With this program in place,

00:04:28.190 --> 00:04:31.420
the next requirement wants to make sure that people have been given

00:04:31.530 --> 00:04:35.700
specific responsibility for making sure that the program happens on

00:04:35.700 --> 00:04:38.710
the final sub requirement here is to make sure those people have

00:04:38.720 --> 00:04:41.840
been given that responsibility, has to be trained in PC,

00:04:41.840 --> 00:04:44.950
idea says, and receive training on an annual basis.

00:04:45.840 --> 00:04:49.020
The next requirement in the DSV is to make sure that an

00:04:49.020 --> 00:04:51.870
entity scope is correctly defining Documented.

00:04:52.540 --> 00:04:56.680
This is because many data breaches have come from areas of organizations

00:04:56.680 --> 00:05:01.190
that were considered out with scope but which magically acquired cardholder

00:05:01.190 --> 00:05:04.250
data after the formal PC idea says assessments.

00:05:04.940 --> 00:05:08.130
The requirement is that scope is validated on a quarterly

00:05:08.130 --> 00:05:10.650
basis and after significant change,

00:05:11.240 --> 00:05:14.790
it should be formally documented and that documentation must include an

00:05:14.790 --> 00:05:19.250
inventory of all in scope and all out of scope networks and systems.

00:05:20.240 --> 00:05:23.040
The documentation must also include a description of any

00:05:23.040 --> 00:05:27.120
segmentation of controls on a revalidation of all third parties

00:05:27.280 --> 00:05:31.460
with access to the cardholder data environments wherever there

00:05:31.460 --> 00:05:33.250
are chased the systems or networks,

00:05:33.400 --> 00:05:35.940
but has to be a more formal process to document the

00:05:35.940 --> 00:05:37.770
impact of the chase of the CD,

00:05:37.860 --> 00:05:42.840
which needs to be formally signed off by responsible personnel and then,

00:05:42.840 --> 00:05:43.670
after a change,

00:05:43.850 --> 00:05:46.460
all of the requirements that we looked at a respective network

00:05:46.460 --> 00:05:48.450
and system changes need to be put in place.

00:05:49.040 --> 00:05:49.730
Essentially,

00:05:49.970 --> 00:05:53.450
all this requirement is asking for is to make sure that any new system and

00:05:53.450 --> 00:05:56.740
networks are brought up to PC Idea says compliance immediately,

00:05:56.980 --> 00:05:59.600
and that this is documented requirement.

00:05:59.610 --> 00:06:03.500
A 3.2 point three is concerned with significant business change,

00:06:03.560 --> 00:06:06.820
such as acquisitions or mergers for key personnel changes,

00:06:07.020 --> 00:06:09.860
and this is broadly in line with what we discussed earlier about the

00:06:09.860 --> 00:06:12.750
requirements that need to be considered when this business change.

00:06:13.790 --> 00:06:17.860
The next requirement just increases the frequency of requirement 11.3

00:06:17.860 --> 00:06:21.640
point four in the any technical controls that are used to segment an

00:06:21.650 --> 00:06:24.430
outlet scope network from an in scope network.

00:06:24.560 --> 00:06:28.550
The ___________ tested every six months rather than every year.

00:06:30.040 --> 00:06:33.620
Because many data breaches have been related to cardholder

00:06:33.620 --> 00:06:36.560
data that was outside of the cardholder data environment

00:06:36.860 --> 00:06:39.370
requirement a 3.2 point five.

00:06:39.600 --> 00:06:43.380
What's a technical data discovery to or a methodology to

00:06:43.380 --> 00:06:45.680
reconfirm scope on a quarterly basis?

00:06:45.980 --> 00:06:46.210
Dr.

00:06:46.210 --> 00:06:50.060
Proactively looking for clear text cardholder data outside of

00:06:50.060 --> 00:06:53.920
the cardholder data environments practically.

00:06:53.950 --> 00:06:54.870
To implement this,

00:06:54.870 --> 00:06:57.790
you'd need to install a data discovery tool or an agent on

00:06:57.790 --> 00:06:59.950
just about every system in the organization.

00:07:01.080 --> 00:07:04.890
This sub requirement has a couple of its own sub sub requirements,

00:07:05.080 --> 00:07:08.880
the first of which is to validate the method used to detect a plain text.

00:07:08.880 --> 00:07:10.950
Cardholder Data is actually effective,

00:07:11.440 --> 00:07:15.410
so that would require some sort of assurance activity where no _____

00:07:15.410 --> 00:07:18.530
plane takes Cardinal Data's put outside the CD.

00:07:18.640 --> 00:07:20.650
When you validate tool detects it.

00:07:21.440 --> 00:07:24.200
If plaintiffs cut all the data is for real,

00:07:24.200 --> 00:07:27.200
discovered outside of the C V eight that needs to be an incident

00:07:27.200 --> 00:07:31.490
response processes initiated to both secure this data and work out how

00:07:31.490 --> 00:07:35.910
it got there in the first place as well as detecting stored cardholder

00:07:35.910 --> 00:07:41.520
data outside of the CD requirement, a 3.2 point six effective.

00:07:41.520 --> 00:07:43.950
He wants data leakage prevention technology

00:07:44.090 --> 00:07:45.700
installed at the bounty of the cuddle,

00:07:45.700 --> 00:07:48.890
the data environment to detect and prevent clear text pounds

00:07:48.890 --> 00:07:51.050
from leaving the cardholder data environment.

00:07:51.740 --> 00:07:52.120
Personally,

00:07:52.120 --> 00:07:55.300
I think this is a dumb requirement because any criminal would encrypt

00:07:55.310 --> 00:07:58.650
cardholder data before trying to exfiltrate it from the CD A.

00:07:59.640 --> 00:08:01.480
There is a subset requirement here,

00:08:01.690 --> 00:08:05.120
which is that if the data leakage prevention technology does

00:08:05.120 --> 00:08:08.410
detail plain text primary account numbers leaving the CD

00:08:08.710 --> 00:08:10.630
which of course it will never do,

00:08:10.630 --> 00:08:13.580
because a criminal would encrypt the data before exhilarating

00:08:13.580 --> 00:08:16.550
it that the entity has a response procedure.

00:08:17.980 --> 00:08:19.410
The third requirement in the D.

00:08:19.410 --> 00:08:19.550
E.

00:08:19.550 --> 00:08:23.530
S V is to make sure that PC I DSS is incorporated

00:08:23.530 --> 00:08:25.550
into business as usual activities.

00:08:26.540 --> 00:08:29.100
If I was in charge of writing these requirements,

00:08:29.210 --> 00:08:31.970
it would have been called make sure were all requirements

00:08:31.980 --> 00:08:35.990
operated maturity level for because the first requirement is that

00:08:35.990 --> 00:08:37.980
critical security controls are monitored.

00:08:38.150 --> 00:08:42.130
So if they start working fast detectives straightaway and you won't be

00:08:42.130 --> 00:08:45.860
surprised to see that there's a sub requirement here that specifies what needs

00:08:45.860 --> 00:08:48.680
to happen once you detected the failure of a control,

00:08:48.800 --> 00:08:51.160
which is to make the control start working again,

00:08:51.430 --> 00:08:53.810
work out why it failed in the first place,

00:08:54.010 --> 00:08:56.800
and put in the necessary controls and processes to

00:08:56.800 --> 00:08:58.650
prevent the control flaming again.

00:08:59.740 --> 00:09:00.450
Requirement.

00:09:00.450 --> 00:09:04.980
A 3.3 point two is a very interesting requirement because

00:09:05.090 --> 00:09:07.780
you might have noticed that PC Idea says,

00:09:07.790 --> 00:09:11.230
does not say anywhere but support systems,

00:09:11.240 --> 00:09:13.850
applications or technologies cannot be used,

00:09:14.480 --> 00:09:17.540
and even the DSV does not quite go this far.

00:09:17.810 --> 00:09:21.520
But what it does require is that every year the organization

00:09:21.520 --> 00:09:24.520
looks at the hardware software it is using and formally

00:09:24.520 --> 00:09:26.570
determines whether it's still fit for purpose.

00:09:26.780 --> 00:09:31.550
Whether it still can continue to meet PC Idea says his requirements and if no,

00:09:31.590 --> 00:09:34.150
have a plan to replace that technology.

00:09:35.940 --> 00:09:39.820
The finals of requirement of a 3.3 It's pride formal

00:09:39.830 --> 00:09:42.660
assurance by way of at least a quarterly review.

00:09:42.930 --> 00:09:46.950
The All PC idea says the B A U activities are being followed.

00:09:47.340 --> 00:09:51.320
So this is something that Internal order or an I s A for a formal

00:09:51.320 --> 00:09:53.250
assurance function would have to carry out.

00:09:54.490 --> 00:09:57.770
The fourth requirement of the DSV is concerned with logical

00:09:57.770 --> 00:09:59.850
access to the cardholder data environments,

00:10:00.340 --> 00:10:04.290
and it just wants there to be a formal six monthly review of all user

00:10:04.290 --> 00:10:06.890
accounts and their associated rights within the CD.

00:10:07.340 --> 00:10:10.800
This is a fairly common requirement of financial services organisations,

00:10:10.980 --> 00:10:15.450
but user accessed assistant and data is re certified on a regular basis.

00:10:16.290 --> 00:10:21.370
On the last sub requirement of the DSV is to make sure the organization is pro,

00:10:21.370 --> 00:10:23.400
actively looking for suspicious events,

00:10:23.630 --> 00:10:28.340
rather just responding to alerts and without saying it in a Zeman E words,

00:10:28.350 --> 00:10:31.990
it basically requires the organization to install a security

00:10:31.990 --> 00:10:35.150
information and event management or a scene platform.

00:10:36.340 --> 00:10:36.780
And so,

00:10:36.880 --> 00:10:40.800
to sum up the supplemental validation requirements with designated entities,

00:10:40.960 --> 00:10:42.960
it takes a lot of work to comply with these

00:10:42.960 --> 00:10:45.320
requirements and in most organisations,

00:10:45.430 --> 00:10:48.050
it would require a dedicated assurance function.

00:10:48.540 --> 00:10:51.370
The bottom line is that the organization would end up

00:10:51.370 --> 00:10:53.710
managing all the PC ideas s requirements,

00:10:53.860 --> 00:10:55.150
the maturity level four.

00:10:55.540 --> 00:10:57.460
They would not be controlled decay.

00:10:57.590 --> 00:10:59.840
All the schedule tests would happen on time,

00:11:00.090 --> 00:11:02.150
and change would be rigorously managed.

00:11:02.640 --> 00:11:05.600
However, compliance with the DSP will be costly,

00:11:05.880 --> 00:11:09.500
and I want to re emphasize this is Noah compulsory part of standard.

00:11:09.630 --> 00:11:12.740
You don't have to comply with it unless you're specifically

00:11:12.740 --> 00:11:15.350
asked to buy a car brand or by your acquirer.

00:11:15.940 --> 00:11:20.130
However, any organization can use some or all of the requirements,

00:11:20.220 --> 00:11:24.350
has a guy toe, have to embed PC idea says fully in their organizations,

00:11:24.490 --> 00:11:29.270
and then use the testing procedures to validate this Personally,

00:11:29.540 --> 00:11:33.710
I would not be surprised if some of these requirements do not end up being

00:11:33.710 --> 00:11:36.600
put into the main requirements in the next version of PC,

00:11:36.600 --> 00:11:37.450
Idea says.

00:11:39.440 --> 00:11:42.810
We've reached the end of this module and therefore the end of this course,

00:11:42.970 --> 00:11:46.390
and they really want to finish with six key point that will help you to be

00:11:46.390 --> 00:11:50.250
successful in achieving and maintaining PC Idea says compliance.

00:11:51.740 --> 00:11:54.880
Perhaps the most important point is it is always more important to

00:11:54.880 --> 00:11:57.740
be secure than it is to be compliance Focus.

00:11:57.740 --> 00:12:00.480
I'm not letting criminals steal the cardholder data you're

00:12:00.480 --> 00:12:04.530
responsible for before you start any compliance journey.

00:12:04.670 --> 00:12:07.840
It's really important to understand who is asking you to comply with

00:12:07.840 --> 00:12:11.230
PC idea assessed and why they are asking this,

00:12:11.340 --> 00:12:14.810
because that will let you know what the destination is.

00:12:14.810 --> 00:12:16.000
You're trying to arrive, er,

00:12:16.160 --> 00:12:19.300
how you're going to be asked to validate your compliance on

00:12:19.300 --> 00:12:21.950
who you're going to give that validation to.

00:12:22.940 --> 00:12:26.380
My personal advice is to always design your systems and scope of

00:12:26.380 --> 00:12:30.130
cardholder data environment to do his little PC idea says,

00:12:30.270 --> 00:12:31.580
as you possibly can,

00:12:32.140 --> 00:12:37.020
because maintaining PC Idea says compliance is hard and expensive on

00:12:37.020 --> 00:12:40.150
will restrict your organization's ability to be agile.

00:12:41.340 --> 00:12:43.750
Perhaps the most important lesson I've learned in 10

00:12:43.750 --> 00:12:45.730
years of working with PC Idea says,

00:12:45.970 --> 00:12:48.920
is that the transition from a compliance program to

00:12:48.920 --> 00:12:51.160
businesses usual is really hard,

00:12:51.500 --> 00:12:55.600
and the best way of succeeding is to have the destination of your PC.

00:12:55.600 --> 00:12:59.600
Idea says Compliance Program is your second formal PC ideas This

00:12:59.600 --> 00:13:05.630
assessment not your first formal PC ideas as assessments and finally

00:13:05.930 --> 00:13:08.580
recognize that alongside control decay,

00:13:08.870 --> 00:13:12.300
andan organizations complete inability to carry out

00:13:12.300 --> 00:13:15.050
the scheduled tasks required by PC, idea says.

00:13:15.540 --> 00:13:18.930
But uncontrolled change will destroy your heart.

00:13:18.930 --> 00:13:21.600
Obtained PC idea says Compliance.

00:13:22.940 --> 00:13:26.620
If you have any questions about achieving and maintaining PC Idea says

00:13:26.620 --> 00:13:29.850
compliance than the discussion Tub is waiting for you.

00:13:30.740 --> 00:13:33.160
If you're wondering which course to take next,

00:13:33.310 --> 00:13:36.420
then please let me recommend the discussion I had with

00:13:36.420 --> 00:13:40.580
experienced PC I forensic investigator Aaron Willis,

00:13:40.760 --> 00:13:45.030
where you learn about how criminal still Kartal the data and

00:13:45.030 --> 00:13:48.110
discover what actually happens in the course of a PC.

00:13:48.110 --> 00:13:49.650
I forensic investigation.

00:13:50.240 --> 00:13:54.100
And I hope that by achieving and maintaining PC Idea says

00:13:54.100 --> 00:13:58.870
compliance that this next course is the closest you will ever

00:13:58.870 --> 00:14:01.750
get to a PC I forensic investigator.
