WEBVTT

00:00:01.040 --> 00:00:03.230
[Autogenerated] the final requirement in peace GUID

00:00:03.230 --> 00:00:07.730
CSS is only for service providers, so if you're not a service provider,

00:00:07.740 --> 00:00:08.470
we're done.

00:00:08.740 --> 00:00:11.250
That's the end of the PC IDE AD FS requirements.

00:00:11.260 --> 00:00:13.960
On the end of the course, however,

00:00:14.340 --> 00:00:17.050
I'd like to encourage you to stick around for a few more

00:00:17.050 --> 00:00:20.780
minutes because 12.11 is a great requirement.

00:00:20.970 --> 00:00:24.910
This _______ requirement that I'd expect to see made mandatory for all

00:00:24.910 --> 00:00:28.230
organizations in a future version of PC Idea says Well,

00:00:28.240 --> 00:00:32.369
or something like this because it marks the start of changing PC IDE CSS

00:00:32.369 --> 00:00:35.880
from an annual assurance activity to a much more regular.

00:00:36.140 --> 00:00:40.070
In fact, I predict eventually a continuous assurance process.

00:00:40.640 --> 00:00:44.990
The requirement is that this it wants the organization to self

00:00:44.990 --> 00:00:48.090
validate that some of the important businesses usual

00:00:48.090 --> 00:00:51.030
requirements such as log fire monitoring,

00:00:51.200 --> 00:00:55.260
firewall reviews and change control are actually happening on.

00:00:55.260 --> 00:00:58.870
It wants the organization to validate this every quarter.

00:00:59.540 --> 00:01:01.330
To validate this requirement,

00:01:01.330 --> 00:01:04.430
the QoS is going to look for policies and procedures that

00:01:04.430 --> 00:01:06.760
require these quarterly reviews to happen.

00:01:06.920 --> 00:01:10.660
They'll speak with the people responsible for carrying out the reviews.

00:01:11.440 --> 00:01:13.820
There's just one sub requirements 12.11,

00:01:13.940 --> 00:01:16.360
which again only applies to service providers,

00:01:16.580 --> 00:01:17.470
and it's this.

00:01:18.040 --> 00:01:20.270
So she got two parts, firstly,

00:01:20.460 --> 00:01:23.290
that the results of the quarterly reviews error documented.

00:01:23.500 --> 00:01:26.550
Now, this doesn't mean you got to document with lots of ticks in saying,

00:01:26.550 --> 00:01:27.880
Well, we checked this and we check this,

00:01:27.880 --> 00:01:29.160
but a real review.

00:01:29.300 --> 00:01:32.420
So I've expected to show there are some things that have failed

00:01:32.420 --> 00:01:34.650
occasionally on that were recommendations.

00:01:34.650 --> 00:01:39.030
The process changes and and lessons learned from a failure

00:01:39.030 --> 00:01:40.880
and what the organization is going to do to make sure it

00:01:40.880 --> 00:01:42.560
didn't happen again and then.

00:01:42.560 --> 00:01:45.210
Secondly, on this is a strange one.

00:01:45.210 --> 00:01:45.860
Secondly,

00:01:45.940 --> 00:01:50.970
the person with responsibility for the organization's maintenance of PC IDE CSS

00:01:50.970 --> 00:01:56.380
compliance They have to sign off this quarterly review because you may remember

00:01:56.520 --> 00:02:02.890
that requirement 12.4 point one demanded that the service providers only an

00:02:02.900 --> 00:02:07.840
individual or a role had defined responsibility for maintaining the PC IDE CSS

00:02:07.840 --> 00:02:09.550
compliance of the organization.

00:02:10.340 --> 00:02:13.840
And it's this person that the Yusa would expect to

00:02:13.840 --> 00:02:16.060
reviewed and signed off the quarterly P.

00:02:16.060 --> 00:02:16.250
C.

00:02:16.250 --> 00:02:16.600
I.

00:02:16.610 --> 00:02:16.870
D.

00:02:16.870 --> 00:02:18.260
S s Compliance review.

00:02:18.840 --> 00:02:20.860
And so that's what they're gonna look for their going to

00:02:20.860 --> 00:02:22.820
Look at requirement 12.4 point one.

00:02:23.000 --> 00:02:24.580
See that person named on.

00:02:24.580 --> 00:02:28.470
Then make sure that person signed off these quarterly reviews.

00:02:29.540 --> 00:02:30.680
That's really it.

00:02:30.920 --> 00:02:33.750
We've reached the end of requirement 12 on the end of

00:02:33.760 --> 00:02:36.350
all the core PC IDE CSS requirements.

00:02:36.840 --> 00:02:40.100
All that remains is to join the discussion I had with Jacob one final

00:02:40.100 --> 00:02:43.260
time where we discuss business as usual Compliance.

00:02:44.340 --> 00:02:46.760
If you've been following this course from Requirement

00:02:46.760 --> 00:02:49.270
one hope it was useful on that.

00:02:49.270 --> 00:02:52.300
The format we did hear of the theory followed by some

00:02:52.300 --> 00:02:54.270
practical insight really worked for you.

00:02:54.840 --> 00:02:57.750
Can you let us know by providing feedback or comments?

00:02:58.140 --> 00:02:58.650
Thank you.
