WEBVTT

00:00:01.040 --> 00:00:01.690
[Autogenerated] given us now.

00:00:01.690 --> 00:00:07.040
An audit trail linking Uses to actions Requirement 10.2 now tells

00:00:07.040 --> 00:00:10.510
you what set of actions taken by a user needs to be able to be

00:00:10.510 --> 00:00:12.290
reconstructed from the audit trail.

00:00:12.500 --> 00:00:16.670
This is actually a rare outcome based word of requirement in PC IDE CSS,

00:00:17.240 --> 00:00:20.400
and it says that auditing must be enabled on all system

00:00:20.400 --> 00:00:24.720
components to be able to reconstruct the specific events

00:00:24.720 --> 00:00:29.360
detailed in the sub requirements, 10.2 point one through to 10.2 point seven.

00:00:29.940 --> 00:00:33.270
It's really useful to pay careful attention to the wording here.

00:00:33.640 --> 00:00:36.900
It does not say the auditing needs to be enabled for

00:00:36.910 --> 00:00:39.070
every system component in the CD,

00:00:39.540 --> 00:00:43.860
just those that are required to construct the specific events.

00:00:45.440 --> 00:00:49.050
The testing procedure for all of the sub requirements is the same,

00:00:49.220 --> 00:00:53.010
which is to verify, but what's specified is logged on the QoS.

00:00:53.010 --> 00:00:56.660
A will do this by looking at the logs and talking to Sister Madman's.

00:00:57.540 --> 00:01:00.120
So the first event that they spelled to be reconstructed from the

00:01:00.120 --> 00:01:03.660
audit logs is individual access to cardholder data.

00:01:04.040 --> 00:01:08.960
Next, any activities carried out by users with admin or root level access,

00:01:09.540 --> 00:01:13.500
and rather recursive Lee access to audit trails because of,

00:01:13.510 --> 00:01:13.900
of course,

00:01:13.900 --> 00:01:16.810
criminals will want to cover up their malicious activity by

00:01:16.810 --> 00:01:18.870
deleting records from the audit trails.

00:01:19.640 --> 00:01:23.450
The next event that needs to be logged is invalid logical access attempts.

00:01:23.760 --> 00:01:25.170
In other words,

00:01:25.170 --> 00:01:28.750
where the user name and password didn't match so that you could look for people

00:01:28.750 --> 00:01:32.150
trying to guess username or trying to brute force passwords.

00:01:33.640 --> 00:01:36.990
Sub requirement 10.2 point five is slightly more involved,

00:01:37.150 --> 00:01:40.020
and there are actually a few actions that need to be able to

00:01:40.030 --> 00:01:41.860
be reconstruct from the logs in this one.

00:01:42.340 --> 00:01:44.660
It's a tough requirement to decipher.

00:01:44.740 --> 00:01:48.730
So first off is the use of identification authentication mechanisms,

00:01:48.880 --> 00:01:52.970
so successful Loggins and details of what authentication we used to

00:01:52.970 --> 00:01:57.690
validate that successful log in next in the sub requirement.

00:01:57.740 --> 00:02:01.330
His changes to identification and authentication mechanisms.

00:02:01.460 --> 00:02:06.070
So changes of username passwords for MF error requirements and

00:02:06.070 --> 00:02:10.229
that must also include the creation of new accounts on any

00:02:10.240 --> 00:02:12.070
elevation of account privileges.

00:02:12.540 --> 00:02:16.290
And finally, anything that's done to root or admin accounts.

00:02:16.500 --> 00:02:17.190
And yes,

00:02:17.190 --> 00:02:19.830
if you're thinking that should have been three separate sub requirements,

00:02:19.840 --> 00:02:20.760
it probably should.

00:02:22.440 --> 00:02:23.200
Thankfully,

00:02:23.210 --> 00:02:26.580
10.2 point six is much simpler which is another slightly

00:02:26.580 --> 00:02:29.110
recursive sounding one that starting,

00:02:29.110 --> 00:02:32.490
stopping or pausing audit logging needs to be logged.

00:02:32.740 --> 00:02:35.880
It's not actually recursive because you'd write that the audit

00:02:35.880 --> 00:02:39.550
log was stopped before it was stopped and are not trying to do it

00:02:39.550 --> 00:02:42.080
afterwards once it was stopped on.

00:02:42.080 --> 00:02:43.900
The final event that needs to be logged so it could

00:02:43.900 --> 00:02:45.780
be reconstructed is quite vague,

00:02:45.890 --> 00:02:49.970
and that's the creation deletion off system level objects.

00:02:50.440 --> 00:02:50.680
Now.

00:02:50.680 --> 00:02:54.000
I think this should also include the modification of system level objects,

00:02:54.010 --> 00:02:54.690
which is clear.

00:02:54.690 --> 00:02:59.090
The intent in the guidance on the question I know that you're asking yourself is

00:02:59.090 --> 00:03:02.390
what on earth is a system level object and you're in luck?

00:03:02.530 --> 00:03:06.950
Because that's actually a term do you find in the PC IDE CSS glossary on

00:03:06.950 --> 00:03:09.620
who's the definition of the term and you can see it's a pretty broad

00:03:09.620 --> 00:03:12.980
definition off anything the system needs to operate.

00:03:13.090 --> 00:03:15.340
So it's the creation deletion of modification of

00:03:15.350 --> 00:03:17.260
everything in the list you see in front of you,

00:03:17.460 --> 00:03:19.980
and that's what needs to be written to the audit logs
