WEBVTT

00:00:00.000 --> 00:00:08.151
Requirement 6.4 is in my opinion one of the most important in PCI DSS.

00:00:08.151 --> 00:00:11.674
In fact, it's so important that it has its module in this course,

00:00:11.674 --> 00:00:14.098
and that's because it deals with change,

00:00:14.098 --> 00:00:17.536
and more specifically change control.

00:00:17.536 --> 00:00:22.079
If you're concerned we finished the last module with 6.2, don't worry.

00:00:22.080 --> 00:00:25.555
Requirement 6.3 is in the next module along with the other

00:00:25.555 --> 00:00:28.307
requirements relating to software development.

00:00:28.307 --> 00:00:30.609
Requirement 6.4 is very simple.

00:00:30.610 --> 00:00:34.276
It demands that an organization must have documented and in use and

00:00:34.276 --> 00:00:39.089
compliant with PCI DSS change control procedures,

00:00:39.089 --> 00:00:43.151
and that such change control procedures follow the requirements laid down in the

00:00:43.152 --> 00:00:47.610
very detailed and quite annoying at times sub requirements.

00:00:47.611 --> 00:00:50.609
I love the PCI DSS guidance series; it says,

00:00:50.609 --> 00:00:52.588
look, without effective change management,

00:00:52.588 --> 00:00:56.239
bad things will happen to the security of the environment,

00:00:56.240 --> 00:00:59.211
which is like that's no surprise, is it?

00:00:59.212 --> 00:01:00.773
What it doesn't say is this,

00:01:00.773 --> 00:01:03.660
that change is also the one thing that is guaranteed to

00:01:03.660 --> 00:01:07.388
make compliance environments noncompliant.

00:01:07.389 --> 00:01:09.052
And I've seen this on so many occasions,

00:01:09.052 --> 00:01:12.014
that a company will put lots of resources into a

00:01:12.014 --> 00:01:16.788
project to get PCI DSS compliance, but then once the project team leaves,

00:01:16.788 --> 00:01:20.454
the cardholder data environment is subject to business as usual change,

00:01:20.455 --> 00:01:22.990
which doesn't follow the requirements of 6.4,

00:01:22.990 --> 00:01:28.773
and so the environment slowly becomes both insecure and noncompliant.

00:01:28.773 --> 00:01:30.506
To test requirement 6.4,

00:01:30.506 --> 00:01:34.403
the QSA is just going to look at the documented change control procedures

00:01:34.403 --> 00:01:39.254
and make sure that these meet the detailed requirements of PCI DSS and have

00:01:39.254 --> 00:01:43.239
all the eight sub requirements included in them.

00:01:43.239 --> 00:01:47.656
The first few sub requirements are actually not so much concerned with how

00:01:47.656 --> 00:01:49.534
an organization manages its change control procedures,

00:01:49.534 --> 00:01:52.818
but in the environment the organization establishes to make

00:01:52.818 --> 00:01:55.311
sure that change is properly managed.

00:01:55.311 --> 00:01:59.771
And so the first requirement is that the test or development environments are

00:01:59.771 --> 00:02:04.245
kept separate from the live or production environments.

00:02:04.246 --> 00:02:05.518
The guidance describes the reason for this,

00:02:05.519 --> 00:02:08.069
and let's be honest; it's really sensible security practice,

00:02:08.069 --> 00:02:11.910
because the test or development environment isn't going to be maintained

00:02:11.910 --> 00:02:16.411
and managed as securely as a production environment.

00:02:16.411 --> 00:02:19.510
And so the key point of this requirement is that the separation is enforced

00:02:19.510 --> 00:02:24.291
at the network level and also by access control lists.

00:02:24.292 --> 00:02:24.921
To test this,

00:02:24.921 --> 00:02:29.364
the QSA is going to look in two areas; firstly at network configurations to

00:02:29.364 --> 00:02:32.418
make sure there's separation between the two environments,

00:02:32.418 --> 00:02:33.399
and secondly,

00:02:33.399 --> 00:02:39.247
that any access control records that allow access to each environment.

00:02:39.248 --> 00:02:40.698
As well as network load separation,

00:02:40.698 --> 00:02:44.978
PCI DSS also wants logical user separation between each environment,

00:02:44.978 --> 00:02:49.513
which I know can be hard to achieve in smaller organizations.

00:02:49.513 --> 00:02:53.525
The requirement of separation of duties between production and development

00:02:53.525 --> 00:02:56.867
means that an account with access to the development environment shouldn't

