WEBVTT

00:00:00.365 --> 00:00:04.829
Well, Jacob, you can probably tell how important I think 6.4 is,

00:00:04.829 --> 00:00:08.566
because I've given it like its own whole module.

00:00:08.566 --> 00:00:08.846
Right.

00:00:08.846 --> 00:00:10.439
My experience of not being an assessor,

00:00:10.439 --> 00:00:12.972
but actually being the person in the organization

00:00:12.972 --> 00:00:17.235
watching my beautiful PCI environment degrade gracefully

00:00:17.235 --> 00:00:19.375
as people keep doing things to it,

00:00:19.375 --> 00:00:23.986
says to me that change control is the most important BAU.

00:00:23.986 --> 00:00:26.075
Do you agree?

00:00:26.075 --> 00:00:26.712
I think so.

00:00:26.712 --> 00:00:27.349
I think so.

00:00:27.349 --> 00:00:30.803
I think being able to manage your changes,

00:00:30.803 --> 00:00:32.687
being able to track them, to document them,

00:00:32.687 --> 00:00:36.541
to understand what happened, how you test them,

00:00:36.541 --> 00:00:41.333
how you make sure they don't create adverse security impacts is really,

00:00:41.333 --> 00:00:42.779
really important.

00:00:42.779 --> 00:00:45.224
So the DSS has got some particular requirements there

00:00:45.224 --> 00:00:47.059
about backing out and things like that.

00:00:47.059 --> 00:00:48.590
Right.

00:00:48.590 --> 00:00:51.171
My most important thing that I really want to talk about in

00:00:51.171 --> 00:00:54.657
terms of change control is change to scope,

00:00:54.657 --> 00:00:58.094
is that what the business is about to do,

00:00:58.094 --> 00:01:01.045
how does it change the scope of your assessment?

00:01:01.045 --> 00:01:03.671
You know, does it add stuff into the assessment?

00:01:03.671 --> 00:01:07.070
Does it, do your firewalls suddenly, does your perimeter change?

00:01:07.070 --> 00:01:08.238
Right.

00:01:08.238 --> 00:01:12.573
Do you all of a sudden start holding your business process that you didn't have?

00:01:12.573 --> 00:01:12.876
As an assessor,

00:01:12.876 --> 00:01:16.657
how many times do you go to an organization and the environment you looked at

00:01:16.657 --> 00:01:20.252
a year ago is exactly the same as the environment today?

00:01:20.252 --> 00:01:21.429
It does happen.

00:01:21.429 --> 00:01:22.519
Right.

00:01:22.519 --> 00:01:24.072
It does happen.

00:01:24.072 --> 00:01:26.143
It is uncommon though.

00:01:26.143 --> 00:01:31.610
There's usually at least something that has changed, right?

00:01:31.610 --> 00:01:31.747
Now,

00:01:31.747 --> 00:01:34.111
sometimes they're not radical and sometimes they're not so

00:01:34.111 --> 00:01:37.046
significant that they really change the scope,

00:01:37.046 --> 00:01:38.323
but that does happen.

00:01:38.323 --> 00:01:42.071
Hey, we got this new business process, we have these new systems,

00:01:42.071 --> 00:01:46.343
we bought this new entity, we got rid of some stuff,

00:01:46.343 --> 00:01:46.759
right?

00:01:46.759 --> 00:01:46.972
Yes.

00:01:46.972 --> 00:01:47.836
You know, all of that.

00:01:47.836 --> 00:01:49.023
Or some people.

00:01:49.023 --> 00:01:49.794
Right!

00:01:49.794 --> 00:01:51.686
In fact, the people who used to do the PCI stuff.

00:01:51.686 --> 00:01:52.585
Yeah, we got rid of them, right?

00:01:52.585 --> 00:01:54.535
Because they were just costing money and complaining,

00:01:54.535 --> 00:01:58.436
and now it's so much easier that we don't have to worry about scans.

00:01:58.436 --> 00:02:01.143
So architecturally, is there a way,

00:02:01.143 --> 00:02:07.711
is there a way of helping organizations be resilient to change architecturally?

00:02:07.711 --> 00:02:11.936
I think, I think from a change management standpoint,

00:02:11.936 --> 00:02:12.256
right,

00:02:12.256 --> 00:02:16.645
some of the things that you maybe want to look at in your

00:02:16.645 --> 00:02:23.223
records keeping or in your sort of process are,

00:02:23.223 --> 00:02:26.523
does it affect your scope, right?

00:02:26.523 --> 00:02:28.600
You know, and that can be like a binary sort of flag.

