WEBVTT

00:00:01.040 --> 00:00:03.390
[Autogenerated] We know that criminals like to remove traces of their

00:00:03.390 --> 00:00:05.980
activity from the audit logs so they can't be detected,

00:00:06.190 --> 00:00:09.170
and that will also hamper forensic investigations.

00:00:09.540 --> 00:00:13.760
And so requirement 10.5 is all about protecting the integrity of

00:00:13.760 --> 00:00:17.800
audit trails on the core of the requirement here.

00:00:17.920 --> 00:00:23.960
Demands the audit trails are in PC terms secured so they can't be altered.

00:00:24.340 --> 00:00:24.860
There are five.

00:00:24.860 --> 00:00:26.650
Some requirements have to be fulfilled.

00:00:28.440 --> 00:00:31.500
The testing procedure for the first four of the five sub

00:00:31.500 --> 00:00:34.420
requirements is the same that the QoS a will look at

00:00:34.420 --> 00:00:35.990
system settings and permissions.

00:00:36.170 --> 00:00:40.020
On also interview the system administrators on the first

00:00:40.020 --> 00:00:42.260
of the log integrity sub requirements.

00:00:42.260 --> 00:00:45.820
10.5 of requirements is to restrict read access of

00:00:45.820 --> 00:00:47.050
the logs to people who need it.

00:00:47.440 --> 00:00:50.860
So making sure that as basically with everything in the c.

00:00:50.860 --> 00:00:51.430
D.

00:00:51.460 --> 00:00:53.840
You've got role based access with least privilege

00:00:53.850 --> 00:00:55.570
based on the need to know basis.

00:00:56.240 --> 00:01:00.440
Requirement 10.5 point two just appears to be a restatement of

00:01:00.440 --> 00:01:04.120
the Maintain 20.5 requirement to protect all that log files

00:01:04.120 --> 00:01:05.700
from unauthorized modifications.

00:01:05.700 --> 00:01:09.250
But like so many things in Requirement 10,

00:01:09.740 --> 00:01:12.570
the actual details in the testing procedure again,

00:01:12.770 --> 00:01:13.430
which I've added.

00:01:13.430 --> 00:01:14.870
Here in the purple text,

00:01:15.240 --> 00:01:18.620
the QoS is going to look to see what logical and

00:01:18.620 --> 00:01:21.270
physical access controls are in place.

00:01:22.340 --> 00:01:26.280
Now we have to be careful with 10.5 point three to make sure

00:01:26.280 --> 00:01:28.850
we don't take a too literal interpretation.

00:01:29.540 --> 00:01:34.740
What the standard wants is for the log files to exist on a system that's

00:01:34.740 --> 00:01:37.370
separate from the system that generated the log files.

00:01:37.740 --> 00:01:40.500
So the use of the word back up here is a bit confusing.

00:01:40.620 --> 00:01:42.660
Remember, the standard is quite old,

00:01:42.670 --> 00:01:46.380
and so it was written when it wasn't common to automatically have

00:01:46.380 --> 00:01:48.660
systems right there logs to central log collectors.

00:01:49.040 --> 00:01:53.270
So if you do that already, if you write your log files to central log collectors,

00:01:53.360 --> 00:01:54.860
you could ignore this requirement.

00:01:55.840 --> 00:01:57.250
If you don't,

00:01:57.280 --> 00:02:00.070
then you need to copy the log files from the system that generated

00:02:00.070 --> 00:02:04.030
it to another system because the actual back But retention of log

00:02:04.030 --> 00:02:06.560
files is part of requirement 10.7.

00:02:07.440 --> 00:02:11.490
It's also important that where we think of this word back up here,

00:02:11.540 --> 00:02:15.800
it's not that it's saying that backups have to be proven to be immutable,

00:02:15.810 --> 00:02:19.290
just difficult to alter on again,

00:02:19.370 --> 00:02:23.770
10.5 point four predates the general way that companies consolidate logs today,

00:02:24.010 --> 00:02:28.640
an explicit calls error blog far as generated by externally facing devices to

00:02:28.640 --> 00:02:32.340
be written to internal servers so that the log files error not directly

00:02:32.340 --> 00:02:35.870
accessible if the external facing devices compromised.

00:02:36.940 --> 00:02:39.210
The last of the sub requirements concerned with the

00:02:39.210 --> 00:02:41.760
integrity of log files is 10.5 point five,

00:02:41.970 --> 00:02:43.730
which asked for file integrity,

00:02:43.730 --> 00:02:47.870
monitoring or or any change detection mechanism to

00:02:47.870 --> 00:02:50.560
detect an alert on changes in log files.

00:02:50.830 --> 00:02:53.300
Now this could be problematic because, of course,

00:02:53.300 --> 00:02:57.370
log files change all of the time because they're constantly being written to.

00:02:57.540 --> 00:03:00.570
So this could be a tricky requirement to Azure fulfill.

00:03:00.820 --> 00:03:05.700
And often we end up with the integrity controls built into seem solutions,

00:03:05.920 --> 00:03:10.950
which then are cited as appropriate controls to meet this requirement.

00:03:11.840 --> 00:03:15.480
The testing procedure of a 10.5 point five is for the QoS A to

00:03:15.480 --> 00:03:18.530
both look at the configuration of the change detection software

00:03:18.710 --> 00:03:20.870
and also the logs generated by it
