Payment Card Industry Data Security Standard

A1.1

Multi-tenant service providers protect and separate all customer environments and data.

A1.1.1

Logical separation is implemented as follows: - The provider cannot access its customers’ environments without authorization. - Customers cannot access the provider’s environment without authorization...

A1.1.2

Controls are implemented such that each customer only has permission to access its own cardholder data and CDE.

A1.1.3

Controls are implemented such that each customer can only access resources allocated to them.

A1.1.4

The effectiveness of logical separation controls used to separate customer environments is confirmed at least once every six months via penetration testing.

A1.2

Multi-tenant service providers facilitate logging and incident response for all customers.

A1.2.1

Audit log capability is enabled for each customer’s environment that is consistent with PCI DSS Requirement 10, including: - Logs are enabled for common third-party applications. - Logs are active by...

A1.2.2

Processes or mechanisms are implemented to support and/or facilitate prompt forensic investigations in the event of a suspected or confirmed security incident for any customer.

A1.2.3

Processes or mechanisms are implemented for reporting and addressing suspected or confirmed security incidents and vulnerabilities, including: - Customers can securely report security incidents and vu...

A2.1

POI terminals using SSL and/or early TLS are confirmed as not susceptible to known SSL/TLS exploits.

A2.1.1

Where POS POI terminals at the merchant or payment acceptance location use SSL and/or early TLS, the entity confirms the devices are not susceptible to any known exploits for those protocols.

A2.1.2

Additional requirement for service providers only: All service providers with existing connection points to POS POI terminals that use SSL and/or early TLS as defined in A2.1 have a formal Risk Mitiga...

A2.1.3

Additional requirement for service providers only: All service providers provide a secure service offering.

A3.1

A PCI DSS compliance program is implemented.

A3.1.1

Responsibility is established by executive management for the protection of account data and a PCI DSS compliance program that includes: - Overall accountability for maintaining PCI DSS compliance. -...

A3.1.2

A formal PCI DSS compliance program is in place that includes: - Definition of activities for maintaining and monitoring overall PCI DSS compliance, including business-as-usual activities. - Annual PC...

A3.1.3

PCI DSS compliance roles and responsibilities are specifically defined and formally assigned to one or more personnel, including: - Managing PCI DSS business-as-usual activities. - Managing annual PCI...

A3.1.4

Up-to-date PCI DSS and/or information security training is provided at least once every 12 months to personnel with PCI DSS compliance responsibilities (as identified in A3.1.3).

A3.2

PCI DSS scope is documented and validated.

A3.2.1

PCI DSS scope is documented and confirmed for accuracy at least once every three months and upon significant changes to the in-scope environment. At a minimum, the scoping validation includes: - Ident...

A3.2.2

PCI DSS scope impact for all changes to systems or networks is determined, including additions of new systems and new network connections. Processes include: - Performing a formal PCI DSS impact asses...

A3.2.2.1

Upon completion of a change, all relevant PCI DSS requirements are confirmed to be implemented on all new or changed systems and networks, and documentation is updated as applicable.

A3.2.3

Changes to organizational structure result in a formal (internal) review of the impact to PCI DSS scope and applicability of controls.

A3.2.4

If segmentation is used, PCI DSS scope is confirmed as follows: • Per the entity’s methodology defined at Requirement 11.4.1. • Penetration testing is performed on segmentation controls at least once...

A3.2.5

A data-discovery methodology is implemented that: - Confirms PCI DSS scope. - Locates all sources and locations of cleartext PAN at least once every three months and upon significant changes to the CD...

A3.2.5.1

Data discovery methods are confirmed as follows: - Effectiveness of methods is tested. - Methods are able to discover cleartext PAN on all types of system components and file formats in use. - The eff...

A3.2.5.2

Response procedures are implemented to be initiated upon the detection of cleartext PAN outside the CDE to include: - Determining what to do if cleartext PAN is discovered outside the CDE, including i...

A3.2.6

Mechanisms are implemented for detecting and preventing cleartext PAN from leaving the CDE via an unauthorized channel, method, or process, including mechanisms that are: - Actively running. - Configu...

A3.2.6.1

Response procedures are implemented to be initiated upon the detection of attempts to remove cleartext PAN from the CDE via an unauthorized channel, method, or process. Response procedures include: -...

A3.3

PCI DSS is incorporated into business-as-usual (BAU) activities.

A3.3.1

Failures of critical security control systems are detected, alerted, and addressed promptly, including but not limited to failure of: - Network security controls - IDS/IPS - FIM - Anti-malware solutio...

A3.3.1.2

Failures of any critical security control systems are responded to promptly. Processes for responding to failures in security control systems include: - Restoring security functions. - Identifying and...

A3.3.2

Hardware and software technologies are reviewed at least once every 12 months to confirm whether they continue to meet the organization’s PCI DSS requirements.

A3.3.3