00:02:28.600 --> 00:02:31.818
Are you tinkering with firewall rules, right?

00:02:31.818 --> 00:02:35.511
Then maybe you need to get your information security or your compliance

00:02:35.511 --> 00:02:38.703
people involved to say does this impact our scope,

00:02:38.703 --> 00:02:39.027
right?

00:02:39.027 --> 00:02:42.454
Or does this bring in some new process or does this affect a system that,

00:02:42.454 --> 00:02:45.364
you know, stores processes, transmits, something like that.

00:02:45.364 --> 00:02:50.131
And I think knowing when to rope in your security people

00:02:50.131 --> 00:02:54.767
who can give you some analysis to say, you know,

00:02:54.767 --> 00:02:58.692
maybe this is relatively subtle, but it has these far-reaching implications,

00:02:58.692 --> 00:03:00.002
it's pretty important.

00:03:00.002 --> 00:03:02.762
As opposed to just like, we made a change and we documented it,

00:03:02.762 --> 00:03:09.105
and then you find out about it after the fact and you tear out your hair.

00:03:09.105 --> 00:03:13.667
Now I think one of the big things of DSS is that there's no

00:03:13.667 --> 00:03:16.715
independence of assessors and advisors.

00:03:16.715 --> 00:03:19.003
There's not.

00:03:19.003 --> 00:03:22.079
However, this is actually one area where it's a real strength,

00:03:22.079 --> 00:03:26.033
because would you like to be called in as a QSA before

00:03:26.033 --> 00:03:28.912
someone does change to give them a steer?

00:03:28.912 --> 00:03:29.972
Yes.

00:03:29.972 --> 00:03:31.055
Yeah?

00:03:31.055 --> 00:03:32.060
Every time.

00:03:32.060 --> 00:03:35.690
And that's I really would see is that now if you're doing changes that

00:03:35.690 --> 00:03:39.797
affect the scope or the CDE or your core business processes,

00:03:39.797 --> 00:03:42.771
when I was assessing, I always like to find out,

00:03:42.771 --> 00:03:43.868
like when they do the change,

00:03:43.868 --> 00:03:46.449
not when I came in at the end of the year to do the reassessment,

00:03:46.449 --> 00:03:48.143
and it's like, oh, you should've told me,

00:03:48.143 --> 00:03:48.773
because if you'd have done it like this,

00:03:48.773 --> 00:03:51.128
or we knew about it earlier,

00:03:51.128 --> 00:03:54.353
it would be much easier to keep you in a compliant state.

00:03:54.353 --> 00:03:58.776
Right, well, and I tell my clients, do this in your planning stage, right?

00:03:58.776 --> 00:04:03.675
Like before you deploy, before you start writing code,

00:04:03.675 --> 00:04:10.254
before you commit resources and opportunity costs to something,

00:04:10.254 --> 00:04:12.573
let's talk, right?

00:04:12.573 --> 00:04:14.633
I don't even want to charge you for that,

00:04:14.633 --> 00:04:14.848
right,

00:04:14.848 --> 00:04:17.951
because it's going to save me a ton of time and grief on the

00:04:17.951 --> 00:04:21.268
back end if I can look at something and say,

00:04:21.268 --> 00:04:24.024
if you do that, you know, here are some consequences,

00:04:24.024 --> 00:04:25.976
right, or if you do that,

00:04:25.976 --> 00:04:30.233
you're going to drive off a cliff from a compliance standpoint.

00:04:30.233 --> 00:04:30.425
Great.

00:04:30.425 --> 00:04:32.957
So let's now talk about the actual change control assessment.

00:04:32.957 --> 00:04:34.445
So you come in for your annual assessment,

00:04:34.445 --> 00:04:37.602
you're about to assess 6.4, what are you looking for?

00:04:37.602 --> 00:04:39.824
So obviously procedures, right?

00:04:39.824 --> 00:04:43.557
Although after a while, a lot of change control procedures start to run together,

00:04:43.557 --> 00:04:48.859
and then you know, show me your population of tickets,

00:04:48.859 --> 00:04:49.291
right?

00:04:49.291 --> 00:04:50.084
And you know,

00:04:50.084 --> 00:04:53.643
we talked in requirement 1 about some change management stuff for that right,

00:04:53.643 --> 00:04:57.026
and a lot of that mirrors what's here on requirement 6,

00:04:57.026 --> 00:05:00.662
which can apply to software or applications that you're developing.

00:05:00.662 --> 00:05:02.941
It can apply to infrastructure.

00:05:02.941 --> 00:05:05.469
I've even seen organizations have their user management,

