WEBVTT

00:00:01.140 --> 00:00:04.320
[Autogenerated] requirement 11.5 aims to detect changes in

00:00:04.320 --> 00:00:07.350
files that shouldn't ordinarily change because this could be

00:00:07.350 --> 00:00:09.270
an indicator of malicious activity.

00:00:10.040 --> 00:00:13.570
This requirement used to say, deploy file integrity monitoring software,

00:00:13.740 --> 00:00:16.710
but it was changed version 3D to allow for any way of detecting

00:00:16.710 --> 00:00:21.410
changes to files and types of files where you want to monitor and

00:00:21.410 --> 00:00:24.650
detect for changes of these critical system files.

00:00:24.650 --> 00:00:29.730
Such Aziz the operating system, libraries and applications configuration files,

00:00:29.850 --> 00:00:33.090
which would affect the security of the system and then content files,

00:00:33.100 --> 00:00:34.170
which, for example,

00:00:34.260 --> 00:00:36.540
you know you could modify a content file to deliver

00:00:36.540 --> 00:00:38.550
malware to a user or to a customer.

00:00:39.340 --> 00:00:39.870
Obviously,

00:00:39.950 --> 00:00:43.010
the type of file monitored by change detection systems is

00:00:43.010 --> 00:00:44.650
going to vary from system to system.

00:00:45.340 --> 00:00:48.030
If you've ever managed a system where this is in place,

00:00:48.190 --> 00:00:51.770
you will know it's critical that is integrated with your patching systems and is

00:00:51.770 --> 00:00:55.360
correctly set up to prevent lots of false positive alerts.

00:00:56.340 --> 00:00:59.370
The system needs to generate alert when there is an

00:00:59.380 --> 00:01:04.890
unauthorized modification to a file, and if the system doesn't run real time,

00:01:05.110 --> 00:01:07.010
it must at least check systems.

00:01:07.120 --> 00:01:08.750
The changes once a week.

00:01:09.940 --> 00:01:12.150
The que se is going to look at the configuration of the

00:01:12.150 --> 00:01:16.230
change detection mechanism by examining its configuration and

00:01:16.230 --> 00:01:18.160
also looking at historical alerts.

00:01:18.940 --> 00:01:22.180
But it should also look the system produces alerts when it should

00:01:22.180 --> 00:01:24.850
do when there's an unauthorized modification.

00:01:26.040 --> 00:01:30.620
It's these alerts that are the focus for requiring 11.5 point one,

00:01:30.780 --> 00:01:33.570
which demands that there should be a process to respond to.

00:01:33.570 --> 00:01:37.420
Alerts generated by the change detection software on the QC.

00:01:37.420 --> 00:01:40.290
Here is simply going to chat with people to make sure

00:01:40.290 --> 00:01:42.250
those alerts error investigating resolved.

00:01:42.740 --> 00:01:44.740
Which of course, may not always happen,

00:01:44.900 --> 00:01:47.950
because often the integrity monitoring software is so

00:01:47.950 --> 00:01:49.930
badly configured and maintained.

00:01:50.110 --> 00:01:53.540
The security operations team get 500 alerts today from it,

00:01:53.600 --> 00:01:57.450
especially on patch days, for which they just completely ignore.

00:01:57.460 --> 00:01:58.380
So look Q.

00:01:58.380 --> 00:01:58.960
SATA is no.

00:01:58.960 --> 00:02:01.020
This is one requirement where they have to look

00:02:01.020 --> 00:02:04.420
particularly closely at how the alerts error produced on

00:02:04.420 --> 00:02:06.370
whether those alerts error responded to
