[Autogenerated] Hello.
My name is John Elliott.
Welcome to the course.
PC IDE CSS restricting access to cardholder data.
In this course,
I bring together the theoretical knowledge of PC
IDE CSS requirements 78 on nine,
along with practical experience of how the standard really works.
And I'm Jacob.
I'm sorry, I'm a qualified security assessor or que se will shaman and company.
And I'm qualified to assess many of the PC I standards,
including PC IDE, CSS, Ph.
D.
S S and P to be.
I've been an assessor for 14 years and have been doing this
since the predecessor standards to PC IDE CSS.
In this course,
we will cover the authorization or and authentication
related requirements of PC IDE CSS.
So that's things like least privileged access control
passwords on multi factor authentication as well as
looking at logical access controls.
We're going to find out about the physical security
requirements and CSS ranging from simple things such as
visitor control and secure buildings,
to how to prevent skimming and tampering attacks
against devices that read payment cards.
But each PC IDE CSS requirement.
I'm going to cover what the standards says,
what it means on what will be assessed by Husa.
Then Jacob and I will discuss some of the key practical aspect
of getting compliance on being assessed.
Ideally,
you'll already understand the basics of payment card processing and PC IDE S s.
But if you just want to get to grips with the requirement,
you'll be able to jump straight in with no problems.
By the end of this course,
you'll have a great understanding of both the theory and the
practice to help you restrict access to cardholder data
following the PC IDE CSS requirements.
We do hope you enjoying us to learn the theory and practice behind PC IDE
CSS requirements 78 and nine with the PC IDE CSS restricting access to
cardholder data course here apps Pluralsight.