00:02:56.867 --> 00:02:59.431
have access to the production environment.

00:02:59.432 --> 00:03:01.401
Yeah, I know, this is tough.

00:03:01.401 --> 00:03:03.902
So look, ideally this would be absolute,

00:03:03.902 --> 00:03:05.036
but it's, you know,

00:03:05.036 --> 00:03:09.075
we recognize or PCI DSS recognizes that developers might sometimes need

00:03:09.075 --> 00:03:11.130
access to production to help with troubleshooting,

00:03:11.130 --> 00:03:14.579
and so it's okay for the same physical person to

00:03:14.579 --> 00:03:20.671
have access to both environments, but they do need to have two separate accounts,

00:03:20.671 --> 00:03:24.903
one for development and the other one with different rights to production,

00:03:24.903 --> 00:03:26.146
and of course,

00:03:26.146 --> 00:03:30.071
in a modern DevOps type of environment where you've got secure

00:03:30.071 --> 00:03:31.870
continuous build and deployment pipeline,

00:03:31.870 --> 00:03:34.510
you'd never have anyone accessing production anyway,

00:03:34.510 --> 00:03:35.181
would you?

00:03:35.181 --> 00:03:38.434
As you'd expect, to assess this requirement is in place,

00:03:38.434 --> 00:03:41.989
the QSA is going to interview people and observe your change control

00:03:41.989 --> 00:03:45.332
process to see that there's adequate separation of duties.

00:03:45.332 --> 00:03:48.846
Requirement 6.4 .3 is a really simple requirement,

00:03:48.846 --> 00:03:53.392
that live card data should never be used in a

00:03:53.392 --> 00:03:56.753
testing or development environment, and that's obviously pretty sensible,

00:03:56.753 --> 00:03:59.673
because the protection around development and test

00:03:59.673 --> 00:04:02.624
environments isn't going to be good enough to prevent both

00:04:02.624 --> 00:04:04.689
systems from being compromised by criminals.

00:04:04.689 --> 00:04:06.315
And if you're asking yourself, well,

00:04:06.315 --> 00:04:08.962
how on earth are you expected to test code and

00:04:08.962 --> 00:04:12.663
systems without using real card data, the answer is actually pretty simple.

00:04:12.663 --> 00:04:16.164
You just need to ask your processor, acquirer,

00:04:16.164 --> 00:04:20.446
or merchant bank, the organization that accepts your payment card transactions,

00:04:20.446 --> 00:04:23.485
to provide you with a set of test card numbers,

00:04:23.485 --> 00:04:27.378
and these test card numbers will have certain rules associated with them

00:04:27.378 --> 00:04:29.713
so that every time you use a particular test number,

00:04:29.713 --> 00:04:32.576
you'll know in advance what response you're supposed to get

00:04:32.576 --> 00:04:35.559
from the bank by using this test card number.

00:04:35.560 --> 00:04:38.133
To test this PCI DSS requirement,

00:04:38.134 --> 00:04:41.902
the QSA will look at the data in your development and testing environments,

00:04:41.902 --> 00:04:43.729
ask you about test card data,

00:04:43.729 --> 00:04:47.218
and check any relevant documentation such as the policy that says,

00:04:47.218 --> 00:04:50.591
you will never use live data in a test environment.

00:04:50.591 --> 00:04:53.437
One other very quick point about this requirement.

00:04:53.437 --> 00:04:57.517
You've probably heard stories and seen movies where a scientist

00:04:57.517 --> 00:05:00.350
tries out some new compound on themselves,

00:05:00.350 --> 00:05:01.671
and you know,

00:05:01.672 --> 00:05:06.152
they get better and they solve a world problem and they become a superhero.

00:05:06.153 --> 00:05:09.248
Well, although it's sometimes pretty complicated,

00:05:09.248 --> 00:05:13.218
writing payment processing code isn't that type of science,

00:05:13.219 --> 00:05:13.991
and so please,

00:05:13.991 --> 00:05:16.472
don't be tempted to use your own personal credit and

00:05:16.472 --> 00:05:18.305
debit card numbers to test your code.

00:05:18.305 --> 00:05:21.243
I've known loads of occasions where people have done this and

00:05:21.243 --> 00:05:23.038
not only has their card been compromised,

00:05:23.038 --> 00:05:26.873
but the card often gets blocked because they try so many transactions with so

00:05:26.873 --> 00:05:30.672
many wrong parameters they may can't get home at night.

00:05:30.672 --> 00:05:34.174
Continue the theme of separating separation between development or

