WEBVTT

00:00:00.040 --> 00:00:00.460
[Autogenerated] we didn't.

00:00:00.460 --> 00:00:02.510
In the end way near the end,

00:00:02.520 --> 00:00:05.300
eso were probably requirement that no one ever even

00:00:05.300 --> 00:00:06.940
because they're bored by now, right,

00:00:06.950 --> 00:00:09.990
we're a 12.10 having an incident response plan and

00:00:09.990 --> 00:00:11.860
testing an incident response plan, right?

00:00:11.870 --> 00:00:14.520
We've just been through the theory of that.

00:00:14.530 --> 00:00:18.100
And people know that I'm passionate about incident response

00:00:18.100 --> 00:00:21.320
planning because it's a way of it's one of the few controls you

00:00:21.320 --> 00:00:24.950
have we can limit the impact off the breach.

00:00:24.960 --> 00:00:28.230
Most of DSS is about limiting the probability of the breach.

00:00:28.240 --> 00:00:30.690
Incident response limits the impact of a breach.

00:00:30.700 --> 00:00:31.910
So there's an assessor.

00:00:31.910 --> 00:00:34.750
What are you looking for in requirement 12 point?

00:00:34.750 --> 00:00:34.990
Tell me.

00:00:34.990 --> 00:00:36.210
Tell me what you're gonna be looking at.

00:00:36.220 --> 00:00:41.520
So I want to start with an incident response plan that has

00:00:41.520 --> 00:00:44.410
some organization specific substance to it.

00:00:44.420 --> 00:00:48.350
A lot of first drafts or a lot of, uh, you know,

00:00:48.360 --> 00:00:50.910
early attempts or a lot of things that maybe other assessors let

00:00:50.910 --> 00:00:53.600
them get away with have very high level stuff for that sort of

00:00:53.600 --> 00:00:58.700
parrots back the language of the PC, IDE s s or the payment brands,

00:00:58.710 --> 00:00:59.020
you know,

00:00:59.020 --> 00:01:01.650
kind of what to do with compromise stuff right and

00:01:01.650 --> 00:01:05.990
doesn't talk about how they handle that.

00:01:06.000 --> 00:01:07.530
Right on there.

00:01:07.530 --> 00:01:08.430
There are There are some.

00:01:08.440 --> 00:01:11.640
There's some sort of business kind of strategy, things that you need to do.

00:01:11.640 --> 00:01:13.820
And there are some kind of tactical technology,

00:01:13.820 --> 00:01:17.950
things that you need to do and and I think to the greatest extent

00:01:17.950 --> 00:01:22.960
possible you want as much of that mapped out in procedure as you can

00:01:22.960 --> 00:01:25.250
because an incident is never gonna be convenient.

00:01:25.340 --> 00:01:29.510
And you don't wanna be making at least those kind of first contact

00:01:29.510 --> 00:01:31.940
decisions at three in the morning on a Sunday,

00:01:31.950 --> 00:01:32.330
right?

00:01:32.340 --> 00:01:34.770
Just want to executable, looking for playbooks as well as an I.

00:01:34.770 --> 00:01:34.950
R.

00:01:34.950 --> 00:01:36.070
P or just an IOP.

00:01:36.080 --> 00:01:40.320
I mean, strictly speaking, there's not a requirement for a playbook, right?

00:01:40.320 --> 00:01:43.760
And maybe the document sort of combines those things, and that's fine.

00:01:43.740 --> 00:01:49.370
But I want to see that you have the ability to executable plan appropriately.

00:01:49.380 --> 00:01:52.080
Does your testing procedure involved interviewing?

00:01:52.080 --> 00:01:53.180
Is it just a documentary?

00:01:53.190 --> 00:01:53.860
It's both.

00:01:53.860 --> 00:01:55.290
It's interviewing and documentation, right?

00:01:55.290 --> 00:01:57.800
So you want to understand that people know what their

00:01:57.800 --> 00:02:01.730
responsibilities are and can demonstrate some competence,

00:02:01.730 --> 00:02:01.940
right?

00:02:01.940 --> 00:02:05.060
Or some understanding of what it is they're supposed to be doing okay,

00:02:05.070 --> 00:02:07.860
you know, and and this this shows up in a couple different ways,

00:02:07.860 --> 00:02:08.169
right?

00:02:08.340 --> 00:02:13.840
If you are, you know, the systems people and you have some evidence,

00:02:13.850 --> 00:02:15.940
you know, of compromise or potential compromise.

00:02:15.950 --> 00:02:20.150
How are you sort of limiting that from widening.

00:02:20.160 --> 00:02:25.900
How do you, uh, control those systems that the breach doesn't widen?

00:02:25.910 --> 00:02:27.040
That doesn't get worse.

00:02:27.040 --> 00:02:28.800
That doesn't spread throughout the organization.

00:02:28.810 --> 00:02:32.600
How do you preserve the systems for forensic investigation purposes?

