9.c PCI Informationr Security `"
Standards Council
Ten Common Myths of PCI DSS
The Payment Card Industry Data Security Standard (PCI DSS)
secures cardholder data that is stored, processed or transmitted
by merchants and processors. PCI DSS specifies 12 requirements
entailing many security technologies and business processes, and
reflects most of the usual best practices for securing sensitive
information. The resulting scope is comprehensive and may seem
daunting - especially for smaller merchants who have no existing
security processes or IT professionals to help guide them through
what is required and what is not. To complicate matters, some
vendors who sell security products or services market their products
in a broader context than just the PCI DSS requirements. As a result,
retailers who are new to security may harbor myths about the PCI
DSS. The PCI Security Standards Council presents ten common
myths about PCI DSS to help your business optimize protection of
cardholder data and ensure compliance with the standard.
AT A GLANCE
PCI DSS MYTHS
GOALS OF PCI DSS Myth 1 - One vendor and product will make us compliant
Build and maintain a secure Many vendors offer an array of software and services for PCI DSS compliance. No single vendor or
network product, however, fully addresses all 12 requirements of PCI DSS. When marketing focuses on one
Protect cardholder data product's capabilities to the exclusion of other PCI DSS requirements, the resulting perception of a
Maintain a vulnerability "silver bullet" might lead some to believe that a point product provides "compliance," when it rea:ly
management program only addresses just one or a few elements of the standard.
Implement strong access
The PCI Security Standards Council urges merchants, service providers and processors to avoid
control measures
focusing on point products for data security and PCI DSS compliance. Instead of relying on a single
Regularly monitor and test
product or vendor, you should implement a holistic security strategy that focuses on the "big picture"
networks
related to the intent of PCI DSS requirements. This approach includes people and processes, not just
Maintain an information
technology.
security policy
Myth 2 - Outsourcing card processing makes us compliant
Outsourcing simplifies payment card processing but does not provide automatic compliance. Don't
forget to address policies and procedures for cardholder transactions and data processing. Your
business must protect cardholder data when you receive it, and when you process charge backs and
refunds. You must also ensure that providers' applications and card payment terminals comply with
respective PCI standards and do not store sensitive cardholder data. You should request proof W
compliance annually from providers.
Myth 3 - PCI DSS compliance is an IT project
The IT staff implements technical and operational aspects of PCI -related systems, but compliance
to the payment brand's programs is much more than a "project" with a beginning and end - it's an
ongoing process of assessment, remediation and reporting. PCI compliance is a business issue
that is best addressed by a multi -disciplinary team. The risks of compromise are financlal and
reputational, so they affect the whole organization. Be sure your business addresses policies and
procedures as they apply to the entire card payment acceptance and processing workflow.
Myth 4 - PCI DSS will make us secure
Successful completion of a system scan or PCI DSS assessment is but a snapshot in time. Security
exploits are non-stop and get stronger every day, which is why PCI DSS compliance efforts must be
a continuous process of assessment and remediation to ensure safety of cardholder data.
PCI AT A -GLANCE
Myth 5 - PCI DSS is unreasonable; it requires too much
(visit www.pcisecuritystandards.org
Most aspects of the PCI DSS are already a common best practice for security. The standard also
for more information)
permits the option of using compensating controls to meet most requirements. The standard
Overview
provides significant detail, which benefits merchants and processors by not leaving them to wonder,
Getting Started with PCI DSS
"Where do I go from here?" This scope and flexibility leads some to view PCI DSS as an effective
10 Common Myths of PCI DSS
standard for securing all sensitive information.
Data Security Do's and Don'ts
Myth G - PCI DSS requires us to hire a Qualified Security Assessor
Because most large merchants have complex IT environments, many hire a OSA to glean their
specialized value for on •site security assessments required by PCI DSS. The QSA also assesses and
validates compensating controls. However, the payment card brands provide the option of doing an
Internal assessment with an officer sign -off if your acquirer and/or merchant bank agrees. The PCI
SSC also provides training for Internal Security Assessors (ISAs). Smaller merchants may be eligible
to self -assess their compliance and validate us'ng the Self -Assessment Ouestionnaire (SAO) found
on the PCI SSG web site.
Myth 7 - We don't take enough credit cards to be compliant
PCI DSS compliance is required for any business that accopts payment cards - even if the quantity
of transactions is just one.
Myth 8 - We completed a SAO so we're compliant
SAQs are va idation tools for eligible merchants and sery ce providers to report that they have
evaluated their PGI DSS compliance through a se`f assessment. it represents a snapshot of the
particular moment in time when the Self -Assessment QuasVonnaire and associated vulnerability scan
(if applicable) is completed. After that moment, only another assessment or post breach forensic
analysis can prove PCI DSS compliance. But a single system change can make you non compliant in
an instant. True security of cardholder data requires non-stop assessment and remediation to ensure
that the likelihood of a breach is kept as low as possible.
Myth 9 - PCI DSS makes us store cardholder data
Both PGI DSS and the payment card brands strongly discourage storage of cardholder data by
merchants and processors. There is no need, nor is it allowed, to store data from the magnetic stripe
on the back of a payment card, or equivalent data from a chip. If merchants or processors have a
business reason to store front -of -card information, such as cardholder name and primary account
number (PAN), PCI DSS requires this data to be protected, and the PAN to be encrypted or otherwise
made unreadable.
Myth 10 - PCI DSS is too hard
Understanding and implementing the 12 requirements of PCI DSS can seem daunting, especially for
merchants without a large security or IT department_ However, PCI DSS mostly calls for good, basic
security. Even if there was no requirement for PCI DSS compliance, the best practices for security
contained in the standard are steps that every business would want to take anyway to protect
sensitive data and continuity of operations. There are many products and services available to help
meet the requirements for security - and PCI DSS compliance.
When people say PCI DSS is too hard, many really mean to say compliance is not cheap. The
business risks and ultimate costs of non-compl'ance, however, can vastly exceed implementing
PCI DSS - such as fines, legal fees, decreases in stock equity, and especially lost business.
Implementing PCI DSS should be part of a sound, basic enterprise security strategy, which requires
making this activity part of your ongoing business plan and budget.
0 2010 PCI Security Standards Council LLC. The intent of this document is to provide supplemental Information, October 2010
which does not replace or supersede PCI SSC Security Standards or their supporting documents.
■ SIG hY •
Standards Counc I
Understanding the SAQs for PCI DSS version 3
The PCI DSS self-assessment questionnaires (SAQs) are validation tools intended to assist merchants
and service providers report the results of their PCI DSS self-assessment. The different SAO types are
shown in the table below to help you identify which SAO best applies to your organization. Detailed
descriptions for each SAO are provided within the applicable SAO.
Note: Entities should ensure they meet all the requirements for a particular SAO before using the SAO.
Merchants are encouraged to contact their merchant bank (acquirer) or the applicable payment brand(s)
to identify the appropriate SAO based on their eligibility.
A Card -not -present merchants (e-commerce or mail/telephone-order) that have fully
outsourced all cardholder data functions to PCI DSS validated third -party service
providers, with no electronic storage, processing, or transmission of any cardholder data
on the merchant's systems or premises.
Not applicable to face-to-face channels.
A -EP* E-commerce merchants who outsource all payment processing to PCI DSS validated third
parties, and who have a website(s) that doesn't directly receive cardholder data but that
can impact the security of the payment transaction. No electronic storage, processing, or
transmission of any cardholder data on the merchant's systems or premises.
Applicable only to e-commerce channels.
B I Merchants using only:
! • Imprint machines with no electronic cardholder data storage; and/or
• Standalone, dial -out terminals with no electronic cardholder data storage.
Not applicable to e-commerce channels.
B -IP* Merchants using only standalone, PTS -approved payment terminals with an IP
connection to the payment processor, with no electronic cardholder data storage.
Not applicable to e-commerce channels.
C -VT Merchants who manually enter a single transaction at a time via a keyboard into an
Intemet-based virtual terminal solution that is provided and hosted by a PCI DSS
validated third -party service provider. No electronic cardholder data storage.
Not applicable to e-commerce channels.
C Merchants with payment application systems connected to the Internet, no electronic
cardholder data storage.
` Not applicable to e-commerce channels.
P2PE-HW Merchants using only hardware payment terminals that are included in and managed via
a validated, PCI SSC-Iisted P2PE solution, with no electronic cardholder data storage.
Not applicable to e-commerce channels.
D SAQ D for Merchants: All merchants not included in descriptions for the above SAO
types.
SAQ D for Service Providers: All service providers defined by a payment brand as
eligible to complete a SAQ.
* New for PCI DSS v3.0
The intent of this document is to provide supplemental Information. Information provided here Page 1
does not replace or supersede PCI SSC Security Standards or their supporting documents.
® 2014-2015 PCI Security Standards Council, LLC. All Rights Reserved.
4X
X
N
D
N
C,
C
C.
r-
H
p
x
Q
a
rL
Q
LU
fY1
X
Xt
'
X
X=
W
X
7LA
X
X
j�
X
O
n
N
!C
>
0
X
X
X
LPI
a
3
X
X
x
♦\
X
X
x
4
N
a
X
M
Cl
Ui
X
O
fx
N
O
X
a
H
w
Lnrn
x
O
ii
Z
a
N
O
a
X
X
X
X
x
>5
?C
d
C_
IZ
Xr,
H
Q
x
X
LCL
uo7
X
O
!(
lD
fU
=1h
x
Ln
C>
H
.0
m
C_
2
V)
X
m
u,
u)
m
X
X
;;
x
O
Y
le
O
aTi
U
O
X
X
N
X
x
r-
x
5
x
O
Y
"
ne
u
O
O
X
p
X
X
Q
�mI
>
M
N
i.
y
"O
�'
.3
V
7
N
Ln
N
X
a
x
?t
X
�'
x
+'
r
CO
Q
C
X
'y
M
N
>
>>
x
>
f�
x
C
Ln
ell
x
N
X
fri
>
X
00
>
v
X
m
LU
a
C
m
rLyr
C.
C
O
ii
u
Q
-r-
a
a
N
fit
i
Un
H
N
ko 19
O
O
C4
LA
N
chi
O
o6
O
r4
t l
OH
-4
X
N
rn
N
r.
x
x
0
0
r -I
C3
N�
C3
ON
fn'
Ol
0 0
0
x
0,
1
p
M
x
x
fV
Ln�yj
X
X
Q
N
r0V
Ln
N
Ln
N
Ln
LnH
N
N
ul
F- F-
u1
F-
X
X
Ln
F-
O
l7
x
x
X
x
a
y�
x
N
U
x
X
dddd
F-
F-
F-
'f�
ddd
X
dF-
X
X
ri
u
x
�
,ct
en Ln
ri
O
o
C7
x
x
r 1
O
x
0
0
N
O
X
XLn
2'
X
N
j�
X
0
O
O
ri
O O
O
O
O
M
mLn
F
fl_
X
N
f:
X
N
N
N
C14
N
N
lQ7 C7
Q
Ln
0
Ln
(7
Ln
cD
0
Ln
Ln
d
LU
CO
N
X
N
X
a
F-
Ln
F-
Ln
F-
Ln
F-
L"
F -Ln
f0.1
�
F-
F-
F-
=
f)
O
Z
O
ddddd�
dtJaaor�
a,o
a
N
X.0
N
x
d
It
O
0
Ln
dCldeait
X
M
N
+�
rf)
X
fV
O
"q
O
O
H
O
-I
Q
H
N
H
X
0
rn '"I
H
N
N
CN
N
X
X
X
X
~
x
X
N
N
X
N
N
W
O
O
O
O
O
x
x
O 0
0
0
V'
0
l7
0
l7
X
X
X
x
x
X
X
X
a
Y
fU
rr
fvl
X
O
X
N
N
In
N
fn
N
fn
N
u1
N
fn
X
IN
N In
lIl
Vl
X
X
X
X
4J
O
Ln
1--
F-
F-
F-
I--
X
F- F-
F-
F-
F-
x
X
x
x
x
p
M
m
UN�fno�;fri
x
Lnx
�dddd[7
Ln
Xardddd
0
X
X
X
V)
p
ac
a)
1f
X
x
t
X
O
H
•0-1
O
m
O
N
O O
O
rV
�
qt
H
t
L
Y
Ld
>
tD
f�
X
W
O
O
H
H
H
[Y
M H
H
H
N
N
00
�
Ln
N
L
�
fL
p
N
ca
m
N
X
N
o
0
o
a
0
0
Q
C7
0
0
Z
O>
0
0
O._
v
a
,p
•L
Ln
Ln
V]
c
Ln
Ln
Ln
Ln
f11
Ln
r4
N Ln
v)
U1
Ln
Ln
T
T
p
Q
-
fll
f]'
>>
�
m
X
a
maoLL
a
a
o
z°���d��ararcfcfclar�c�c�
m
0
w
fY
V
CL
O
Z
c
LU
Z
a
X
X
a
X
Y
X
X
p
C
Ox
O
T
x
0
m
O.
f�
u
a
u
U
fy
Ln
Ln
OP
Ln
t
N
co`
6q
O
O
cq
0
C
N
'C
M
v
m
L
>
&.n
>
N
Ln
d
�
X
p¢
a
a
X
'u.
L
�
rn
nom.
O
G
a
T
L
L
fL
C
Q
O
a
-�
E
E
E
°
u
o
E
Z
z
Z
a
s
f6
U
to
CL
cc
fu
m
O
m
O
,n
CO
m
Z
m
�
i
p�
a
M
41
CELC
+�
'++
O
L
O
X
n
Z
w
O
z
p
U
2_
m
U.
Q
Q>
ry
a
w<
a
�Z
fi
M.
u.
A P2PE B B -1P C -VT C A -EP D-MERCH
PCI DSS Requirements v3.2
21 24 36 60 62 114 148 248
<---«< Number of Requirements to be Met for Compliance
Requirement 1: Install and maintain a firewall configuration to protect
Req -N Req -N Req -N Req -Y Req -Y Req -Y Req -Y Req -Y
cardholder data
No No No No No No Yes Yes
1.1 Establish and implement firewall and router configuration standards that include the following:
No No No No No No Yes Yes
1.1.1 A formal process for approving and testing all network connections and changes to the firewall
and router configurations
No No No Yes No No Yes Yes
1.1.2 Current network diagram that identifies all connections between the cardholder data environment
and other networks, including any wireless networks
No No No No No NO Yes Yes
1.1.3 Current diagram that shows all cardholder data flows across systems and networks
No No No Yes No No Yes Yes
1.1.4 Requirements for a firewall at each Internet connection and between any demilitarized zone
DM and the internal network zone
No No No No No No No Yes
1.1.5 Description of groups, roles, and responsibilities for management of network components
1.1.5 Documentation of business justification and approval for use of all services, protocols, and poAs
No No No Yes No No Yes Yes
allowed, including documentation of security features implemented for those protocols considered to
be insecure.
No No No No No No Yes Yes
1.1.7 Requirement to review firewall and router rule sets at least every six months
1.2 Build firewall and router configurations that restrict connections between untrusted networks and
any system components in the cardholder data environment.
No No No Yes Yes Yes Yes Yes
Note: An •untrusted network" is any network that is external to the networks belonging to the entity
Under review, and/or which is out of the enLAys ability to control or manage.
No No No Yes Yes Yes Yes Yes
1.2.1 Restrict inbound and outbound traffic to that which is necessary for the cardholder data
environment, andspecifically deny all other traffic.
No No No No Yes No Yes Yes
1.2.2 Secure and synchronize router configuration files.
1.2.3 Install perimeter firewalls between all wireless networks and the cardholder data environment,
No No No Yes No Yes Yes Yes
and configure these firewalls tc deny or, if traffic is necessary for business purposes, permit only
authorized traffic between the wireless environment and the cardholder data environment.
No No No Yes Yes Yes Yes Yes
rohibit direct public access between the Internet and any system component in the cardholder
environment.
No No No No No No Yes Yes
Implement a DMZ to limit inbound traffic to only system components that provide authorized
[data
cl accessible services, rotocols, and rts.
No No No No No No Yes Yes
Limit inbound Internet traffic to IP addresses wiRtin the DMZ.
Implement anti -spoofing measures to detect and block forged source IP addresses from entering
No No No Yes No No Yes Yes
etwork.
For example, block traffic originating from the Internet with an internal source address.
No NO No Yes Yes Yes Yes Yes
1.3.4 Do not allow unauthorized outbound traffic from the cardholder data environment to the Internet.
No No No Yes Yes Yes Yes Yes
1.3.5 Permit only'established' connections into the network.
No No No No No No No Yes
1.3.8 Place system components that store cardholder data (such as a database) in an internal network
zone, ser aced from the DMZ and other untrusted networks.
1.3.7 Do not disclose private IP addresses and routing information to unauthorized parties.
Note: Methods to obscure iP addressing may include, but are not limited to:
No No No No No No Yes Yes
• Network Address Translation (NAT}
. Placing servers containing cardholder data behind proxy servers/ffrewalls,
• Removal or filtering of route advertisements for private networks that employ registered addressing,
• Internal use of RFC1916 address space instead of registered addresses.
1.4 Install personal firewall software or equivalent functionality on any portable computing devices
(including company andfor employee -owned) that connect to the Internet when outside the network (for
example, laptops used by employees), and which are also used to access the CDE. Firewall (or
No No No No Yes No Yes Yes
equivalent) configurations include:
• Specific configuration settings are defined.
• Personal firewall (or equivalent functionality) is actively running.
• Personal firewall (or equivalent functionality) is not alterable by users of the portable computing
devices.
No No No No No No Yes Yes
1.5 Ensure that security policies and operational procedures for managing firewalls are documented,
in use, and known to all affected arties.
Requirement 2: Do not use vendor -supplied defaults for system passwords
Req -Y Req -N Req -N Req -Y Req -Y Req -Y Req -Y Req -Y
and other securityperameters
2.1 Always change vendor -supplied defaults and remove or disable unnecessary default accounts
before installing a system on the network.
Yes No No Yes Yes Yes Yes Yes
This applies to ALL default passwords, including but not limited to those used by operating systems,
software that provides security services, application and system accounts, point-of-sale (POS)
terminals, payment applications, Simple Network Management Protocol (SNMP) community strings,
etc.).
2.1.1 For wireless environments connected to the cardholder data environment or transmitting
No No No Yes Yes Yes No Yes
cardholder data, change ALL wireless vendor defaults at installation, including but not limited to
default wireless encryption keys, passwords, and SNMP community strings.
2.2 Develop configuration standards for all system components. Assure that these standards address
all known security vulnerabilities and are consistent with industry -accepted system hardening
standards.
No No No No No Yes Yes Yes
Sources of indusfry-accepted system hardening standards may include, but are not limited to:
• Center for Internet Security (CIS)
• International Organization for Standardization (ISO)
• SysAdmin Audit Network Security (SANS) Institute
• National Institute of Standards Technology (NIST).
A P2PE B B -IP C -VT C A -EP D-MERCH
PCI DSS Requirements 0.2
2.2.1 Implement only one primary function per server to prevent functions that require diHarent security
levels from co-exisling on the same server. (For example, web servers, database servers, and DNS
No No No No No Yes Yes Yes
should be implemented on separate servers.)
Note: Where virtualization technologies are in use, implement only one primary function per virtual
system component.
2.2.2 Enable only necessary services, protocols, daemons, etc., as required for the function of the
No No No No Yes Yes Yes Yes
system.
2.2.3 Implement additional security features for any required services, protocols, or daemons that are
No No No No Yes Yes Yes Yes
considered to be insecure.
Note: Where SSIJeady TLS is used, the requirements in AppendixA2 must be completed.
2.2.4 Configure system security parameters to prevent misuse.
No No No No Yes Yes Yes Yes
2.2.5 Remove all unnecessary functionality, such as scripts, driven:, features, subsystems, file
No No No No Yes Yes Yes Yes
systems, and unnecessary web servers.
2.3 Encrypt all non -console administrative access using strong cryptography.
No No No Yes Yes Yes Yes Yes
Note: Where SSUeady TLS is used the requirements in Appendix A2 must be completed,
No No No No NO No No Yes
24 Maintain an inventory of system components that are in scope for PCL DSS.
2.5 Ensure that security policies and operational procedures for managing vendor defaults and other
No No No No No Yes No Yes
securilvi parameters are documented, in use, and known to all affected parties.
2.13 Shared hosting providers must protect each entity's hosted environment and cardholder data.
No No No No No No No Yes
These providers must meet specific requirements as detailed in Appendix A 1: Additional PCI DSS
Requirements for Shared Having Providers.
Req -N Reg -Y Re -Y Re -Y Re -Y Req -Y Req -Y Re -Y
Re ulreme>1f 3: Protect stored cardholder data
3.1 Keep cardholder data storage to a minimum by implementing data retention and disposal policies,
procedures and processes that include at least the following for all cardholder data (CHO) storage:
• Umiling data storage amount and retention time to that which is required for legal, regulatory, and/or
business requirements
No Yes No No No No No Yes
Specific relention requirements for cardholder data
• Processes for secure deletion of data when no longer needed
• A quarterly process for identifying and securely deleting stored cardholder data that exceeds defined
retention.
3.2 Do not store sensitive authentication data after authorization (even if encrypted). If sensitive
authentication data is received, render all data unrecoverable upon completion of the authorization
process.
It is permissible for issuers and companies that support issuing services to store sensitive
No No Yes Yes Yes Yes Yes Yes
authentication data if:
• There is a business justification and
• The data is stored securely.
Sensitive authentication data includes the data as cited in the following Requirements 3.2.1 through
3.2.3:
3.2.1 Do riot store the full contents of any track (from the magnetic stripe located on the back of a card,
equivalent data contained on a chip, or elsewhere) after authorization. This data is alternatively called
full track, track, track 1, track 2, and magnetic -stripe data.
Note: In the normal course of business, the following data elements from the magnetic stripe may
No No Yes Yes No Yes No Yes
need to be retained:
• The cardholder's name
• Primary account number (PAN)
• Expiration date
• Service code
To minimize risk store only these data elements as needed for business.
3.2.2 Do not store the card verification code or value (three -digit or lour -digit number printed on the
No Yes Yes Yes Yes Yes Yes Yes
front or back of a payment card used to verify card -not -present transactions) after authorization.
3.2.3 Do riot store the personal identification number (PIN) or the encrypted PIN block after
No No Yes Yes Yes Yes Yes Yes
authorization.
3.3 Mask PAN when displayed (the first six and last four digits are the maximum number of digits to be
displayed), such that only personnel with a legitimate business need can see more than the first
snxilast four digits of the PAN.
No No Yes Yes Yes Yes No Yes
Note: This requirement does not supersede stricter requirements in place for displays of cardholder
data—for example, legal or payment card brand requirements for pointolsale (POS) receipts.
3.4 Render PAN unreadable anywhere it is stored (including on portable digital media, backup media,
and in togs) by using any of the following approaches:
• One-way hashes based on strong cryptography, (hash must be of the entire PAN)
• Truncation (hashing cannot be used to replace the truncated segment of PAN)
+ Index tokens and pads (pads must be securely stored)
Strong cryptography with associated key -management processes and procedures.
No No No No No No No Yes
Note. It is a relatively trivial effort fora malicious individual to reconstruct original PAN data if they
have access to both the truncated and hashed version of a PAN. Where hashed and truncated
versions of the same PAN are present in an entity's environment, additional controls must be in place
to ensure that the hashed and truncated versions cannot be correlated to reconstnrct the original PAN.
3.4.1 It disk encryption is used (rather than file- or column -level database encryption), logical access
must be managed separately and independently of native operating system authentication and access
control mechanisms (for example, by not using local user account databases or general network login
credentials). Decryption keys must not be associated with user accounts.
No No No No No No No Yes
Note: This requirement applies in addition to all other PCi DSS encryption and key -management
requirements.
A P2PE B 8-IP C-VT C A-EP D-MERCH
PCI DSS Re uirements v3.2
3.5 Document and implement procedures to protect keys used to secure stored cardholder data
against disclosure and misuse:
No No No No No No No Yes
Note: This requirement applies to keys used to encrypt stored cardhofderdata, and also applies to
key-encrypting keys used to protect data-encrypting keys such key-encrypling keys must be at feast
as strong as the dala-enctyptingi key.
3.S.i Additional requirement for service providers only: Maintain a documented description of
the cryptographic architecture that Includes:
• Details of all algorithms, protocols, and keys used for the protection of cardholder data, including key
strength and expiry date
No No No No No No No Yes
• Description of the key usage for each key.
• Inventory of any HSMs and other SCDs used for key management
Note: This requirement is a best practice until January 31, 2018, after which it becomes a
Le uirement.
No No No No No No No Yes
3.5.2 Restdcl access to cryptographic keys to the fewest number of custodians necessary.
3.5.3 Store secret and private keys used to encrypUdecrypi cardholder data in one (or more) of the
following forms at all times:
• Encrypted with a key-encrypting key that is at least as strong as the data-encrypting key, and that is
stored separately from the data-encrypting key
No No No No No No No Yes
• within a secure cryptographic device (such as a hardware (host) security module (HSM) or PTS-
approved point-of-interaclion device)
• As at least two full-length key components or key shares, in accordance with an industry-acmpted
method
Note: 11 is not required that public keys be stored in one of these forms.
3.5.4 Store cryptographic keys in the fewest possible locations.
No No No No No No No Yes
3.6 Fully document and implement all key-management processes and procedures for cryptographic
keys used for encryption of cardholder data, including the following:
No No No No No No No Yes
Note: Numerous industry standards for key management are available from various resources
includin NIST, which can be found at h y/csrc.rtrst. ov.
No No No No No No No Yes
3.6.1 Generation of strong cryptographic keys
No No No No No No No Yes
3.5.2 Secure cryptographic key distribution
No No No No No No No Yes
3.5.3 Secure cryptographic key storage
3.6.4 Cryptographic key changes for keys that have reached the end of their cryptoperiod (for
example, after a defined period of time has passed and/or after a certain amount of cipher-text has
No No No No No No No Yes
been produced by a given key), as defined by the associated application vendor or key owner, and
based on industry best practices and guidelines (for example, NIST Special Publication 800.57).
3.6.5 Retirement or replacement (for example, archiving, destruction, and/or revocation) of keys as
deemed necessary when the integrily of the key has been weakened (for example, departure of an
employee with knowledge of a clear-text key component), or keys are suspected of being
No No No No No No No Yes
compromised.
Note: it retired or replaced cryptographic keys need to be retained, these keys must be securely
archived (for exampfe, by using a key-encryption key). Archived cryptographic keys should only be
used for decryptionlyefirtation purposes.
3.6.8 If manual clear-text cryptographic key-management operations are used, these operations must
be managed using split knowledge and dual control.
No No No No No No No Yes
Note: Examples of manual key-management operations include, but are not limited to: key
generation, transmission, loading, storage and destruction.
No No No No No No No Yes
3.8.7 Prevention of unaulhorized substitution of cryptographic keys.
No No No No No No No Yes
3.8.8 Requirement for cryptographic key custodians to formally acknowledge that they understand and
accept their key-custodian responsibilities.
No Yes NO No No No No Yes
3.7 Ensure that security policies and operational procedures for protecting stored cardholder data are
documented, in use and known to all affected parties.
Req-N Req-N Req-Y Req-Y Req-Y Req-Y Req-Y Req-Y
Requirement 4: Encrypt transmisslon of cardholder data across open, public
networks
4.1 Use strong cryptography and security protocols to safeguard sensitive cardholder data during
transmission over open, public networks, including the following:
• Only misted keys and certificates are accepted.
• The protocol in Lisa only supports secure versions or configurations.
• The encryption strength is appropriate for the encryption methodology in use.
Note: Where SSUeady TLS is used, the requirements in Appendix A2 must be completed.
No No No Yes Yes Yes Yes Yes
Examples of open, public networks include but are not limited to:
• The Internet
• Wireless technologies, including 802.1 Y and Bluetooth
• Cellular technologies, for example, Global System for Mobile communications (GSM), Code drosion
mult-0ple access (CDMA)
• General Packet Radio Service (GPRS).
• Satellite communications.
4.1.1 Ensure wireless networks transmitting cardholder data or connected to the cardholder data
No No No Yes Yes Yes No Yes
environment, use industry best practices to implement strong encryption for authentication and
transmission.
No No Yes Yes Yes Yes Yes Yes
4.2 Never send unprotected PANS by end-user messaging technologies (for example, e-mail, instant
messaging. SMS. chat, etc.).
No No No No No No Yes Yes
4.3 Ensure that security policies and operational procedures for encrypting transmissions of cardholder
data are documented, in use and known to all affected parties.
Req-N Req-N Req-N Req-N Req-Y Req-Y Req-Y Req-Y
Requirement 5. Use and regularly update anti-virus software or programs
No No No No Yes Yes Yes Yes
5.1 Deploy anti-virus software on all systems commonly affected by malicious software (particularly
rsonal computers and servers).
A P2PE B B -IP C -VT C A -EP D-MERCH
PCI DSS Requirements 0.2
No No No No Yes Yes Yes Yes
5.1.1 Ensure that anti-virus programs are capable of detecting, removing, and protecting against all
known types of malicious software.
5.1.2 For systems considered to be not commonly affected by malicious software, perform periodic
No No No No Yes Yes Yes Yes
evaluations to identify and evaluate evolving malware threats in order to confirm whether such
systems continue to not require anti-virus software.
5.2 Ensure that all anti-virus mechanisms are maintained as follows:
No No No No Yes Yes Yes Yes
• Are kept current,
• Perform periodic scans
• Generate audit logs which are retained per PCI DSS Requirement 10.7.
5.3 Ensure that anti-virus mechanisms are actively running and cannot be disabled or altered by users,
unless specifically authorized by management on a case-by-case basis for a limited time period.
Note: Anti-virus solutions may be temporarily disabled only if there is legitimate technical need, as
No No No No Yes Yes Yes Yes
authorized by management on a case-by-case basis. If anti-nrus protection needs to be disabled for a
specific purpose, if must be formally authorized. Additional secunly measures may also need to be
implemented for the period of time during which anti-virus protection is not active.
No No No No NO NO Yes Yes
5.4 Ensure that security policies and operational procedures for protecting systems against malware
are documented, in use, and known to all affected parties.
Req -N Req -N Re -N Req -Y Re -Y Re -Y Re -Y Req -Y
Requirement B: Develop and maintain secure systems and ap llcatirons
6.1 Establish a process to identify security vulnerabilities, using reputable outside sources for security
vulnerability information, and assign a risk ranking (for example, as "high," "medium," or "low) to newly
discovered security vulnerabilities.
Note: Risk rankings should be based on industry best practices as well as consideration of potential
impact. For example, criteria for ranking vulnerabilities may include consideration of the CUSS base
score, and/or the classification by the vendor, and/or type of systems affected.
No No No Yes Yes Yes Yes Yes
Methods for evaluating vulnerabilities and assigning risk ratings will vary based on an organization's
environment and risk -assessment strategy. Risk rankings should, at a minimum, identify all
vulnerabilities considered to be a high risk' to the environment. In addition to the risk ranking,
vulnerabilities may be considered critical -if they pose an imminent threat to the environment, impact
critical systems, and/or would result in a potential compromise if not addressed. Examples of critical
systems may include secunly systems, publle, facing devices and systems, databases, and other
systems that store, process, or transmit cardholder data.
6.2 Ensure that all system components and software are protected from known vulnerabilities by
installing applicable vendor -supplied security patches. Install critical security patches within one month
No No No Yes Yes Yes Yes Yes
of release.
Note: Critical security patches should be identified according to the risk ranking process defined in
Requirement 6.1.
6.3 Develop internal and exlemal software applications (including web -based administrative access to
applications) securely, as follows:
• In accordance with PCI DSS (for example, secure authentication and logging)
No No NO No No No No Yes
Based on industry standards and/or best practices.
• Incorporating infomlation security throughout the software -development life cycle
Note: This applies to all software developed internally as well as bespoke or custom software
developed by a third
No No NO No No No No Yes
6.3.1 Remove development, test and/or custom application accounts, user IDs, and passwords before
applications become active or are released to customers.
6.3.2 Review custom code prior to release to production or customers in order to identify any potential
voding vulnerability (using either manual or automated processes) to include at least the following:
• Code changes are reviewed by individuals other than the originating code author, and by individuals
knowledgeable about code -review techniques and secure coding practices.
• Code reviews ensure code is developed according to secure coding guidelines
• Appropriate corrections are implemented prior to release.
No No No No No No No Yes
• Code -review results are reviewed and approved by management prior to release.
Note: This requirement for code reviews applies to all custom code (both internal and public -facing),
as part of the system development life cycle. Code reviews can be conducted by knowledgeable
krtemal personnel or third parties. Public -facing web applications are also subject to additional
controls, to address ongoing threats and vulnerabilities after implementation, as delrned at PCI DSS
Requirement 6.6.
No No No No No No No Yes
6.4 Follow change control processes and procedures for all changes to system components. The
processes must include the followi
No No No No No NO No Yes
6.4.1 Separate developmentAest environments from production environments, and enforce the
separation with access controls.
8.4.2 Separation of duties between developmentltest and production environments
No No No No No No No Yes
No No No No No No NO Yes
6.4.3 Production data (live PANS) are not used for testing or development
No No No No No No No Yes
8.4.4 Removal of test data and accounts from system components before the system becomes
aclivelgloes into production.
8.4.5 Change control procedures must include the following:
No No No No No No Yes Yes
No No No No No No Yes Yes
8.4.5.1 Documentation of impact.
No No No No No No Yes Yes
6A.5.2 Documented change approval by authorized parties.
No No No No No No Yes Yes
6A.5.3 Functionality testing to verify that the change does not adversely impact the security of the
system.
GAZA Back -out procedures.
No No No No No No Yes Yes
A
P2PE
B
B -IP
C -VT
C
A -EP
D-MERCH
PCI DSS Requirements v3.2
6.4.6 Upon completion of a significant change, all relevant PCI DSS requirements must be
implemented on all now or changed systems and networks, and documentation updated as applicable.
Kl
%C,
No
No
No
Yes
Yes
Yes
Note: This requirement is a best practice until January 31, 2018, after which it becomes a
requirement.
6.5 Address common coding vulnerabilities in software -development processes as follows:
• Train developers at least annually in up-to-date secure coding techniques, including how to avoid
common coding vulnerabilities.
• Develop applications based on secure coding guidelines.
No
No
No
No
No
No
Yes
Yes
Note: The vulnerabilities fisted at 6.5.1 through 6.5. 10 were current with industry best practices when
this version of PCl DSS was published. However, as industry best practices lar vulnerability
management are updated (for example, the OWASP Guide, SANS CWE Top 25, CERT Secure
Coding, etc.), the current best practices must be used for these requirements.
Note
Note
Note
Note
Note
Note
Note
Note
Note: Requirements 6.5. f through 6.5.6, below, apply to all applications (internal or external).
No
No
No
No
No
No
Yes
Yes
6.5.1 Injection flaws, particularly SQL injection. Also consider OS Command Injection, LDAP and
XPalh injection flaws as well as other i, -'action flaws.
No
No
No
No
No
No
Yes
Yes
6.5.2 Buffer overflows
No
No
No
No
No
No
No
Yes
6.5.3 Insecure cryptographic storage
No
No
No
No
No
No
Yes
Yes
6.5.4 Insecure communications
No
No
No
No
No
No
Yes
Yes
6.5.5 Improper error handling
6.5.6 All "high risk* vulnerabilities identified in the vulnerability ident ficalion process (as defined in PCI
No
No
No
No
No
No
Yes
Yes
DSS Requirement 6.1),
Note: Requirements 6.5.7 through 6.5. 10, berow, apply to web applications and application interfaces
Note
Note
Note
Note
Note
Note
Note
Note
(internal or external):
No
No
No
No
No
No
Yes
Yes
6.5.7 Cross -site scripting (XSS)
No
No
No
No
No
No
Yes
Yes
6.5.6 Improper access oontrol (such as insecure direct object references, fail. re to restrict UAL
access, directo traversal, and failure to restrict user access to functionsi.
No
No
No
No
No
No
Yes
Yes
5.5.9 Crass -site request forgery (CSRF)
No
No
No
No
No
No
Yes
Yes
6.5.10 Broken authentication and session management
6.6 For public -facing web applications, address new threats and vulnerabilities on an ongoing bass
and ensure these applications are protected against known attacks by either of the following methods:
• Reviewing public -facing web applications via manual or automated appl cation vul^erabilily security
assessment tools or methods, at least annually and after any changes
Note: This assessment is not the same as the vulnerebirity scans performed for Requirement 11.2
Nn
N
N6
No
No
No
Yes
Yes
• Installing an automated technical solution that detects and prevents web. based attacks (for example,
a web -application firewall) in front of public -facing web applications. I, i 4onlinually check all traffic.
No
No
No
No
No
No
Yes
Yes
6.7 Ensure that security polii:ie; and operations procedures for developing and maintaining secure
s ;terns and applications are documented in use, and known to all affected parties.
Req -N
Req -N
Req -Y
Req -Y
Req -Y
Req -Y
Req -Y
Req -Y
Requirement 7: Restrict access to cardholder data by business need to know
No
No
Yes
No
Yes
Yes
Yes
Yes
7.1 Limit access to system components and cardholder data to only those individuals whose job
requires such access.
7.1.1 Define access needs for each role, including:
No
No
No
No
No
Na
No
Yes
• System components and data resources that each role needs to access for their job function
• Level of privi ego required (for example, user, administrator, etc.) for accessing resources.
No
No
Yes
Yes
Yes
Yes
Yes
Yes
7.1.2 Restrict access to privileged user IDs to least privileges necessary to perform job
responsibilities.
No
No
Yes
Yes
Yes
Yes
Yes
Yes
7.1.3 Assign access based on individual personnel's job classification and function.
No
No
No
No
No
No
Yes
Yes
7.1.4 Require documented approval by authorized parties specifying required privileges.
7.2 Establish an access control system(s) for systems components that restricts access based on a
No
No
No
No
No
No
No
Yes
users need to know, and is set to deny all" unless specifically allowed.
This access controls tem s must include the followi :
No
No
No
No
No
No
No
Yes
7.2.1 Coverage of all system components
No
No
No
No
No
No
No
Yes
7.2.2 Assignment of privileges to individuals based on job classification and function.
No
No
No
No
No
No
No
Yes
7.2.3 Default deny -a6" setting
No
No
No
No
No
No
No
Yes
7.3 Ensure that security po ides and operational procedures for restricting access to cardholder data
are documented. in use. and known to all affected parties.
Req -Y
Req -N
Req -N
Req -Y
Req -Y
Req -Y
Req -Y
Req -Y
Requirement 8: Assign a unique ID to each person with computer access
6.1 Define and implement policies and procedures to ensure proper user identification management
Yes
No
No
No
No
Yes
Yes
Yes
for non -consumer users and administratom on all system components as follows:
No
No
No
No
Yes
Yes
Yes
Yes5'1'1
Assign all users a unique ID before allowing them to access system components or cardholder
data.
No
No
No
No
No
No
Yes
Yes
6.1.2 Control addition, deletion, and modification of user IDs, credentials, and other identifier objects.
Yes
No
No
No
Yes
No
Yes
Yes
6.1.3 Immediately revoke arta;; for any terminated users.
No
No
No
No
No
No
Yes
Yes
6.1.4 Removeldisable inactive user accounts within 90 days.
5.1.5 Manage IDs used by third parties to access, support, or maintain system components via remote
No
No
No
Yes
No
Yes
Yes
Yes
access as follows:
• Enabled only during the time period needed and disabled when not in use.
• Monitored when in use.
A P2PE B B -IP C -VT C A -EP D-MERCH
PCI DSS Requirements 0.2
8.1.8 Umit repeated access attempts by locking out the user ID after not more than six attempts.
No No No No No Yes Yes Yes
8.1.7 Set The lockout duration to a minimum of 30 minutes or until an administrator enables the user
No No No No NO Yes Yes Yes
ID.
8.1.8 If a session has been idle for more than 15 minutes, require the user to re-authenlicate to re-
No No No No No Yes Yes Yes
activate the terminal or session.
8.2 In addition to assigning a unique ID, ensure proper user -authentication management for non-
consumer users and administrators on all system components by employing at least one of the
Yes No No No Yes Yes Yes Yes
following methods to authenticate all users:
• Something you know, such as a password or passphrase
• Something you have, such as a token device OF smart card
• Something u are, such as a biometric.
8.2.1 Using strong cryptography, render all authentication credentials (such as passwords/phrases)
No No No No No No Yes Yes
unreadable during transmission and storage on all system components.
8.2.2 Verify user identity before modifying any authentication credential—for example, performing
No No No No No No Yes Yes
password resets, provisioning new tokens, or generating new keys.
8.2.3 Passwords/passphrases must meet the following:
• Require a minimum length of at least seven characters.
Yes No No No Yes Yes Yes Yes
• Contain both numeric and alphabetic characters.
Alternatively, the passwords/passphrases must have complexity and strength at least equivalent to the
parameters specified above.
8.2.4 Change user passwordslpassphrases at least once every 90 days.
No No No No No Yes Yes Yes
8.2.5 Do not allow an individual to submit a new passwordlpassphrase that is the same as any of the
No No No No No Yes Yes Yes
last four asswords/ ass hrases he or she has used.
8.2.8 Set passwords/passphrases for first-time use and upon reset to a unique value for each user,
No No No No No Yes Yes Yes
and change immediately after the first use.
8.3 Secure all individual non -console administrative access and all remote access to the CDE using
multi -factor authentication.
No No No Yes No Yes Yes Yes
Note: Muni -factor authentication requires that a minimum of two of the three authentication methods
(see Requirement 8.2 for descriptions of authentication methods) be used for authentication. Using
one factor twice (for example, using two separate passwords) is not considered multi -factor
authentication.
8.3.1 Incorporate multi -factor authentication for all non -console access into the CDE for personnel with
administrative access.
No No No No No Yes Yes Yes
Note: This requirement is a best practice unid January 31, 2018, after which it becomes a
requirement.
8.3.2 Incorporate multi -factor authentication for all remote network access (both user and
No No No Yes No Yes Yes Yes
administrator, and including third party access for support or maintenance) originating from outside the
entity's network.
8.4 Document and cammunicate authentication policies and procedures V, all users including:
• Guidance on selecting strong authentication credentials
• Guidance for how users should protect their authentication credentials
No No No No No Yes Yes Yes
• Instructions not to reuse previously used passwords
• Instructions to change passwords it there is any suspicion the password could be compromised.
8.5 Do not use group, shared, or generic IDs, passwords. or other authentication methods as follows:
• Generic user IDs are disabled or removed.
Yes No No Yes Yes Yes Yes Yes
Shared user IDs do not exist for system administration and other critical funct ens
• Shared and generic user IDs are not used to administer any system components.
8.5.1 Additional requirement for service providers only: Service providers with remote access to
customer premises (for example, for support of POS systems or servers) must use a unique
authentication credential (such as a password/phrase} for each customer.
No Na No No No No Na Yes
Note: This requirement is not intended to apply to shared hosting providers accessing their own
hosting environment, where multiple customer environments are hosted.
8.8 Where other authentication mechanisms are used Ifor example, physical or logica security tokens,
smart cards, certificates, etc.), use of these mechanism* must be assigned as follows.
No No No No No No Yes Yes
• Authent cation mechanisms must be assigned to ars nd:vidual account and not shared among
multiple accounts.
• Physical and/or logical controls must be in place to e. .,ure only the intended account can use that
mechanism to gain access.
8.7 All access to any database containing cardholder data (inc uding access by appli cat ons,
administrators, and at' other users) is restricted as fol-ows'
• All user access to, user queries of, and user adians on databases are through programmatic
NO No No No NO No No Yes
methods.
• Only database administrators have the ability to directly access or query databases.
• Application IDs for database applications can only be used by the applications (and not by individual
users or other non -application processes).
8.8 Ensure that security policies and operational procedures for denlificaTion and authentication are
No No No No NO Yes Yes Yes
documented, in use, aril known to all affected parties.
Re -Y Re -Y Re -Y Req -Y Req -Y Re -Y Re -Y Re -Y
Regtrlrement 9: Restrict ph alcal access to cardholder data
9.1 Use appropriate facility entry controls to limit and monitor physical access to systems in the
No No No No Yes Yes Yes Yes
cardholder data environment.
A P2PE B B-IP C-VT C A-EP D-MERCH
PCI DSS Requirements v3.2
9.1.1 Use either video cameras or access control mechanisms (or both) to monitor individual physical
access to sensitive areas. Review collected data and correlate with other entries. Store for at least
three months, unless otherwise restricted by law.
No No No No No Yes No Yes
Note: "Sensitive areas' refers to any data center, server room or any area that houses systems that
store, process, or transmit cardholder data. This excludes public-facing areas whew only point-of-sale
terminals are present, such as the cashier areas in a relaid store.
9.1.2 Implement physical and/or logical controls to restrict access to publicly accessible network jacks.
For example, network jacks located in public areas and areas accessible to visitors could be disabled
No No No Yes No Yes No Yes
and only enabled when network access is explicitly authorized. Alternatively, processes could be
implemented to ensure that visitors are escorted at all limes in areas with active network jacks
No No No No No No No Yes
9.1.3 Restrict physical access to wireless access points, gateways, handheld devices,
networking/communications hardware, and telecommunication I Ines
9.2 Develop procedures to easily distinguish between onsile personnel and visitor:, to include:
• Identifying Onsite personnel and visitors (for example, assigning badges)
No No No No No No No Yes
• Changes to access requirements
• Revoking or terminating onsile personnel and expired visitor identification (such as ID badges).
9.3 Control physical access for onsite personnel to sensitive areas as follows:
No No No No No No No Yes
• Access must be authorized and based on individual job function.
• Access is revoked immediately upon termination, and all physical access mechanisms, such as
keys, access cards, etc., are returned or disabled.
No No No No No No No Yes
9.4 Implement procedures to identify and authorize visitors.
Procedures should include the follovd :
No No No No No No No Yes
9.4.1 Visitors are authorized before entering, and escorted at all times within, areas where cardholder
data is processed or maintained.
No No No No No No Na Yes
9 .4.2 Visitors are identified and given a badge or other.denfification that expires and that vis bly
disli wishes the visitors from onsite personnel.
No No No No No No No Yes
9.4.3 Visitors are asked to surrender the badge or identification before leaving the facility or at the dale
ofexpiration.
9.4.4 A visitor log is used to maintain a physical audit trail of visitor activity to the facility as well as
computer rooms and data centers where cardholder data is stored or transmitted.
No No No No No No No Yes
Document the visitors name, the firm represented, and the onsite personnel authorizing physical
access on the log.
Retain this log for a minimum of three months, unless otherwise restricted by law.
Yes Yes Yes Yes Yes Yes Yes YesI.11owing:
5 Physically secure all media.
5.1 Store media backups in a secure location, preferably an off-site facility such as an alternate or
No No No No No No No Yes
m
ackup site, or a comer hal storage facility. Review the localicd's security at least annually.
Yes No Yes Yes Yes Yes Yes Yes
$ Maintain strict control over the inlemal or external distribution of any kind of media, including the
Yes No Yes Yes Yes Yes Yes Yes
9.8.1 Ctassity media so the sensitivity of the data can be determined.
Yes No Yes Yes Yes Yes Yes Yes
9.8.2 Send the media by secured courier or other delivery method that can be accurately tracked.
Yes No Yes Yes Yes Yes Yes Yes
9.8.3 Ensure management approves any and all media that is moved from a secured area (including
when media is distributed to individuals).
Yes No Yes Yes Yes Yes Yes Yes
9.7 Maintain strict control over the storage and accessibility of media.
No NO No No No No No Yes
9.7.1 Property maintain inventory logs of all media and conduct media inventories at least annually.
Yes Yes Yes Yes Yes Yes Yes Yes
9.8 Destroy media when it is no longer needed for business or legal reasons as follows:
Yes Yes Yes Yes Yes Yes Yes Yes
9.8.1 Shred, incinerate, or pulp hard-copy materials so that cardholder data cannot be reconstructed.
Secure storage containers used for materials that are to be clastic d.
9.8.2 Render cardholder data on electronic media unrecoverable so that cardholder data cannot be
reconstructed.
No No No No No No No Yes
9.9 Protect devices that capture payment card data via direct physical interaction with the card from
tampering and substitution.
No Yes Yes Yes No Yes No Yes
Note: These requirements apply to card-reading devices used in card present transactions (that kis,
card swipe or dip) at the point of sale. This requirement is not untended to apply to manual key-entry
convonerits such as computer keyboards and POS keypads.
9.9.1 Maintain an up-to-date list of devices. The list should include the following:
• Make, model of device
No Yes Yes Yes No Yes No Yes
- Location of device (for example, the address of the site or facility where the device is located)
• Device serial number or other method of unique identification.
9.9.2 Periodically inspect device surfaces to detect tampering (for example, addition of card skimmers
to devices), or substitution (for example, by checking the serial number or other device characteristics
to verify it has not been swapped with a fraudulent device).
No Yes Yes Yes No Yes No Yes
Note: Exarrlples of signs that a device might have been tampered with or substituted include
unexpected attachments or cables plugged unto the device, missing or changed security labels, broken
or differently colored casing, or changes to the serial number or other external markings.
9.9.3 Provide training for personnel to be aware of attempted tampering or replacement of devices.
Training should include the following:
- Verify the identity of any third-pally persons claiming to be repair or maintenance personnel, prior to
granting them access to modify or troubleshoot devices.
No Yes Yes Yes No Yes No Yes
• Do not install, replace, or return devices without verification.
• Be aware of suspicious behavior around devices (for example, attempts by unknown persons to
unplug or open devices).
• Report suspicious behavior and indications of device tampering or substitution to appropriate
personnel (for example, to a M92!Lar or security officer).
9.10 Ensure that security policies and operational procedures for restricting physical access to
cardholder data are documented, in use, and known to all affected parties.
No Yes No Na Na No No Yes
A
P2PE
B
B -IP
C -VT
C
A -EP
D-MERCH
PCI DSS Requirements v3.2
Req -N
Req -N
Req -N
Req -N
Req -N
Req -Y
Req -Y
Req Y
Requirement 10: Track and monitor all access to network resources and
cardholder data
No
No
No
No
No
No
Yes
Yes
10.1 Implement audit trails to ink all access to system components to each individual user.
No
No
No
No
No
Yes
Yes
Yes
10.2 Implement automated audit trails for all system components to reconstruct the following sverhs:
No
No
No
No
No
No
No
Yes
10.2.1 All individual user accesses to cardholder data
No
No
No
NO
NO
Yes
Yes
Yes
10.2.2 All actions taken by any individual with root or adminisirat ve privileges
No
No
No
No
No
No
Yes
Yes
10.2.3 Access to all audit trails
No
No
No
No
No
Yes
Yes
Yes
10.2.4 Invalid logical access attempts
10.2.5 Use of and changes to identification and authentication mechanisms--�incfuding but not limited
No
No
No
No
No
Yes
Yes
Yes
to creation of new ac¢ounls and elevation of privileges—and all changes, additions, or deletions to
accounts with root or administrative privileges
No
No
No
No
No
No
Yes
Yes
10.2.6 Initialization, stopping, or pausing of the audit ogs
10.2.7 Creation and deletion of system -level objects
No No No No No No Yes Yes
No
No
No
No
No
Yes
Yes
Yes
10.3 Record at least the following audit trail entries for all system components for each event:
No
No
No
No
No
Yes
Yes
Yes
10.3.1 User identification
10.3.2 Type of event
No
No
No
No
No
Yes
Yes
Yes
10.3.3 Date and time
No
No
No
No
No
Yes
Yes
Yes
10.3.4 Success or fa lure indication
No
No
No
No
No
Yes
Yes
Yes
10.3.5 Origination of event
No No No No No Yes Yes Yes
No
No
No
No
No
Yes
Yes
Yes
10.3.6 Identity or name of affected data, system component or resource.
10.4 Using time -synchronization technology, synchronize all critical system clocks and times and
No
No
No
No
No
No
Yes
Yes
ensure that the following is implemented for acquiring, distributing, and storing lime.
Note: One example of time synchronization tectindbov is Network Time Protocol NTP .
No
No
No
No
No
No
Yes
Yes
10AA Crit cat systems have the correct and consistent t me
No
No
No
No
No
No
Yes
Yes
10.4.2 Time data is protected.
No
No
No
No
No
No
Yes
Yes
10.4.3 Time sett ngs are received fromindustry-accepted lime sources.
No
No
No
No
No
No
Yes
Yes
10.5 Secure audit trails so they cannot be altered
No
No
No
No
No
No
Yes
Ye.-
10.5.1 Limit viewing of audit trails to those with a job-reiated need.
No
No
No
No
No
No
Yes
Yes
10.5.2 Protect audit trail files from unauthorized mod fications.
No
No
No
No
No
No
Yes
Yes
10.5.3 Promptly back up audit trail files to a centralized log server or media that is difficult to alter.
No
No
No
No
No
No
Yes
Yes
10.5.4 Write logs fcr external faang ter/' -L fogies ora:) a :;m-ure, central'zed, internal log server or
media device.
10.5.5 Use file -integrity monitoring or change -detection software on logs to ensure that existing log
No
No
No
No
No
No
Yes
Yes
data cannot be changed without generating a arts (although new data being added should not cause
an alert).
10.6 Review logs and security events for all system components to identify anomalies or suspicious
No
No
NO
No
No
Yes
Yes
Yes
activity.
Note. Log harvesting. parsing, and alerting tools may be used to meet this Requirement.
10.6.1 Review the following at least daily:
• All security events
• Lags of all system components that store, process, or transmit CHD and/or SAD
No
No
No
No
No
Yes
Yes
Yes
• Logs of all critical system components
• Logs of all servers and system components that perform security functions (for example, firewalls,
intrusion -detection systernsfintrusion-prevention systems (IDSAPS), authentication servers, e-
commerce redirection servers, etc.).
10.6.2 Review logs of all other system components periodically based on the organization's policies
No
No
No
No
No
Yes
Yes
Yes
and risk management strategy. as determined by the organization's annual risk assessment.
No
No
No
No
No
Yes
Yes
Yes
10.6.3 Follow up exceptions and anomalies identified during the review process.
No
No
No
No
No
Yes
Yes
Yes
10.7 Retain audit trail history for at least one year, with a minimum of three months immediately
available for anal sis for example, online, archived, or restorable from backup).
10.8 Additional requirement for service providers only: Implement a prooess for the timely
detection and reporting of failures of critical security control systems, including but not lim'ted to failure
of:
• Firewalls
• IDSIIPS
• FIM
No
No
No
No
No
No
No
No
• Anti-virus
. Physical access controls
• Logical access controls
• Audit logging mechanisms
• Segmentation controls (it used)
Note: This requirement is a best practice unid January 31, 2018, after which d becomes a
requirement
A WE B B -IP C -VT C A -EP D-MERCH
PCI DSS Requirements 0.2
10.9.1 Additional requirement for service providers only: Respond to failures of any critical
security controls in a timely manner. Processes for responding to failures in security controls must
include:
• Restoring security functions
• Identifying and documenting the duration (date and time start to end) of the security failure
• Identifying and documenting cause(s) of failure, Including root cause, and documenting remediation
required to address root cause
No No No No No No No No
• Identifying and addressing any security issues that arose during the failure
• Performing a risk assessment to determine whether further actions are required as a result of the
security failure
• Implementing controls to prevent cause of fat ure from reoccurring
• Resuming monitoring of security controls
Note: This requirement is a best practice until January 31, 2018, after which it becomes a
requirement.
10.9 Ensure that security policies and operational procedures for monitoring all access to network
No No No No No No No Yes
resources and cardholder data are documented, in use, and known to all affected parties.
Req -N Rec-N Req -N Re -Y Req -N Req -Y ReQ-Y Rei -Y
Requirement 11: Regularty test security systems and processes
11.1 Implement processes to test for the presence of wireless access points (802.11) and detect and
identify all authorized and unaulhonzed wire. ess access pa: nus on a quarterly basis.
No No No No No Yes No Yes
Note: Methods that may be used in the process include but are not limited to wireless network scans,
physicaftical inspections of system components and infrastructure, network access control (NAC),
or wireless )DWS. Whichever methods are used, they must be suftrcient to defect and identify both
authorized and unauthorized devices.
No No No No No Yes No Yes
11.1.1 Maintain an inventory of authorized wireless access points including a documented business
ustification.
No No No No No Yes No Yes
11.1.2 Implement incident response procedures In the event unauthorized wireless access points are
detected.
11.2 Run internal and external network vulnerability scans at least quarterly and after any significant
change In the network (such as new system component i natal ations, changes i n network topology,
firewall rule modifications, product upgrades).
Note: Multiple scan reports car be combined for the quarterly scan process to show that all systems
were scanned and all applicable vulnerabilities have been addressed. Additional documentation may
be required to verity non-remediated vulnerabilities are in the process of being addressed.
No No No No No Yes No Yes
For initial PCI OSS compliance, it is nc t required that four quarters of passing scans be completed if
the assessor verifies 1) the most recent scan result was a passing scan, 2) the entity has documented
policies and procedures requinng quarterly scanning, and 3) vulnerabdities noted in the scan results
have been corrected as shown in a ra-scan(s). For subsequent years after the initial PC/ OSS review,
four quarters of passing scans must have occurred.
11.2.1 Perform quarterly internal vulnerability scans. Address vulnerabilities and perform rescan to
No No No No No Yes No Yes
verify all `high risk" vulnerabilities are resolved in accordance with the entity's vulnerability ranking (pe
Requirement 6.1). Scans must be performed by qualified personnel.
11.2.2 Perform quarterly external vulnerability scans, via an Approved Scanning Vendor (ASV)
approved by the Payment Card Industry Security Standards Council (PCI SSC). Perform rescan as
needed, until passing scans are achieved.
No No No Yes No Yes Yes Yes
Nota: Quarterly axtamal vulnerability scans must be performed by an Approved Scanning Vendor
(ASV), approved by the Payment Card industry Security Standards Councif (PCI SSC). Refer to the
ASV Program Guide published on the PC! SSC website for scan customer responsibilities, scan
nr,ration. etc.
No No No No No Yes Yes Yes
11'2'3 Perform internal and external scans, and rescan as needed, after any significant change.
Scans must be performed by qualified personnel.
11.3 Implement a methodology for penetration testing that includes the fallowing:
• Is based on industry-acoepted penetration testing approaches (for example, NIST SP800-115)
• Includes coverage for the entire COE perimeter and critical systems
• Includes testing from both inside and outside the network
• Includes testing to validate any segmentation and scope -reduction controls
• Defines application -layer penetration tests to include, at a minimum, the vulnerabilities listed in
No No No No No No Yes Yes
Requirement 6.5
- Defines network -layer penetration tests to include components that support network function as well
as operating systems
• Includes review and consideration of threats and vulnerabilities experienced in the last 12 months
• Specifies retention of penetration testing results and remediation activities results.
11.3.1 Perform external penetration testing at least annually and after any significant infrastructure or
No No No No No No Yes Yes
application upgrade or modification (such as an operating system upgrade, a sub -network added to
the environment, or a web server added to the environmentl.
11.3.2 Perform internal penetration testing at least annually and after any significant infrastructure or
No No No No No No No Yes
application upgrade or modification (such as an operating system upgrade, a sub -network added to
the environment, or a web server added to the environment).
No No No No No No Yes Yes 111.3.3
Exploitable vulnerabilities found during penetration testing are corrected and testing is repeated
to verily the corrections.
11.3A If segmentation is used to isolate the CDE from other networks, perform penetration tests at
No No No No No Yes Yes Yes
least annually and after any changes to segmentation controls/methods to verify that the segmentation
methods are operational and effective, and isolate all out -of -scope systems from systems in the CDE.
A P2PE B B -IP C -VT C A -EP D-MERCH
PCI DSS Requirements 0.2
11.3.4.1 Additional requirement for service providers only: If segmentation is used, confirm PCI.
DSS scope by performing penetration testing on segmentation controls at least every six months and
No No NO NO No No No Yes
after any changes to segmentation controWmelhods.
Note: This requirement is a best practice until January 31, 2018, after which it becomes a
re uirement.
11.4 Use intrusion -detection andlor imrusion-prevention techniques to detect andlor prevent intrusions
alto the network. Monitor all traffic at the perimeter of the cardholder data environment as well as at
No NO No No No No Yes Yes
critical points in the cardholder data environment, and alert personnel to suspected compromises.
Keep all intrusion -detection and prevention engines baselines, and signatures up to date.
11.5 Deploy a change -detection mechanism (for example, file -integrity monitoring tools) to alert
personnel to unauthorized modification (including changes, additions, and deletions) of critica system
fi as oonfiguralum files, or content files; and configure the software to perform Cdt!L:al file comparisons
at least weeWy.
No No No No No Yes Yes Yes
Note: For change-deteclion purposes, critical lues are usually those that do not regutarty change, but
the modification of which could indicate a system compromise or risk of comprom tie. Change
defection mechanisms such as fife -integrity monitoring products usually come pre-confrgurad with
critical files for the related operating system. Other critical riles, such as those for custom spp6cations,
must be evaluated and defined by the entity {that is, the merchant elr service provider).
No No No No No Yes Yes Yes
11.5.1 Implement a process to respond to any alerts generated by the change -detection solution.
No Na No No No No No Yes
11.6 Ensure that security policies and operational procedures for se�=urity monitoring and testing are
documented, in use, and known to all affected parties.
Req -Y Req -Y Req -Y Req -Y Req -Y Req -Y Req -Y Req -Y
Requirement 12: Maintain a policy that addresses Information security for all
personnel
No Yes Yes Yes Yes Yes Yes Yes
12.1 Establish, publish, maintain, and disseminate a security policy
No Yes Yes Yes Yes Yes Yes Yes
12.1.1 Review the sl,l urity pod cy at least annual y and update the policy when the environment
changes.
12.2 Implement a risk -assessment process that:
• Is performed at least annually and upon significant changes to the environment Ifor example,
acquisition, merger, relocation, etc.),
No NO No No No No No Yes
• Identifies critical assets threats, and vulnerabilities, and
• Results in a ICrmal. di::umented analysis of risk.
Examples of risk -assessment methodologies include but are not limited to OCTAVE. ISO 27005 and
NIST SP 800.30,
12.3 Develop usage policies for critical technol :-gies and define pro^=r use of Ihe-�n tr:rhnologies.
Note: Examples of critical technologies include, but are not hailed to, remote access and rnreless
No NO Yes Yes Yes Yes No Yes
technologies, laptops, tablets, removable electrons media, a -mad usage and Internet usage.
Ensure these usage policies require the following
No No Yes Yes Yes Yes No Yes
12.3.1 Exp.icit approval by authorized part as
12.3.2 Authentication for use of the technology
No No No No No Yes NO Yes
12.3.3 A list of all such devices and personne° with access
No No Yes Yes Yes Yes No Yes
No No No NO No No No Yes
12.3.4 A method to accurately and readily determine owner, contact information, and purpose (for
exam le labeling, coding, and/or invenforving of devices
12.3.5 Acceptable uses of the techno:ogy
No No Yes Yes Yes Yes No Yes
12.3.6 Acceptable network locations for the technoiog as
No No No No No Yes No Yes
12.3.7 Ust of company -approved products
No No No No No No No Yes
12.3.8 Automatic disconnect of sessions for remote -access technologies after a specific period of
inactivity
Na No No No NO Yes No Yes
No No NO Yes No Yes No Yes
12.3.9 Activation of remote -access technologies for vendors and business partners only when needed
by vendors and business partners, with immediate dead vation after use
12.3.10 For personnel accessing cardholder data via remote -access technologies, prohibit the
copying, moving, and storage of cardho der data onto local hard drives and removable electronic
No No MO No No No No Yes
media, undess explicitly authorized for a defined business need.
Where there ;s an authorized business need, the usage po icies must require the data be protected in
accordance with all applicable PCI DSS Requirements
No Yes Yes No Yes Yes Yes Yes
12A Ensure that the security policy and procedures deafly define information security responsibilities
for a1 personnel.
12.4.1 Additional requirement for service providers only: Executive management shall establish
responsib Iity for the protection of cardholder data and a PCI DSS compliance program to include:
• Overall accouniab-lity, for me'Maining PCI DSS compliance
• Defining a charter for a PCI DSS comp canoe program and communication to executive management
No No No No No No No Yes
Note: This requirement is a best practice unlit January 31. 2018, after which it becomes a
requirement
NO Yes Yes Yes Yes Yes Yes Yes
12.5 Assign to an ndrvidual or team the following information security management responsibilities:
No No No No No No No Yes
125.1 Establish, di K.umerd, and distribute security policies and procedures.
12.5.2 Monitor and ana,yze security alerts and information. and distribute to appropriate personnel.
No No No No NO No No Yes
NO Yes Yes Yes Yes Yes Yes Yes
12.5.3 Establ-sh document, and distribute security incident response and escalation procedures to
ensure timely and effective handl) of all situations.
12.5.4 Administer user accounts, inctud'ng additions, deletions, and modifications.
No No No No No No No Yes
12.5.5 Monitor and control all access to data.
No No No No No No NO Yes
12.6 Implement a formal security awareness program to make all personnel aware of the cardholder
data security icy and procedures.
No Yes Yes Yes Yes Yes Yes Yes
P2PE B B -IP C -VT C A -EP D-MERCH
No No No No No No No Yes
No No No No No No No Yes
ND No trio No No No No Yes
IYos Ycs Yes Yes Yes Yes Yes Yes
Yes Yes ops Yes Yes Yes Yes Yes
I Yes Yes Yes Yes Yes Yes Yes Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
I No NO No No No No No Yes
Nu No ND No No No No Yes
I Yes Yes Yps res Yes Yes Yes Yes
No
No
No
No
No
No
No
Yes
No
No
No
No
No
No
No
Yes
No
No
No
No
No
No
No
Yes
No
No
No
No
No
No
No
Yes
No
No
No
No
No
No
No
Yes
I No Nu No ND No No No Yes
I rnb No NO No No No No No
PCI DSS Requirements 0.2
12.6.1 Educate personnel upon hire and at least annually.
Note: Methods can vary depending on the role of the personnel and their level of access to the
cardholder data.
12.6.2 Require personnel to acknowledge at least annually that they have read and understood the
security poliand procedures.
12.7 Screen potential personnel prior to hire to minimize the risk of attacks from internal sources.
(Examples of background checks include previous employment history, criminal record, credit history,
and reference checks.)
Note: For !hose potential personnel to be hired for certain positions such as store cashiers who only
have access to one card number at a time when fadlitating a transaction, this requirement is a
recommendation onr .
12.8 Maintain and implement policies and procedures to manage service providers, with whom
cardholder data is shared, or that could affect the security of cardholder data, as follows
12.6.1 Maintain a list of service providers including a description of the service provided.
12.8.2 Maintain a written agreement that includes an acknowledgement that the service providers are
responsible for the security of cardholder data the service providers possess or otherwise store,
process or transmit on behalf of the customer, or to the a)dent that they could impact the security of the
customer's cardholder data environment.
Note: The exact wording of an acknowledgement wdl depend on the agreement between the two
parties, the details of the service being provided, and ft responsibilities assigned to each party. The
acknowledgement does not have to include the exact wording provided in this requirement.
12.8.3 Ensure there is an established process for engaging service providers including proper due
diligence priortoengagement.
12,8.4 Maintain a program to monitor service providers' PCI DSS compliance status at least annually.
12.8.5 Maintain information about which PCI DSS requirements are managed by each service
provider, and which are managed b the entity.
12.9 Additional requirement for service providers only: Service providers acknowledge in writing
to customers that they are responsible for the security of cardholder data the service provider
possesses or Otherwise stores, processes, Or transmits on behalf of the customer, or to the extent that
they could impact the security of the customer's cardholder data environment.
Note: The exact wording of an acknowledgement will depend on the agreement between the two
parties, the details of the service being provided, and the responsibilities assigned to each party. The
acknowledgement does not have to include the exact wording provided in this requirement.
12.10 Implement an incident response plan. Be prepared to respond immediately to a system breach.
12.10.1 Create the incident response plan to be implemented in the event of system breach. Ensure
the plan addresses the fodnwing, at a minimum:
• Roles, responsibilities, and communication and contact strategies in the event of a compromise
including notification of the payment brands, at a minimum
• Specific incident response procedures
• Business recovery and continuity procedures
• Data backup processes
• Analysis of legal requirements for reporting compromises
• Coverage and responses of all critical system components
• Reference or inclusion of incident response procedures from the payrrent brands.
12.10.2 Review and test the plan, including all elements listed in Requirement 12.10.1, at least
annually.
12.10.3 Designate specific personnel to be available on a 2417 basis to respond to alerts.
12.10.4 Provide appropriate Iraining to staff with security breach response responsibilities.
12.10.5 1 nclude alerts from security monitoring systems, including but not limited to intrusion-datection,
irdrusisn reventfon, firewal s and file-inte:.rir . monitorir s „ lems.
12.10.6 Develop a process to modify and evolve the incident response plan according to lessons
teamed and to imorporale industry developments.
12.11 Additional requirement for service providers only: Perform reviews at least quarterly to
confirm personnel are following security policies and operational procedures. Reviews must cover the
following processes:
• Dai y log reviews
• Firewall rule -set reviews
• Applying configuration standards to new systems
• Responding to s•.;urity alerts
• Change management processes
Note: This requirement is a best practice until January 31, 2018, alter which it becomes a
Wirrrament
12.11.1 Additional requirement for service providers only: Maintain documentation of quarterly
review process to include:
• Documeming results of the reviews
• Review and sign off of results by personnel assigned responsibility for the PCI DSS compliance
program
Note: This requirement is a best practice until January 31, 2018, alter which it becomes a
re. uirement