00:05:34.174 --> 00:05:35.954
test environments and production environments,

00:05:35.954 --> 00:05:38.884
the next requirement aims to make sure that when a change is

00:05:38.884 --> 00:05:40.930
promoted from development or test to production,

00:05:40.930 --> 00:05:44.179
there's nothing that can compromise the integrity of the production

00:05:44.179 --> 00:05:47.528
environment that's promoted at the same time.

00:05:47.529 --> 00:05:51.557
And the two things that PCI DSS is really concerned about are migrating

00:05:51.557 --> 00:05:56.434
accounts and data from data and test environments into production.

00:05:56.434 --> 00:05:57.421
In my experience,

00:05:57.421 --> 00:06:01.452
accounts using the test environment and particularly hard-coded test

00:06:01.452 --> 00:06:04.296
credentials are the most common things you need to look out for here,

00:06:04.296 --> 00:06:08.074
especially if you've got some API access involved.

00:06:08.074 --> 00:06:10.171
The QSA is going to look at your test and release processes and

00:06:10.171 --> 00:06:13.877
they'll speak to the people responsible for releasing systems and

00:06:13.877 --> 00:06:16.071
releasing applications into production.

00:06:16.071 --> 00:06:19.034
They'll also look at some recent changes and make sure that

00:06:19.034 --> 00:06:22.078
these procedures were followed and actually that there was

00:06:22.078 --> 00:06:24.489
documentation to prove they were followed.

00:06:24.489 --> 00:06:29.778
Now requirement 6.4 .5 is one of the longest in PCI DSS,

00:06:29.778 --> 00:06:33.799
because it is split down into even smaller,

00:06:33.799 --> 00:06:35.675
more prescriptive requirements.

00:06:35.675 --> 00:06:40.307
It says that your change control procedures must contain four specific things

00:06:40.307 --> 00:06:43.388
and these specific things are concerned with documentation,

00:06:43.388 --> 00:06:48.894
management approval, security testing, and a way of reversing the change.

00:06:48.894 --> 00:06:52.850
The first prescriptive change control requirement is that the

00:06:52.850 --> 00:06:54.531
impact of the change is being documented,

00:06:54.532 --> 00:06:59.199
and PCI is particularly concerned about any changes to payment flows,

00:06:59.200 --> 00:07:01.736
changes to the cardholder data environment,

00:07:01.736 --> 00:07:04.588
and anything that impacts security.

00:07:04.588 --> 00:07:09.237
The next is that the changes documented requires approval by whatever

00:07:09.237 --> 00:07:13.360
level of management your change control process requires.

00:07:13.360 --> 00:07:14.845
So it's not saying, you know,

00:07:14.845 --> 00:07:17.480
this is how change control has to be working in your organization,

00:07:17.480 --> 00:07:21.209
but it does say you have to have a documented approval process and your

00:07:21.209 --> 00:07:24.770
changes have to go through this approval process.

00:07:24.770 --> 00:07:25.092
Thirdly,

00:07:25.092 --> 00:07:29.381
that the change control process requires functionality testing to validate

00:07:29.382 --> 00:07:33.428
that the security of the system isn't affected by the change,

00:07:33.428 --> 00:07:34.868
and for me,

00:07:34.868 --> 00:07:38.190
this frequently translates into a manual pen test of whatever change is being

00:07:38.190 --> 00:07:40.707
proposed in sort of a pre-production type of environment,

00:07:40.707 --> 00:07:45.586
but then also some sort of test when things are being promoted.

00:07:45.586 --> 00:07:47.413
And finally, a really interesting requirement,

00:07:47.413 --> 00:07:50.724
that change control procedures must require that any change

00:07:50.724 --> 00:07:54.519
also has a back-out or a reversal process.

00:07:54.519 --> 00:07:58.256
Now, look, in mature organizations,

00:07:58.257 --> 00:08:02.565
these back-out and reversal processes will exist in the

00:08:02.565 --> 00:08:06.219
change control process so they'll require that the

00:08:06.219 --> 00:08:10.007
back-out procedure is thought about, it's documented,

00:08:10.008 --> 00:08:11.834
so that if there's a change that breaks functionality,

00:08:11.834 --> 00:08:13.823
it can be reversed.

00:08:13.823 --> 00:08:14.295
However,

00:08:14.295 --> 00:08:19.113
PCI DSS requires backup procedures to be in place in case the

00:08:19.113 --> 00:08:20.701
change breaks the security of the system,

00:08:20.701 --> 00:08:22.752
not the functionality of the system.

