text
stringlengths 106
3.99k
| source
stringclasses 1
value |
|---|---|
Payment Card Industry Data Security Standard Requirements and Testing Procedures Version 4. 0 March 2022 | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 ©2006-2022 PCI Security Standards Council, LLC. All Rights Reserved. Page ii Document Changes Date Version Description October 2008 1. 2 To introduce PCI DSS v1. 2 as “PCI DSS Requirements and Security Assessment Procedures,” eliminating redundancy between documents, and making both general and specific changes from PCI DSS Security Audit Procedures v1. 1. For complete information, see PCI Data Security Standard Summary of Changes from PCI DSS Version 1. 1 to 1. 2. July 2009 1. 2. 1 Add sentence that was incorrectly deleted between PCI DSS v1. 1 and v1. 2. Correct “then” to “than” in testing procedures 6. 3. 7. a and 6. 3. 7. b. Remove grayed-out marking for “in place” and “not in place” columns in testing procedure 6. 5. b. For Compensating Controls Worksheet-Completed Example, correct wording at top of page to say, “Use this worksheet to define compensating controls for any requirement noted as “in place” via compensating controls. ” October 2010 2. 0 Update and implemented changes from v1. 2. 1. See PCI DSS-Summary of Changes from PCI DSS Version 1. 2. 1 to 2. 0. November 2013 3. 0 Update from v2. 0. See PCI DSS-Summary of Changes from PCI DSS Version 2. 0 to 3. 0. April 2015 3. 1 Update from PCI DSS v3. 0. See PCI DSS-Summary of Changes from PCI DSS Version 3. 0 to 3. 1 for details of changes. April 2016 3. 2 Update from PCI DSS v3. 1. See PCI DSS-Summary of Changes from PCI DSS Version 3. 1 to 3. 2 for details of changes. May 2018 3. 2. 1 Update from PCI DSS v3. 2. See PCI DSS-Summary of Changes from PCI DSS Version 3. 2 to 3. 2. 1 for details of changes. March 2022 4. 0 Rename document title to “ Payment Card Industry Data Security Standard: Requirements and Testing Procedures. ” Update from PCI DSS v3. 2. 1. See PCI DSS- Summary of Changes from PCI DSS Version 3. 2. 1 to 4. 0 for details of changes. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page iii Table of Contents 1 Introduction and PCI Data Security Standard Overview ................................................................................................................................... 1 2 PCI DSS Applicability Information ....................................................................................................................................................................... 4 3 Relationship between PCI DSS and PCI SSC Software Standards .................................................................................................................. 7 4 Scope of PCI DSS Requireme nts......................................................................................................................................................................... 9 5 Best Practices for Implementing PCI DSS into Business-as-Usual Processes ............................................................................................ 19 6 For Assessors: Sampling for PCI DSS Assessments...................................................................................................................................... 22 7 Description of Timeframes Used in PCI DSS Requirements .......................................................................................................................... 25 8 Approaches for Implementing and Validating PCI DSS .................................................................................................................................. 28 9 Protecting Information About an Entity's Security Posture ........................................................................................................................... 31 10 Testing Methods for PCI DSS Requirements .................................................................................................................................................... 32 11 Instructions and Content for Report on Compliance ....................................................................................................................................... 33 12 PCI DSS Assessment Process ........................................................................................................................................................................... 34 13 Additional References ......................................................................................................................................................................................... 35 14 PCI DSS Versions ................................................................................................................................................................................................ 36 15 Detailed PCI DSS Requirements and Testing Procedures .............................................................................................................................. 37 Build and Maintain a Secure Network and Systems ............................................................................................................................................. 39 Protect Account Data ............................................................................................................................................................................................. 73 Maintain a Vulnerability Management Program .................................................................................................................................................. 111 Implement Strong Access Control Measures ...................................................................................................................................................... 149 | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page iv Regularly Monitor and Test Networks ................................................................................................................................................................. 212 Maintain an Information Security Policy .............................................................................................................................................................. 259 Appendix A Additional PCI DSS Requirements ............................................................................................................................................. 298 Appendix A1: Additional PCI DSS Requirements for Multi-Tenant Service Providers ........................................................................................ 298 Appendix A2: Additional PCI DSS Requirements f or Entities Using SSL/Early TLS for Card-Present POS POI Terminal Connections .......... 304 Appendix A3: Designated Entities Supplemental Validation (DESV) .................................................................................................................. 308 Appendix B Compensating Controls ............................................................................................................................................................... 330 Appendix C Compensating Controls Worksheet ........................................................................................................................................... 332 Appendix D Customized Approach ................................................................................................................................................................. 333 Appendix E Sample Templates to Support Customized Approach ............................................................................................................. 335 Appendix F Leveraging the PCI Software S ecurity Framework to Support Requirement 6 ..................................................................... 341 Appendix G PCI DSS Glossary of Terms, Abbreviations, and Acronyms ................................................................................................... 344 | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Stan dards Council, LLC. All rights reserved. Page 1 1 Introduction and PCI Data Security Standard Overview The Payment Card Industry Data Security Standard (PCI DSS) was developed to encourage and enhance payment card account data security and facilitate the broad adoption of consistent data security measures globally. PCI DSS provides a baseline of technical and operational requirements designed to protect account data. While specifically designed to focus on environments with payment card account data, PCI DSS can also be used to protect against threats and secure other elements in the payment ecosystem. Table 1 shows the 12 principal PCI DSS requirements. Table 1. Principal PCI DSS Requirements PCI Data Security Standard-High Level Overview Build and Maintain a Secure Network and Systems 1. Install and Maintain Network Security Controls. 2. Apply Secure Configurations to All System Components. Protect Account Data 3. Protect Stored Account Data. 4. Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks. Maintain a Vulnerability Management Program 5. Protect All Systems and Networks from Malicious Software. 6. Develop and Maintain Secure Systems and Software. Implement Strong Access Control Measures 7. Restrict Access to System Components and Cardholder Data by Business Need to K now. 8. Identify Users and Authenticate Access to S ystem Components. 9. Restrict Physical Access to C ardholder Data. Regularly Monitor and Test Networks 10. Log and Monitor All Access to System Components and Cardholder Data. 11. Test Security of S ystems and Networks Regularly. Maintain an Information Security Policy 12. Support Information Security with Organizational Policies and Programs. This document, the Payment Card Industry Data Security Standard Requirements and Testing Procedures, consists of the 12 PCI DSS principal requirements, detailed security requirements, corresponding testing procedures, and other information pertinent to each requirement. The following sections provide detailed guidelines and best practices to assist entities to prepare for, conduct, and report the results of a PCI DSS assessment. The PCI DSS requirements and testing procedures begin on page 43. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 2 PCI DSS comprises a minimum set of requirements for pr otecting account data and may be enhanced by additional controls and practices to further mitigate risks, and to incorporate local, regional, and sector laws and regulations. Additionally, legislation or regulatory requirements may require specific protect ion of personal information or other data elements (for example, cardholder name). Limitations If any of the requirements contained in this standard conflict with country, state, or local laws, the country, state, or loc al law will apply. PCI DSS Resource s The PCI Security Standards Council (PCI SSC) website ( www. pcisecuritystandards. org) provides the following additional resources to assist organizations with their PCI DSS assessments and validations: Document Library, including: -PCI DSS Summary of Changes -PCI DSS Quick Reference Guide -Information Supplements and Guidelines -Prioritized Approach for PCI DSS -Report on Compliance ( ROC) Reporting Template and Reporting Instructions -Self-Assessment Questionnaires (SAQs) and SAQ Instructions and Guidelines -Attestations of Compliance (AOCs ) Frequently Asked Questions (FAQs) PCI for Small Merchants website PCI training courses and infor mational webinars List of Qualified Security Assessors (QSAs) and Approved Scanning Vendors ( ASVs ) Lists of PCI approved devices, applications, and solutions | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 3 There are over 60 guidance documents and information supplements available on the PCI SSC website that provide specific guidance and considerations for PCI DSS. Examples include: Guidance for PCI DSS Scoping and Network Segmentation PCI SSC Cloud Computing Guidelines Multi-Factor Authentication Guidance Third-Party Security Assurance Effective Daily Log Monitoring Penetration Testing Guidance Best Practices for Implementing a Security Awareness Program Best Practices for Maintaining PCI DSS Compliance PCI DSS for Large Organizations Use of SSL/Early TLS and Impact on ASV Scans Use of SSL/Early TLS for POS POI Terminal Connections Tokenization Product Security Guidelines Protecting Telephone-Based Payment Card Data Refer to the Document Library at www. pcisecuritystandards. org for information about these and other resources. In addition, r efer to Appendix G for definitions of PCI DSS terms. Note : Information Supplements complement PCI DSS and identify additional considerations and recommendations for meeting PCI DSS requirements. Information Supplements do not supersede, replace, or extend PCI DSS or any of its requirements. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 4 2 PCI DSS Applicability Informatio n PCI DSS is intended for all entities that store, process, or transmit cardholder data (CHD) and/or sensitive authentication data (SAD) or could impact the security of the cardholder data environment (CDE). This includes all entities involved in payment c ard account processing — including merchants, processors, acquirers, issuers, and other service providers. Whether any entity is required to comply with or validate their compliance to PCI DSS is at the discretion of those organizat ions that manage complia nce programs (such as payment brands and acquirers). Contact the organizations of interest for any additional criteria. Defining Account Data, Cardholder Data, and Sensitive Authentication Data Cardholder data and sensitive authentication data are consider ed account data and are defined as follows: Table 2. Account Data Account Data Cardholder Data includes: Sensitive Authentication Data includes : Primary Account Number (PAN) Cardholder Name Expiration Date Service Code Full track data (magnetic-stripe data or equivalent on a chip) Card verification code PINs/PIN blocks PCI DSS requirements apply to entities with environments where account data (cardholder data and/or sensitive authentication data) is stored, processed, or transmitted, and entities with environments that can impact the security of the CDE. Some PCI DSS requirements may also apply to entities with environments that do not store, process, or transmit account data-for example, entities that outsource payment operations or management of their CDE1. Entities that outsource their payment environments or payment operations to third parties remain responsible for ensuring that the account data is protected by the third party per applicable PCI DSS requirements. The primary account number (PAN) is the defining factor for cardholder data. The term account data therefore covers the following: the full PAN, any other elements of cardholder data that are present with the PAN, and any elements of sensitive authentic ation data. 1 In accordance with those organizations that manage compliance programs (such as payment brands and acquirers) ; entities should contact the organizations of interest for more details. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 5 If cardholder name, service code, and/or expiration date are stored, processed, or transmitted with the PAN, or are otherwise present in the CDE, they must be protected in accordance with the PCI DSS requirements applicable to cardholder data. If an entity stores, processes, or transmits PAN, then a CDE exists to which PCI DSS requirements will apply. Some requirements may not be applicable, for example if the entity does not store PAN, then the requirements relating to the protection of stored PAN in Requirement 3 will not be applicable to the entity. Even if an entity does not store, process, or transmit PAN, some PCI DSS requirements may still apply. Consider the following : If the entity stores SAD, requirements specifically related to SAD storage in Requirement 3 will be applicable. If the entity engages third-party service providers to store, process or transmit PAN on its behalf, requirements related to the management of service providers in Requirement 12 will be applicable. If the entity can impact the security of a CDE because the security of an entity's infrastructure can affect how cardholder data is processed (for example, via a web server that controls the generation of a payment form or page) some requirements will be applicab le. If cardholder data is only present on physical media (for example paper), requirements relating to the security and disposal of physical media in Requirement 9 will be applicable. Requirements related to an incident response plan are applicable to all entities, to ensure that there are procedures to follow in the event of a suspected or actual breach of the confidentiality of cardholder data. Use of Account Data, Sensitive Authentication Data, Cardholder Data, and Primary Account Number in PCI DSS PCI D SS includes requirements that specifically refer to account data, cardholder data, and sensitive authentication data. It is i mportant to note that each of these types of data are different and the terms are not interchangeable. Specific references within r equirements to account data, cardholder data, or sensitive authentication data are purposeful, and the requirements apply specifically to the type of data that is referenced. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 6 Elements of Account Data and Storage Requirements Table 3 identifies the elements of cardholder and sensitive authentication data, whether storage of each data element is permitted or prohibited, and whether each data element must be rendered unreadable—for example, with strong cryptography —when stored. This table is not exhaustive and is presented to illustrate only how the stated requirements apply to the different data elements. Table 3. Account Data Element Storage Requirements Data Elements Storage Restrictions Required to Render Stored Data Unreadable Account Data Cardholder Data Primary Account Number (PAN) Storage is kept to a minimum as defined in Requirement 3. 2 Yes, as defined in Requirement 3. 5 Cardholder Name Storage is kept to a minimum as defined in Requirement 3. 22 No Service Code Expiration Date Sensitive Authentication Data Full Track Data Cannot be stored after authorization as defined in Requirement 3. 3. 13 Yes, data stored until authorization is complete must be protected with strong cryptography as defined in Requirement 3. 3. 2 Card verification code PIN/PIN Block If PAN is stored with other elements of cardholder data, only the PAN must be rendered unreadable according to PCI DSS Requir ement 3. 5. 1. Sensitive authentication data must not be stored after authorization, even if encrypted. This applies even for environments where there is no PAN present. 2 Where data exists in the same environment as PAN. 3 Except as permitte d for issuers and companies that support issuing services. Requirements for issuers and issuing services are separately defined in Requirement 3. 3. 3. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 7 3 Relationship between PCI DSS and PCI SSC Software Standards PCI SSC supports the use of secure payment software within cardholder data environments (CDE) via the Payment Application Dat a Security Standard (PA-DSS) and the Software Security Framework (SSF), which consists of the Secure Software Standard and the Secure Software Lifecycle (Secure SLC) Standard. Software that is PCI SSC validated and listed provides assurance that the software has been developed using secure practices and has met a defined set of software security requirements. The PCI SSC secure software programs include listings of payment software and software vendors that have been validated as meeting the applicable PCI SSC Software Standards. Validated Software : Payment software listed on the PCI SSC website as a Validated Payment Application (PA-DSS) or Validated Payment Software (the Secure Software Standard) has been evaluated by a qualified assessor to confirm the software meets the security requirements within that standard. The security requirements in these standards are focused on protecting the integrity and confidentiality of p ayment transactions and account data. Validated Software Vendors : The Secure SLC Standard defines security requirements for software vendors to integrate secure software development practices throughout the entire software lifecycle. Software vendors that have been validated as meeting the Secure SLC Standard are listed on the PCI SSC website as a Secure SLC Qualified Vendor. For more information about the SSF or PA-DSS, refer to the respective Program Guides at www. pcisecuritystandards. org. All software that stores, processes, or transmits account data, or that could impact the security of account data or a CDE, i s in scope for an entity's PCI DSS assessment. While the use of validated payment software supports the security of an entity's CDE, the use of such software does not by itself make an entity PCI DSS compliant. The entity's PCI DSS assessment should include verification that the sof tware is properly configured and securely implemented to support applicable PCI DSS requirements. Additionally, if PCI-listed payment software has been customized, a more in-depth review will be required during the PCI DSS assessment because the software may no longer be representative of the version that was originally validated. Because security threats ar e constantly evolving, software that is no longer supported by the vendor (for example, identified by the vendor as “end of life”) may not offer the same level of security as supported versions. Entities are strongly encouraged to keep their software current and updated to the latest software versions available. Entities that develop their own software are encouraged to refer to PCI SSC's software security standards and consider the requirements therein as best practices to use in their development environments. Secure payment software implemented in a PCI DSS compliant environment will help minimize the potential for security breaches leading to compromises of account data and fraud. See Bespoke and Custom Software. Note : PA-DSS and the rel ated program will be retired in October 2022. Refer to the PCI SSC List of Validated Payment Applications for expiry dates for PA-DSS validated applications. After the expiry date, applications are listed as “Acceptable only for Pre-Existing Deployments. ” Whether an entity can continue to use a PA-DSS application with an expired listing is at the discretion of organizations that manage compliance programs (such as payment brands and acquirers ); entities should contact the organizations of interest for more details. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 8 Applicability of PCI DSS to Payment Software Vendors PCI DSS may apply to a payment software vendor if the vendor is also a service provider that stores, process es, or transmit s account data, or has access to their customers' account data —for example, in the role of a payment service provider or via remote access to a customer environment. Software vendors to which PCI DSS may be applicable include those offering payment services, as well as cloud service providers offering payment terminals in the cloud, software as a service (Saa S), e-commerce in the cloud, and other cloud payment services. Bespoke and Custom Software All bespoke and custom software that stores, processes, or transmits account data, or that could impact the security of account data or a CDE, is in scope for an entity's PCI DSS assessment. Bespoke and custom software that has been developed and maintained in accordance with one of PCI SSC's Software Security Framework standards (the Secure Software Standard or the Secure SLC standard) will support an entity in meeting PCI DSS Requirement 6. See Appendix F for more details. Note : PCI DSS Requirement 6 fully applies to bespoke and custom software that has not been developed and maintained in accordance with one of PCI SSC's Software Security Framework standards. Entities that use software vendors to develop bespoke or custom software that could impact the security of account data or their CDE are responsible for ensuring those software vendors develop the software according to PCI DSS Requirement 6. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 9 4 Scope of PCI DSS Requirements PCI DSS requirements apply to: The cardholder data environment (CDE), which is comprised of: -System components, people, and processes that store, process, and transmit cardholder data and/or sensitive authentication data, and, -System components that may not store, process, or transmit CHD/SAD but have unrestricted connectivity to system components that store, process, or transmit CHD/SAD. AND System components, people, and processes that could impact the security of the CDE. 4 “System components” include network devices, servers, computing devices, virtual components, cloud components, and software. Examples of system components include but are not limited to: Systems that store, process, or transmit account data (for example, payment terminals, authorization systems, clearing systems, payment middleware systems, payment back-office systems, shopping cart and store front systems, payment gate way/switch systems, fraud monitoring systems). Systems that provide security services (for example, authentication servers, access control servers, security information and event management (SIEM) systems, physical security systems (for example, badge acc ess or CCTV), multi-factor authentication systems, anti-malware systems). Systems that facilitate segmentation (for example, internal network security controls). Systems that could impact the security of account data or the CDE (for example, name resolutio n, or e-commerce (web) redirection servers). Virtualization components such as virtual machines, virtual switches/routers, virtual appliances, virtual applications /desktops, and hypervisors. Cloud infrastructure and components, both external and on premises, and including instantiations of containers or images, virtual private clouds, cloud-based identity and access management, CDEs residing on premises or in the cloud, service meshes with containerized applications, and container orchestration tools. 4 For additional guidance, refer to Information Supplement: Guidance for PCI DSS Scoping and Network Segmentation on the PCI SSC website. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 10 Network components, including but not limited to network security controls, switches, routers, Vo IP network devices, wireless access points, network appliances, and other security appliances. Server types, including but not limited to web, application, database, authentication, mail, proxy, Network Time Protocol (NTP), and Domain Name System (DNS). End-user devices, such as computers, laptops, workstations, administrative workstations, tablets, and mobile devices. Printers, and multi-function devices that scan, print, and fax. Storage of account data in any format (for example, paper, data files, audio files, images, and video recordings). Applications, software, and software components, serverless applications, including all purchased, subscribed (for example, S oftware-as-a-Service), bespoke and custom software, including internal and external (for example, Internet) applications. Tools, code repositories, and systems that implement software configuration management or for deployment of objects to the CD E or to systems that can impact the CDE. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 11 Figure 1 shows considerations for scoping system components for PCI DSS. Figure 1. Understanding PCI DSS Scoping | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 12 Annual PCI DSS Scope Confirmation The first step in preparing for a PCI DSS assessment is for the entity to accurately determine the scope of the review. The assessed entity must confirm the accuracy of their PCI DSS scope according to PCI DSS Requirement 12. 5. 2 by identifying all locations and flows of account data, and identifying all systems that are connected to or, if compromised, could impact the CDE (for example, authentication servers, remote access servers, logging servers) to ensure they are included in the PCI DSS sc ope. All types of systems and locations should be considered during the scoping process, including backup/recovery sites and fail-over systems. The minimum steps for an entity to confirm the accuracy of their PCI DSS scope are specified in PCI DSS Requirement 12. 5. 2. The entity is expected to retain documentation to show how PCI DSS scope was determined. The documentation is retained for assessor review and for reference during the entity's next PCI DSS scope confirmation activity. For each PCI DSS assessment, the assessor validates that the entity accurately defined and documented the scope of the assessment. Note : This annual confirmation of PCI DSS scope is defined at PCI DSS Requirement at 12. 5. 2 and is an activity expected to be per formed by the entity. This activity is not the same, nor is it intended to be replaced by, the scoping confirmation performed by the entity's ass essor during the assessment. Segmentation Segmentation (or isolation) of the CDE from the remainder of an entity's network is not a PCI DSS requirement. However, it is strongly recommended as a method that may reduce the: Scope of the PCI DSS assessment Cost of the PCI DSS assessment Cost and difficulty of implementing and maintaining PCI DSS controls Risk to an organization relative to payment card account data (reduced by consolidating that data into fewer, more controlled locations) Without adequate segmentation (sometimes called a "flat network"), the entire network is in scope for the PCI DSS assessment. S egmentation can be achiev ed using a number of physical or logical methods, such as properly configured internal network security controls, routers wit h strong access control lists, or other technologies that restrict access to a particular segment of a network. To be considere d out of scope for PCI DSS, a system component must be properly segmented (isolated) from the CDE, such that the out-of-scope system component could not impact the security of the CDE, even if that component was compromised. An important prerequisite to reduce the scope of the CDE is a clear understanding of business needs and processes related to the storage, processing, and transmission of account data. Restricting account data to as few locations as possible by eliminating unneces sary data and consolidating necessary data may require reengineering of long-standing business practices. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 13 Documenting account data flows via a data-flow diagram helps an entity fully understand how account data comes into an organization, where it resides within the organization, and how it traverses through various systems within the organization. Data-flow diagrams also illustrate all locations where account data is stored, processed, and transmitted. This information supports an entity implementing segmentation and can also support confirming that segmentation is being used to isolate the CDE from out-of-scope networks. If segmentation is used to reduce the scope of the PCI DSS assessment, the assessor must verify that the segmentation is adequate to reduce the scope of the assessment, as illustrated in Figure 2. At a high level, adequate segmentation isolates systems that store, process, or transmit account data from those that do not. However, the adequacy of a specific segmentation implementation is highly variable and depends on several factors such as a given network's configuration, the technologies deployed, and other controls that may be implemented. Figure 2. Segmentation and Impact to PCI DSS Scope | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 14 Wireless If wireless technology is used to store, process, or transmit account data (for example, wireless point-of-sale devices), or if a wireless local area network (WLAN) is part of or connected to the CDE, the PCI DSS requirements and testing procedures for sec uring wireless environments apply and must be performed. Rogue wireless detection must be performed per PCI DSS Requirement 11. 2. 1 even when wireless is not used within the CDE and t he entity has a policy that prohibits the use of wireless technology with in its environment. This is because of the ease with which a wireless access point can be attached to a network, the difficulty in detecting its presence, and the increased risk presented by unauthorize d wireless devices. Before wireless technology is implemented, an entity should carefully evaluate the need for the technology against the risk. Consider deploying wireless technology only for non-sensitive data transmission. Encrypted Cardholder Data and Impact on PCI DSS Scope Encryption of cardholder dat a with strong cryptography is an acceptable method of rendering the data unreadable according to PCI DSS Requirement 3. 5. However, encryption alone is generally insufficient to render the cardholder data out of scope for PCI DSS and does not remove the need for PCI DSS in that environment. The entity's environment is still in scope for PCI DSS due to the presence of cardholder data. For example, for a merchant card-present environment, there is physical access to the payment cards to complete a transaction and there may also be paper reports or receipts with cardholder data. Similarly, in merchant card-not-present environments, such as mail-order/ telephone-order and e-commerce, payment card details are provided via channels that need to be evaluated and prot ected according to PCI DSS. The following are each in scope for PCI DSS: Systems performing encryption and/or decryption of cardholder data, and systems performing key management functions, Encrypted cardholder data that is not isolated from the encryption and decryption and key management processes, Encrypted cardholder data that is present on a system or media that also contains the decryption key, Encrypted cardholder data that is present in the same environment as the decryption key, Encrypted cardholder data that is accessible to an entity that also has access to the decryption key. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 15 Note : A PCI-listed P2PE solution can significantly reduce the number of PCI DSS requirements applicable to a merchant's cardholder data environment. However, it does not completely remove the applicability of PCI DSS in the merchant environment. Encrypted Cardholder Data and Impact to PCI DSS Scope for Third-Party Service Providers Where a third-party service provider (TPSP) receives and/or stores only data encrypted by another entity, and where they do not have the ability to decrypt the data, the TPSP may be able to consider the encrypted data out of scope if certain conditions are met. This is because responsibility for the data generally remains with the entity, or entities, with the ability to decrypt the data or impact the security of the encrypted data. Determining which party is responsible for specific PCI DSS controls will depend on several factors, including who has access to the decryption keys, the role performed by each party, and the agreement between parties. Responsibilities should be clearly defined and documented to ensure both the TPSP and the entity providing the encrypted data understand which entity is responsible for whi ch security controls. As an example, a TPSP providing storage services receives and stores encrypted cardholder data provided by customers for back-up purposes. This TPSP does not have access to the encryption or decryption keys, nor does it perform any key management for its customers. The TPSP can exclude any such encrypted data when determining its PCI DSS scope. However, the TPSP does maintain responsibility f or controlling access to the encrypted data storage as part of its service agreements with its customers. Responsibility for ensuring that the encrypted data and the cryptographic keys are protected according to applicable PCI DSS requirements is often shared between entities. In the above example, the customer determines which of their personnel are authorized to acces s the storage media, and the storage facility is responsible for managing the physical and/or logical access controls to ensure that only persons authorized by the customer are granted access to the storage media. The specific PCI DSS requirements applicable to a TPSP will depend on the services provided and the agreement between the two parties. In the example of a TPSP providing storage services, the physical and logical access controls provided by the TPSP will need to be reviewed at least annually. This review could be performed as part of the merchant's PCI DSS assessment or, alternatively, the review could be performed, and controls validated, by the TPSP with appropriate evidence provided to the merchant. For information about “appropriate evidence, ” see Options for TPSPs to Validate PCI DSS Compliance for TPSP Services that Meet Customers' PCI DSS Requirements. As another example, a TPSP that receives only encrypted cardholder data for the purposes of routing to other entities, and that does not have access to the data or cryptographic keys, may not have any PCI DSS responsibility for that encrypted data. In this scenario, where the TPSP is not providing any security services or access controls, they may be considered t he same as a public or untrusted network, and it would be the responsibility of the entity(s) sending/receiving account data through the TPSP's network to ensure PCI DSS controls are applied to protect the data being transmitted. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 16 Use of Third-Party Service Providers An entity (referred to as the “customer” in this section) might cho ose to use a third-party service provider (TPSP) to store, process, or transmit account data or to manage in-scope system components on the customer's behalf. Use of a TPSP may h ave an impact on the security of a customer's CDE. Note : Use of a PCI DSS compliant TPSP does not make a customer PCI DSS compliant, nor does it remove the customer's responsibility for its own PCI DSS compliance. Even if a customer uses a TPSP to meet all account data functions, that customer remains responsible for confirming its own compliance as requested by organizations that manage compliance programs (for example, payment brands and acquirers ). Customers should contact the organizations of interes t for any requirements. Using TPSPs and the I mpact on Customers Meeting PCI DSS Requirement 12. 8 There are many different scenarios where a customer might use one or more TPSPs for functions within or related to the customer's CDE. In all scenarios where a TPSP is used, the customer must manage and oversee the PCI DSS compliance status of all their TPSPs in accordance with Requirement 12. 8, including TPSPs that: Have access to the customer's CDE, Manage in-scope system components on the customer's behalf, and/or Can impact the security of the customer's CDE. Managing TPSPs in accordance with Requirement 12. 8 includes performing due diligence, having appropriate agreements in place, identifying which requirements apply to the customer and which apply to t he TPSP, and monitoring the compliance status of TPSPs at least annually. Requirement 12. 8 does not specify that the customer's TPSPs must be PCI DSS compliant, only that the customer monitor their compliance status as specified in the requirement. Theref ore, a TPSP do es not need to be PCI DSS compliant for its customer to meet Requirement 12. 8. Impact of U sing TPSPs for S ervices that Meet Customers' PCI DSS R equirements When the TPSP provides a service that meets a PCI DSS requirement(s) on the customer's behalf or where that service may impact the security of the customer's CDE, then those requirements are in scope for the customer's assessment and the compliance of that service will impact t he customer's PCI DSS compliance. The TPSP must demonstrate it meets applicable PCI DSS requirements for those requirements to be in place for its customers. For example, if an entity engages a TPSP to manage its network security controls, and the TPSP doe s not provide evidence that it meets the applicable requirements in PCI DSS Requirement 1, then those requirements are not in place for the customer's assessment. As another example, TPSPs that store backups of cardholder data on behalf of customer s | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 17 would need to meet the applicable requirements related to access controls, physical security, etc., for their customers to consider those requirements in place for their assessments. Importance of U nderstanding Responsibilities Between TPSP Customers and TPSPs Customers and TPSPs should clearly identify and understand the following: The services and system components included in the scope of the TPSP's PCI DSS assessment, The specific PCI DSS requirements and sub-requirements covered by the TPSP's PCI DSS asses sment, Any requirements that are the responsibility of the TPSP's customers to include in their own PCI DSS assessments, and Any PCI DSS requirements for which the responsibility is shared between the TPSP and its customers. For example, a cloud provider should clearly define which of its IP addresses are scanned as part of its quarterly vulnerability scan process and which IP addresses are their customers' responsibility to scan. Per Requirement 12. 9. 2, TPSPs are required to support their customers' requests for information about the TPSP's PCI DSS compliance status related to the services provided to customers, and about which PCI DSS requirements are the responsibility of the TPSP, which are the responsibility of the customer, and any responsibilities between the customer and the TPSP. Refer to Tips and Tools for Understanding PCI DSS v4. 0 for a responsibility matrix template that may be used for documenting and clarifying how responsibilities are shared between TPSPs and customers. Options for TPSPs to Validate PCI DSS C ompliance for TPSP S ervices that Meet Customers' PCI DSS Requirements TPSPs are responsible for demonstrating their PCI DSS compliance as requested by organizations that manage compliance programs (for example, payment brands and acqui rers). TPSPs should contact the organizations of interest for any requirements. When a TPSP provides services that are intended to meet or facilitate meeting a customer's PCI DSS requirements or that may i mpact the security of a customer's CDE, these requi rements are in scope for the customer's PCI DSS assessments. There are two options for TPSPs to validate compliance in this scenario: Annual assessment : TPSP u ndergoes an annual PCI DSS assessment(s) and provides evidence to its customers to show the TPSP meets the applicable PCI DSS requirements; or Multiple, on-demand assessments: If a TPSP do es not undergo an annual PCI DSS assessment, it must undergo assessments upon request of their customers and/or participate in each of its customers ' PCI DSS assessments, with the results of each review provided to the respective customer(s). | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 18 If the TPSP undergoes its own PCI DSS assessment, it is expected to provide sufficient evidence to its customers to verify that the scope of the TPSP's PCI DSS as sessment covered the services applicable to the customer, and that the relevant PCI DSS requirements were examined and determined to be in place. If the provider has a n PCI DSS Attestation of Compliance ( AOC ), it is expected that the TPSP provides the AOC to customers upon request. The customer may also request relevant sections of the TPSP's PCI DSS Report on Compliance (ROC). The ROC may be redacted to protect any confidential information. If the TPSP does not undergo its own PCI DSS assessment and theref ore does not have an AOC, the TPSP is expected to provide specific evidence related to the applicable PCI DSS requirements, so that the customer (or its assessor) is able to confirm t he TPSP is meeting those PCI DSS requirements. TPSPs Presence on a P aymen t Brand List(s) of PCI DSS C ompliant Service Providers For a customer that is monitoring a TPSP's compliance status in accordance with Requirement 12. 8, the TPSP's presence on a payment brand's list of PCI DSS compliant service providers may be sufficient evidence of the TPSP's compliance status if it is clear from the list that the services applicable to the customer were covered by the TPSP's PCI DSS assessment. If it is not clear from the list, the customer should obtain other written confirmation that addresses the TPSP's PCI DSS compliance status. For a customer that is looking for evidence of PCI DSS compliance for requirements that a TPSP meets on a customer's behalf or where t he service provided can impact the security of the customer's CDE, the TPSP's presence on a payment brand's list of PCI DSS compl iant service providers is not sufficient evidence that the applicable PCI DSS requirements for that TPSP were included in the assessment. If the TPSP has an PCI DSS AOC, it is expected to provide it to customers upon request. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 19 5 Best Practices for Implementing PCI DSS into Business-as-Usual Processes An ent ity that implements business-as-usual processes, otherwise known as BAU, as part of their overall security strategy is taking measures to ensure that security controls that have been implemented to secure data and an environment continue to be implemented correctly and functioning properly as normal course of business. Some PCI DSS requirements are intended to act as BAU processes by monitoring security controls to ensure their effectiveness on an ongoing basis. This oversight by the entity assists with providing reasonable assurance that the compliance of its environment is preserved between PCI DSS assessments. While there are currently some BAU requirements defined within the standard, an entity should ad opt additional BAU processes specific to their organization and environment when possible. BAU processes are a way to verify that automated and manual controls are performing as expected. Regardless of whether a PCI DSS requirement is automated or manual, it is imp ortant for BAU processes to detect anomali es, and alert and report so that responsible individuals address the situation in a timely manner. Examples of how PCI DSS should be incorporated into BAU activities include but are not limited to: Assigning overall responsibility and accountability for P CI DSS compliance to an individual or team. This can include a charter defined by executive management for a specific PCI DSS compliance program and communication to executive management. Developing performance metrics to measure the effectiveness of secur ity initiatives and continuous monitoring of security controls, including those that are heavily relied upon, such as network security controls, intrusion-detection systems/intrusion-prevention systems (IDS/IPS), change-detection mechanisms, anti-malware solutions, and access controls, to ensure they are operating effectively and as intended. Reviewing logged data more frequently to gain insights to trends or behaviors that may not be obvious with only monitoring. Ensuring that all failures in security cont rols are detected and responded to promptly. Processes to respond to security control failures should include: -Restoring the security control. -Identifying the cause of failure. -Identifying and addressing any security issues that arose during the failure of the security control. -Implementing mitigation, such as process or technical controls, to prevent the cause of the failure from recurring. -Resuming monitoring of the security control, perhaps with enhanced monitoring for a period of time, to verify the control is operating effectively. Reviewing changes that could introduce security risks to the environment (for example, addition of new systems, changes in system or network configurations) prior to completing the change, and including the following: | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 20 -Perform a risk assessment to determine the potential impact to PCI DSS scope (for example, a new network security control rule that permits connectivity between a system in the CDE and another system could bring additional systems or networks into scop e for PCI D SS). -Identify PCI DSS requirements applicable to systems and networks affected by the changes (for example, if a new system is in scope for PCI DSS, it would need to be configured per system configuration standards, including change-detection mechanisms, anti-malware software, patches, and audit logging. These new systems and networks would need to be added to the inventory of in-scope system components and to the quarterly vulnerability scan schedule). -Update PCI DSS scope and implement security controls as appropriate. -Update documentation to reflect implemented changes. Reviewing the impact to PCI DSS scope and requirements upon changes to organizational structure (for example, a company merger or acquisition). Reviewing external connections and third-party access periodically. For entities that use third parties for software development, periodically confirming that those software development activit ies continue to comply with software development requirements in Requirement 6. Performing periodic review s to confirm that PCI DSS requirements continue to be in place and personnel follow established processes. Periodic reviews should cover all facilities and locations, including retail outlets and data centers, whether self-managed or if a TPSP is used. For example, periodic reviews can be used to confirm that configuration standards have been applied to applicable systems, default vendor accounts and passwords are removed or disabled, patches and anti-malware solutions are up to date, audit logs are being r eviewed, and so on. The frequency of periodic reviews should be determined by the entity as appropriate for the size and complexity of their environment, if not otherwise stated in PCI DSS. These reviews can also be used to verify that required evidence f or a PCI DSS assessment is being maintained. For example, evidence of audit logs, vulnerability scan reports, and reviews of network security control rulesets are necessary to assist the entity in preparing for its next PCI DSS assessment. Establishing com munication with all impacted parties, both external and internal, about newly identified threats and changes to the organization structure. Communication materials should help recipients understand the impact of threats, mitigating steps, and contact point s for further information or escalation. Reviewing hardware and software technologies at least once every 12 months to confirm that they continue to be supported by t he vendor and can meet the entity's security requirements, including PCI DSS. If technologies are no longer supported by the vendor or cannot meet the entity's security needs, the entity should prepare a remediation plan, including replacement of the technology, as necessary. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 21 Note : Some best practices in this section are also included as PCI DSS requirements for certain entities. For example, those undergoing a full PCI DSS assessment, service providers validating to the additional “service provider only” requirements, and designated entities that are required to validate according to Appendix A3: Designated Entities Supplemental Validation. Each entity should consider implementing these best practices into their environment, even if the entity is not required to validate to them (for example, merchants undergoing self-assessment). Refer to Best Practices for Maintaining PCI DSS Compliance in the Document Library on the PCI SSC website for additional guidance. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 22 6 For Assessors: Sampling for PCI DSS Assessments Sampling is an option for a ssessors conducting PCI DSS assessments to facilitate the assessment process when there are large numbers of items in a population being tested. While it is acceptable for an assessor to sample from similar items in a population being tested as part of it s review of an entity's PCI DSS compliance, it is not acceptable for an entity to apply PCI DSS requirements to only a sample of its environment (for example, requirements for quarterly vulnerability scans apply to all system components). Similarly, it is not acceptable for an assessor to review only a sample of PCI DSS requirements for compliance. While sampling allows assessors to test less than 100% of a given sampling population, assessors should always strive for the most complete review possible. Assessors are encouraged to use automated processes or other mechanisms if the complete population, regardless of size, can be tested quickly and efficiently with minimal impact on the resources of the entity being assessed. Where automated proc esses are not available to test 100% of a population, sampling is an equally acceptable approach. After considering the overall scope, complexity, and consistency of the environment being assessed, and the nature (automated or manual) of the processes used by an entity t o meet a requirement, the assessor may independently select representative samples from the populations being reviewed in order to assess the entity's compliance with PCI DSS requirements. Samples must be a representative selecti on of all variants of the population and must be sufficiently large to provide the assessor with assurance that controls are implemented as expected across the entire population. Where testing the periodic performance of a requirement (for example, weekly or quarterly, or p eriodically), the assessor should attempt to select a sample that represents the entire period covered by the assessment so that the assessor may make a reasonable judgment that the requirement was met throughout the assessment period. Testing the same sample of it ems year after year could allow unknown variations in the non-sampled items to remain undetected. Assessors must revalidate the sampling rationale for each assessment and consider previous sample sets. Different samples must be selected for each assessment. Appropriate selection of the sample depends on what is being considered in examining the sample members. For example, determi ning the presence of anti-malware on servers known to be affected by malicious software may lead to determining the population to be all servers in the environment, or all servers in the environment that are running a particular operating system, or all servers that are not mainframes, etc. Selection of an appropriate sample would then include representatives of ALL members of the i dentified population, including all servers running the identified operating system including all versions, as well as servers within the population that are used for di fferent functions (web server, application servers, database servers, etc. ). In the cas e that a specific configuration item is being considered, the population might be appropriately divided, and separate sample groups identified. For example, a sample of all servers may not be appropriate when reviewing an operating system configuration set ting, where different operating systems are present within the environment. In this case, samples from each operating system type would b e appropriate in identifying that the configuration has been appropriately set for each operating system. Each sample s et should include servers that are representative of each operating system type, including version, as well as representative functions. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 23 Other examples of sampling include selections of personnel with similar or varied roles, based on the requirement being assessed, for example, a sample of administrators vs. a sample of all employees. The assessor is required to use professional judgment in the planning, performance, and evaluation of the sample to support t heir conclusion about whether and how the entity has met a requirement. The assessor's goal in sampling is to obtain enough evidence to have a reasonable basis for their opinion. When independently selecting samples, assessors should consider the following: The assessor must select the sample from the complete population without influence from the assessed entity. If the entity has standardized processes and controls in place that ensure consistency and which is applied to each item in t he population, the sample can be smaller than if the entity has no s tandardized processes/controls in place. The sample must be large enough to provide the assessor with reasonable assurance that items in the population adhere to the standardized processes that are applied to each item in the population. The assessor must verify that the standardized controls are implemented and working effectively. If the entity has more than one type of standardized process in place (for example, for different types of business facilities/system components), the sample must include items subject to each type of process. For example, populations could be divided into sub-populations based on characteristics that may impact the consistency of the assessed requirements, such as the use of different processes or tools. Samples would then be selected from each sub-population. If the entity has no standardized PCI DSS processes/controls in place and each item in the population is managed through non-standardized processes, the sample must be larger for the assessor to be assured that the PCI DSS requirements are appropriately applied to each item in the population. Samples of system components must include every type and combination being used. When an entity has more than one CDE, samples must include populations across all in-scope system components. For example, where applications are sampled, the sample must include all versions and platforms for each type of application. Sample sizes must always be greater than one unless there is only one item in the given population, or an automated control is used where the assessor has confirmed the control is functioning as programmed for each assessed sample population. If the assessor relies on standardized processes and controls being in place as a basis for selecting a sample, but then finds out during testing that standardized processes and controls are not in place or not operating effectively, the assessor should then incr ease the sample size to attempt to gain assurance that PCI DSS requirements are being met. For each instance where sampling is used, the assessor must: Document the rationale behind the sampling technique and sample size. Validate and document the standardized processes and controls used to determine sample size. Explain how the sample is appropriate and representative of the overall population. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 24 Figure 3 shows considerations for determining sample size. Figure 3. PCI DSS Sampling Considerations Note : In PCI DSS v4. 0, specific references to sampling have been removed from all testing procedures. These references were removed because calling out sampling only in some testing procedures may have implied that sampling was mandatory for those testing procedures (which it was not) or that sampling was only allowable where it was specifically mentioned. Assessors should select samples when it is appropriate to the population being tested, and, per above, render those decisions after considering the overall scope and comp lexity of an environment. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 25 7 Description of Timeframes Used in PCI DSS Requirements Certain PCI DSS requirements have been established with specific timeframes for activities that need to be performed consiste ntly via a regularly scheduled and repeatable proc ess. The intent is that the activity is performed at an interval as close to that timeframe as possible without exceeding it. The entity has the discretion to perform an activity more often than specified (for example, performing an activity monthly where the PCI DSS requirement specifies it be performed every three months). Table 4 outlines the frequency for the different time periods used in PCI DSS Requirements. Table 4. PCI DSS Requirement Timeframes Timeframes in PCI DSS Requirements Descriptions and Examples Daily Every day of the year (not only on business days). Weekly At least once every seven days. Monthly At least once every 30 to 31 days, or on the nth day of the month. Every three months (“quarterly”) At least once every 90 to 92 days, or on the nth day of each third month. Every six months At least once every 180 to 184 days, or on the nth day of each sixth month. Every 12 months (“annually”) At least once every 365 (or 366 for leap years) days or on the same date every year. Periodically Frequency of occurrence is at the entity's discretion and is documented and supported by the entity's risk analysis. The entity must demonstrate that the frequency is appropriate for the activity to be effective and to meet the intent of the requirement. Immediately Without delay. In real time or near real time. Promptly As soon as reasonably possible. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 26 Timeframes in PCI DSS Requirements Descriptions and Examples Significant change There are certain requirements for which performance is specified upon a significant change in an entity's environment. While what constitutes a significant change is highly dependent on the configuration of a given environment, each of the following activities, at a minimum, has potential impacts on the security of the CDE and must be considered as a significant change in the context of related PCI DSS requirements: New hardware, software, or networking equipment added to the CDE. Any replacement or major upgrades of hardware and software in the CDE. Any changes in the flow or storage of account data. Any changes to the boundary of the CDE and /or to the scope of the PCI DSS assessment. Any changes to the underlying supporting infrastructure of the CDE (inc luding, but not limited to, changes to directory services, time servers, logging, and monitoring). Any changes to third party vendors/service providers (or services provided) that support the CDE or meet PCI DSS requirements on behalf of the entity. For other PCI DSS requirements, where the standard does not define a minimum frequency for recurring activities but instead allow s for the requirement to be met “periodically,” the entity is expected to define the frequency as appropriate for its business. The frequency defined by the entity must be supported by the entity's security policy and the risk analysi s conducted according to PCI DSS Requirement 12. 3. 1. The entity must also be able to demonstrate that the frequency it has defined is appropriate for the activity to be effective and to meet the intent of the requirement. In both cases, where PCI DSS specifies a required frequency and where PCI DSS allows for “periodic” performance, the entity i s expected to have documented and implemented processes to ens ure that activities are performed within a reasonable timeframe, including at least the following: The entity is promptly notified any time an activity is not performed per its defined schedule, The entity determines the events that led to missing a scheduled activity, The entity performs the activity as soon as possible after it is missed and either gets back on schedule or establishes a new schedule, The entity produces documentation that shows the above elements occurred. When an entity has the above processes in place to detect and address when a scheduled activity is missed, a reasonable approach is allowable, meaning that if an activity is required to be performed at least once every three months, the entity is not automatically non-compliant if the activity is per formed late where the entity's documented and implemented process (per above) was followed. However, where no such process is in place and/or the activity was not performed according to schedule due to oversight, mismanagement, or l ack of monitoring, the entity has not met the requirement. In such cases, the requirement will only be in place when the entity 1) documents (or | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 27 reconfirms) the process per above to ensure the scheduled activity occurs on time, 2) re-establishes the schedule, and 3) provides evid ence that the entity has performed the scheduled activity at least once per their schedule. Note : For an initial PCI DSS assessment (meaning an entity has never undergone a prior assessment), where a requirement has a def ined timeframe within which an acti vity is to occur, it is not required that the activity has been performed for every such timeframe during the previous year, if the assessor verifies: The activity was performed in accordance with the applicable requirement within the most recent timeframe (for example, the most recent three-month or six-month period), and The entity has documented policies and procedures for continuing to perform the activity within the defined timeframe. For subsequent years after the initial assessment, the activity must have been performed at least once within each required timeframe. For example, an activity required every three months must have been performed at least four times during the previous year at an interval that does not exceed 90-92 days. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 28 8 Approaches for I mplementing and Validating PCI DSS To support flexibility in how security objectives are met, there are two approaches for implementing and validating to PCI DS S. Entities should identify the approach best suited to their security implementation and use th at approach to validate the controls. Defined Approach Follows the traditional method for implementing and validating PCI DSS and uses the Requirements and Testing Procedures defined within the standard. In the defined approach, the entity implements security controls to meet the stated requirements, and the assessor follows the defined testing procedures to verify that requirement s have been met. The defined approach supports entities with controls in place that meet PCI DSS requirements as stated. This approach may also suit entities that want more direction about how to meet security objectives, as well as entities new to information security or PCI DSS. Compensating Controls As part of the defined approach, entities that cannot meet a PCI DSS requireme nt explicitly as stated due to a legitimate and documented technical or business constraint may implement other, or compensating, controls, that sufficiently mitigate the risk associated with the requirement. On an annual basis, any compensating controls m ust be documented by the entity and reviewed and validated by the assessor and included with the Report on Compliance submission. Note : For more details, s ee Appendix B : Compensating Controls and Appendix C : Compensating Controls Worksheet. Customized Approach Focuses on the Objective of each PCI DSS requirement (if applicable), allowing entities to implement controls to meet the requirement's stated Customized Approach Objective in a way that does not strictly follow the defined requirement. Because each customized implementation will be different, there are no defined testing procedures; the assessor is required to derive testing procedures that are appropriate to the specific i mplementation to validate that the implemented controls meet the stated Objective. The customized approach supports innovation in security practices, allowing entities greater flexibility to show how their current security controls meet PCI DSS objectives. This approach is intended for risk-mature entities that demonstrate a robust risk-management approach to security, including, but not limited to, a dedicated risk-management department or an organization-wide risk management approach. Note : For more details, s ee Appendix D : Customized Approach and Appendix E : Sample Templates to Support Cust omized Approach. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 29 The controls imple mented and validated using the customized approach are expected to meet or exceed the security provided by the requirement in the defined approach. The level of documentation and effort required to validate customized implementations will also be greater t han for the defined approach Most PCI DSS requirements can be met using either the defined or customized approach. However, several requirements do not have a stated Customized Approach Objective; the customized approach is not an option for these requirements. Entities can use both the defined and customized approaches within their environment. This means an entity could use the defi ned approach to meet some requirements and use the customized approach to meet other requirements. This also means that an entity could use the defined approach to meet a given PCI DSS requirement for one system component or within one environment and use the customized approach to meet that same PCI DSS requirement for a different system component or within a different environment. In this way, a PCI DSS assessment could include both defined and customized testing procedures. Figure 4 shows the two validation options for PCI DSS v4. 0. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 30 Figure 4. PCI DSS Validation Approaches | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 31 9 Protecting Information About an Entity's Security Posture The processes related to becoming and maintaining a PCI DSS compliant environment results in many artifacts that an entity may consider sensitive and may want to protect as such, including such items as the following: The Report on Compliance or Self-Assessment Questionnaire (the associated Attestation of Compliance is not considered sensitive and third-party service providers ( TPSPs) are expected to share their AOC with customers). Network diagrams and account data-flow diagrams, and security configurations and rules. System configuration standards. Cryptography and key management methods and protocols. Entities should review all the artifacts related to PCI DSS controls or the assessment and protect them in accordance with th e entity's security policies for this type of information. TPSPs are required (PCI DSS Requirement 12. 9) to support their customers with the following: Information needed for customers to monitor the TPSPs' PCI DSS compliance status (to enable the customer to comply with Requirement 12. 8), and Eviden ce that the TPSP is meeting applicable PCI DSS requirements where the TPSP 's services are intended to meet or facilitate meeting a customer's PCI DSS requirements, or where those services may impact the security of a customer's CDE. This section does not impact or negate a TPSP's obligation to support and provide information to their customers per Requirement 12. 9. For more details about expectations for TPSPs and relationships between TPSPs and customers, see Use of Third-Party Service Providers. Protection of C onfidential and S ensitive Information by Qualified Security Assessor Companies Each Qualified Security Assessor (QSA) Company signs an agreement with PCI SSC that they will adhere to the Qualification Requirements for QSAs. The Protection of Confidential and Sensitive Information section of that document includes the following: “The QSA company must have and adhere to a documented process for protection of confidential and sensitive information. This must include adequate physical, electronic, and procedural safeguards consistent with industry-accepted practices to protect confidential and sensitive information against any threats or unauthorized access during storage, processing, and/or communicating of this information. The QSA Company must maintain the privacy and confidentiality of information obtained in the course of performing its duties and obligations as a QSA Company, unless (and to the extent) disclosure is required by legal authority. ” | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 32 10 Testing Methods for PCI DSS Requirements The testing methods identified in the Testing Procedures for each requirement describe the expected activities to be performe d by the assessor to determine whether the entity has met the requirement. The intent behind each testing method is described as follows: Examine: The assessor critically evaluates data evidence. Common examples include documents (electronic or physical), screens hots, configuration fi les, audit logs, and data files. Observe: The assessor watches an action or views something in the environment. Examples of observation subjects include personnel performing a task or process, system components performing a function or responding to input, environmental conditions, and physical controls. Interview: The assessor converses with individual personnel. Interview objectives may include confirmation of whether an acti vity is performed, descriptions of how an activity is performed, and whether personnel have particular knowledge or understanding. The testing methods are intended to allow the assessed entity to demonstrate how they have met a requirement. They also provi de the assessed entity and the assessor with a common understanding of the assessment activities to be performed. The specific items to be examined or observed and personnel to be interviewed should be appropriate for both the requirement being assessed and each e ntity's particular imp lementation. When documenting the assessment results, the assessor identifies the testing activities performed and the result of each activity. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 33 11 Instructions and Content for Report on Compliance Instructions and content for the Report on Compliance (ROC) ar e provided in the PCI DSS Report on Compliance (ROC) Template. The PCI DSS Report on Compliance (ROC) Template must be used as the template for creating a PCI DSS Report on Compliance. Whether any entity is required to comply with or validate their compl iance to PCI DSS is at the discretion of those organizations that manage compliance programs (such as payment brands and acquirers ). Entities should contact the organizations of interest to determine any reporting requirements and instructions. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 34 12 PCI DSS Assessment Process The PCI DSS assessment process includes the following high-level steps :5 1. Confirm the scope of the PCI DSS assessment. 2. Perform the PCI DSS assessment of the environment. 3. Complete the applicable report for the assessment according to PCI DSS guidance and instructions. 4. Complete the Attestation of Compliance for Service Providers or Merchants, as applicable, in its entirety. Official Attestations of Compliance are only available on the PCI SSC website. 5. Submit the applicable PCI SSC documentation and the Attestation of Compliance, along with any other requested documentation—such as ASV scan reports —to the requesting organization (those that manage compliance programs such as payment brands and acquirers (for merchants), or ot her requester s (for service providers)). 6. If required, perform remediation to address requirements that are not in place and provide an updated report. Note: PCI DSS requirements are not considered to be in place if controls are not yet implemented or are s cheduled to be completed at a future date. After any open or not-in-place items are addressed by the entity, the assessor will reassess to validate that the remediation is completed and that all requirements are satisfied. Refer to the following resources (available on the PCI SSC website) to document the PCI DSS assessment: For instructions about completing reports on compliance (ROC), refer to the PCI DSS Report on Compliance (ROC) Template. For instructions about completing self-assessment questionnaires (SAQ), refer to the PCI DSS SAQ Instructions and Guidelines. For instructions about submitting PCI DSS compliance validation reports, refer to the PCI DSS Attestation of Compliance. 5 The PCI DSS assessment process, and the roles and responsibilities for completion of each step, var y depending on the type of assessment and on compliance programs, which are managed by payment brands and acquirers. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 35 13 Additional References Table 5 lists external organizations referenced within PCI DSS requirements or related guidance. These external organizations and the ir references are provided as information only and do not replace or extend any PCI DSS requirement. Table 5. External Organizations Referenced in PCI DSS Requirements Reference Full Name Source ANSI American National Standards Institute www. ansi. org CIS Center for Internet Security www. cisecurity. org CSA Cloud Security Alliance www. csa. org ENISA European Union Agency for Cybersecurity (formerly European Network and Informatio n Security Agency) www. enisa. europa. eu FIDO Alliance The FIDO Alliance www. fidoalliance. org ISO International Organization for Standardization www. iso. org NCSC The UK National Cyber Security Centre www. ncsc. gov. uk NIST National Institute of Standards and Technology www. nist. gov OWASP Open Web Application Security Project www. owasp. org SAFEcode Software Assurance Forum for Excellence in Code www. safecode. org | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 36 14 PCI DSS Versions As of the publi shed date of this document, PCI DSS v3. 2. 1 is valid through 31 March 2024, after which it is retired. All PCI DSS validations after this date must be to PCI DSS 4. 0 or later. Either PCI DSS version 3. 2. 1 or 4. 0 can be used for assessments between March 2022 and 31 March 2024. Table 6 summarizes PCI DSS versions and their relevant dates. 6 Table 6. PCI DSS Versions Version Published Retired PCI DSS v4. 0 (this document ) March 2022 To be determined PCI DSS v3. 2. 1 May 2018 31 March 2024 6 Subject to change upon release of a new version of PCI DSS. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 37 15 Detailed PCI DSS Requirements and Testing Procedures Figure 5 describes the column headings and content for the PCI DSS requirements. Figure 5. Understanding the Parts of the Requirements Applicability Notes apply to both the Defined and Customiz ed Approach. Includes i nformation that affects how the requirement is interpreted in the context of the entity or in scoping. These notes are an integral part of PCI DSS and must be fully considered during an assessment. Guidance provides information to understand how to meet a requirement. Guidance is not required to be followed- it does not replace or extend any PCI DSS requirement. Not every Guidance section described here is present for each requirement. Not every section will be present for each requirement. Purpose describes the goal, benefit, or threat to be avoided; why the requirement exists. A Good Practice can be considered by the entity when meeting a requirement. Definitions Terms that may help understand the requirement. Examples describe ways a requirement could be met. Further Information includes references to relevant external documentation. The Requirement Description at the X. X level organizes and describes the requirements that fall under it. The Defined Approach Requirements and Testing Procedures describes the traditional method for implementing and validating PCI DSS using the Requirements and Testing Procedures defined in the standard. The Customized Approach Objective is the intended goal or outcome for the requirement. It must be met by entities using a Customized Approach. Most PCI DSS requirements have this Objective. Appendix D describes expectations for entities and assessors when the Customized Approach is used. Entities following the Defined Approach can refer to the Customized Approach Objective as guidance, but the objective does not replace or supersede the Defined Approach Requirement. For each new PCI DSS v4. 0 requirement with an extended implementation period. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 38 Additional Requirements for Service Providers Only Some requirements apply only when the entity being assessed is a service provider. These are identified within the requirement as “ Additional requirement for service providers only” and apply in addition to all other applicable requirements. Where the entity being assessed is both a merchant and a service provider, requirements noted as “ Additional requirement for service providers only” apply to the service provider portion of the entity's business. Requirements identified with “Additional requirement for service providers only” are also recommended as best practi ces for consideration by all entities. Appendices with Additional PCI DSS Requirements for Different Types of Entities In addition to the 12 principal requirements, PCI DSS Appendix A contains additional PCI DSS requirements for different types of entities. The sections within Appendix A include: Appendix A1: Additional PCI DSS Requirements for Multi-Tenant Service Providers. Appendix A2: Additional PCI DSS Requirements for Entities using SSL/Early TLS for Card-Present POS POI Terminal Connections. Appendix A3: Designated Entities Supplemental Validation (DESV). | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 39 Build and Maintain a Secure Network and Systems Requirement 1: Install and Maintain Network Security Controls Sections 1. 1 Processes and mechanisms for installing and maintaining network security controls are defined and understood. 1. 2 Network security controls (NSCs) are configured and maintained. 1. 3 Network access to and from the cardholder data environment is restricted. 1. 4 Network connections between trusted and untrusted networks are controlled. 1. 5 Risks to the CDE from computing devices that are able to connect to both untrusted networks and the CDE are mitigated. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 40 Overview Network security controls (NSCs), such as firewalls and other network security technologies, are network policy enforcement p oints that typically control network traffic between two or more logical or physical network segments (or subnets) based on pre-defined policies or rules. NSCs examine all network traffic entering (ingress) and leaving (egress) a segment and decide, based on the policies defined, whether the network traffic is allowed to pass or whether it should be rejected. Typically, NSCs are plac ed between environments with different security needs or levels of trust, however in some environments NSCs control the traffic to individual devices irrespective of trust boundaries. Policy enforcement generally occurs at layer 3 of the OSI model, but dat a present in higher layers is also frequently used to determine policy decisions. Traditionally this function has been provided by physical firewalls; however, now this functionality may be provided by virtual devices, cloud access controls, virtualization /container systems, and other software-defined networking technology. NSCs are used to control traffic within an entity's own networks —for example, between highly sensitive and less sensitive areas —and also to protect the entity's resources from exposure to untrusted networks. The cardholder data environment (CDE) is an example of a more sensitive area within an entity's network. Often, seemingly insignificant paths to and from untrusted networks can provide unprotected pathways into sensitive systems. NSCs provide a key protection mechanism for any computer network. Common examples of untrusted networks include the Internet, dedicated connections such as business-to-business communication channels, wireless networks, carrier networks (such as cellular), third-party networks, and other sources outside the entity's ability to control. Furthermore, untrusted networks also include corporate networks that are considered out-of-scope for PCI DSS, because they are not assessed, and therefore must be t reated as untrusted because the existence of security controls has not been verified. While an entity may consider an internal network to be trusted from an infrastructure perspective, if a network is out of scope for PCI DSS, that network mus t be consider ed untrusted for PCI DSS. Refer to Appendix G for definitions of PCI DSS terms. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 41 Requirements and Testing Procedures Guidance 1. 1 Processes and mechanisms for installing and maintaining network security controls are defined and understood. Defined Approach Requirements Defined Approach Testing Procedures Purpose Requirement 1. 1. 1 is about effectively managing and maintaining the various policies and procedures specified throughout Requirement 1. While it is important to define the specific policies or procedures called out in Requirement 1, it is equally important to ensure they are properly documented, maintained, and disseminated. Good Practice It is important to update policies and procedures as needed to address changes in processes, technologies, and business objectives. For these reasons, consider updating t hese documents as soon as possible after a change occurs and not only on a periodic cycle. Definitions Security policies define the entity's security objectives and principles. Operational procedures describe how to perform activities, and define the contr ols, methods, and processes that are followed to achieve the desired result in a consistent manner and in accordance with policy objectives. 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. 1 Examine documentation and interview personnel to verify that security policies and operat ional procedures identified in Requirement 1 are managed in accordance with all elements specified in this requirement. Customized Approach Objective Expectations, controls, and oversight for meeting activities within Requirement 1 are defined, understood, and adhered to by affected personnel. All supporting activities are repeatable, consistently applied, and conform to management's intent. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 42 Requirements and Testing Procedures Guidance Defined Approach Requirements Defined Approach Testing Procedures Purpose If roles and responsibilities are not formally assigned, personnel may not be aware of their day-to-day responsibilities and critical activities may not occur. Good Practice Roles and responsibilities may be documented within policies and procedures or maintained within separate documents. As part of communicating roles and responsibilities, entities can consider having personnel acknowledge their acceptance and understanding of their assigned roles and responsibilities. Examples A method to document roles and respons ibilities is a responsibility assignment matrix that includes who is responsible, accountable, consulted, and informed (also called a RACI matrix). 1. 1. 2 Roles and responsibilities for performing activities in Requirement 1 are documented, assigned, and understood. 1. 1. 2. a Examine documentation to verify that descriptions of roles and responsibilities for performing activities in Requirement 1 are document ed and assigned. 1. 1. 2. b Interview personnel responsible for performing activities in Requirement 1 to verify that roles and responsibilities are assigned as documented and are understood. Customized Approach Objective Day-to-day responsibilities for performing all the activities in Requirement 1 are allocated. Personnel are accountable for successful, continuous operation of these requirements. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 43 Requirements and Testing Procedures Guidance 1. 2 Network security controls (NSCs) are configured and maintained. Defined Approach Requirements Defined Approach Testing Procedures Purpose The implementation of these configuration standards results in the NSC being configured and managed to properly perform their security function (often referred to as the ruleset). Good Practice These standards often define the requirements for acceptable protocols, ports that are permitted to be used, and specific configuration requirements that are acceptable. Configuration standards may also outline what the entity considers not acceptable or not permitted within its network. Definitions NSCs are key components of a network architecture. Most commonly, NSCs are used at the boundaries of the CDE to control network traffic flowing inbound and outbound from the CDE. Configuration standards outlin e an entity's minimum requirements for the configuration of its NSCs Examples Examples of NSCs covered by these configuration standards include, but are not limited to, firewalls, routers configured with access control lists, and cloud virtual networks. 1. 2. 1 Configuration standards for NSC rulesets are: Defined. Implemented. Maintained. 1. 2. 1. a Examine the configuration standards for NSC rulesets to verify the standards are in accordance with all elements specified in this requirement. 1. 2. 1. b Examine configuration settings for NSC rulesets to verify that rulesets are implemented according to the configuration standards. Customized Approach Objective The way that NSC s are configured and operate are defined and consistently applied. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 44 Requirements and Testing Procedures Guidance Defined Approach Requirements Defined Approach Testing Procedures Good Practice Changes should be approved by individuals with the appropriate authority and knowledge to understand the impact of the change. Verification should provide reasonable assurance that the change did not adversely impact the security of the network and that the change performs as expected. To avoid having to address security issues introduced by a change, all changes should be approved prior to being implemented and verified after the change is implemented. Once approved and verified, network documentation should be updated to include the changes to prevent inconsistencies between network documentation and the actual configuration. 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. 2. a Examine documented procedures to verify that changes to network connections and configurations of NSCs are included in the formal change control process in accordance with Requirement 6. 5. 1. 1. 2. 2. b Examine network configuration settings to identify changes made to network connections. Interview responsible personnel and examine change control records to verify that identified changes to network connections were approved and managed in accorda nce with Requirement 6. 5. 1. 1. 2. 2. c Examine network configuration settings to identify changes made to configurations of NSCs. Interview responsible personnel and examine change control records to verify that identified changes to configurations of NSC s were approved and managed in accordance with Requirement 6. 5. 1. Customized Approach Objective Changes to network connections and NSC s cannot result in misconfiguration, implementation of insecure services, or unauthorized network connections. Appli cability Notes Changes to network connections include the addition, removal, or modification of a connection. Changes to NSC configurations include those related to the component itself as well as those affecting how it performs its security function. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 45 Requirements and Testing Procedures Guidance Defined Approach Requirements Defined Approach Testing Procedures Purpose Maintaining an accurate and up-to-date network diagram(s) prevents network connections and devices from being overlooked and unknowingly left unsecured and vulnerable to compromise. A properly maintained network diagram(s) helps an organization verify its PCI DSS scope by identifying systems connecting to and from the CDE. Good Practice All connections to and from the CDE should be identified, including systems providing security, management, or maintenance services to CDE system components. Entities should consider including the following in their network diagrams: All locations, including retail locations, data centers, corporate locations, cloud providers, etc. Clear labeling of all network segments. All security controls providing segmentation, including unique identifiers for each control (for example, name of control, make, model, and version). All in-scope system components, including NSCs, web app firewalls, anti-malware solutions, change management solutions, IDS/IPS, log aggregation systems, payment terminals, payment applications, HSMs, etc. Clear labeling of any out-of-scope areas on the diagram via a shaded box or other mechanism. Date of last update, and names of people that made and approved the updates. A legend or key to explain the diagram. Diagrams should be updated by authorized personnel to ensure diagrams continue to provide an accurate description of the network. 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. 3. a Examine diagram(s) and network configurations to verify that an accurate network diagram(s) exists in acco rdance with all elements specified in this requirement. 1. 2. 3. b Examine documentation and interview responsible personnel to verify that the network diagram(s) is accurate and updated when there are changes to the environment. Customized Approach Objective A representation of the boundaries between the CDE, all trusted networks, and all untrusted networks, is maintained and available. Applicability Notes A current network diagram(s) or other technical or topological solution that identifies network connections and devices can be used to meet this requirement. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 46 Requirements and Testing Procedures Guidance Defined Approach Requirements Defined Approach Testing Procedures Purpose An up-to-date, readily available data-flow diagram helps an organization understand and keep track of the scope of its environment by showing how account data flows across networks and between individual systems and devices. Maintaining an up-to-date data-flow diagram(s) prevents account data from being overlooked and unknowingly left unsecured. Good Practice The data-flow diagram should include all connection points where account data is received into and sent out of the network, including connections to open, public networks, application process ing flows, storage, transmissions between systems and networks, and file backups. The data-flow diagram is meant to be in addition to the network diagram and should reconcile with and augment the network diagram. As a best practice, entities can consider including the following in their data-flow diagrams: All processing flows of account data, including authorization, capture, settlement, chargeback, and refunds. All distinct acceptance channels, including card-present, card-not-present, and e-commerce. All types of data receipt or transmission, including any involving hard copy/paper media. The flow of account data from the point where it enters the environment, to its final disposition. Where account data is transmitted and processed, where i t is stored, and whether storage is short term or long term. (continued on next page) 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 t o the environment. 1. 2. 4. a Examine data-flow diagram(s) and interview personnel to verify the diagram(s) show all account data flows in accordance with all elements specified in this requirement. 1. 2. 4. b Examine documentation and interview responsible personnel to verify that the data-flow diagram(s) is accurate and updated when there are changes to the environment. Customized Approach Objective A representation of all transmissions of account data between system components and across network segments is maintained and available. Applicability Notes A data-flow diagram(s) or other technical or topological solution that identifies flows of account data across systems and networks can be used to meet this requirement. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 47 Requirements and Testing Procedures Guidance The source of all account data received (for example, customers, third party, etc. ), and any entities with which account data is shared. Date of last update, and names of people that made and approved the updates. Defined Approach Requirements Defined Approach Testing Procedures Purpose Compromises often happen due to unused or insecure services (for example, telnet and FTP), protocols, and ports, since these can lead to unnecessary points of access being opened into the CDE. Additionally, services, pro tocols, and ports that are enabled but not in use are often overlooked and left unsecured and unpatched. By identifying the services, protocols, and ports necessary for business, entities can ensure that all other services, protocols, and ports are disable d or removed. Good Practice The security risk associated with each service, protocol, and port allowed should be understood. Approvals should be granted by personnel independent of those managing the configuration. Approving personnel should possess knowl edge and accountability appropriate for making approval decisions. 1. 2. 5 All services, protocols, and ports allowed are identified, approved, and have a defined business need. 1. 2. 5. a Examine documentation to verify that a list exists of all allowed services, protocols, and ports, including business justification and approval for each. 1. 2. 5. b Examine configuration settings for NSC s to verify that only approved services, protocols, and ports are in use. Customized Approach Objective Unauthorized network traffic (services, protocols, or packets destined for specific ports) cannot enter or leave the network. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 48 Requirements and Testing Procedures Guidance Defined Approach Requirements Defined Approach Testing Procedures Purpose Compromises take advantage of insecure network configurations. Good Practice If insecure services, protocols, or ports are necessary for business, the risk posed by these services, protocols, and ports should be clearly understood and accepted by the organization, the use of the service, protocol, or port should be justified, and the security features that mitigate the risk of using these services, protocols, and ports should be defined and implemented by the entity. Further Information For guidance on services, protocols, or ports considered to be insecure, refer to industry standards and guidance (for example, from NIST, ENISA, OWASP). 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. 6. a Examine documentation that identifies all insecure services, protocols, and ports in use to verify that for each, security features are defined to mitigate the risk. 1. 2. 6. b Examine configuration settings for NSC s to verify that the defined security features are implemented for each identified insecure service, protocol, and port. Customized Approach Objective The specific risks associated with the use of insecure services, protocols, and ports are understood, assessed, and appropriately mitigated. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 49 Requirements and Testing Procedures Guidance Defined Approach Requirements Defined Approach Testing Procedures Purpose Such a review gives the organization an opportunity to clean up any unneeded, outdated, or incorrect rules and configurations which could be utilized by an unauthorized person. Furthermore, it ensures that all rules and configurations al low only authorized services, protocols, and ports that match the documented business justifications. Good Practice This review, which can be implemented using manual, automated, or system-based methods, is intended to confirm that the settings that manage traffic rules, what is allowed in and out of the network, match the approved configurations. The review should provide confirmation that all permitted access has a justified business reason. Any discrepancies or uncertainties about a rule or configuratio n should be escalated for resolution. While this requirement specifies that this review occur at least once every six months, organizations with a high volume of changes to their network configurations may wish to consider performing reviews more frequentl y to ensure that the configurations continue to meet the needs of the business. 1. 2. 7 Configurations of NSC s are reviewed at least once every six months to confirm they are relevant and effective. 1. 2. 7. a Examine documentation to verify procedures are defined for reviewing configurations of NSCs at least once every six months. 1. 2. 7. b Examine documentation of reviews of configurations for NSCs and interview responsible personnel to verify that reviews occur at least once every six months. 1. 2. 7. c Examine configurations for NSC s to verify that configurations identified as no longer being supported by a business justification are removed or updated. Customized Approach Objective NSC configurations that allow or restrict access to trusted networks are verified periodically to ensure that only authorized connections with a current business justification are permitted. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 50 Requirements and Testing Procedures Guidance Defined Approach Requirements Defined Approach Testing Procedures Purpose To prevent unauthorized configurations from being applied to the network, stored files with configurations for network controls need to be kept up to date and secured against unauthorized changes. Keeping configuration information current and secure ensures that the correct settings for NSCs are applied whenever the configuration is run. Examples If the secure configuration for a router is stored in non-volatile memory, when that router is restarted or rebooted, these controls should ensure that its secure configuration is reinstated. 1. 2. 8 Configuration files for NSC s are: Secured from unauthorized access. Kept consistent with active network configurations. 1. 2. 8 Examine configuration files for NSC s to verify they are in accordance with all elements specified in this requirement. Customized Approach Objective NSC s cannot be defined or modified using untrusted configuration objects (including files). Appli cability Notes Any file or setting used to configure or synchronize NSCs is considered to be a “configuration file. ” This includes files, automated and system-based controls, scripts, settings, infrastructure as code, or other parameters that are backed up, archived, or stored remotely. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 51 Requirements and Testing Procedures Guidance 1. 3 Network access to and from the cardholder data environment is restricted. Defined Approach Requirements Defined Approach Testing Procedures Purpose This requirement aims to prevent malicious individuals from accessing the entity's network via unauthorized IP addresses or from using services, protocols, or ports in an unauthorized manner. Good Practice All traffic inbound to the CDE, regardless of where it originates, should be evaluated to ensure it follows established, authorized rules. Connections should be inspected to ensure traffic is restrict ed to only authorized communications —for example, by restricting source/destination addresses and ports, and blocking of content. Examples Implementing a rule that denies all inbound and outbound traffic that is not specifically needed— for example, by using an explicit “deny all” or implicit deny after allow statement —helps to prevent inadvertent holes that would allow unintended and potentially harmful traffic. 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. 1. a Examine configuration standards for NSC s to verify that they define restricting inbound traffic to the CDE is in accordance with all elements specified in this requirement. 1. 3. 1. b Examine configurations of NSC s to verify that inbound traffic to the CD E is restricted in accordance with all elements specified in this requirement. Customized Approach Objective Unauthorized traffic cannot enter the CDE. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 52 Requirements and Testing Procedures Guidance Defined Approach Requirements Defined Approach Testing Procedures Purpose This requirement aims to prevent malicious individuals and compromised system components within the entity's network from communicating with an untrusted external host. Good Practice All traffic outbound from the CDE, regardless of the destination, should be evaluated to ensure it follows established, authorized rules. Connections should be inspected to restrict traffic to only authorized communications —for example, by restricting source/destination addresses and ports, and blocking of content. Examples Implementing a rule that denies all inbound and outbound traffic that is not specifically needed—for example, by using an explicit “deny all” or implicit deny after allow statement —helps to prevent inadvertent holes that would allow unintended and potentially harmful traffic. 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. 2. a Examine configuration standards for NSC s to verify that they define restricting outbound traffic from the CDE in accordance with all elements specified in this requirement. 1. 3. 2. b Examine configurations of NSC s to verify that outbound traffic from the CDE is restricted in accordance with all elements specified in this requirement. Customized Approach Objective Unauthorized traffic cannot leave the CDE. Defined Approach Requirements Defined Approach Testing Procedures Purpose The known (or unknown) implementation and exploitation of wireless technology within a network is a common path for malicious individuals to gain access to the network and account data. If a wireless device or network is installed without the entity's knowledge, a malicious individual could easily and “invisibly” enter the network. If NSCs do not restrict access from wireless networks into the CDE, malicious individuals that gain unauthorized access to the wireless networ k can easily connect to the CDE and compromise account information. 1. 3. 3 NSC s 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 default. Only wireless traffic with an authorized business purpose is allowed into the CDE. 1. 3. 3 Examine configuration settings and network diagrams to verify that NSCs are implemented between all wireless networks and the CDE, in accordance with all elements specified in this requirement. Customized Approach Objective Unauthorized traffic cannot traverse network boundaries between any wireless networks and wired environments in the CDE. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 53 Requirements and Testing Procedures Guidance 1. 4 Network connections between trusted and untrusted networks are controlled. Defined Approach Requirements Defined Approach Testing Procedures Purpose Implementing NSCs at every connection coming into and out of trusted networks allows the entity to monitor and control access and minimizes the chances of a malicious individual obtaining access to the internal network via an unprotected connection. Examples An entity could implement a DMZ, which is a part of the network that manages connections between an untrusted network (for examples of untrusted networks refer to the Requirement 1 Overview) and services that an organization needs to have available to the public, such as a web server. Please note that if an entity's DMZ processes or transmits account data (for example, e-commerce website ), it is also considered a CDE. 1. 4. 1 NSC s are implemented between trusted and untrusted networks. 1. 4. 1. a Examine configuration standards and network diagrams to verify that NSCs are defined between trusted and untrusted networks. 1. 4. 1. b Examine network configurations to verify that NSCs are in place between trusted and untrusted networks, in accordance with the documented configuration standards and network diagrams. Customized Approach Objective Unauthorized traffic cannot traverse network boundaries between trusted and untrusted networks. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 54 Requirements and Testing Procedures Guidance Defined Approach Requirements Defined Approach Testing Procedures Purpose Ensuring that public access to a system component is specifically authorized reduces the risk of system components being unnecessarily exposed to untrusted networks. Good Practice System components that provide publicly accessible services, such as email, web, and DNS servers, are the most vulnerable to threats originati ng from untrusted networks. Ideally, such systems are place d within a dedicated trusted network that is public facing (for example, a DMZ) but that is separated via NSCs from more sensitive internal systems, which helps protect the rest of the network in the event these externally accessible systems are compromised. This functionality is intended to prevent malicious actors from accessing the organization's internal network from the Internet, or from using services, protocols, or ports in an unauthorized m anner. Where this functionality is provided as a built-in feature of an NSC, the entity should ensure that its configurations do not result in the functionality being disabled or bypassed. Definitions Maintaining the "state" (or status) for each connection into a network means the NSC “knows” whether an apparent response to a previous connection is a valid, authorized response (since the NSC retains each connection's status) or whether it is malicious traffic trying to fool the NSC into allowing the connection. 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. Stateful responses to communications initiated by system components in a trusted network. All other traffic is denied. 1. 4. 2 Examine vendor documentation and configurations of NSCs to verify that inbound traffic from untrusted networks to trusted networks is restricted in accordance with all elements specified in this requirement. Customized Approach Objective Only traffic that is authorized or that is a response to a system component in the trusted network can enter a trusted network from an untrusted network. Appl icability Notes The intent of this requirement is to address communication sessions between trusted and untrusted networks, rather than the specifics of protocols. This requirement does not limit the use of UDP or other connectionless network protocols if state is maintained by the NSC. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 55 Requirements and Testing Procedures Guidance Defined Approach Requirements Defined Approach Testing Procedures Purpose Filtering packets coming into the trusted network helps to, among other things, ensure packets are not “spoofed” to appear as if they are coming from an organization's own internal network. For example, anti-spoofing measures prevent internal addresses ori ginating from the Internet from passing into the DMZ. Good Practice Products usually come with anti-spoofing set as a default and may not be configurable. Entities should consult the vendor's documentation for more information. Examples Normally, a packet contains the IP address of the computer that originally sent it so other computers in the network know where the packet originated. Malicious individuals will often try to spoof (or imitate) the sending IP address to fool the target system into believing the packet is from a trusted source. 1. 4. 3 Anti-spoofing measures are implemented to detect and block forged source IP addresses from entering the trusted network. 1. 4. 3 Examine vendor documentation and configurations for NSCs to verify that anti-spoofing measures are implemented to detect and block forged source IP addresses from entering the trusted network. Customized Approach Objective Packets with forged IP source addresses cannot enter a trusted network. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 56 Requirements and Testing Procedures Guidance Defined Approach Requirements Defined Approach Testing Procedures Purpose Cardholder data that is directly accessible from an untrusted network, for example, because it is stored on a system within the DMZ or in a cloud database service, is easier for an external attacker to access because there are fewer defensive layers to penetrate. Using NSC s to ensure that system components that store cardholder data (suc h as a database or a file) can only be directly accessed from trusted networks can prevent unauthorized network traffic from reaching the system component. 1. 4. 4 System components that store cardholder data are not directly accessible from untrusted networks. 1. 4. 4. a Examine the data-flow diagram and network diagram to verify that it is documented that system components storing cardholder data are not directly acc essible from the untrusted networks. 1. 4. 4. b Examine configurations of NSC s to verify that controls are implemented such that system components storing cardholder data are not directly accessible from untrusted networks. Customized Approach Objective Stored cardholder data cannot be accessed from untrusted networks. Appli cability Notes This requirement is not intended to apply to storage of account data in volatile memory but does apply where memory is being treated as persistent storage (for example, RAM disk). Account data can only be stored in volatile memory during the time necessary to support the associated business process (for example, until comp letion of the related payment card transaction). | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 57 Requirements and Testing Procedures Guidance Defined Approach Requirements Defined Approach Testing Procedures Purpose Restricting the disclosure of internal, private, and local IP addresses is useful to prevent a hacker from obtaining knowledge of these IP addresses and using that information to access the network. Good Practice Methods used to meet the intent of this requirement may vary, depending on the specific networking technology being used. For example, the controls used to meet this requirement may be different for IPv4 networks than for IPv6 networks. Examples Methods to obscure IP addressing may include, but are not limited to: IPv4 Network Address Translation (NAT). Placing system components behind proxy servers/ NSCs. Removal or filtering of route advertisements for internal networks that use registered addressing. Internal use of RFC 1918 (IPv4) or use IPv6 privacy extension (RFC 4941) when initiating outgoing sessions to the internet. 1. 4. 5 The disclosure of internal IP addresses and routing information is limited to only authorized parties. 1. 4. 5. a Examine configurations of NSC s to verify that the dis closure of internal IP addresses and routing information is limited to only authorized parties. 1. 4. 5. b Interview personnel and examine documentation to verify that controls are implemented such that any disclosure of internal IP addresses and routing information is limited to only authorized parties. Customized Approach Objective Internal network information is protected from unauthorized disclosure. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 58 Requirements and Testing Procedures Guidance 1. 5 Risks to the CDE from computing devices that are able to connect to both untrusted networks and the CDE are mitigated. Defined Approach Requirements Defined Approach Testing Procedures Purpose Computing devices that are allowed to connect to the Internet from outside the corporate environment —for example, desktops, laptops, tablets, smartphones, and other mobile computing devices used by employees —are more vulnerable to Internet-based threats. Use of security controls such as host-based controls (for example, personal firewall software or end-point protection solutions), network-based security controls (for example, firewalls, network-based heuristics inspection, and malware simulation), or hard ware, helps to protect devices from Internet-based attacks, which could use the device to gain access to the organization's systems and data when the device reconnects to the network. (continued on next page) 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 : Specific configuration settings are defined to prevent thr eats being introduced into the entity's network. Security controls are actively running. Security controls are not alterable by users of the computing devices unless specifically documented and authorized by management on a case-by-case basis for a limite d period. 1. 5. 1. a Examine policies and configuration standards and interview personnel to verify security controls for computing devices that connect to both untrusted networks, and the CDE, are implemented in accordance with all elements specified in this requirement. 1. 5. 1. b Examine configuration settings on computing devices that connect to both untrusted networks and the CDE to verify settings are implemented in accordance with all elements specified in this requirement. Customized Approach Objective Devices that connect to untrusted environments and also connect to the CDE cannot introduce threats to the entity's CDE. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 59 Requirements and Testing Procedures Guidance Applicability Notes Good Practice The specific configuration se ttings are determined by the entity and should be consistent with its network security policies and procedures. Where there is a legitimate need to temporarily disable security controls on a company-owned or employee-owned device that connects to both an untrusted network and t he CDE —for example, to support a specific maintenance activity or investigation of a technical problem —the reason for taking such action is understood and approved by an appropriate management representative. Any disabling or altering of these security controls, including on administrators' own devices, is performed by authorized personnel. It is recognized that administrators have privileges that may allow them to disable security controls on their own computers, but there should be alerting mechanisms in place when such controls are disabled and follow up that occurs to ensure processes were followed. Examples Practices include forbidding split-tunneling of VPNs for employee-owned or corporate-owned mobile devices and requiring that such devices boot up into a VPN. These security controls may be temporarily disabled only if there is legitimate technical need, as authorized by management on a case-by-case basis. If these security controls need to be disabled for a specific purpose, it must be formally authorized. Additional security measures may also need to be implemented for the period during which these security controls are not active. This requirement applies to employee-owned and company-owned computing devices. Systems that cannot be managed by corporate policy introduce weaknesses and provide opportunities that malicious individuals may exploit. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 60 Requirement 2: Apply Secure Configurations to All System Components Sections 2. 1 Processes and mechanisms for applying secure configurations to all system components are defined and understood. 2. 2 System components are configured and managed securely. 2. 3 Wireless environments are configured and managed securely. Overview Malicious individuals, both external and internal to an entity, often use default passwords and other vendor default settings to compromise systems. These passwords and settings are well known and are easily determined via public information. Applying secure configurations to system components reduces the means available to an attacker to compromise the system. Changing default passwords, removing unnecessar y software, functions, and accounts, and disabling or removing unnecessary services all help to reduce the potential attack surface. Refer to Appendix G for definitions of PCI DSS terms. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 61 Requirements and Testing Procedures Guidance 2. 1 Processes and mechanisms for applying secure configurations to all system components are defined and understood. Defined Approach Requirements Defined Approach Testing Procedures Purpose Requirement 2. 1. 1 is about effectively managing and maintaining the various policies and procedures specified throughout Requirement 2. While it is important to define the specific policies or procedures called out in Requirement 2, it is equally important to ensure they are properly documented, maintained, and disseminated. Good Practice It is important to update policies and procedures as needed to address changes in processes, technologies, and business objectives. For this reason, consider updating the se documents as soon as possible after a change occurs and not only on a periodic cycle Definitions Security policies define the entity's security objectives and principles. Operational procedures describe how to perform activities, and define the control s, methods, and processes that are followed to achieve the desired result in a consistent manner and in accordance with policy objectives. 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. 1 Examine documentation and interview personnel to verify that security policies and operat ional procedures identified in Requirement 2 are managed in accordance with all elements specified in this requirement. Customized Approach Objective Expectations, controls, and oversight for meeting activities within Requirement 2 are defined and adhered to by affected personnel. All supporting activities are repeatable, consistently applied, and conform to management's intent. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 62 Requirements and Testing Procedures Guidance Defined Approach Requirements Defined Approach Testing Procedures Purpose If roles and responsibilities are not formally assigned, personnel may not be aware of their day-to-day responsibilities and critical activities may not occur. Good Practice Roles and responsibilities may be documented within policies and procedures or ma intained within separate documents. As part of communicating roles and responsibilities, entities can consider having personnel acknowledge their acceptance and understanding of their assigned roles and responsibilities. Examples A method to document rol es and responsibilities is a responsibility assignment matrix that includes who is responsible, accountable, consulted, and informed (also called a RACI matrix). 2. 1. 2 Roles and responsibilities for performing activities in Requirement 2 are documented, assigned, and understood. 2. 1. 2. a Examine documentation to verify that descriptions of roles and responsibilities for performing activities in Requirement 2 are document ed and assigned. 2. 1. 2. b Interview personnel with responsibility for performing activities in Requirement 2 to verify that roles and responsibilities are assigned as documented and are understood. Customized Approach Objective Day-to-day responsibilities for performing all the activities in Requirement 2 are allocated. Personnel are accountable for successful, continuous operation of these requirements. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 63 Requirements and Testing Procedures Guidance 2. 2 System components are configured and managed securely. Defined Approach Requirements Defined Approach Testing Procedures Purpose There are known weaknesses with many operating systems, databases, network devices, software, applications, container images, and other devices used by an entity or within an entity's environment. There are also known ways to configure these system components to fix security vulnerabilities. Fixing sec urity vulnerabilities reduces the opportunities available to an attacker. By developing standards, entities ensure their system components will be configured consistently and securely, and address the protection of devices for which full hardening may be m ore difficult. Good Practice Keeping up to date with current industry guidance will help the entity maintain secure configurations. The specific controls to be applied to a system will vary and should be appropriate for the type and function of the system. Numerous security organizations have established system-hardening guidelines and recommendations, which advise how to correct common, known weaknesses. Further Information Sources for guidance on configuration standards include but are not limited to: C enter for Internet Security (CIS), International Organization for Standardization (ISO), National Institute of Standards and Technology (NIST), Cloud Security Alliance, and product vendors. 2. 2. 1 Configuration standards are developed, implemented, and maintained to: Cover all system components. Address all known security vulnerabilities. Be consistent with industry-accepted system hardening standards or vendor hardening recommendations. Be updat ed as new vulnerability issues are identified, as defined in Requirement 6. 3. 1. Be applied when new systems are configured and verified as in place before or immediately after a system component is connected to a production environment. 2. 2. 1. a Examine sys tem configuration standards to verify they define processes that include all elements specified in this requirement. 2. 2. 1. b Examine policies and procedures and interview personnel to verify that system configuration standards are updated as new vulnerability issues are identified, as defined in Requirement 6. 3. 1. 2. 2. 1. c Examine configuration settings and interview personnel to verify that system configuration standards are applied when new systems are configured and verified as being in place before or immediately after a system component is connected to a production environment. Customized Approach Objective All system components are configured securely and consistently and in accordance with industry-accepted hardening standards or vendor recommendations. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 64 Requirements and Testing Procedures Guidance Defined Approach Requirements Defined Approach Testing Procedures Purpose Malicious individuals often use vendor default account names and passwords to compromise operating systems, applications, and the systems on which they are installed. Because these default settings are often published and are wel l known, changing these settings will make systems less vulnerable to attack. Good Practice All vendor default accounts should be identified, and their purpose and use understood. It is important to establish controls for application and system accounts, including those used to deploy and maintain cloud services so that they do not use default passwords and are not usable by unauthorized individuals. Where a default account is not intended to be used, changing the default password to a unique password that meets PCI DSS Requirement 8. 3. 6, removing any access to the default account, and then disabling the account, will prevent a malicious individual from re-enabling the account and gaining access with the default password. Using an isolated staging network t o install and configure new systems is recommended and can also be used to confirm that default credentials have not been introduced into production environments. Examples Defaults to be considered include user IDs, passwords, and other authentication credentials commonly used by vendors in their products. 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 used, the account is removed or disabled. 2. 2. 2. a Examine system configuration standards to verify they include managing vendor default accounts in accordance with all elements specified in this requirement. 2. 2. 2. b Examine vendor documentation and observe a system administrator logging on using vendor default accounts to verify accounts are implemented in accordance with all elements specified in this requirement. 2. 2. 2. c Examine configuration files and interview personnel to verify that all vendor default accounts that will not be used are removed or disabled. Customized Approach Objective System components cannot be accessed using default passwords. Applicability Notes This applies to ALL vendor default accounts and 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, and Simple Network Management Protocol (SNMP) defaults. This requirement also applies where a system component is not installed within an entity's environment, for example, software and applications that are part of the CDE and are accessed via a cloud subscription service. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 65 Requirements and Testing Procedures Guidance Defined Approach Requirements Defined Approach Testing Procedures Purpose Systems containing a combination of services, protocols, and daemons for their primary function will have a security profile appropriate to allow that function to operate effectively. For example, systems that need to be directly connect ed to the Internet would have a particular profile, like a DNS server, web server, or an e-commerce server. Conversely, other system components may operate a primary function comprising a different set of services, protocols, and daemons that performs functions that an entity does not want exposed to the Internet. This requirement aims to ensure that different functions do not impact the security profiles of other services in a way which may cause them to operate at a higher or lower security level. Good Practice Ideally, each function should be placed on different system components. This can be achieved by implementing only one primary function on each system component. Another option is to isolate primary functions on the same system component that have different security levels, for example, isolating web servers (which need to be directly connected to the Internet) from application and database servers. (continued on next page) 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 exist on the same system component are isolated from each other, OR Primary functions with differing security levels on the same system component are all secured to the level required by the function with the highest security need. 2. 2. 3. a Examine system configuration standards to verify they include managing primary functions requiring different security levels as specified in this requirement. 2. 2. 3. b Examine system configurations to verify that primary functions requiring different se curity levels are managed per one of the ways specified in this requirement. 2. 2. 3. c Where virtualization technologies are used, examine the system configurations to verify that system functions requiring different security levels are managed in one of the following ways: Functions with differing security needs do not co-exist on the sam e system component. Functions with differing security needs that exist on the same system component are isolated from each other. Functions with differing security needs on the same system component are all secured to the level required by the function wit h the highest security need. Customized Approach Objective Primary functions with lower security needs cannot affect the security of primary functions with higher security needs on the same system component. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 66 Requirements and Testing Procedures Guidance If a system component contains primary functions that need different security levels, a third option is to implement additional controls to ensure that the resultant security level of the primary function(s) with higher security needs is not reduced by the presence of the lower security primary functions. Additionally, the functions with a lower security level should be isolated and/or secured to ensure they cannot access or affect the resources of another system function, and do not introduce security weak nesses to other functions on the same server. Functions of differing security levels may be isolated by either physical or logical controls. For example, a database system should not also be hosting web services unless using controls like virtualization t echnologies to isolate and contain the functions into separate sub-systems. Another example is using virtual instances or providing dedicated memory access by system function. Where virtualization technologies are used, the security levels should be identi fied and managed for each virtual component. Examples of considerations for virtualized environments include: The function of each application, container, or virtual server instance. How virtual machines (VMs) or containers are stored and secured. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 67 Requirements and Testing Procedures Guidance Defined Approach Requirements Defined Approach Testing Procedures Purpose Unnecessary services and functions can provide additional opportunities for malicious individuals to gain access to a system. By removing or disabling all unnecessary services, protocols, daemons, and functions, organizations can focus on securing the functions that are required and reduce the risk that unknown or unnecessary functions will be exploited. Good Practice There are many protocols that could be enabled by default that are commonly used by malicious individuals to compromise a network. Disabling or removing all services, functions, and protocols that are not used minimizes the potential attack surface —for example, by removing or disabling an unused FTP or web server. Exampl es Unnecessary functionality may include, but is not limited to scripts, drivers, features, subsystems, file systems, interfaces (USB and Bluetooth), and unnecessary web servers. 2. 2. 4 Only necessary services, protocols, daemons, and functions are enabled, and all unnecessary functionality is removed or disabled. 2. 2. 4. a Examine system configuration standards to verify necessary system services, protocols, and daemons are identified and documented. 2. 2. 4. b Examine system configurations to verify the following: All unnecessary functionality is removed or disabled. Only required functionality, as documented in the configuration standards, is enabled. Customized Approach Objective System components cannot be compromised by exploiting unnecessary functionality present in the system component. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 68 Requirements and Testing Procedures Guidance Defined Approach Requirements Defined Approach Testing Procedures Purpose Ensuring that all insecure services, protocols, and daemons are adequately secured with appropriate security features makes it more difficult for malicious individuals to exploit common points of compromise within a network. Good Practice Enabling security features before new system component s are deployed will prevent insecure configurations from being introduced into the environment. Some vendor solutions may provide additional security functions to assist with securing an insecure process. Further Information For guidance on services, prot ocols, or daemons considered to be insecure, refer to industry standards and guidance (for example, as published by NIST, ENISA, and OWASP). 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 insecure services, protocols, or daemons. 2. 2. 5. a If any insecure services, protocols, or daemons are present, examine system configuration standards and interview personnel to verify they are managed and implemented in accordance with all elements specified in this requirement. 2. 2. 5. b If any insecure services, protocols, or daemons, are present, examine configuration settings to verify that additional security features are implemented to reduce the risk of using insecure services, daemons, and protocols. Customized Approach Objective System components cannot be compromised by exploiting insecure services, protocols, or daemons. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 69 Requirements and Testing Procedures Guidance Defined Approach Requirements Defined Approach Testing Procedures Purpose Correctly configuring security parameters provided in system components takes advantage of the capabilities of the system component to defeat malicious attacks. Good Practice System configuration standards and related processes should specifically address security settings and parameters that have known security implications for each type of system in use. For systems to be configured securely, personnel responsible for configuration and/or administering systems should be knowledgeable in the specific security parameters and settings that apply to the system. Conside rations should also include secure settings for parameters used to access cloud portals. Further Information Refer to vendor documentation and industry references noted in Requirement 2. 2. 1 for information about applicable security parameters for each type of system. 2. 2. 6 System security parameters are configured to prevent misuse. 2. 2. 6. a Examine system configuration standards to verify they include configuring system security parameters to prevent misuse. 2. 2. 6. b Interview system administrators and/or security managers to verify they have knowledge of common security parameter settings for system components. 2. 2. 6. c Examine system configurations to verify that common security parameters are set appropriately and in accordance with the system configuration standards. Customized Approach Objective System components cannot be compromised because of incorrect security parameter configuration. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 70 Requirements and Testing Procedures Guidance Defined Approach Requirements Defined Approach Testing Procedures Purpose If non-console (including remote) administration does not use encrypted communications, administrative authorization factors (such as IDs and passwords) can be revealed to an eavesdropper. A malicious individual could us e this information to access the network, become administrator, and steal data. Good Practice Whichever security protocol is used, it should be configured to use only secure versions and configurations to prevent use of an insecure connection—for example, by using only trusted certificates, supporting only strong encryption, and not supporting fallback to weaker, insecure protocols or methods. Examples Cleartext protocols (such as HTTP, telnet, etc. ) do not encrypt traffic or logon details, making it easy for an eavesdropper to intercept this information. Non-console access may be facilitated by technologies that provide alternative access to systems, including but not limited to, out-of-band (OOB), lights-out management (LOM), Intelligent Platform Management Interface (IPMI), and keyboard, video, mouse (KVM) switches with remote capabilities. These an d other non-console access technologies and methods must be secured with strong cryptography. Further Information Refer to industry standards and best practices such as NIST SP 800-52 and SP 800-57. 2. 2. 7 All non-console administrative access is encrypted using strong cryptography. 2. 2. 7. a Examine system configuration standards to verify they include encrypting all n on-console administrative access using strong cryptography. 2. 2. 7. b Observe an administrator log on to system components and examine system configurations to verify that non-console administrative access is managed in accordance with this requirement. 2. 2. 7. c Examine settings for system components and authentication services to verify that insecure remote login services are not available for non-console administrative access. 2. 2. 7. d Examine vendor documentation and interview personnel to verify that strong cryptography for the technology in use is implemented according to industry best practices and/or vendor recommendations. Customized Approach Objective Cleartext administrative authorization factors cannot be read or intercepted from any network transmissions. Applicability Notes This includes administrative access via browser-based interfaces and application programming interfaces (API s). | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 71 Requirements and Testing Procedures Guidance 2. 3 Wireless environments are configured and managed securely. Defined Approach Requirements Defined Approach Testing Procedures Purpose If wireless networks are not implemented with sufficient security configurations (including changing default settings), wireless sniffers can eavesdrop on the traffic, easily capture data and passwords, and easily enter and attack the network. Good Practi ce Wireless passwords should be constructed so that they are resistant to offline brute force attacks. 2. 3. 1 For wireless environments connected to the CDE or transmitting account data, all wireless vendor defaults are changed at installation or are confi rmed to be secure, including but not limited to: Default wireless encryption keys. Passwords on wireless access points. SNMP defaults. Any other security-related wireless vendor defaults. 2. 3. 1. a Examine policies and procedures and interview responsible personnel to verify that processes are defined for wireless vendor defaults to either change them upon installation or to confirm them to be secure in accordance with all elements of this requirement. 2. 3. 1. b Examine vendor documentation and observe a system administrator logging into wireless devices to verify: SNMP defaults are not used. Default passwords/passphrases on wireless access points are not used. 2. 3. 1. c Examine vendor documentation and wireless configuration settings to verify other security-related wireless vendor defaults were changed, if applicable. Customized Approach Objective Wireless networks cannot be accessed using vendor default passwords or default configurations. Applicability Notes This includes, but is not limited to, default wireless encryption keys, passwords on wireless access points, SNMP defaults, and any other security-related wireless vendor defaults. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 72 Requirements and Testing Procedures Guidance Defined Approach Requirements Defined Approach Testing Procedures Purpose Changing wireless encryption keys whenever someone with knowledge of the key leaves the organization or moves to a role that no longer requires knowledge of the key, helps keep knowl edge of keys limited to only those with a business need to know. Also, changing wireless encryption keys whenever a key is suspected or known to be comprised makes a wireless network more resistant to compromise. Good Practice This goal can be accomplished in multiple ways, including periodic changes of keys, changing keys via a defined “joiners-movers-leavers” (JML) process, implementing additional technical controls, and not using fixed pre-shared keys. In addition, any keys that are known to be, or suspected of being, compromised should be managed in accordance with the entity's incident response plan at Requirement 12. 10. 1. 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 role for which the knowledge was necessary. Whenever a key is suspected of or known to be compromised. 2. 3. 2 Interview responsible personnel and examine key-management documentation to verify that wireless encryption keys are changed in accordance with all elements specified in this requirement. Customized Approach Objective Knowledge of wireless encryption keys cannot allow unauthorized access to wireless networks. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 73 Protect Account Data Requirement 3: Protect Stored Account Data Sections 3. 1 Processes and mechanisms for protecting stored account data are defined and understood. 3. 2 Storage of account data is kept to a minimum. 3. 3 Sensitive authentication data (SAD) is not stored after authorization. 3. 4 Access to displays of full PAN and ability to copy cardholder data are restricted. 3. 5 Primary ac count number ( PAN) is secured wherever it is stored. 3. 6 Cryptographic keys used to protect stored account data are secured. 3. 7 Where cryptography is used to protect stored account data, key management processes and procedures covering all aspects of the key lifecycle are defined and implemented. Overview Protection methods such as encryption, truncation, masking, and hashing are critical components of account data protection. If an intruder circumvents other security controls and gains access to encrypted account data, the data is unreadable without the proper cry ptographic keys and is unusable to that intruder. Other effective methods of protecting stored data should also be considered as potential risk-mitigation opportunities. For example, methods for minimizing risk include not storing account data unless necessary, truncating cardholder data if full PAN is not need ed, and not sending unprotected PANs using end-user messaging technologies such as e-mail and instant messaging. If account data is present in non-persistent memory (for example, RAM, volatile memory), encryption of account data is not required. However, proper controls must be in place to ensure that memory maintains a non-persistent state. Data should be removed from volatile memory once the business purpose (for example, the associated transaction) is complete. In the case that data storage becomes persi stent, all applicable PCI DSS Requirements will apply including encryption of stored data. Requirement 3 applies to protection of stored account data unless specifically called out in an individual requirement. Refer to Appendix G for definitions of “strong cryptography” and other PCI DSS terms. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 74 Requirements and Testing Procedures Guidance 3. 1 Processes and mechanisms for protecting stored account data are defined and understood. Defined Approach Requirements Defined Approach Testing Procedures Purpose Requirement 3. 1. 1 is about effectively managing and maintaining the various policies and procedures specified throughout Requirement 3. While it is important to define the specific policies or procedures called out in Requirement 3, it is equally important to ensure they are properly documented, maintained, and disseminated. Good Practice It is important to update policies and procedures as needed to address changes in processes, technologies, and business objectives. For this reason, consider updating the se documents as soon as possible after a change occurs and not only on a periodic cycle. Definitions Security policies define the entity's security objectives and principles. Operational procedures describe how to perform activities, and define the controls, methods, and processes that are followed to achieve the desired result in a consistent manner and in accordance with policy objectives. 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. 1 Examine documentation and interview personnel to verify that security policies and operat ional procedures identified in Requirement 3 are managed in accordance with all elements specified in this requirement. Customized Approach Objective Expectations, controls, and oversight for meeting activities within Requirement 3 are defined and adhered to by affected personnel. All supporting activities are repeatable, consistently applied, and conform to management's intent. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 75 Requirements and Testing Procedures Guidance Defined Approach Requirements Defined Approach Testing Procedures Purpose If roles and responsibilities are not formally assigned, personnel may not be aware of their day-to-day responsibilities, and critical activities may not occur. Good Practice Roles and responsibilities may be documented within policies and procedures or maintained within separate documents. As part of communicating roles and responsibilities, entities can consider having personnel acknowledge their acceptance and understanding of their assigned roles and responsibilities. Examples A method to document roles and responsibilities is a responsib ility assignment matrix that includes who is responsible, accountable, consulted, and informed (also called a RACI matrix). 3. 1. 2 Roles and responsibilities for performing activities in Requirement 3 are documented, assigned, and understood. 3. 1. 2. a Examine documentation to verify that descriptions of roles and responsibilities performing activities in Requirement 3 are documented and assigned. 3. 1. 2. b Interview personnel with responsibility for performing activities in Requirement 3 to verify that roles and responsibilities are assigned as documented and are understood. Customized Approach Objective Day-to-day responsibilities for performing all the activities in Requirement 3 are allocated. Personnel are accountable for successful, continuous operation of these requirements. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 76 Requirements and Testing Procedures Guidance 3. 2 Storage of account data is kept to a minimum. Defined Approach Requirements Defined Approach Testing Procedures Purpose A formal data retention policy identifies what data needs to be retained, for how long, and where that data resides so it can be securely destroyed or deleted as soon as it is no longer needed. The only account data that may be stored after authorization i s the primary account number or PAN (rendered unreadable), expiration date, cardholder name, and service code. The storage of SAD data prior to the completion of the authorization process is also included in the data retention and disposal policy so that storage of this sensitive data is kept to minimum, and only retained for the defined amount of time. Good Practice When identifying locations of stored account data, consider all processes and personnel with access to the data, as data could have been move d and stored in different locations than originally defined. Storage locations that are often overlooked include backup and archive systems, removable data storage devices, paper-based media, and audio recordings. To define appropriate retention requirements, an entity first needs to understand its own business needs as well as any legal or regulatory obligations that apply to its industry or to the type of data being retained. Implementing an automated process to ensure data is automatically and securely deleted upon its defined retention limit can help ensure that account data is not retained beyond what is necessary for business, legal, or regulatory purposes. (continued on next page) 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 stored account data. Coverage for any sensitive authentication data (SAD ) stored prior to completion of authorization. This bullet is a best practice until its effective date; r efer to Applicability Notes below for details. Limiting data storage amount and retention time to that which is required for legal or regulatory, and/or business requirements. Specific retention requirements for stored account data that defines length of retention period and includes a documented busi ness justification. Processes for secure deletion or rendering account data unrecoverable when no longer needed per the retention policy. A process for verifying, at least once every three months, that stored account data exceeding the defined retention period has been securely deleted or rendered unrecoverable. 3. 2. 1. a Examine the data retention and disposal policies, procedures, and processes and interview personnel to verify processes are defined to include all elements specified in this requirement. 3. 2. 1. b Examine files and system records on system components where account data is stored to verify that the data storage amount and retention time does not exceed the requirements defined in the data retention policy. 3. 2. 1. c Observe the mechanisms used to render account data unrecoverable to verify data cannot be recovered. Customized Approach Objective Account data is retained only where necessary and for the least amount of time needed and is securely deleted or rendered unrecoverable when no longer needed. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 77 Requirements and Testing Procedures Guidance Applicability Notes Methods of eliminating data when it exceeds the retention period include secure deletion to complete remov al of the data or rendering it unrecoverable and unable to be reconstructed. Identifying and securely eliminating stored data that has exceeded its specified retention period prevents unnecessary retention of data that is no longer needed. This process may be automated, manual, or a combination of both. The deletion function in most operating systems is not “secure d eletion” as it allows deleted data to be recovered, so instead, a dedicated secure deletion function or application must be used to make data unrecoverable. Remember, if you don't need it, don't store it! Examples An automated, programmatic procedure coul d be run to locate and remove data, or a manual review of data storage areas could be performed. Whichever method is used, it is a good idea to monitor the process to ensure it is completed successfully, and that the results are recorded and validated as being complete. Implementing secure deletion methods ensures that the data cannot be retrieved when it is no longer needed. Further Information See NIST SP 800-88 Rev. 1, Guidelines for Media Sanitization. Where account data is stored by a TPSP (for example, in a cloud environment), entities are responsible for working with their service providers to understand how the TPSP meets this requirement for the entity. Considerations include ensuring that all geographic instances of a data element are securely deleted. The bullet above (for coverage of SAD stored prior to completion of authorization) is a best practice until 31 March 2025, after which it will be required as part of Requirement 3. 2. 1 and must be fully considered during a PCI DSS assessment. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 78 Requirements and Testing Procedures Guidance 3. 3 Sensitive authentication data (SAD) is not stored after authorization. Defined Approach Requirements Defined Approach Testing Procedures Purpose SAD is very valuable to malicious individuals as it allows them to generate counterfeit payment cards and create fraudulent transactions. Therefore, the storage of SAD upon completion of the authorization process is prohibited. Definitions The authorization process completes when a merchant receives a transaction response (for example, an approval or decline). 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. a If SAD is received, examine documented policies, procedures, and system conf igurations to verify the data is not retained after authorization. 3. 3. 1. b If SAD is received, examine the documented procedures and observe the secure data deletion processes to verify the data is rendered unrecoverable upon completion of the authorization process. Customized Approach Objective This requirement is not eligible for the customized approach. Applicability Notes This requirement does not apply to issuers and companies that support issuing services (where SAD is needed for a legitimate issuing business need) and have a business justification to store the sensitive authentication data. Refer to Requirement 3. 3. 3 for additional requirements specifically for issuers. Sensitive authentication data includes the data cited in Requirements 3. 3. 1. 1 through 3. 3. 1. 3. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 79 Requirements and Testing Procedures Guidance Defined Approach Requirements Defined Approach Testing Procedures Purpose If full contents of any track (from the magnetic stripe on the back of a card if present, equivalent data contained on a chip, or elsewhere) is stored, malicious individuals who obtain that data can use it to reproduce payment cards and complete fraudulent transactions. Definitions Full track data is alternatively called full track, track, track 1, track 2, and magnetic-stripe data. Each track contains a number of data elements, and this requirement specifies only those that may be retained post-authorizat ion. Examples Data sources to review to ensure that the full contents of any track are not retained upon completion of the authorization process include, but are not limited to: Incoming transaction data. All logs (for example, transaction, history, debugging, error). History files. Trace files. Database schemas. Contents of databases, and on-premise and cloud data stores. Any existing memory/crash dump files. 3. 3. 1. 1 The full contents of any track are not retained upon completion of the authorization process. 3. 3. 1. 1 Examine data sources to verify that the full contents of any track are not stored upon completion of the authorization process. Customized Approach Objective This requirement is not eligible for the customized approach. Applicability Notes In the normal course of business, the following data elements from the track may need to be retained: Cardholder name. Primary account number (PAN). Expiration date. Service code. To minimize risk, store securely only these data elements as needed for bus iness. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 80 Requirements and Testing Procedures Guidance Defined Approach Requirements Defined Approach Testing Procedures Purpose If card verification code data is stolen, malicious individuals can execute fraudulent Internet and mail-order/telephone-order ( MO/TO ) transactions. Not storing this data reduces the probability of it being compromised. Examples If card verification codes are stored on paper media prior to completion of authorization, a method of erasing or covering the codes should prevent them from bei ng read after authorization is complete. Example methods of rendering the codes unreadable include removing the code with scissors and applying a suitably opaque and un-removable marker over the code. Data sources to review to ensure that the card verifica tion code is not retained upon completion of the authorization process include, but are not limited to: Incoming transaction data. All logs (for example, transaction, history, debugging, error). History files. Trace files. Database schemas. Contents of databases, and on-premise and cloud data stores. Any existing memory/crash dump files. 3. 3. 1. 2 The card verification code is not retained upon completion of the authorization process. 3. 3. 1. 2 Examine data sources, to verify that the card verif ication code is not stored upon completion of the authorization process. Customized Approach Objective This requirement is not eligible for the customized approach. Applicability Notes The card verification code is the three-or four-digit number printed on the front or back of a payment card used to verify card-not-present transactions. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 81 Requirements and Testing Procedures Guidance Defined Approach Requirements Defined Approach Testing Procedures Purpose PIN and PIN blocks should be known only to the card owner or entity that issued the card. If this data is stolen, malicious individuals can execute fraudulent PIN-based transactions (for example, in-store purchases and ATM withdrawals). Not storing this data reduces the probability of it being compromised. Examples Data sources to review to ensure that PIN and PIN blocks are not retained upon completion of the authorization process include, but are not limited to: Incoming transaction data. All logs (for example, transaction, history, debugging, error). History files. Trace files. Database schemas. Contents of databases, and on-premise and cloud data stores. Any existing memory/crash dump files. 3. 3. 1. 3 The personal identification number (PIN) and the PIN block are not retained upon completion of the authorization process. 3. 3. 1. 3 Examine data sources, to verify that PINs and PIN blocks are not stored upon completion of the authorization process. Customized Approach Objective This requirement is not eligible for the customized approach. Applicability Notes PIN blocks are encrypted during the natural course of transaction processes, but even if an entity encrypts the PIN block again, it is still not allowed to be stored after the completion of the authorization process. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 82 Requirements and Testing Procedures Guidance Defined Approach Requirements Defined Approach Testing Procedures Purpose SAD can be used by malicious individuals to increase the probability of successfully generating counterfeit payment cards and creating fraudulent transactions. Good Practice Entities should consider encrypting SAD with a different cryptographic key than is used to encrypt PAN. Note that this does not mean that PAN present in S AD (as part of track data) would need to be separately encrypted. Definitions The authorization process is completed as soon as the response to an authorization request response— that is, an approval or decline—is received. 3. 3. 2 SAD that is stored electronically prior to completion of authorization is encrypted using strong cryptography. 3. 3. 2 Examine data stores, system configurations, and/or vendor documentation to verify that all SAD that is stored electronically prior to completion of authorization is encrypted using strong cryptography. Customized Approach Objective This requirement is not eligible for the customized approach. Applicability Notes Whether SAD is permitted to be stored prior to authorization is determined by the organizations that manage compliance programs (for example, payment brands and acquirers ). Contact the organizations of interest for any additional criteria. This requirement applies to all storage of SAD, even if no PAN is present in the environment. Refer to Requirement 3. 2. 1 for an additional requirement that appl ies if SAD is stored prior to completion of authorization. This requirement does not apply to issuers and companies that support issuing services where there is a legitimate issuing business justification to store SAD ). Refer to Requirement 3. 3. 3 for requirements specifically for issuers. This requirement does not replace how PIN blocks are required to be managed, nor does it mean that a properly encrypted PIN block needs to be encrypted again. This requirement is a best practice until 31 March 2025, after which it will be required and must be fully considered during a PCI DSS assessment. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 83 Requirements and Testing Procedures Guidance Defined Approach Requirements Defined Approach Testing Procedures Purpose SAD can be used by malicious individuals to increase the probability of successfully generating counterfeit payment cards and creating fraudulent transactions. Good Practice Entities should consider encrypting SAD with a different cryptographic key than is used to encrypt PAN. Note that this does not mean that PAN present in SAD (as part of track data) would need to be separately encrypted. Definitions Legitimate issuing business need mean s that the data is needed to facilitate the issuing business process. Further Information Refer to ISO/DIS 9564-5 Financial services — Personal Identification Number (PIN) 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 needed for a legitimate issuing business need and is secured. Encrypted using strong cryptography. This bullet is a best practice until its effective date; refer to Applicability Notes below for details. 3. 3. 3. a Additional testing procedure for issuers and companies that support issuing services and store sensitive authentication data: Examine documented policies and interview personnel to verify there is a documented business justification for the storage of sensitive authentication data. 3. 3. 3. b Additional testing procedure for issuers and companies that support issuing services and store sensitive authentication data: Examine data stores and system configurations to verify that the sensitive authentication data is stored securely. Customized Approach Objective Sensitive authentication data is retained only as required to support issuing functions and is secured from unauthorized access. Applicability Notes | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 84 Requirements and Testing Procedures Guidance This requirement applies only to issuers and companies that support issuing services and store sensitive authentication data. Entities that issue payment cards or that perform or support issuing services will often create and control sensitive authenticat ion data as part of the issuing function. It is allowable for companies that perform, facilitate, or support issuing services to store sensitive authentication data ONLY IF they have a legitimate business need to store such data. PCI DSS requirements are intended for all entities that store, process, or transmit account data, including issuers. The only exception for issuers and issuer processors is that sensitive authentication data may be retained if there is a legitimate reason to do so. Any such data must be stored securely and in accordance with all PCI DSS and specific payment brand requirements. The bullet above (for encrypting stored SAD with strong cryptography) is a best practice until 31 March 2025, after which it will be required as part of Requirement 3. 3. 3 and must be fully considered during a PCI DSS assessment. management and security — Part 5: Methods for the generation, change, and verification of PINs and card security data using the advanced encryption standard. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 85 Requirements and Testing Procedures Guidance 3. 4 Access to displays of full PAN and ability to copy PAN is restricted. Defined Approach Requirements Defined Approach Testing Procedures Purpose The display of full PAN on computer screens, payment card receipts, paper reports, etc. can result in this data being obtained by unauthorized individuals and used fraudulently. Ensuring that the full PAN is displayed only for those with a legitimate business need minimizes t he risk of unauthorized persons gaining access to PAN data. Good Practice Applying access controls according to defined roles is one way to limit access to viewing full PAN to only those individuals with a defined business need. The masking approach shoul d always display only the number of digits needed to perform a specific business function. For example, if only the last four digits are needed to perform a business function, PAN should be mask ed to only show the last four digits. As another example, if a function needs to view to the bank identification number (BIN) for routing purposes, unmask only the BIN digits for that function. Definitions Masking is not synonymous with truncation and these terms cannot be used interchangeably. Masking refers to the concealment of certain digits during display or printing, even when the entire PAN is stored on a system. This is different from truncation, in which the truncated digits are removed and cannot be retrieved within the system. Masked PAN could be “unmasked”, but there is no "un-truncation" without recreating the PAN from another source. Further Information For more information about masking and truncation, see PCI SSC's FAQs on these topic s. 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 last four digits of the PAN. 3. 4. 1. a Examine documented policies and procedures for masking the display of PAN s to verify: A list of roles that need access to more than the BIN and last four digits of the PAN (includes full PAN) is documented, together with a legitimate business need for each role to have such access. PAN is masked when displayed such that only personnel with a legitimate business need can see more than the BIN and last four digits of the PAN. All roles not specifically authorized to see the full PAN must only see masked PANs. Customized Approach Objective PAN displays are restricted to the minimum number of digits necessary to meet a defined business need. Applicability Notes 3. 4. 1. b Examine system configurations to verify that full PAN is only displayed for roles with a documented business need, and that PAN is masked for all other requests. This requirement does not supersede stricter requirements in place for displays of cardholder data—for example, legal or payment brand requirements for point-of-sale (POS) receipts. This requirement relates to protection of PAN where it is displayed on screens, paper receipts, printouts, etc., and is not to be confused with Requirement 3. 5. 1 for protection of PAN when stored, processed, or transmitted. 3. 4. 1. c Examine displays of PAN (for example, on screen, on paper receipts) to verify that PANs are masked when displayed, and that only those with a legitimate business need are able to see more than the BIN and/or last four digits of the PAN. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 86 Requirements and Testing Procedures Guidance Defined Approach Requirements Defined Approach Testing Procedures Purpose Relocation of PAN to unauthorized storage devices is a common way for this data to be obtained and used fraudulently. Methods to ensure that only those with explicit authorization and a legitimate business reason can copy or relocate PAN minimizes the risk of unauthorized persons gaining access to PAN. Good Practice Copying and relocation of PAN should only be done to storage devices that are permissible and authorized for that individual. Definitions A virtual desktop is an example of a remote-access technology. Storage devices include, but are not limited to, local hard drives, virtual drives, removable electronic media, network drives, and cloud storage. Further Information Vendor documentation for the remote-access technology in use will provide information about the system settings needed to implement this requirement. 3. 4. 2 When using remote-access technologies, technical controls prevent copy and/or relocati on of PAN for all personnel, except for those with documented, explicit authorization and a legitimate, defined business need. 3. 4. 2. a Examine documented policies and procedures and documented evidence for technical controls that prevent copy and/or reloca tion of PAN when using remote-access technologies onto local hard drives or removable electronic media to verify the following: Technical controls prevent all personnel not specifically authorized from copying and/or relocating PAN. A list of personnel w ith permission to copy and/or relocate PAN is maintained, together with the documented, explicit authorization and legitimate, defined business need. Customized Approach Objective PAN cannot be copied or relocated by unauthorized personnel using remote-access technologies. Applicability Notes 3. 4. 2. b Examine configurations for remote-access technologies to verify that technical controls to prevent copy and/or relocation of PAN for all personnel, unless explicitly authorized. Storing or relocating PAN onto local hard drives, removable electronic media, and other storage devices brings these devices into scope for PCI DSS. This requirement is a best practice until 31 March 2025, after which it will be required and must be fully considered during a PCI DSS assessment. 3. 4. 2. c Observe processes and interview personnel to verify that only personnel with documented, explicit authorization and a legitimate, defined business need have permission to copy and/or relocate PAN when using remote-access technologies. | PCI-DSS-v4_0 1.pdf |
Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4. 0 March 2022 © 2006-2022 PCI Security Standards Council, LLC. All rights reserved. Page 87 Requirements and Testing Procedures Guidance 3. 5 Primary account number ( PAN) is secured wherever it is stored. Defined Approach Requirements Defined Approach Testing Procedures Purpose The removal of cleartext stored PAN is a defense in depth control designed to protect the data if an unauthorized individual gains access to stored data by taking advantage of a vulnerability or misconfiguration of an entity's primary access control. Seco ndary independent control systems (for example governing access to, and use of, cryptography and decryption keys) prevent the failure of a primary access control system leading to a breach of confidentiality of stored PAN. If hashing is used to remove stor ed cleartext PAN, by correlating hashed and truncated versions of a given PAN, a malicious individual can easily derive the original PAN value. Controls that prevent the correlation of this data will help ensure that the original PAN remains unreadable. Further Information For information about truncation formats and truncation in general, see PCI SSC's FAQs on the topic. Sources for information about index tokens include: PCI SSC's Tokenization Product Security Guidelines (https://www. pcisecuritystandards. org/documents/Tokenization_Product_Security_Guidelines. pdf) ANSI X9. 119-2-2017: Retail Financial Services -Requirements For Protection Of Sensitiv e Payment Card Data-Part 2: Implementing Post-Authorization Tokenization Systems 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 replace the truncated segment of PAN). -If hashed and truncated versions of the same PAN, or different truncation formats of the same PAN, are present in an environment, additional controls are in place such that the different versions cannot be correlated to reconstruct the original PAN. Index tokens. Strong cryptography with associated key-management processes and procedures. 3. 5. 1. a Examine documentation about the system used to render PAN unreadable, including the vendor, type of system/process, and the encryption algorithms (if applicable) to verify that the PAN is rendered unreadable using any of the methods specified in this requirement. 3. 5. 1. b Examine data repositories and audit logs, including payment application logs, to verify the PAN is rendered unreadable using any of the methods specified in this requirement. 3. 5. 1. c If hashed and truncated versions of the same PAN are present in the environment, examine implemented controls to verify that the hashed and truncated versions cannot be correlated to reconstruct the original PAN. Customized Approach Objective Cleartext PAN cannot be read from storage media. Applicability Notes It is a relatively trivial effort for a malicious individual to reconstruct original PAN data if they have access to both the truncated and hashed version of a PAN. This requirement applies to PANs stored in primary storage (databases, or flat files such as text files spreadsheets) as well as non-primary storage (backup, audit logs, exception, or troubleshooting logs) must all be protected. This requirement does not preclude the use of temporary files containing cleartext PAN while encrypting and decrypting PAN. | PCI-DSS-v4_0 1.pdf |
End of preview. Expand
in Dataset Viewer.
README.md exists but content is empty.
Use the Edit dataset card button to edit it.
- Downloads last month
- 2