00:02:32.600 --> 00:02:35.390
How do you maybe disconnect them from the network

00:02:35.390 --> 00:02:39.640
or put them in a in a preserve, a ble state where the evidence,

00:02:39.650 --> 00:02:43.610
you know, can't get adversely impacted by somebody continuing to operate That,

00:02:43.620 --> 00:02:48.170
uh, I want to stop you briefly, because throughout requirement 12,

00:02:48.170 --> 00:02:50.950
you said stuff has to be in place, but there's no quality threshold.

00:02:50.960 --> 00:02:52.390
Do you have a quality threshold?

00:02:52.390 --> 00:02:53.660
Then, in requirement 12 10,

00:02:53.670 --> 00:02:57.060
I would say I apply a more rigorous quality threshold,

00:02:57.070 --> 00:03:03.510
but it's it's difficult to sort of expressly point to that in the text.

00:03:03.520 --> 00:03:06.060
And I find a lot of organizations where maybe they've been getting

00:03:06.060 --> 00:03:09.220
assessments from other parties in years past.

00:03:09.230 --> 00:03:11.370
Uh, have a much lower quality threshold.

00:03:11.370 --> 00:03:15.940
Haven't have much more sort of boilerplate language and and little specificity.

00:03:15.950 --> 00:03:18.190
But you're looking at what is a policy?

00:03:18.200 --> 00:03:21.050
It's a plan for this organization, not a generic plan.

00:03:21.060 --> 00:03:21.440
Right.

00:03:21.450 --> 00:03:26.360
Okay, Now there's a requirement to review and test the plan annually, right?

00:03:26.640 --> 00:03:27.950
What evidence are you looking for?

00:03:27.950 --> 00:03:28.350
That.

00:03:28.640 --> 00:03:31.770
So I mean, testing could take a couple of different shapes, right?

00:03:31.770 --> 00:03:37.110
I don't necessarily require somebody to deliberately introduce malware

00:03:37.110 --> 00:03:39.390
into the organization or do something like that.

00:03:39.400 --> 00:03:42.130
It can be a tabletop exercise, right?

00:03:42.140 --> 00:03:43.970
And that could be valuable, really.

00:03:43.970 --> 00:03:45.640
And the testing and the training, you know,

00:03:45.640 --> 00:03:49.460
sometimes travel together in that In that regard where you know,

00:03:49.460 --> 00:03:52.010
the point of the testing is walk through the procedure.

00:03:52.010 --> 00:03:53.860
Here is a possible scenario.

00:03:53.870 --> 00:03:55.840
Right here is something that's gone wrong.

00:03:55.850 --> 00:03:57.340
What do we do?

00:03:57.350 --> 00:03:59.470
I think if you're going to do that, you know,

00:03:59.470 --> 00:04:02.920
one tip to really consider is to have someone whose job

00:04:02.930 --> 00:04:07.500
is to sort of make things go wrong, right?

00:04:07.500 --> 00:04:10.650
And and sort of raised the stakes and make sure that the plan is sort of,

00:04:10.660 --> 00:04:16.160
uh, rigorous enough to withstand that facilitated to able to \.

00:04:16.170 --> 00:04:16.709
Right?

00:04:16.720 --> 00:04:17.200
Right.

00:04:17.209 --> 00:04:17.660
Definitely.

00:04:17.660 --> 00:04:19.029
You have somebody facilitate that.

00:04:19.029 --> 00:04:23.020
Have somebody, uh, you know, potentially introduced problems, right?

00:04:23.020 --> 00:04:26.880
If if your plan documentation resides, uh,

00:04:26.890 --> 00:04:29.200
you know, in some particular storage repository,

00:04:29.210 --> 00:04:29.690
right?

00:04:29.700 --> 00:04:33.400
What happens when the incident also takes out the storage repository?

00:04:33.410 --> 00:04:33.740
Right.

00:04:33.750 --> 00:04:34.670
Uh,

00:04:34.680 --> 00:04:38.460
or what happens if a particular critical person is unavailable

00:04:38.460 --> 00:04:40.950
because they're on vacation or ill or whatever,

00:04:40.960 --> 00:04:43.000
but never happens when you do, you know,

00:04:43.010 --> 00:04:45.100
you organize the test for when everyone's there,

00:04:45.110 --> 00:04:45.480
right?

00:04:45.490 --> 00:04:49.510
Clearly, uh, eso so that I mean,

00:04:49.510 --> 00:04:51.260
those are the kinds of things you want to think about,

00:04:51.260 --> 00:04:51.570
right?

00:04:51.580 --> 00:04:52.950
And, you know,

00:04:52.950 --> 00:04:55.120
certainly if you have the capacity to do some sort

00:04:55.120 --> 00:04:59.140
of more realistic live activity, then sure.

00:04:59.150 --> 00:05:02.500
I think you could accomplish that with again.

00:05:02.500 --> 00:05:05.230
Sort of a usefully rigorous tabletop exercise.