00:08:22.753 --> 00:08:24.278
And this is a great discipline to have,

00:08:24.279 --> 00:08:27.833
because I've often seen changes that were made where the functionality worked,

00:08:27.833 --> 00:08:30.282
but at the expense of the security of the system,

00:08:30.282 --> 00:08:31.950
but the change wasn't backed out,

00:08:31.950 --> 00:08:34.771
because the system was working and there wasn't a back-out plan.

00:08:34.770 --> 00:08:35.290
So look,

00:08:35.290 --> 00:08:38.318
having a back-out plan makes it much easier to

00:08:38.318 --> 00:08:41.255
maintain the security of the system.

00:08:41.256 --> 00:08:43.433
To test these four sub requirements,

00:08:43.433 --> 00:08:45.416
the QSA is going to firstly check your change control

00:08:45.416 --> 00:08:48.750
procedures to make sure that the requirements of PCI DSS

00:08:48.750 --> 00:08:50.818
are written into your procedures.

00:08:50.819 --> 00:08:53.666
They're then going to pick a sample of changes that occurred

00:08:53.666 --> 00:08:55.868
in the previous year and for each one,

00:08:55.868 --> 00:08:59.144
the QSA is going to look at the specific change control record for

00:08:59.145 --> 00:09:01.888
evidence that the relevant documentation was produced,

00:09:01.888 --> 00:09:04.312
that the impact of the change was documented,

00:09:04.312 --> 00:09:07.328
the approval's there, and that the testing is there,

00:09:07.329 --> 00:09:09.547
and the back-out plan is also there.

00:09:09.547 --> 00:09:12.633
The QSA is going to interview people to make sure that

00:09:12.633 --> 00:09:13.698
that process is generally followed,

00:09:13.698 --> 00:09:16.166
but they might also ask about specific changes.

00:09:16.166 --> 00:09:19.324
They might pick a specific change from the previous year and ask people,

00:09:19.324 --> 00:09:23.227
how did you test that, how did that back-out plan work?

00:09:23.228 --> 00:09:26.853
If this is an organization's first initial PCI DSS assessment,

00:09:26.853 --> 00:09:30.239
there's obviously no change records for the QSA to look at,

00:09:30.240 --> 00:09:32.445
so what they're going to do then is just look at your

00:09:32.445 --> 00:09:34.822
documented change control policies and procedures.

00:09:34.823 --> 00:09:37.877
The last requirement in 6.4 is a big one,

00:09:37.877 --> 00:09:41.421
and I know from my experience looking at data breaches,

00:09:41.421 --> 00:09:44.341
this is one of the most important security

00:09:44.341 --> 00:09:47.371
requirements in the whole of the standard,

00:09:47.371 --> 00:09:52.439
and the requirement is to reassess all relevant PCI DSS

00:09:52.439 --> 00:09:55.154
requirements after a significant change,

00:09:55.155 --> 00:09:57.230
because as I said at the beginning of the module,

00:09:57.230 --> 00:10:01.636
change is what makes secure payment systems that

00:10:01.636 --> 00:10:04.362
were previously secure insecure.

00:10:04.362 --> 00:10:09.011
It's what makes previously compliant systems noncompliant.

00:10:09.011 --> 00:10:10.505
So after a significant change,

00:10:10.505 --> 00:10:13.694
it's vital to verify that all of the relevant PCI DSS

00:10:13.694 --> 00:10:15.815
requirements are still in place.

00:10:15.815 --> 00:10:16.584
Of course,

00:10:16.584 --> 00:10:19.860
this requirement means that you need to decide on what

00:10:19.860 --> 00:10:21.467
constitutes a significant change.

00:10:21.467 --> 00:10:27.538
There is some help in the guidance bit of PCI DSS, but my general rule is this.

00:10:27.538 --> 00:10:31.202
Significant change is anything added to the cardholder data environment,

00:10:31.203 --> 00:10:33.341
whether that's new hardware, new software,

00:10:33.341 --> 00:10:35.395
or new networking equipment,

00:10:35.396 --> 00:10:37.704
any replacement or upgrades of hardware and software

00:10:37.704 --> 00:10:39.086
in the cardholder data environment,

00:10:39.086 --> 00:10:43.244
any changes in the flow or storage of payment card data,

00:10:43.245 --> 00:10:46.517
any changes to the boundary of the cardholder data environment,

00:10:46.517 --> 00:10:49.555
and therefore the scope of the PCI DSS assessment,

