[Autogenerated] the final requirement in peace GUID
CSS is only for service providers, so if you're not a service provider,
we're done.
That's the end of the PC IDE AD FS requirements.
On the end of the course, however,
I'd like to encourage you to stick around for a few more
minutes because 12.11 is a great requirement.
This _______ requirement that I'd expect to see made mandatory for all
organizations in a future version of PC Idea says Well,
or something like this because it marks the start of changing PC IDE CSS
from an annual assurance activity to a much more regular.
In fact, I predict eventually a continuous assurance process.
The requirement is that this it wants the organization to self
validate that some of the important businesses usual
requirements such as log fire monitoring,
firewall reviews and change control are actually happening on.
It wants the organization to validate this every quarter.
To validate this requirement,
the QoS is going to look for policies and procedures that
require these quarterly reviews to happen.
They'll speak with the people responsible for carrying out the reviews.
There's just one sub requirements 12.11,
which again only applies to service providers,
and it's this.
So she got two parts, firstly,
that the results of the quarterly reviews error documented.
Now, this doesn't mean you got to document with lots of ticks in saying,
Well, we checked this and we check this,
but a real review.
So I've expected to show there are some things that have failed
occasionally on that were recommendations.
The process changes and and lessons learned from a failure
and what the organization is going to do to make sure it
didn't happen again and then.
Secondly, on this is a strange one.
Secondly,
the person with responsibility for the organization's maintenance of PC IDE CSS
compliance They have to sign off this quarterly review because you may remember
that requirement 12.4 point one demanded that the service providers only an
individual or a role had defined responsibility for maintaining the PC IDE CSS
compliance of the organization.
And it's this person that the Yusa would expect to
reviewed and signed off the quarterly P.
C.
I.
D.
S s Compliance review.
And so that's what they're gonna look for their going to
Look at requirement 12.4 point one.
See that person named on.
Then make sure that person signed off these quarterly reviews.
That's really it.
We've reached the end of requirement 12 on the end of
all the core PC IDE CSS requirements.
All that remains is to join the discussion I had with Jacob one final
time where we discuss business as usual Compliance.
If you've been following this course from Requirement
one hope it was useful on that.
The format we did hear of the theory followed by some
practical insight really worked for you.
Can you let us know by providing feedback or comments?
Thank you.