00:05:05.240 --> 00:05:05.590
Okay,

00:05:05.600 --> 00:05:08.910
what about the city's actually had a breach and they've actually

00:05:08.910 --> 00:05:10.680
documented what they were doing is part of the breach.

00:05:10.680 --> 00:05:12.330
Is that is that better than a test?

00:05:12.340 --> 00:05:16.040
I mean, I think it's I think it is interesting for other reasons.

00:05:16.050 --> 00:05:20.770
I think, um, it doesn't qualify for the test.

00:05:20.770 --> 00:05:21.250
Your plan?

00:05:21.260 --> 00:05:25.430
Well, I think I think maybe what you could do from that right is okay.

00:05:25.430 --> 00:05:29.750
You have the actual incident and then you should have after that

00:05:29.750 --> 00:05:33.060
incident some sort of after action activity where you say,

00:05:33.070 --> 00:05:35.700
Here's what lessons Here's what we learned right here is

00:05:35.700 --> 00:05:37.440
where we did what we were supposed to do.

00:05:37.450 --> 00:05:39.150
Here's where we failed that.

00:05:39.160 --> 00:05:43.670
Here's where maybe we executed on the plan.

00:05:43.680 --> 00:05:46.830
But the plan was not satisfactory, right?

00:05:46.840 --> 00:05:49.260
Let's let's sort of put all of those lessons,

00:05:49.740 --> 00:05:54.990
you know, into play, and then maybe maybe let's do a tabletop on on,

00:05:54.990 --> 00:05:57.980
like a rematch right of that activity, right?

00:05:57.980 --> 00:06:00.640
Or some similar thing and say, now that we've made these changes,

00:06:00.640 --> 00:06:02.250
does our plan get better?

00:06:02.840 --> 00:06:03.350
Um,

00:06:04.740 --> 00:06:07.710
looking again at the standard of of of what's expected

00:06:07.710 --> 00:06:10.250
there is that everyone has to be trained,

00:06:10.250 --> 00:06:10.410
which,

00:06:10.410 --> 00:06:12.940
you said often can happen is part of the breach Exercise

00:06:12.950 --> 00:06:18.360
Training can happen in the exercise, but people who should be responsible 24 7.

00:06:19.140 --> 00:06:28.570
So you need some 24 7 capacity to do the first contact stuff, right?

00:06:28.580 --> 00:06:30.620
And then e.

00:06:30.620 --> 00:06:31.800
I mean part of training right?

00:06:31.810 --> 00:06:35.450
Isn't just, you know, the very technical sort of aspects of incident response,

00:06:35.450 --> 00:06:38.560
but it's understanding your role, right?

00:06:38.540 --> 00:06:42.210
And so then you need to be able to escalate that appropriately, right?

00:06:42.220 --> 00:06:48.820
If you're if your night shift help desk person is the first contact, right?

00:06:48.830 --> 00:06:52.550
You know, do they know who they're supposed to call, right?

00:06:52.560 --> 00:06:54.180
And then is your second tier person.

00:06:54.180 --> 00:06:56.140
Like, Do you have a schedule for who takes the,

00:06:56.150 --> 00:06:58.060
you know, the call, you know,

00:06:58.070 --> 00:07:00.830
so that they can expect to get woken up in the middle of the night or

00:07:00.830 --> 00:07:02.470
at least realize that that's part of their job.

00:07:02.480 --> 00:07:04.660
And then go do something about it on.

00:07:04.660 --> 00:07:06.650
Do you see this done particularly well, Particularly badly.

00:07:06.650 --> 00:07:07.370
An organization?

00:07:07.380 --> 00:07:10.520
Is it lip service requirement that people do, You see good stuff.

00:07:10.530 --> 00:07:13.970
I generally find lip service and generally have to sort

00:07:13.970 --> 00:07:17.000
of kind of herd them towards better, better stuff,

00:07:17.010 --> 00:07:17.430
right?

00:07:17.440 --> 00:07:19.690
You know, in some of this, you know,

00:07:19.690 --> 00:07:24.560
the I t people are capable of doing sort of the useful first contact stuff.

00:07:24.740 --> 00:07:29.740
Uh, but then you need some leadership from people higher up in the organization.

00:07:29.750 --> 00:07:30.080
Right?

00:07:30.090 --> 00:07:32.130
How do you then engage?

00:07:32.140 --> 00:07:38.460
Maybe a forensic assessor who communicates with the banks or the payment brands.

00:07:38.470 --> 00:07:41.290
Who makes the decision to call law enforcement?

00:07:41.300 --> 00:07:41.770
Right?

00:07:41.780 --> 00:07:43.430
You can't unring that bell.

00:07:43.440 --> 00:07:46.920
So you want somebody who has the right authority to do.

00:07:46.920 --> 00:07:50.560
That s o for real practical purposes.

00:07:50.560 --> 00:07:52.770
You need to go a bit above where the standard is on this one.

00:07:52.780 --> 00:07:53.860
I think so.
