WEBVTT

00:00:01.140 --> 00:00:02.110
[Autogenerated] in this module,

00:00:02.120 --> 00:00:05.070
we're going to look at the final two parts of requirement 12.

00:00:05.350 --> 00:00:06.540
That's 12.10,

00:00:06.550 --> 00:00:12.020
which deals with incident response and applies to all organizations and 12.11,

00:00:12.030 --> 00:00:16.120
which looks at ongoing compliance and is just for the moment,

00:00:16.300 --> 00:00:21.340
just a requirement that service providers has to fulfill Requirement 12.10,

00:00:21.340 --> 00:00:25.050
then requires these organization to have an incident response plan.

00:00:25.640 --> 00:00:27.720
The requirement itself actually asked for the incident

00:00:27.720 --> 00:00:29.750
response plan to be implemented,

00:00:30.140 --> 00:00:32.950
and I love this on that the organization is ready to

00:00:32.950 --> 00:00:35.060
respond to a breach immediately.

00:00:35.640 --> 00:00:39.030
The testing procedure for 12.10 is basically to make sure

00:00:39.030 --> 00:00:40.860
that the six of requirements are in place.

00:00:41.540 --> 00:00:45.290
The first of these sub requirements, 12.10 point one,

00:00:45.540 --> 00:00:50.080
is to have written incident response Plan on the Standard defines

00:00:50.080 --> 00:00:52.660
the minimum elements that need to be in the plan,

00:00:53.140 --> 00:00:56.520
and these are defined roles and responsibilities,

00:00:56.650 --> 00:01:00.170
including communications responsibilities and importantly,

00:01:00.310 --> 00:01:03.760
if there's been a suspected breaching the confidentially of cardholder data,

00:01:03.770 --> 00:01:06.150
how to communicate that to the payment brands?

00:01:06.740 --> 00:01:10.390
There needs to be a specific procedures to be followed in an incident,

00:01:10.390 --> 00:01:12.570
and my recommendation here is that there are formal

00:01:12.570 --> 00:01:15.500
checklist that people work through and then also procedures

00:01:15.500 --> 00:01:17.650
to restore normal business operations.

00:01:18.140 --> 00:01:19.690
Now, interestingly,

00:01:19.690 --> 00:01:25.000
although PC Ideas has just focuses on breaches of confidentiality strangely,

00:01:25.000 --> 00:01:28.940
the incident response plan needs to cover how Data's backed up and restored.

00:01:29.270 --> 00:01:32.540
The incident response plan should also detail other legal or

00:01:32.540 --> 00:01:34.760
regulatory notifications that need to be made,

00:01:35.140 --> 00:01:40.290
such as US state data breach notification requirements or in Europe.

00:01:40.300 --> 00:01:44.720
The data breach notification requirements contained in the GDP are on.

00:01:44.720 --> 00:01:48.370
The last thing that PC IDE AD DS insists is in the incident

00:01:48.370 --> 00:01:51.230
response plan is that it's Pluralsight.

00:01:51.240 --> 00:01:53.520
It covers the whole organization,

00:01:53.530 --> 00:01:58.260
all the critical components on also the interface with any service providers.

00:01:58.440 --> 00:01:59.600
The QoS is going to check.

00:01:59.600 --> 00:02:01.650
The plan meets these requirements on Also,

00:02:01.650 --> 00:02:06.460
look back over historical incidents to verify the response plan was followed.

00:02:06.640 --> 00:02:10.870
The next of Requirement 12.10 point two has two parts.

00:02:11.440 --> 00:02:14.170
Firstly, that the plan is reviewed annually.

00:02:14.540 --> 00:02:16.570
You want to verify the plan is still fit?

00:02:16.570 --> 00:02:17.190
The purpose,

00:02:17.190 --> 00:02:22.260
based on how you process cars as an organization that everyone named in it is

00:02:22.260 --> 00:02:26.090
still actually working at the organization and they're doing the same jobs on

00:02:26.090 --> 00:02:29.310
that there'd be no other changes in the environment that mean the plan wouldn't

00:02:29.310 --> 00:02:31.850
work like you might have moved offices.

00:02:32.240 --> 00:02:35.850
The second part, this requirement is the plan is actually tested annually.

00:02:36.100 --> 00:02:39.730
This is usually going to be a tabletop exercise where all of the people who have

00:02:39.730 --> 00:02:43.290
got responsibilities that error named of the plan they gathered together in a

00:02:43.290 --> 00:02:46.460
room they role play their way through an incident.

00:02:46.840 --> 00:02:50.560
It ensures that everyone understands their roles, and the plan has got no gaps.

00:02:51.240 --> 00:02:51.560
The U.

00:02:51.560 --> 00:02:51.690
S.

00:02:51.690 --> 00:02:51.760
A.

00:02:51.760 --> 00:02:54.120
Is going to want to see evidence that that test took

00:02:54.120 --> 00:02:56.160
place and speak with the participants.

00:02:56.540 --> 00:02:57.410
He's a really good tip.

00:02:57.410 --> 00:02:59.730
If you had real incidents over the past 12 months,

00:02:59.830 --> 00:03:03.080
I've often managed to persuade uses that basically

00:03:03.270 --> 00:03:05.560
everyone participated in the actual incident,

00:03:05.570 --> 00:03:07.850
so we don't really need to have going to Testa's well.

00:03:08.340 --> 00:03:11.050
The next thing that PC IDE CSS wants is to make sure that

