WEBVTT

00:00:00.000 --> 00:00:00.740
Hello.

00:00:00.740 --> 00:00:06.722
Welcome to PCI DSS: Securing Data, Systems, and Applications.

00:00:06.723 --> 00:00:10.716
I'm John Elliott, and together we're going to look at requirements 3,

00:00:10.716 --> 00:00:17.201
4, 5, and 6 of PCI DSS, which are the ones focused on securing applications,

00:00:17.201 --> 00:00:20.982
securing operating systems, and securing card holder data.

00:00:20.983 --> 00:00:23.531
Before we dive into the PCI DSS requirements,

00:00:23.531 --> 00:00:27.442
I just want to quickly go over how this course works.

00:00:27.442 --> 00:00:31.646
If you've seen this introduction on another of my PCI DSS courses,

00:00:31.646 --> 00:00:34.170
then you're fine to skip this clip.

00:00:34.170 --> 00:00:37.460
If you haven't, this will only a couple of minutes.

00:00:37.461 --> 00:00:41.402
You see, learning about PCI DSS can be a bit boring.

00:00:41.402 --> 00:00:46.311
Altogether there are about three-hundred individual sub requirements,

00:00:46.312 --> 00:00:49.257
and as you expect, I'm going to talk about each one.

00:00:49.257 --> 00:00:52.815
When I did my QSA training many years ago,

00:00:52.815 --> 00:00:55.618
what the instructor did was read out each requirement

00:00:55.618 --> 00:01:00.190
just as it was printed in the standard, like this.

00:01:00.190 --> 00:01:09.676
Requirement 8.1 .4 ; remove or disable inactive user accounts within 90 days.

00:01:09.677 --> 00:01:12.492
Any questions?

00:01:12.492 --> 00:01:14.352
Now as I'm sure you agree,

00:01:14.353 --> 00:01:18.103
that's perhaps the most dull training course you can imagine,

00:01:18.103 --> 00:01:21.741
and so I'm not going to do that.

00:01:21.742 --> 00:01:22.015
Instead,

00:01:22.015 --> 00:01:26.349
I want you to make sure you've downloaded a copy of the latest

00:01:26.349 --> 00:01:30.562
version of PCI DSS from the PCI SSC website.

00:01:30.563 --> 00:01:35.300
Either print it out or have it open in another window so you can refer to it.

00:01:35.301 --> 00:01:37.521
When you look at the standard,

00:01:37.522 --> 00:01:40.842
you'll see that each sub requirement is split into three

00:01:40.842 --> 00:01:45.698
sections; the sub requirement itself, the testing procedure,

00:01:45.698 --> 00:01:48.924
and finally the guidance section,

00:01:48.924 --> 00:01:52.613
which describes the intent behind the requirements.

00:01:52.613 --> 00:01:55.419
As I talk about each sub requirement,

00:01:55.419 --> 00:01:59.019
I'm going to briefly summarize the point of the requirements,

00:01:59.019 --> 00:02:03.798
the guidance, and what a QSA will look for when do an assessment.

00:02:03.799 --> 00:02:07.924
Then, when we get to the end of a number of PCI DSS requirements,

00:02:07.924 --> 00:02:11.190
we're going to join the discussion I had with Jacob Ansari,

00:02:11.190 --> 00:02:15.301
who's one of the most experienced QSAs on the planet.

00:02:15.301 --> 00:02:18.350
Jacob and I will discuss the real-world issues you need to

00:02:18.350 --> 00:02:21.850
know about when implementing PCI DSS.

00:02:21.851 --> 00:02:25.107
We'll talk about common problems, what QSAs look for,

00:02:25.107 --> 00:02:28.101
and how security breaches happen.

00:02:28.101 --> 00:02:30.861
So I hope at the end of the course you'll understand both

00:02:30.861 --> 00:02:35.829
the theory and the practice of PCI DSS.

00:02:35.830 --> 00:02:37.811
To get the best out of the course,

00:02:37.812 --> 00:02:41.884
you need to understand PCI DSS concepts such what a PAN is,

00:02:41.884 --> 00:02:43.421
the cardholder data environment,

00:02:43.421 --> 00:02:49.750
and PCI DSS roles such as qualified security assessors.

00:02:49.750 --> 00:02:52.076
If you're a bit unsure about any of these foundations,

00:02:52.076 --> 00:02:58.483
then my Pluralsight PCI DSS, The Big Picture course will help.

00:02:58.483 --> 00:03:02.065
Sometimes I'm going to need to refer to PCI DSS requirements in

00:03:02.065 --> 00:03:05.267
the context of a network or system components.

00:03:05.267 --> 00:03:09.344
So I've invented a network for an imaginary merchant that accepts

00:03:09.344 --> 00:03:14.084
card payments in physical stores and on the web.

00:03:14.085 --> 00:03:17.323
In each store, there's a point-of-sale system,

00:03:17.323 --> 00:03:20.617
a local server that collects payment data,

00:03:20.617 --> 00:03:25.140
which it then sends over a VPN to a payment server at head office,

00:03:25.140 --> 00:03:29.262
which talks to the bank for authorization and settlements.

00:03:29.262 --> 00:03:34.320
Once a transaction has been authorized, all transaction details,

00:03:34.320 --> 00:03:39.300
including payment card data is stored in a database.

00:03:39.301 --> 00:03:41.199
There's also an e-commerce channel,

00:03:41.199 --> 00:03:45.144
which consists of an e-commerce web server at head

00:03:45.144 --> 00:03:47.411
office sitting inside the DMZ,

00:03:47.411 --> 00:03:51.700
which also talks to the payment server through a firewall.

00:03:51.701 --> 00:03:55.742
There's also a separate network used to manage the cardholder data environment,

00:03:55.743 --> 00:03:58.913
which itself is segmented from the corporate

00:03:58.913 --> 00:04:03.259
network and has no access to the CDE.

00:04:03.260 --> 00:04:05.771
Of course, your network probably doesn't look anything like this,

00:04:05.771 --> 00:04:08.401
but it will have the same sort of things in it,

00:04:08.402 --> 00:04:12.452
and most importantly, the different types of components.

00:04:12.452 --> 00:04:16.265
There's the cardholder data environment where cardholder data is stored,

00:04:16.266 --> 00:04:17.747
processed, or transmitted.

00:04:17.747 --> 00:04:21.616
There's systems that are connected to or that can affect the

00:04:21.616 --> 00:04:24.737
security of the cardholder data environment,

00:04:24.738 --> 00:04:30.638
and systems that are intended to be out of scope of PCI DSS requirements.

00:04:30.638 --> 00:04:33.143
That's the end of talking about how the course is structured so now

00:04:33.143 --> 00:04:40.761
it's time to look at requirement 3 of PCI DSS.