00:10:49.555 --> 00:10:54.383
any changes to the underlying supporting infrastructure such as,

00:10:54.383 --> 00:10:57.415
I mean like directory services or time services or

00:10:57.415 --> 00:10:59.186
your logging and monitoring system,

00:10:59.186 --> 00:11:02.350
and then finally any changes to third-party suppliers who

00:11:02.350 --> 00:11:06.147
support the cardholder data environment.

00:11:06.147 --> 00:11:08.191
And the minimum requirements that should be checked

00:11:08.191 --> 00:11:10.866
after a significant change are: firstly,

00:11:10.866 --> 00:11:13.349
the key documentation, the network diagram,

00:11:13.349 --> 00:11:16.713
cardholder data flows, records of what systems are in scope,

00:11:16.714 --> 00:11:19.651
these are essentials to check because they show that you've understood

00:11:19.651 --> 00:11:22.842
and actually have recorded the scale of the change.

00:11:22.842 --> 00:11:28.920
Secondly, that anything added or upgraded has that standard secure build to it,

00:11:28.921 --> 00:11:31.970
it's been hardened, default accounts and passwords have been removed,

00:11:31.970 --> 00:11:34.622
anti-malware software is installed and working.

00:11:34.622 --> 00:11:34.955
Next,

00:11:34.955 --> 00:11:39.012
any changes to the storage of cardholder data and the

00:11:39.012 --> 00:11:41.979
pre-authorization storage of sensitive authentication data.

00:11:41.980 --> 00:11:45.406
Next, look at the loggings.

00:11:45.406 --> 00:11:48.945
Is every component in the cardholder data environment still generating logs,

00:11:48.945 --> 00:11:51.681
and are these logs being monitored?

00:11:51.682 --> 00:11:56.115
Next, whether the vulnerability scan covers all systems and devices.

00:11:56.115 --> 00:11:59.833
And finally, is a penetration test needed?

00:11:59.833 --> 00:12:01.465
Now this isn't an exhaustive check list.

00:12:01.465 --> 00:12:04.391
It's my list of the bare minimum things I look for,

00:12:04.391 --> 00:12:07.179
and your environment changes might be different so it's always

00:12:07.179 --> 00:12:10.625
worth taking a really quick run through all 300 requirements

00:12:10.625 --> 00:12:12.326
in the standard to ask yourself,

00:12:12.326 --> 00:12:15.481
should I revalidate this requirement or is it okay?

00:12:15.481 --> 00:12:16.859
Should I revalidate this requirement?

00:12:16.859 --> 00:12:18.000
Just keep going through.

00:12:18.000 --> 00:12:21.089
I mean, it's a bit of a pain to do, I'll be really honest,

00:12:21.089 --> 00:12:25.736
but as I say, this is where I've seen most breaches of cardholder data.

00:12:25.736 --> 00:12:28.244
The QSA is going to check for the evidence that you've done this,

00:12:28.244 --> 00:12:30.937
so having actually have a checklist of things you've checked for and go,

00:12:30.937 --> 00:12:33.455
yes, I'm going to do this, no, I'm not going to do this,

00:12:33.455 --> 00:12:35.281
is a great idea to show them.

00:12:35.281 --> 00:12:38.120
The QSA themselves are going to make specific checks of your change

00:12:38.120 --> 00:12:41.172
control records and they'll try to match this up with a documentation

00:12:41.172 --> 00:12:43.200
of records that should've been updated.

00:12:43.201 --> 00:12:45.935
So they're really going to pay particular attention to the network diagram,

00:12:45.935 --> 00:12:48.488
inventory, and cardholder data flows.

00:12:48.488 --> 00:12:53.819
A good QSA will use their knowledge of the significant changes to your

00:12:53.819 --> 00:12:56.940
environment that occurred in the past 12 months when they pick systems

00:12:56.940 --> 00:12:59.174
to sample test for the other requirements.

00:12:59.174 --> 00:13:02.261
So they'll look at what's been added to the CDE in the past 12 months,

00:13:02.261 --> 00:13:04.875
and you can guarantee those are the ones that they're going to

00:13:04.875 --> 00:13:07.582
look at to see if they can play with PCI DSS.

00:13:07.583 --> 00:13:10.941
Now it's time to return to that conversation I had with Jacob

00:13:10.941 --> 00:13:15.065
about how to manage change to ensure that all PCI DSS compliance

00:13:15.065 --> 00:13:18.600
and cardholder data security is embedded and becomes business as

00:13:18.600 --> 00:13:21.220
usual in an organization.