00:03:11.050 --> 00:03:14.710
their specific people who are on call to respond to a

00:03:14.710 --> 00:03:17.400
breach at any hour of the day, seven days a week,

00:03:17.430 --> 00:03:21.920
and also that these people will be contacted if a critical alert is

00:03:21.920 --> 00:03:25.570
generated and 12 points endpoint four wants to make sure that these

00:03:25.570 --> 00:03:29.280
people on call on the other people who might deal with an incident are

00:03:29.280 --> 00:03:31.160
properly trained in incident response,

00:03:31.350 --> 00:03:35.650
including how to safely preserved any evidence that may

00:03:35.650 --> 00:03:38.250
prove useful to a forensic investigator.

00:03:39.240 --> 00:03:40.570
So taken together,

00:03:40.570 --> 00:03:45.660
the testing requirements for 12.10 point three and 12.10 point four I mean,

00:03:45.660 --> 00:03:47.760
the que se is going to look at a lot of things.

00:03:47.760 --> 00:03:49.490
They're going to look at the training manuals.

00:03:49.500 --> 00:03:51.200
They're going to look at policies.

00:03:51.210 --> 00:03:53.240
They're going to look a training records.

00:03:53.250 --> 00:03:55.100
They're going to speak with personnel to validate.

00:03:55.100 --> 00:03:57.880
The people have had training and incident response on that.

00:03:57.880 --> 00:04:01.350
Those people are on core, unavailable 24 by seven.

00:04:01.840 --> 00:04:03.980
And if there have been historical alert,

00:04:04.100 --> 00:04:07.660
the QoS is going to look to see how those historical alerts were handled.

00:04:08.140 --> 00:04:11.710
Next in these incident response requirements is the demand that

00:04:11.720 --> 00:04:15.180
alerts from systems that are installed specifically as detective

00:04:15.180 --> 00:04:18.170
controls are actually responded to in the plan.

00:04:18.420 --> 00:04:20.890
So things like intruder detection system alerts,

00:04:21.019 --> 00:04:23.440
change detection or find integrity monitoring software,

00:04:23.440 --> 00:04:26.770
firewalls, rogue wireless access, point detection,

00:04:27.140 --> 00:04:30.590
all of their alert should be specifically dealt with a managed by

00:04:30.590 --> 00:04:34.320
this incident response process on the QoS a will.

00:04:34.320 --> 00:04:35.280
Again, What to check?

00:04:35.280 --> 00:04:38.900
This is the case by reference to the plan on also looking for historical

00:04:38.900 --> 00:04:42.560
evidence in how past alerts from detective controls were managed.

00:04:42.670 --> 00:04:46.590
So if you have an alert from, say, on IDE S that said,

00:04:46.600 --> 00:04:49.280
there's definitely an intruder here the QoS so could be

00:04:49.280 --> 00:04:52.300
looking to make sure that you instigate the first part we

00:04:52.300 --> 00:04:53.670
were Incident response plan.

00:04:54.040 --> 00:04:58.450
The final incident Response requirement 12.10 point six wants to make

00:04:58.450 --> 00:05:01.750
sure that the plan is modified and improved after each incident

00:05:02.140 --> 00:05:04.980
because there's actually implies requirement here to conduct the

00:05:04.980 --> 00:05:07.150
lessons learned exercise after incidents.

00:05:07.840 --> 00:05:11.110
The plan should also be updated in response to any external

00:05:11.110 --> 00:05:13.330
developments that might affect him on.

00:05:13.330 --> 00:05:14.040
Very typically,

00:05:14.040 --> 00:05:16.780
that's going to be communication from the card brands or the

00:05:16.780 --> 00:05:20.350
acquirer's on what to do when you have a data incident.

00:05:20.740 --> 00:05:25.970
And this time the QoS A is actually not looking explicitly here for evidence

00:05:25.970 --> 00:05:30.200
that this updating is happened because you might not have had an incident and

00:05:30.200 --> 00:05:32.230
therefore that might not be any lessons learned,

00:05:32.230 --> 00:05:34.280
and therefore you haven't updated the plan,

00:05:34.290 --> 00:05:38.250
so the QoS a wants to see evidence that you've got a process in place to review

00:05:38.250 --> 00:05:41.670
the plan after an incident and incorporate what you learned.

00:05:42.040 --> 00:05:42.780
And actually,

00:05:42.780 --> 00:05:45.140
while we're on the subject of incident response and

00:05:45.140 --> 00:05:46.780
what to do if there's a data breach,

00:05:46.790 --> 00:05:50.920
there's a really interesting Pluralsight play by play cause I made within

00:05:50.920 --> 00:05:54.940
experienced PC forensic investigator called Aaron Will is,

00:05:54.990 --> 00:05:59.670
and error has Bean bean doing incident response and going into

00:05:59.670 --> 00:06:02.440
merchants for breach of cardholder data for years on.

00:06:02.440 --> 00:06:03.350
In this play by play,

00:06:03.350 --> 00:06:06.060
we discuss what happens when there's a data breach incident,

00:06:06.240 --> 00:06:09.960
what the forensic investigator does on what the merchant needs to do.

00:06:10.740 --> 00:06:14.650
So now let's see what Jacob thinks about those generic incident response

00:06:14.650 --> 00:06:18.140
plans you can download from the Internet because he's got some views on that

00:06:18.150 --> 00:06:21.060
on also what good incident preparation looks like.