00:05:05.469 --> 00:05:09.630
you know, work in the same kind of change management repository,

00:05:09.630 --> 00:05:14.813
right, because all of that, you know, can work together.

00:05:14.813 --> 00:05:16.913
And so I want to see the different kind of strata of changes,

00:05:16.913 --> 00:05:19.377
and then I want to get some samples out of each of that.

00:05:19.377 --> 00:05:20.805
I want to understand what the size of the population

00:05:20.805 --> 00:05:22.581
is and then pick some tickets.

00:05:22.581 --> 00:05:25.167
So you're actually going to go in, randomly pick some tickets,

00:05:25.167 --> 00:05:27.753
and check that the procedure's being followed?

00:05:27.753 --> 00:05:34.154
Right, and actually read, you know, some of the text in those tickets,

00:05:34.154 --> 00:05:37.271
right, where they talk about, this is how we tested it or this is what we did,

00:05:37.271 --> 00:05:40.909
or this is why it's here, and then pull at those threads and say,

00:05:40.909 --> 00:05:43.040
tell me a little bit more about this.

00:05:43.040 --> 00:05:47.793
It sounds to me this might be a common course of failure.

00:05:47.793 --> 00:05:50.241
It can be.

00:05:50.241 --> 00:05:51.057
Usually,

00:05:51.057 --> 00:05:55.104
this requirement sort of travels together with some of the

00:05:55.104 --> 00:05:58.272
software security things that I think we're going to talk about

00:05:58.272 --> 00:06:02.662
shortly where the change ticket often has a lot of like the

00:06:02.662 --> 00:06:04.262
code review or other things.

00:06:04.262 --> 00:06:06.972
And so it's not so much that the change management stuff

00:06:06.972 --> 00:06:11.815
in 6.4 is where things can fall down, or it fails catastrophically,

00:06:11.815 --> 00:06:12.617
right?

00:06:12.617 --> 00:06:16.341
But if it's also the vehicle for the 6.3,

00:06:16.341 --> 00:06:20.159
the software development stuff, that's often where I find more failures.

00:06:20.159 --> 00:06:23.561
Okay, great.

00:06:23.561 --> 00:06:25.201
What if people fail on their second, I mean,

00:06:25.201 --> 00:06:26.653
you know, you get to the second assessment,

00:06:26.653 --> 00:06:30.661
you're looking back historically rather than optimistically forward.

00:06:30.661 --> 00:06:31.170
Right.

00:06:31.170 --> 00:06:33.786
You see there's a lot of failures in change control,

00:06:33.786 --> 00:06:37.211
how does the organization get into a compliance state?

00:06:37.211 --> 00:06:40.240
I mean, are they now noncompliant for the rest of their lives?

00:06:40.240 --> 00:06:43.854
Well again, you know, there's a lot of the idea that okay,

00:06:43.854 --> 00:06:47.999
we fix things and we go forward in PCI DSS writing; you're not sort

00:06:47.999 --> 00:06:51.163
of compelled to sit out of a compliance state.

00:06:51.163 --> 00:06:53.607
Now again, if you're showing me year over year,

00:06:53.607 --> 00:06:56.733
you do a little bit of change management around the assessment time,

00:06:56.733 --> 00:06:58.317
you let it all go in the interim,

00:06:58.317 --> 00:07:00.931
you scrape it back together when I come back around,

00:07:00.931 --> 00:07:01.265
right,

00:07:01.265 --> 00:07:03.676
then I guess I really want to reevaluate my

00:07:03.676 --> 00:07:08.004
relationship with you as your assessor, right?

00:07:08.004 --> 00:07:10.205
Or at least try to understand what's happening here.

00:07:10.205 --> 00:07:12.068
Is this a lack of leadership?

00:07:12.068 --> 00:07:15.718
Is this some sort of competing priority?

00:07:15.718 --> 00:07:19.301
Is this something else that's giving rise to this,

00:07:19.301 --> 00:07:24.464
we only do change management when Jacob is staring over our shoulders?

00:07:24.464 --> 00:07:25.689
What causes that, right?

00:07:25.689 --> 00:07:29.599
And if it's just we only do compliance three days out of the year,

00:07:29.599 --> 00:07:33.090
you know, then I think we need to be sort of done working together.

00:07:33.090 --> 00:07:36.625
Okay, and that's your sanction as a QSA is like, we're done working together.

00:07:36.625 --> 00:07:42.172
Well, and that's kind of the best you can do in many cases is to realize,

00:07:42.172 --> 00:07:46.172
I don't want renew.