Reviews are performed at least once every three months to verify BAU activities are being followed. Reviews are performed by personnel assigned to the PCI DSS compliance program (as identified in A3.1...

A3.4

Logical access to the cardholder data environment is controlled and managed.

A3.4.1

User accounts and access privileges to in-scope system components are reviewed at least once every six months to ensure user accounts and access privileges remain appropriate based on job function, an...

A3.5

Suspicious events are identified and responded to.

A3.5.1

A methodology is implemented for the prompt identification of attack patterns and undesirable behavior across systems that includes: - Identification of anomalies or suspicious activity as it occurs....

1.1

Processes and mechanisms for installing and maintaining network security controls are defined and understood.

1.1.1

All security policies and operational procedures that are identified in Requirement 1 are: - Documented. - Kept up to date. - In use. - Known to all affected parties.

1.1.2

Roles and responsibilities for performing activities in Requirement 1 are documented, assigned, and understood.

1.2

Network security controls (NSCs) are configured and maintained.

1.2.1

Configuration standards for NSC rulesets are - Defined. - Implemented - Maintained.

1.2.2

All changes to network connections and to configurations of NSCs are approved and managed in accordance with the change control process defined at Requirement 6.5.1.

1.2.3

An accurate network diagram(s) is maintained that shows all connections between the CDE and other networks, including any wireless networks.

1.2.4

An accurate data-flow diagram(s) is maintained that meets the following: - Shows all account data flows across systems and networks. - Updated as needed upon changes to the environment.

1.2.5

All services, protocols, and ports allowed are identified, approved, and have a defined business need.

1.2.6

Security features are defined and implemented for all services, protocols, and ports that are in use and considered to be insecure, such that the risk is mitigated.

1.2.7

Configurations of NSCs are reviewed at least once every six months to confirm they are relevant and effective.

1.2.8

Configuration files for NSCs are: - Secured from unauthorized access. - Kept consistent with active network configurations.

1.3

Network access to and from the cardholder data environment is restricted.

1.3.1

Inbound traffic to the CDE is restricted as follows: - To only traffic that is necessary. - All other traffic is specifically denied.

1.3.2

Outbound traffic from the CDE is restricted as follows: - To only traffic that is necessary. - All other traffic is specifically denied.

1.3.3

NSCs are installed between all wireless networks and the CDE, regardless of whether the wireless network is a CDE, such that: - All wireless traffic from wireless networks into the CDE is denied by d...

1.4

Network connections between trusted and untrusted networks are controlled.

1.4.1

NSCs are implemented between trusted and untrusted networks.

1.4.2

Inbound traffic from untrusted networks to trusted networks is restricted to: - Communications with system components that are authorized to provide publicly accessible services, protocols, and ports....

1.4.3

Anti-spoofing measures are implemented to detect and block forged source IP addresses from entering the trusted network.

1.4.4

System components that store cardholder data are not directly accessible from untrusted networks.

1.4.5

The disclosure of internal IP addresses and routing information is limited to only authorized parties.

1.5

Risks to the CDE from computing devices that are able to connect to both untrusted networks and the CDE are mitigated.

1.5.1

Security controls are implemented on any computing devices, including company- and employee-owned devices, that connect to both untrusted networks (including the Internet) and the CDE as follows: - Sp...

2.1

Processes and mechanisms for applying secure configurations to all system components are defined and understood.

2.1.1

All security policies and operational procedures that are identified in Requirement 2 are: - Documented. - Kept up to date. - In use. - Known to all affected parties.

2.1.2

Roles and responsibilities for performing activities in Requirement 2 are documented, assigned, and understood.

2.2

System components are configured and managed securely.

2.2.1

Configuration standards are developed, implemented, and maintained to: - Cover all system components. - Be consistent with industry-accepted system hardening standards or vendor hardening recommendati...

2.2.2

Vendor default accounts are managed as follows: - If the vendor default account(s) will be used, the default password is changed per Requirement 8.3.6. - If the vendor default account(s) will not be u...

2.2.3

Primary functions requiring different security levels are managed as follows: - Only one primary function exists on a system component. OR - Primary functions with differing security levels that exi...

2.2.4

Only necessary services, protocols, daemons, and functions are enabled, and all unnecessary functionality is removed or disabled.

2.2.5

If any insecure services, protocols, or daemons are present: - business justification is documented. - additional security features are documented and implemented that reduce the risk of using insecur...

2.2.6

System security parameters are configured to prevent misuse.

2.2.7

All non-console administrative access is encrypted using strong cryptography.

2.3

Wireless environments are configured and managed securely.

2.3.1

For wireless environments connected to the CDE or transmitting account data, all wireless vendor defaults are changed at installation or are confirmed to be secure, including but not limited to:   - D...

2.3.2

For wireless environments connected to the CDE or transmitting account data, wireless encryption keys are changed as follows: - Whenever personnel with knowledge of the key leave the company or the ro...

7.1

Processes and mechanisms for restricting access to system components and cardholder data by business need to know are defined and understood.

7.1.1

All security policies and operational procedures that are identified in Requirement 7 are: - Documented. - Kept up to date. - In use. - Known to all affected parties.

7.1.2

Roles and responsibilities for performing activities in Requirement 7 are documented, assigned, and understood.

7.2

Access to system components and data is appropriately defined and assigned.

7.2.1

An access control model is defined and includes granting access as follows: - Appropriate access depending on the entity’s business and access needs. - Access to system components and data resources t...

7.2.2

Access is assigned to users, including privileged users, based on: - Job classification and function. - Least privileges necessary to perform job responsibilities.

7.2.3

Required privileges are approved by authorized personnel.

7.2.4

All user accounts and related access privileges, including third-party/vendor accounts, are reviewed as follows: - At least once every six months. - To ensure user accounts and access remain appropria...

7.2.5

All application and system accounts and related access privileges are assigned and managed as follows: - Based on the least privileges necessary for the operability of the system or application. - Acc...

7.2.5.1

All access by application and system accounts and related access privileges are reviewed as follows: - Periodically (at the frequency defined in the entity’s targeted risk analysis, which is performed...

7.2.6

All user access to query repositories of stored cardholder data is restricted as follows: - Via applications or other programmatic methods, with access and allowed actions based on user roles and leas...

7.3

Access to system components and data is managed via an access control system(s).

7.3.1

An access control system(s) is in place that restricts access based on a user’s need to know and covers all system components.

7.3.2

The access control system(s) is configured to enforce permissions assigned to individuals, applications, and systems based on job classification and function.

7.3.3

The access control system(s) is set to “deny all” by default.

8.1

Processes and mechanisms for identifying users and authenticating access to system components are defined and understood.

8.1.1

All security policies and operational procedures that are identified in Requirement 8 are: - Documented. - Kept up to date. - In use. - Known to all affected parties.

8.1.2

Roles and responsibilities for performing activities in Requirement 8 are documented, assigned, and understood.

8.2

User identification and related accounts for users and administrators are strictly managed throughout an account’s lifecycle.

8.2.1

All users are assigned a unique ID before access to system components or cardholder data is allowed.

8.2.2

Group, shared, or generic accounts, or other shared authentication credentials are only used when necessary on an exception basis, and are managed as follows: - Account use is prevented unless needed...

8.2.3

Additional requirement for service providers only: Service providers with remote access to customer premises use unique authentication factors for each customer premises.

8.2.4

Addition, deletion, and modification of user IDs, authentication factors, and other identifier objects are managed as follows: - Authorized with the appropriate approval. - Implemented with only the p...

8.2.5

Access for terminated users is immediately revoked.

8.2.6

Inactive user accounts are removed or disabled within 90 days of inactivity.

8.2.7

Accounts used by third parties to access, support, or maintain system components via remote access are managed as follows: - Enabled only during the time period needed and disabled when not in use. -...

8.2.8

If a user session has been idle for more than 15 minutes, the user is required to re-authenticate to re-activate the terminal or session.

8.3

Strong authentication for users and administrators is established and managed.

8.3.1

All user access to system components for users and administrators is authenticated via at least one of the following authentication factors: • Something you know, such as a password or passphrase. • S...

8.3.10

Additional requirement for service providers only: If passwords/passphrases are used as the only authentication factor for customer user access to cardholder data (i.e., in any single- factor authenti...

8.3.10.1

Additional requirement for service providers only: If passwords/passphrases are used as the only authentication factor for customer user access (i.e., in any single-factor authentication implementatio...

8.3.11

Where authentication factors such as physical or logical security tokens, smart cards, or certificates are used: - Factors are assigned to an individual user and not shared among multiple users. - Phy...

8.3.2

Strong cryptography is used to render all authentication factors unreadable during transmission and storage on all system components.

8.3.3

User identity is verified before modifying any authentication factor.

8.3.4

Invalid authentication attempts are limited by: - Locking out the user ID after not more than 10 attempts. - Setting the lockout duration to a minimum of 30 minutes or until the user’s identity is con...

8.3.5

If passwords/passphrases are used as authentication factors to meet Requirement 8.3.1, they are set and reset for each user as follows: - Set to a unique value for first-time use and upon reset. - For...

8.3.6

If passwords/passphrases are used as authentication factors to meet Requirement 8.3.1, they meet the following minimum level of complexity: - A minimum length of 12 characters (or IF the system does n...

8.3.7

Individuals are not allowed to submit a new password/passphrase that is the same as any of the last four passwords/passphrases used.

8.3.8

Authentication policies and procedures are documented and communicated to all users including: - Guidance on selecting strong authentication factors. - Guidance for how users should protect their auth...

8.3.9

If passwords/passphrases are used as the only authentication factor for user access (i.e., in any single-factor authentication implementation) then either: • Passwords/passphrases are changed at least...

8.4

Multi-factor authentication (MFA) is implemented to secure access into the CDE.

8.4.1

MFA is implemented for all non-console access into the CDE for personnel with administrative access.

8.4.2

MFA is implemented for all access into the CDE.

8.4.3

MFA is implemented for all remote network access originating from outside the entity’s network that could access or impact the CDE as follows: - All remote access by all personnel, both users and admi...

8.5

Multi-factor authentication (MFA) systems are configured to prevent misuse.

8.5.1

MFA systems are implemented as follows: - The MFA system is not susceptible to replay attacks. - MFA systems cannot be bypassed by any users, including administrative users unless specifically documen...

8.6

Use of application and system accounts and associated authentication factors is strictly managed.

8.6.1

If accounts used by systems or applications can be used for interactive login, they are managed as follows: - Interactive use is prevented unless needed for an exceptional circumstance. - Interactive...

8.6.2

Passwords/passphrases for any application and system accounts that can be used for interactive login are not hard coded in scripts, configuration/property files, or bespoke and custom source code.

8.6.3

Passwords/passphrases for any application and system accounts are protected against misuse as follows: - Passwords/passphrases are changed periodically (at the frequency defined in the entity’s target...

9.1

Processes and mechanisms for restricting physical access to cardholder data are defined and undood.

9.1.1

All security policies and operational procedures that are identified in Requirement 9 are: - Documented. - Kept up to date. - In use. - Known to all affected parties.

9.1.2

Roles and responsibilities for performing activities in Requirement 9 are documented, assigned, and understood.

9.2

Physical access controls manage entry into facilities and systems containing cardholder data.

9.2.1

Appropriate facility entry controls are in place to restrict physical access to systems in the CDE.

9.2.1.1

Individual physical access to sensitive areas within the CDE is monitored with either video cameras or physical access control mechanisms (or both) as follows: - Entry and exit points to/from sensitiv...

9.2.2

Physical and/or logical controls are implemented to restrict use of publicly accessible network jacks within the facility.

9.2.3

Physical access to wireless access points, gateways, networking/communications hardware, and telecommunication lines within the facility is restricted.

9.2.4

Access to consoles in sensitive areas is restricted via locking when not in use.

9.3

Physical access for personnel and visitors is authorized and managed.

9.3.1

Procedures are implemented for authorizing and managing physical access of personnel to the CDE, including: - Identifying personnel. - Managing changes to an individual’s physical access requirements....

9.3.1.1

Physical access to sensitive areas within the CDE for personnel is controlled as follows: - Access is authorized and based on individual job function. - Access is revoked immediately upon termination....

9.3.2

Procedures are implemented for authorizing and managing visitor access to the CDE, including: - Visitors are authorized before entering. - Visitors are escorted at all times. - Visitors are clearly id...

9.3.3

Visitor badges or identification are surrendered or deactivated before visitors leave the facility or at the date of expiration.

9.3.4

A visitor log is used to maintain a physical record of visitor activity within the facility and within sensitive areas, including: - The visitor’s name and the organization represented. - The date and...

9.4

Media with cardholder data is securely stored, accessed, distributed, and destroyed.

9.4.1

All media with cardholder data is physically secured.

9.4.1.1

Offline media backups with cardholder data are stored in a secure location.

9.4.1.2

The security of the offline media backup location(s) with cardholder data is reviewed at least once every 12 months.

9.4.2

All media with cardholder data is classified in accordance with the sensitivity of the data.

9.4.3

Media with cardholder data sent outside the facility is secured as follows: - Media sent outside the facility is logged. - Media is sent by secured courier or other delivery method that can be accurat...

9.4.4

Management approves all media with cardholder data that is moved outside the facility (including when media is distributed to individuals).

9.4.5

Inventory logs of all electronic media with cardholder data are maintained.

9.4.5.1

Inventories of electronic media with cardholder data are conducted at least once every 12 months.

9.4.6

Hard-copy materials with cardholder data are destroyed when no longer needed for business or legal reasons, as follows: • Materials are cross-cut shredded, incinerated, or pulped so that cardholder da...

9.4.7

Electronic media with cardholder data is destroyed when no longer needed for business or legal reasons via one of the following: - The electronic media is destroyed. - The cardholder data is rendered...

9.5

Point of interaction (POI) devices are protected from tampering and unauthorized substitution.

9.5.1

POI devices that capture payment card data via direct physical interaction with the payment card form factor are protected from tampering and unauthorized substitution, including the following: - Main...

9.5.1.1

An up-to-date list of POI devices is maintained, including: - Make and model of the device. - Location of device. - Device serial number or other methods of unique identification.

9.5.1.2

POI device surfaces are periodically inspected to detect tampering and unauthorized substitution.

9.5.1.2.1

The frequency of periodic POI device inspections and the type of inspections performed is defined in the entity’s targeted risk analysis, which is performed according to all elements specified in Requ...

9.5.1.3

Training is provided for personnel in POI environments to be aware of attempted tampering or replacement of POI devices, and includes: - Verifying the identity of any third-party persons claiming to b...

5.1

Processes and mechanisms for protecting all systems and networks from malicious software are defined and understood.

5.1.1

All security policies and operational procedures that are identified in Requirement 5 are: - Documented. - Kept up to date. - In use. - Known to all affected parties.

5.1.2

Roles and responsibilities for performing activities in Requirement 5 are documented, assigned, and understood.

5.2

Malicious software (malware) is prevented, or detected and addressed.

5.2.1

An anti-malware solution(s) is deployed on all system components, except for those system components identified in periodic evaluations per Requirement 5.2.3 that concludes the system components are n...

5.2.2

The deployed anti-malware solution(s): - Detects all known types of malware. - Removes, blocks, or contains all known types of malware.

5.2.3

Any system components that are not at risk for malware are evaluated periodically to include the following: - A documented list of all system components not at risk for malware. - Identification and e...

5.2.3.1

The frequency of periodic evaluations of system components identified as not at risk for malware is defined in the entity’s targeted risk analysis, which is performed according to all elements specifi...

5.3

Anti-malware mechanisms and processes are active, maintained, and monitored.

5.3.1

The anti-malware solution(s) is kept current via automatic updates.

5.3.2

The anti-malware solution(s): - Performs periodic scans and active or real-time scans. OR - Performs continuous behavioral analysis of systems or processes.

5.3.2.1

If periodic malware scans are performed to meet Requirement 5.3.2, the frequency of scans is defined in the entity’s targeted risk analysis, which is performed according to all elements specified in R...

5.3.3

For removable electronic media, the anti-malware solution(s): - Performs automatic scans of when the media is inserted, connected, or logically mounted, OR - Performs continuous behavioral analysis of...

5.3.4

Audit logs for the anti-malware solution(s) are enabled and retained in accordance with Requirement 10.5.1.

5.3.5

Anti-malware mechanisms cannot be disabled or altered by users, unless specifically documented, and authorized by management on a case-by-case basis for a limited time period.

5.4

Anti-phishing mechanisms protect users against phishing attacks.

5.4.1

Processes and automated mechanisms are in place to detect and protect personnel against phishing attacks.

6.1

Processes and mechanisms for developing and maintaining secure systems and software are defined and understood.

6.1.1

All security policies and operational procedures that are identified in Requirement 6 are: - Documented. - Kept up to date. - In use. - Known to all affected parties.

6.1.2

Roles and responsibilities for performing activities in Requirement 6 are documented, assigned, and understood.

6.2

Bespoke and custom software are developed securely.

6.2.1

Bespoke and custom software are developed securely, as follows: - Based on industry standards and/or best practices for secure development. - In accordance with PCI DSS (for example, secure authentica...

6.2.2

Software development personnel working on bespoke and custom software are trained at least once every 12 months as follows: - On software security relevant to their job function and development langua...

6.2.3

Bespoke and custom software is reviewed prior to being released into production or to customers, to identify and correct potential coding vulnerabilities, as follows: - Code reviews ensure code is dev...

6.2.3.1

If manual code reviews are performed for bespoke and custom software prior to release to production, code changes are: - Reviewed by individuals other than the originating code author, and who are kno...

6.2.4

Software engineering techniques or other methods are defined and in use by software development personnel to prevent or mitigate common software attacks and related vulnerabilities in bespoke and cust...

6.3

Security vulnerabilities are identified and addressed.

6.3.1

Security vulnerabilities are identified and managed as follows: - New security vulnerabilities are identified using industry-recognized sources for security vulnerability information, including alerts...

6.3.2

An inventory of bespoke and custom software, and third-party software components incorporated into bespoke and custom software is maintained to facilitate vulnerability and patch management.

6.3.3

All system components are protected from known vulnerabilities by installing applicable security patches/updates as follows: - Critical or high-security patches/updates (identified according to the ri...

6.4

Public-facing web applications are protected against attacks.

6.4.1

For public-facing web applications, new threats and vulnerabilities are addressed on an ongoing basis and these applications are protected against known attacks as follows: - Reviewing public-facing...

6.4.2

For public-facing web applications, an automated technical solution is deployed that continually detects and prevents web-based attacks, with at least the following: - Is installed in front of public-...

6.4.3

All payment page scripts that are loaded and executed in the consumer’s browser are managed as follows: • A method is implemented to confirm that each script is authorized. • A method is implemented t...

6.5

Changes to all system components are managed securely.

6.5.1

Changes to all system components in the production environment are made according to established procedures that include: - Reason for, and description of, the change. - Documentation of security impa...

6.5.2

Upon completion of a significant change, all applicable PCI DSS requirements are confirmed to be in place on all new or changed systems and networks, and documentation is updated as applicable.

6.5.3

Pre-production environments are separated from production environments and the separation is enforced with access controls.

6.5.4

Roles and functions are separated between production and pre-production environments to provide accountability such that only reviewed and approved changes are deployed.

6.5.5

Live PANs are not used in pre-production environments, except where those environments are included in the CDE and protected in accordance with all applicable PCI DSS requirements.

6.5.6

Test data and test accounts are removed from system components before the system goes into production.

12.1

A comprehensive information security policy that governs and provides direction for protection of the entity’s information assets is known and current.

12.1.1

An overall information security policy is: - Established. - Published. - Maintained. - Disseminated to all relevant personnel, as well as to relevant vendors and business partners.

12.1.2

The information security policy is: - Reviewed at least once every 12 months. - Updated as needed to reflect changes to business objectives or risks to the environment.

12.1.3

The security policy clearly defines information security roles and responsibilities for all personnel, and all personnel are aware of and acknowledge their information security responsibilities.

12.1.4

Responsibility for information security is formally assigned to a Chief Information Security Officer or other information security knowledgeable member of executive management.

12.10

Suspected and confirmed security incidents that could impact the CDE are responded to immediately.

12.10.1

An incident response plan exists and is ready to be activated in the event of a suspected or confirmed security incident. The plan includes, but is not limited to: - Roles, responsibilities, and commu...

12.10.2

At least once every 12 months, the security incident response plan is: - Reviewed and the content is updated as needed. - Tested, including all elements listed in Requirement 12.10.1.

12.10.3

Specific personnel are designated to be available on a 24/7 basis to respond to suspected or confirmed security incidents.

12.10.4

Personnel responsible for responding to suspected and confirmed security incidents are appropriately and periodically trained on their incident response responsibilities.

12.10.4.1

The frequency of periodic training for incident response personnel is defined in the entity’s targeted risk analysis, which is performed according to all elements specified in Requirement 12.3.1.

12.10.5

The security incident response plan includes monitoring and responding to alerts from security monitoring systems, including but not limited to: - Intrusion-detection and intrusion-prevention systems....

12.10.6

The security incident response plan is modified and evolved according to lessons learned and to incorporate industry developments.

12.10.7

Incident response procedures are in place, to be initiated upon the detection of stored PAN anywhere it is not expected, and include: - Determining what to do if PAN is discovered outside the CDE, inc...

12.2

Acceptable use policies for end-user technologies are defined and implemented.

12.2.1

Acceptable use policies for end-user technologies are documented and implemented, including: - Explicit approval by authorized parties. - Acceptable uses of the technology. - List of products approved...

12.3

Risks to the cardholder data environment are formally identified, evaluated, and managed.

12.3.1

Each PCI DSS requirement that provides flexibility for how frequently it is performed (for example, requirements to be performed periodically) is supported by a targeted risk analysis that is document...

12.3.2

A targeted risk analysis is performed for each PCI DSS requirement that the entity meets with the customized approach, to include: - Documented evidence detailing each element specified in Appendix D:...

12.3.3

Cryptographic cipher suites and protocols in use are documented and reviewed at least once every 12 months, including at least the following: - An up-to-date inventory of all cryptographic cipher suit...

12.3.4

Hardware and software technologies in use are reviewed at least once every 12 months, including at least the following: • Analysis that the technologies continue to receive security fixes from vendors...

12.4

PCI DSS compliance is managed.

12.4.1

Additional requirement for service providers only: Responsibility is established by executive management for the protection of cardholder data and a PCI DSS compliance program to include: - Overall ac...

12.4.2

Additional requirement for service providers only: Reviews are performed at least once every three months to confirm that personnel are performing their tasks in accordance with all security policies...

12.4.2.1

Additional requirement for service providers only: Reviews conducted in accordance with Requirement 12.4.2 are documented to include: - Results of the reviews. - Documented remediation actions taken f...

12.5

PCI DSS scope is documented and validated.

12.5.1

An inventory of system components that are in scope for PCI DSS, including a description of function/use, is maintained and kept current.

12.5.2

PCI DSS scope is documented and confirmed by the entity at least once every 12 months and upon significant change to the in-scope environment. At a minimum, the scoping validation includes: - Identify...

12.5.2.1

Additional requirement for service providers only: PCI DSS scope is documented and confirmed by the entity at least once every six months and upon significant change to the in-scope environment. At a...

12.5.3

Additional requirement for service providers only: Significant changes to organizational structure result in a documented (internal) review of the impact to PCI DSS scope and applicability of controls...

12.6

Security awareness education is an ongoing activity.

12.6.1

A formal security awareness program is implemented to make all personnel aware of the entity’s information security policy and procedures, and their role in protecting the cardholder data.

12.6.2

The security awareness program is: - Reviewed at least once every 12 months, and - Updated as needed to address any new threats and vulnerabilities that may impact the security of the entity’s CDE, or...

12.6.3

Personnel receive security awareness training as follows: - Upon hire and at least once every 12 months. - Multiple methods of communication are used. - Personnel acknowledge at least once every 12 mo...

12.6.3.1

Security awareness training includes awareness of threats and vulnerabilities that could impact the security of the CDE, including but not limited to: - Phishing and related attacks. - Social engineer...

12.6.3.2

Security awareness training includes awareness about the acceptable use of end-user technologies in accordance with Requirement 12.2.1.

12.7

Personnel are screened to reduce risks from insider threats.

12.7.1

Potential personnel who will have access to the CDE are screened, within the constraints of local laws, prior to hire to minimize the risk of attacks from internal sources

12.8

Risk to information assets associated with third-party service provider (TPSP) relationships is managed.

12.8.1

A list of all third-party service providers (TPSPs) with which account data is shared or that could affect the security of account data is maintained, including a description for each of the services...

12.8.2

Written agreements with TPSPs are maintained as follows: - Written agreements are maintained with all TPSPs with which account data is shared or that could affect the security of the CDE. - Written ag...

12.8.3

An established process is implemented for engaging TPSPs, including proper due diligence prior to engagement.

12.8.4

A program is implemented to monitor TPSPs’ PCI DSS compliance status at least once every 12 months.

12.8.5

Information is maintained about which PCI DSS requirements are managed by each TPSP, which are managed by the entity, and any that are shared between the TPSP and the entity.

12.9

Third-party service providers (TPSPs) support their customers’ PCI DSS compliance.

12.9.1

Additional requirement for service providers only: TPSPs acknowledge in writing to customers that they are responsible for the security of account data the TPSP possesses or otherwise stores, processe...

12.9.2

Additional requirement for service providers only: TPSPs support their customers’ requests for information to meet Requirements 12.8.4 and 12.8.5 by providing the following upon customer request: - PC...

3.1

Processes and mechanisms for protecting stored account data are defined and understood.

3.1.1

All security policies and operational procedures that are identified in Requirement 3 are: - Documented. - Kept up to date. - In use. - Known to all affected parties.

3.1.2

Roles and responsibilities for performing activities in Requirement 3 are documented, assigned, and understood.

3.2

Storage of account data is kept to a minimum.

3.2.1

Account data storage is kept to a minimum through implementation of data retention and disposal policies, procedures, and processes that include at least the following: - Coverage for all locations of...

3.3

Sensitive authentication data (SAD) is not stored after authorization.

3.3.1

SAD is not retained after authorization, even if encrypted. All sensitive authentication data received is rendered unrecoverable upon completion of the authorization process.

3.3.1.1

The full contents of any track are not retained upon completion of the authorization process.

3.3.1.2

The card verification code is not retained upon completion of the authorization process.

3.3.1.3

The personal identification number (PIN) and the PIN block are not retained upon completion of the authorization process

3.3.2

SAD that is stored electronically prior to completion of authorization is encrypted using strong cryptography.

3.3.3

Additional requirement for issuers and companies that support issuing services and store sensitive authentication data: Any storage of sensitive authentication data is: - Limited to that which is need...

3.4

Access to displays of full PAN and ability to copy cardholder data are restricted.

3.4.1

PAN is masked when displayed (the BIN 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 BIN and las...

3.4.2

When using remote-access technologies, technical controls prevent copy and/or relocation of PAN for all personnel, except for those with documented, explicit authorization and a legitimate, defined bu...

3.5

Primary account number (PAN) is secured wherever it is stored.

3.5.1

PAN is rendered unreadable anywhere it is stored by using any of the following approaches: - One-way hashes based on strong cryptography of the entire PAN. - Truncation (hashing cannot be used to repl...

3.5.2

Hashes used to render PAN unreadable (per the first bullet of Requirement 3.5.1) are keyed cryptographic hashes of the entire PAN, with associated key-management processes and procedures in accordance...

3.5.3

If disk-level or partition-level encryption rather than file-, column-, or field-level database encryption) is used to render PAN unreadable, it is implemented only as follows: - On removable electron...

3.5.4

If disk-level or partition-level encryption is used (rather than file-, column-, or field--level database encryption) to render PAN unreadable, it is managed as follows: - Logical access is managed se...

3.6

Cryptographic keys used to protect stored account data are secured.

3.6.1

Procedures are defined and implemented to protect cryptographic keys used to protect stored account data against disclosure and misuse that include: - Access to keys is restricted to the fewest number...

3.6.1.1

Additional requirement for service providers only: A documented description of the cryptographic architecture is maintained that includes: - Details of all algorithms, protocols, and keys used for the...

3.6.1.2

Secret and private keys used to encrypt/decrypt stored account data are stored in one (or more) of the following forms at all times: - Encrypted with a key-encrypting key that is at least as strong as...

3.6.1.3

Access to cleartext cryptographic key components is restricted to the fewest number of custodians necessary.

3.6.1.4

Cryptographic keys are stored in the fewest possible location.

3.7

Where cryptography is used to protect stored account data, key management processes and procedures covering all aspects of the key

3.7.1

Key-management policies and procedures are implemented to include generation of strong cryptographic keys used to protect stored account data.

3.7.2

Key-management policies and procedures are implemented to include secure distribution of cryptographic keys used to protect stored account data.

3.7.3

Key-management policies and procedures are implemented to include secure storage of cryptographic keys used to protect stored account data.

3.7.4

Key management policies and procedures are implemented for cryptographic key changes for keys that have reached the end of their cryptoperiod, as defined by the associated application vendor or key ow...

3.7.5

Key management policies procedures are implemented to include the retirement, replacement, or destruction of keys used to protect stored account data, as deemed necessary when: - The key has reached t...

3.7.6

Where manual cleartext cryptographic key-management operations are performed by personnel, key-management policies and procedures are implemented include managing these operations using split knowledg...

3.7.7

Key management policies and procedures are implemented to include the prevention of unauthorized substitution of cryptographic keys.

3.7.8

Key management policies and procedures are implemented to include that cryptographic key custodians formally acknowledge (in writing or electronically) that they understand and accept their key-custod...

3.7.9

Additional testing procedure for service provider assessments only: If the service provider shares cryptographic keys with its customers for transmission or storage of account data, examine the docume...

4.1

Processes and mechanisms for protecting cardholder data with strong cryptography during transmission over open, public networks are defined and documented.

4.1.1

All security policies and operational procedures that are identified in Requirement 4 are: - Documented. - Kept up to date. - In use. - Known to all affected parties

4.1.2

4.2

PAN is protected with strong cryptography during transmission.

4.2.1

Strong cryptography and security protocols are implemented as follows to safeguard PAN during transmission over open, public networks: - Only trusted keys and certificates are accepted. - Certificates...

4.2.1.1

An inventory of the entity’s trusted keys and certificates used to protect PAN during transmission is maintained.

4.2.1.2

Wireless networks transmitting PAN or connected to the CDE use industry best practices to implement strong cryptography for authentication and transmission.

4.2.2

PAN is secured with strong cryptography whenever it is sent via end-user messaging technologies.

10.1

Processes and mechanisms for logging and monitoring all access to system components and cardholder data are defined and documented.

10.1.1

All security policies and operational procedures that are identified in Requirement 10 are: - Documented. - Kept up to date. - In use. - Known to all affected parties.

10.1.2

Roles and responsibilities for performing activities in Requirement 10 are documented, assigned, and understood

10.2

Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events.

10.2.1

Audit logs are enabled and active for all system components and cardholder data.

10.2.1.1

Audit logs capture all individual user access to cardholder data.

10.2.1.2

Audit logs capture all actions taken by any individual with administrative access, including any interactive use of application or system accounts.

10.2.1.3

Audit logs capture all access to audit logs.

10.2.1.4

Audit logs capture all invalid logical access attempts.

10.2.1.5

Audit logs capture all changes to identification and authentication credentials including, but not limited to: - Creation of new accounts. - Elevation of privileges. - All changes, additions, or delet...

10.2.1.6

Audit logs capture the following: - All initialization of new audit logs, and - All starting, stopping, or pausing of the existing audit logs.

10.2.1.7

Audit logs capture all creation and deletion of system-level objects.

10.2.2

Audit logs record the following details for each auditable event: - User identification. - Type of event. - Date and time. - Success and failure indication. - Origination of event. - Identity or name...

10.3

Audit logs are protected from destruction and unauthorized modifications.

10.3.1

Read access to audit logs files is limited to those with a job-related need.

10.3.2

Audit log files are protected to prevent modifications by individuals.

10.3.3

Audit log files, including those for external-facing technologies, are promptly backed up to a secure, central, internal log server(s) or other media that is difficult to modify.

10.3.4

File integrity monitoring or change-detection mechanisms is used on audit logs to ensure that existing log data cannot be changed without generating alerts.

10.4

Audit logs are reviewed to identify anomalies or suspicious activity.

10.4.1

The following audit logs are reviewed at least once daily: - All security events. - Logs of all system components that store, process, or transmit CHD and/or SAD. - Logs of all critical system compone...

10.4.1.1

Automated mechanisms are used to perform audit log reviews.

10.4.2

Logs of all other system components (those not specified in Requirement 10.4.1) are reviewed periodically.

10.4.2.1

The frequency of periodic log reviews for all other system components (not defined in Requirement 10.4.1) is defined in the entity’s targeted risk analysis, which is performed according to all element...

10.4.3

Exceptions and anomalies identified during the review process are addressed.

10.5

Audit log history is retained and available for analysis.

10.5.1

Retain audit log history for at least 12 months, with at least the most recent three months immediately available for analysis.

10.6

Time-synchronization mechanisms support consistent time settings across all systems.

10.6.1

System clocks and time are synchronized using time-synchronization technology.

10.6.2

Systems are configured to the correct and consistent time as follows: - One or more designated time servers are in use. - Only the designated central time server(s) receives time from external sources...

10.6.3

Time synchronization settings and data are protected as follows: - Access to time data is restricted to only personnel with a business need. - Any changes to time settings on critical systems are logg...

10.7

Failures of critical security control systems are detected, reported, and responded to promptly.

10.7.1

Additional requirement for service providers only: Failures of critical security control systems are detected, alerted, and addressed promptly, including but not limited to failure of the following cr...

10.7.2

Failures of critical security control systems are detected, alerted, and addressed promptly, including but not limited to failure of the following critical security control systems: - Network security...

10.7.3

Failures of any critical security controls systems are responded to promptly, including but not limited to: - Restoring security functions. - Identifying and documenting the duration (date and time fr...

11.1

Processes and mechanisms for regularly testing security of systems and networks are defined and understood.

11.1.1

All security policies and operational procedures that are identified in Requirement 11 are: - Documented. - Kept up to date. - In use. - Known to all affected parties.

11.1.2

Roles and responsibilities for performing activities in Requirement 11 are documented, assigned, and understood.

11.2

Wireless access points are identified and monitored, and unauthorized wireless access points are addressed.

11.2.1

Authorized and unauthorized wireless access points are managed as follows: - The presence of wireless (Wi-Fi) access points is tested for, - All authorized and unauthorized wireless access points are...

11.2.2

An inventory of authorized wireless access points is maintained, including a documented business justification.

11.3

External and internal vulnerabilities are regularly identified, prioritized, and addressed.

11.3.1

Internal vulnerability scans are performed as follows: - At least once every three months. - High-risk and critical vulnerabilities (per the entity’s vulnerability risk rankings defined at Requirement...

11.3.1.1

All other applicable vulnerabilities (those not ranked as high-risk or critical per the entity’s vulnerability risk rankings defined at Requirement 6.3.1) are managed as follows: - Addressed based on...

11.3.1.2

Internal vulnerability scans are performed via authenticated scanning as follows: - Systems that are unable to accept credentials for authenticated scanning are documented. - Sufficient privileges are...

11.3.1.3

Internal vulnerability scans are performed after any significant change as follows: - High-risk and critical vulnerabilities (per the entity’s vulnerability risk rankings defined at Requirement 6.3.1)...

11.3.2

External vulnerability scans are performed as follows: • At least once every three months. • By a PCI SSC Approved Scanning Vendor (ASV). • Vulnerabilities are resolved and ASV Program Guide requireme...

11.3.2.1

External vulnerability scans are performed after any significant change as follows: - Vulnerabilities that are scored 4.0 or higher by the CVSS are resolved. - Rescans are conducted as needed. - Scans...

11.4

External and internal penetration testing is regularly performed, and exploitable vulnerabilities and security weaknesses are corrected.

11.4.1

A penetration testing methodology is defined, documented, and implemented by the entity, and includes: - Industry-accepted penetration testing approaches. - Coverage for the entire CDE perimeter and c...

11.4.2

Internal penetration testing is performed: - Per the entity’s defined methodology. - At least once every 12 months. - After any significant infrastructure or application upgrade or change. - By a qual...

11.4.3

External penetration testing is performed: - Per the entity’s defined methodology. - At least once every 12 months. - After any significant infrastructure or application upgrade or change. - By a qual...

11.4.4

Exploitable vulnerabilities and security weaknesses found during penetration testing are corrected as follows: - In accordance with the entity’s assessment of the risk posed by the security issue as d...

11.4.5

If segmentation is used to isolate the CDE from other networks, penetration tests are performed on segmentation controls as follows: - At least once every 12 months and after any changes to segmentati...

11.4.6

Additional requirement for service providers only: If segmentation is used to isolate the CDE from other networks, penetration tests are performed on segmentation controls as follows: - At least once...

11.4.7

Additional requirement for multi-tenant service providers only: Multi-tenant service providers support their customers for external penetration testing per Requirement 11.4.3 and 11.4.4.

11.5

Network intrusions and unexpected file changes are detected and responded to.

11.5.1

Intrusion-detection and/or intrusion- prevention techniques are used to detect and/or prevent intrusions into the network as follows: - All traffic is monitored at the perimeter of the CDE. - All traf...

11.5.1.1

Additional requirement for service providers only: Intrusion-detection and/or intrusion-prevention techniques detect, alert on/prevent, and address covert malware communication channels.

11.5.2

A change-detection mechanism (for example, file integrity monitoring tools) is deployed as follows: - To alert personnel to unauthorized modification (including changes, additions, and deletions) of c...

11.6

Unauthorized changes on payment pages are detected and responded to.

11.6.1

A change- and tamper-detection mechanism is deployed as follows: - To alert personnel to unauthorized modification (including indicators of compromise, changes, additions, and deletions) to the HTTP h...