WEBVTT

00:00:00.000 --> 00:00:02.360
[Autogenerated] now Jacob are organizations comply?

00:00:02.400 --> 00:00:04.260
Were into business is usual, right?

00:00:04.460 --> 00:00:07.130
What's going to go wrong and knocked me out of compliance.

00:00:07.590 --> 00:00:12.780
Really sustainability for for so many controls,

00:00:12.920 --> 00:00:17.490
there's a need to provide effort right to keep working at what

00:00:17.490 --> 00:00:20.850
the control entails to continue to review logs,

00:00:20.850 --> 00:00:22.650
to continue to fix vulnerabilities,

00:00:23.160 --> 00:00:27.240
tohave sort of functional process that informs essentially

00:00:27.240 --> 00:00:30.110
how the organization needs to operate right or at least

00:00:30.120 --> 00:00:33.620
put securing the environment, securing the payment data,

00:00:33.900 --> 00:00:34.300
you know,

00:00:34.590 --> 00:00:38.040
in a seat at the table about sort of the management of the organization.

00:00:38.680 --> 00:00:42.800
And so if you're doing PC ideas s compliance to sort

00:00:42.800 --> 00:00:45.550
of tick a box or to make it an I t.

00:00:45.550 --> 00:00:51.670
Problem that that the leadership doesn't want to engage with or to

00:00:51.870 --> 00:00:54.620
make the fewest number of change is possible,

00:00:54.870 --> 00:00:59.420
then Year two is probably going to be sort of rough as you find that

00:00:59.420 --> 00:01:04.599
things sort of broke under the strain of kind of the indifference of the

00:01:04.599 --> 00:01:09.300
organization or just that the needs of work at it,

00:01:09.420 --> 00:01:09.950
Yeah,

00:01:09.940 --> 00:01:13.950
and not really committing those resource is One thing I often see

00:01:14.050 --> 00:01:18.330
is a great project to become PC idea says compliant There's a whole

00:01:18.330 --> 00:01:20.290
project team that some contractors,

00:01:20.510 --> 00:01:23.570
everyone's running for this sort of compliance get compliance.

00:01:23.710 --> 00:01:25.880
All those people leave rate on.

00:01:25.880 --> 00:01:27.980
Then there's no one holding the PC.

00:01:27.980 --> 00:01:29.990
Idea says Compliance, baby, Right,

00:01:30.380 --> 00:01:33.450
How do you is a curious I How do you How do you help

00:01:33.450 --> 00:01:35.440
your organization not do that?

00:01:35.460 --> 00:01:35.820
Well,

00:01:35.830 --> 00:01:39.670
part of it is is getting you preparing for the end of the

00:01:39.670 --> 00:01:46.060
project and then translating that from Project into it into

00:01:46.060 --> 00:01:48.310
its amore sort of routine operations.

00:01:49.240 --> 00:01:54.450
And again, sustainability is a big sort of notion behind making that work.

00:01:54.440 --> 00:01:58.950
How do you make sure that if if those contractors or those other people that

00:01:58.950 --> 00:02:03.570
came in specifically for this project are rolling off are leaving are going

00:02:03.570 --> 00:02:05.350
back to whatever it was they were doing beforehand?

00:02:05.940 --> 00:02:08.340
Who's picking up those responsibilities?

00:02:08.539 --> 00:02:11.180
How do we make sure this stuff continues to happen, right?

00:02:11.220 --> 00:02:13.830
If we had to sort of blood in the database,

00:02:13.830 --> 00:02:17.710
add men's into letting us patch the database so it wasn't

00:02:17.710 --> 00:02:19.640
running someone supported version right?

00:02:19.650 --> 00:02:23.240
Who's going to bludgeon the DVDs again in a month when there is a heap

00:02:23.240 --> 00:02:26.550
of new vulnerabilities to be fixed on the systems uh,

00:02:26.960 --> 00:02:28.900
Or maybe better yet,

00:02:28.900 --> 00:02:32.260
how do you persuade them that this is actually a good idea and,

00:02:32.270 --> 00:02:34.100
you know, obviate the need for bludgeoning?

00:02:34.410 --> 00:02:37.920
Um, you know, I think I think you see a lot of cases where there's a lot of,

00:02:37.920 --> 00:02:41.730
like, personal heroics amongst a few kind of key people.

00:02:41.890 --> 00:02:45.540
Teoh, get over the finish line of you have compliance, right?

