WEBVTT

00:00:01.240 --> 00:00:02.240
[Autogenerated] requirement 10.

00:00:02.340 --> 00:00:06.070
It's all about the ability to detect and investigate incidents.

00:00:06.330 --> 00:00:09.670
It's commonly thought of us the logging and monitoring requirement.

00:00:10.140 --> 00:00:13.630
It's quite a long requirement for something so simple and

00:00:13.630 --> 00:00:17.100
starts off with the basic requirement to have audit trails or

00:00:17.100 --> 00:00:19.650
logs tied to individual use activity.

00:00:20.240 --> 00:00:23.640
Then the standard is quite prescriptive about the systems and

00:00:23.640 --> 00:00:26.640
events that should be logged on the level of detail that has to

00:00:26.650 --> 00:00:31.670
be logged because log correlation, needs or systems degree in what time is.

00:00:31.880 --> 00:00:34.460
There is a requirement for time synchronization and time

00:00:34.460 --> 00:00:37.880
servers and also the audit log files error secure from

00:00:37.880 --> 00:00:39.850
tampering and retained for a year.

00:00:40.640 --> 00:00:41.570
Unsurprisingly,

00:00:41.580 --> 00:00:45.740
the standard also wants to be to respond to events that you notice in the logs.

00:00:45.910 --> 00:00:49.010
And as with all of the PC IDE CSS requirement,

00:00:49.030 --> 00:00:52.070
you need to have policies and procedures to support the requirements.

00:00:52.740 --> 00:00:56.460
Finally, there's a requirement that just applies to service providers,

00:00:56.640 --> 00:01:00.210
which is to respond to failures of critical security systems

00:01:00.350 --> 00:01:03.150
such as firewalls or anti malware protection.

00:01:04.739 --> 00:01:06.880
In terms of the scope of this requirement,

00:01:07.130 --> 00:01:11.660
every system in and connected to the 500 potentially needs to be able to

00:01:11.660 --> 00:01:15.150
generate audit logs and synchronized to the correct time.

00:01:16.140 --> 00:01:19.730
The requirement starts off quite simply with Requirement 10.1,

00:01:19.740 --> 00:01:23.160
which wants to make sure that the audit trail links

00:01:23.160 --> 00:01:25.470
people to activity on systems.

00:01:25.940 --> 00:01:30.350
We'll see soon that in 10.2 Standard then specifies what sort of

00:01:30.350 --> 00:01:33.420
access has to be recorded and 10.3 tells us what events

00:01:33.420 --> 00:01:35.430
associated with activity should be logged.

00:01:35.600 --> 00:01:40.750
But to start off the requirement is simply the audit trails link individual

00:01:40.750 --> 00:01:45.600
user accounts to system component access and QoS A will look at system

00:01:45.600 --> 00:01:50.430
configurations to make sure that the user IDE or name is associated with all

00:01:50.430 --> 00:01:54.220
the events on they will also talk with system admin is to make sure this is

00:01:54.220 --> 00:01:56.750
standard practice across all systems.
