WEBVTT

00:00:01.040 --> 00:00:02.320
[Autogenerated] There will be many systems and

00:00:02.320 --> 00:00:04.030
components generating log entries,

00:00:04.100 --> 00:00:06.470
so it's important that they're all synchronized to the same

00:00:06.470 --> 00:00:09.230
time so you can reconstruct analyze events.

00:00:09.500 --> 00:00:12.350
And that's what requirement 10.4 is all about.

00:00:13.440 --> 00:00:16.840
It's important to remember now that the DSS is over 10 years

00:00:16.840 --> 00:00:20.670
old on what we take for granted now that just about every

00:00:20.670 --> 00:00:24.110
system will automatically wanted external time souls wasn't

00:00:24.110 --> 00:00:25.890
really true when CSS was written.

00:00:26.220 --> 00:00:29.620
And so this is quite involved that requirements to make sure that

00:00:29.620 --> 00:00:33.570
time within the 100 is synchronized and protected.

00:00:34.240 --> 00:00:34.640
Now,

00:00:34.650 --> 00:00:37.540
although this is a top level requirement with the detail

00:00:37.540 --> 00:00:38.950
to follow in the sub requirements,

00:00:39.340 --> 00:00:43.860
the testing procedure wants to QoS A to make sure that doing time properly is

00:00:43.860 --> 00:00:47.860
included in system build on the system update processes.

00:00:49.040 --> 00:00:51.000
The first sub requirement, however,

00:00:51.190 --> 00:00:54.730
looks like a restatement of the main requirement on this is one where you

00:00:54.730 --> 00:00:57.550
have to dig deeply to understand what the standard wants,

00:00:57.760 --> 00:01:01.990
because the requirement itself is really light on details just asking for

00:01:01.990 --> 00:01:04.760
correct and consistent time across critical systems.

00:01:05.239 --> 00:01:07.910
But the hard detail of the requirements error actually

00:01:07.910 --> 00:01:09.440
hidden in the testing procedure,

00:01:09.510 --> 00:01:13.630
which we need to look at and error two parts of the testing procedure.

00:01:13.630 --> 00:01:16.180
The 1st 10.4 point one a.

00:01:16.220 --> 00:01:21.020
Ask use A to check processes and procedures on the 2nd 10.4 point

00:01:21.020 --> 00:01:25.810
one b to look at configuration settings to check for three time

00:01:25.810 --> 00:01:29.530
related configuration requirements, which are this Firstly,

00:01:29.530 --> 00:01:32.760
there's a central time server or servers that get time

00:01:32.760 --> 00:01:34.610
from a reputable external source.

00:01:34.790 --> 00:01:37.300
Secondly, if you've got multiple times servers,

00:01:37.300 --> 00:01:38.750
they synchronized with each other.

00:01:38.940 --> 00:01:39.930
And finally,

00:01:40.080 --> 00:01:44.540
all the critical systems in the 500 get their time from your Central

00:01:44.540 --> 00:01:48.050
time server on not directly from external time sources.

00:01:49.040 --> 00:01:51.440
Again, with requirement 10.4 point two.

00:01:51.440 --> 00:01:53.450
There's not much detail in the requirement.

00:01:53.500 --> 00:01:56.560
It just asked that all time data is protected,

00:01:56.840 --> 00:01:59.190
and you may have noticed that the guidance is the same

00:01:59.190 --> 00:02:01.250
for all of the 10.4 requirements.

00:02:01.940 --> 00:02:05.220
But again, the real detail of the requirement is in the testing procedure,

00:02:05.220 --> 00:02:08.509
which I paraphrased here below the requirement so you can see what the

00:02:08.509 --> 00:02:11.660
standard means when it says Time database protects did,

00:02:12.040 --> 00:02:16.150
and that is the least privileged access and change controller.

00:02:16.150 --> 00:02:19.360
What's really, really meant by this requirement.

00:02:19.740 --> 00:02:23.440
So the things that the QoS A will look for to validate that these two aspects

00:02:23.440 --> 00:02:27.400
of protecting time or in place of the system configurations,

00:02:27.540 --> 00:02:31.200
settings and log files back for the last time search

00:02:31.200 --> 00:02:33.660
requirement does actually say what it means,

00:02:34.040 --> 00:02:36.930
which is that your Central time server or time servers

00:02:37.060 --> 00:02:39.840
actually get time from industry accepted sources.

00:02:39.950 --> 00:02:41.200
So that could be well known.

00:02:41.200 --> 00:02:45.430
Protected NTP servers on the Internet or something like a GPS receiver

00:02:45.580 --> 00:02:50.360
plugged into your own time server on to test this the QoS A is just going

00:02:50.360 --> 00:02:52.460
to look at the configuration of your time servers.

00:02:53.040 --> 00:02:53.550
Now.

00:02:53.560 --> 00:02:56.580
I think we spent enough time on time servers,

00:02:56.610 --> 00:02:59.160
so let's move on to the security of audit trails.