00:02:46.450 --> 00:02:47.890
But you know,

00:02:47.900 --> 00:02:52.010
you can't You can't build a sustainable business model on the personal

00:02:52.010 --> 00:02:54.350
heroics of somebody that you know very desperately,

00:02:54.350 --> 00:02:56.490
probably wants to go lie down for a few hours thereafter.

00:02:57.780 --> 00:03:03.500
So that, to me, is almost like a failure in a sense that it took,

00:03:04.240 --> 00:03:06.360
you know, somebody's, you know,

00:03:06.370 --> 00:03:10.160
assiduous efforts above and beyond what what you know was

00:03:10.160 --> 00:03:14.370
reasonable for them to compensate for, in the end,

00:03:14.370 --> 00:03:16.020
the lack of leadership in the organization.

00:03:16.560 --> 00:03:21.440
So one thing I always try and do if the client will allow it to happen,

00:03:21.850 --> 00:03:27.460
is Teoh contract with a Q s, a thumb to do what I call interim many assessments.

00:03:27.770 --> 00:03:30.260
So, in your first year of compliance,

00:03:30.260 --> 00:03:32.980
I want the Q S A to come back after a couple of months,

00:03:32.980 --> 00:03:35.020
four months six months, eight months on.

00:03:35.020 --> 00:03:36.750
Just come and sample some controls.

00:03:36.750 --> 00:03:39.360
The controls that I know from reading.

00:03:39.480 --> 00:03:41.960
Well, from experience of reading the Verizon reports,

00:03:42.150 --> 00:03:43.810
the ones that people get wrong.

00:03:44.060 --> 00:03:44.950
Do you do that?

00:03:44.950 --> 00:03:45.660
Secure Siphon.

00:03:45.660 --> 00:03:46.800
Would you be open for doing that?

00:03:46.800 --> 00:03:51.150
Sometimes I've been I've been sort of trying to consider how to make

00:03:51.150 --> 00:03:53.710
this of a sustainable service idea for a long time.

00:03:53.710 --> 00:03:54.010
Right?

00:03:54.180 --> 00:03:58.160
How do we How do we do some intermediate check ins, right?

00:03:58.170 --> 00:04:02.850
For some sample of requirements in such a way that if maybe the

00:04:02.850 --> 00:04:06.230
client passes all those little health checks along the way that

00:04:06.440 --> 00:04:10.950
there's some benefit to them, you know, in the in the validation.

00:04:11.000 --> 00:04:11.290
Right.

00:04:11.480 --> 00:04:16.240
I feel like there would be conceivably some benefit for us if I can say,

00:04:16.240 --> 00:04:18.329
Yeah, this is working as advertised.

00:04:18.600 --> 00:04:22.650
You know, the next year is gonna run more smoothly, right?

00:04:23.410 --> 00:04:23.620
You know,

00:04:23.620 --> 00:04:26.310
then maybe I can budget a little bit less for for

00:04:26.310 --> 00:04:27.530
the time and effort spent on that.

00:04:27.540 --> 00:04:27.770
Yeah.

00:04:27.770 --> 00:04:27.950
I mean,

00:04:27.950 --> 00:04:32.000
what I found is a city in organizations where they don't have a

00:04:32.070 --> 00:04:35.380
assessment and compliance history where they're not used to someone

00:04:35.380 --> 00:04:40.510
coming in and checking our work that it really helps focus the

00:04:40.510 --> 00:04:42.630
organization the first time when they go,

00:04:42.630 --> 00:04:43.660
Well, I just looked up.

00:04:43.670 --> 00:04:47.330
Six change control tickets on their all incomplete, right?

00:04:47.360 --> 00:04:50.940
But I've caught that two months into the DSS lifecycle.

00:04:51.110 --> 00:04:53.810
I'm not most nine or 10 for the first reassessment.

00:04:54.040 --> 00:04:58.190
I found that that there actually is something that the that the

00:04:58.200 --> 00:05:01.890
helps do the embedding into be a you because the head of the

00:05:01.890 --> 00:05:05.620
service delivery team has Suddenly you got a problem that they

00:05:05.620 --> 00:05:06.530
didn't actually understand.

00:05:06.530 --> 00:05:07.810
They have that problem, right?

00:05:08.230 --> 00:05:12.560
I find that that in some cases, in a lot of cases with our clients,

00:05:12.750 --> 00:05:15.580
that kind of the opposite thing happens because many of our clients

00:05:15.590 --> 00:05:19.960
also get other kinds of audits to get an essay 18 sock to where they

00:05:19.960 --> 00:05:21.600
get a nice to 27 Neville Owen auto.

00:05:21.600 --> 00:05:25.050
And so they feel like they're constantly being audited.

00:05:25.220 --> 00:05:25.520
Right?

00:05:25.530 --> 00:05:29.370
And they get this sort of fatigue from that where you know Hey,

00:05:29.370 --> 00:05:31.700
I already provided a bunch of change tickets to the ice.

00:05:31.700 --> 00:05:33.140
A team that was here a few months ago.

00:05:33.150 --> 00:05:34.860
Why am I doing this again?

00:05:34.870 --> 00:05:36.820
Well, yeah, different requirements, right?

00:05:36.960 --> 00:05:38.320
Or you know why?

00:05:38.320 --> 00:05:41.600
Why do I have to show you this patch management history?

00:05:41.760 --> 00:05:42.390
When?

00:05:42.400 --> 00:05:42.680
When?

00:05:42.690 --> 00:05:44.840
You know, somebody already asked me about that earlier this year.

00:05:44.840 --> 00:05:47.300
Well, you know, has been a long time, right?

00:05:47.300 --> 00:05:48.190
I can't rely on stuff.

00:05:48.190 --> 00:05:49.140
That was six months ago.

00:05:49.490 --> 00:05:52.350
Uh, and so that's tough, right?

00:05:52.570 --> 00:05:54.320
Uh, where?

00:05:54.320 --> 00:05:56.990
Yeah, You want to embed the sort of business as usual?

00:05:57.100 --> 00:06:00.590
You know, maybe by doing more frequent examinations, right?

00:06:00.630 --> 00:06:04.400
But it's absolutely possible toe sort of do enough

00:06:04.400 --> 00:06:06.590
examinations that you sort of burn everybody out.

00:06:06.790 --> 00:06:08.900
And they feel like they're always, you know,

00:06:08.970 --> 00:06:10.880
trying to work with somebody standing over their shoulder,

00:06:10.880 --> 00:06:13.540
auditing them, wanting to see what they're doing,

00:06:13.550 --> 00:06:17.050
needing to collect evidence and supply that to somebody for something,

00:06:17.310 --> 00:06:18.400
you know, all the time.

00:06:18.400 --> 00:06:21.220
And, yeah, I can understand how that would get tiresome.

00:06:21.410 --> 00:06:24.560
Jovan Answer for how the U get over.

00:06:24.870 --> 00:06:26.220
That's a tough one, I think.

00:06:26.230 --> 00:06:30.780
I think there's, ah sort of a right kind of measure somewhere in the middle on,

00:06:30.780 --> 00:06:31.420
then Obviously, you know,

00:06:31.420 --> 00:06:33.720
for our for where we do a bunch of different kinds of audits.

00:06:33.960 --> 00:06:38.460
Uh, the the thing that we can do in many cases,

00:06:38.460 --> 00:06:41.380
is very assiduous amount of planning to say,

00:06:41.510 --> 00:06:46.880
How do we structure our timing structure or requests to?

00:06:47.310 --> 00:06:50.450
You know, it's a leverage as much as we can across these different things,

00:06:50.560 --> 00:06:50.820
right?

00:06:51.190 --> 00:06:54.790
If your requesting policies for a sock one can I use the

00:06:54.790 --> 00:06:56.980
same policy documents for my purposes, right.

00:06:57.120 --> 00:06:59.910
If I'm requesting a bunch of change tickets for PC idea assess,

00:07:00.100 --> 00:07:02.430
you know, then when my colleagues and I are so practice,

00:07:02.430 --> 00:07:03.410
come along a little later.

00:07:03.540 --> 00:07:06.050
Can I just give them those work papers and say, Here you go right.

00:07:06.060 --> 00:07:07.180
And sometimes the answer is yes.

00:07:07.180 --> 00:07:11.180
And sometimes the answer is no on sometimes our scopes are divergent and

00:07:11.180 --> 00:07:14.650
sometimes our timing just doesn't work where that could happen.

00:07:15.060 --> 00:07:16.210
But obviously,

00:07:16.210 --> 00:07:18.280
managing those expectations with our clients and then

00:07:18.280 --> 00:07:20.650
planning appropriately is how we do that Kuhm.
