Skip to main content

πŸ’Ό PCI DSS v3.2.1

  • ID: /frameworks/pci-dss-v3.2.1

Stats​

not available

Description​

Empty...

Similar​

  • Internal
    • ID: dec-a-8f3c08bb

Sub Sections​

SectionSub SectionsInternal RulesPoliciesFlagsCompliance
πŸ’Ό 1 Install and maintain a firewall configuration to protect cardholder data519101no data
γ€€πŸ’Ό 1.1 Establish and implement firewall and router configuration standards7145no data
γ€€γ€€πŸ’Ό 1.1.1 A formal process for approving and testing all network connections and changes to the firewall and router configurations.no data
γ€€γ€€πŸ’Ό 1.1.2 Current network diagram that identifies all connections between the cardholder data environment and other networks, including any wireless networks.no data
γ€€γ€€πŸ’Ό 1.1.3 Current diagram that shows all cardholder data flows across systems and networks.no data
γ€€γ€€πŸ’Ό 1.1.4 Requirements for a firewall at each Internet connection and between any demilitarized zone (DMZ) and the internal network zone.no data
γ€€γ€€πŸ’Ό 1.1.5 Description of groups, roles, and responsibilities for management of network components.no data
γ€€γ€€πŸ’Ό 1.1.6 Documentation of business justification and approval for use of all services, protocols, and ports allowed, including documentation of security features implemented for those protocols considered to be insecure.132no data
γ€€γ€€πŸ’Ό 1.1.7 Requirement to review firewall and router rule sets at least every six months.9no data
γ€€πŸ’Ό 1.2 Build firewall and router configurations that restrict connections between untrusted networks and any system components in the cardholder data environment31067no data
γ€€γ€€πŸ’Ό 1.2.1 Restrict inbound and outbound traffic to that which is necessary for the cardholder data environment, and specifically deny all other traffic.1067no data
γ€€γ€€πŸ’Ό 1.2.2 Secure and synchronize router configuration files.no data
γ€€γ€€πŸ’Ό 1.2.3 Install perimeter firewalls between all wireless networks and the cardholder data environment, and configure these firewalls to deny or, if traffic is necessary for business purposes, permit only authorized traffic between the wireless environment and the cardholder data environment.no data
γ€€πŸ’Ό 1.3 Prohibit direct public access between the Internet and any system component in the cardholder data environment.7844no data
γ€€γ€€πŸ’Ό 1.3.1 Implement a DMZ to limit inbound traffic to only system components that provide authorized publicly accessible services, protocols, and ports.630no data
γ€€γ€€πŸ’Ό 1.3.2 Limit inbound Internet traffic to IP addresses within the DMZ.30no data
γ€€γ€€πŸ’Ό 1.3.3 Implement anti-spoofing measures to detect and block forged source IP addresses from entering the network.no data
γ€€γ€€πŸ’Ό 1.3.4 Do not allow unauthorized outbound traffic from the cardholder data environment to the Internet.15no data
γ€€γ€€πŸ’Ό 1.3.5 Permit only β€œestablished” connections into the network.30no data
γ€€γ€€πŸ’Ό 1.3.6 Place system components that store cardholder data in an internal network zone, segregated from the DMZ and other untrusted networks.15no data
γ€€γ€€πŸ’Ό 1.3.7 Do not disclose private IP addresses and routing information to unauthorized parties.1no data
γ€€πŸ’Ό 1.4 Install personal firewall software or equivalent functionality on any portable computing devices that connect to the Internet when outside the network, and which are also used to access the CDE.8no data
γ€€πŸ’Ό 1.5 Ensure that security policies and operational procedures for managing firewalls are documented, in use, and known to all affected parties.8no data
πŸ’Ό 2 Do not use vendor-supplied defaults for system passwords and other security parameters.6651no data
γ€€πŸ’Ό 2.1 Always change vendor-supplied defaults and remove or disable unnecessary default accounts before installing a system on the network.111no data
γ€€γ€€πŸ’Ό 2.1.1 For wireless environments connected to the cardholder data environment or transmitting cardholder data, change ALL wireless vendor defaults at installation, including but not limited to default wireless encryption keys, passwords, and SNMP community strings.2no data
γ€€πŸ’Ό 2.2 Develop configuration standards for all system components. Assure that these standards address all known security vulnerabilities and are consistent with industry-accepted system hardening standards.5333no data
γ€€γ€€πŸ’Ό 2.2.1 Implement only one primary function per server to prevent functions that require different security levels from co-existing on the same server.no data
γ€€γ€€πŸ’Ό 2.2.2 Enable only necessary services, protocols, daemons, etc., as required for the function of the system.3no data
γ€€γ€€πŸ’Ό 2.2.3 Implement additional security features for any required services, protocols, or daemons that are considered to be insecure.33no data
γ€€γ€€πŸ’Ό 2.2.4 Configure system security parameters to prevent misuse.17no data
γ€€γ€€πŸ’Ό 2.2.5 Remove all unnecessary functionality, such as scripts, drivers, features, subsystems, file systems, and unnecessary web servers.3no data
γ€€πŸ’Ό 2.3 Encrypt all non-console administrative access using strong cryptography.312no data
γ€€πŸ’Ό 2.4 Maintain an inventory of system components that are in scope for PCI DSS.1no data
γ€€πŸ’Ό 2.5 Ensure that security policies and operational procedures for managing vendor defaults and other security parameters are documented, in use, and known to all affected parties.8no data
γ€€πŸ’Ό 2.6 Shared hosting providers must protect each entity's hosted environment and cardholder data.no data
πŸ’Ό 3 Protect stored cardholder data7716no data
γ€€πŸ’Ό 3.1 Keep cardholder data storage to a minimum by implementing data retention and disposal policies.1no data
γ€€πŸ’Ό 3.2 Do not store sensitive authentication data after authorization (even if encrypted).35no data
γ€€γ€€πŸ’Ό 3.2.1 Do not store the full contents of any track after authorization.no data
γ€€γ€€πŸ’Ό 3.2.2 Do not store the card verification code or value after authorization.no data
γ€€γ€€πŸ’Ό 3.2.3 Do not store the personal identification number (PIN) or the encrypted PIN block after authorization.no data
γ€€πŸ’Ό 3.3 Mask PAN when displayed, such that only personnel with a legitimate business need can see more than the first six/last four digits of the PAN.no data
γ€€πŸ’Ό 3.4 Render PAN unreadable anywhere it is stored.1713no data
γ€€γ€€πŸ’Ό 3.4.1 If disk encryption is used, logical access must be managed separately and independently of native operating system authentication and access control mechanisms.712no data
γ€€πŸ’Ό 3.5 Document and implement procedures to protect keys used to secure stored cardholder data against disclosure and misuse.41no data
γ€€γ€€πŸ’Ό 3.5.1 Maintain a documented description of the cryptographic architectureno data
γ€€γ€€πŸ’Ό 3.5.2 Restrict access to cryptographic keys to the fewest number of custodians necessary.no data
γ€€γ€€πŸ’Ό 3.5.3 Store secret and private keys used to encrypt/decrypt cardholder data in one (or more) of the described forms at all times.no data
γ€€γ€€πŸ’Ό 3.5.4 Store cryptographic keys in the fewest possible locations.no data
γ€€πŸ’Ό 3.6 Fully document and implement all keymanagement processes and procedures for cryptographic keys used for encryption of cardholder data.81no data
γ€€γ€€πŸ’Ό 3.6.1 Generation of strong cryptographic keys.no data
γ€€γ€€πŸ’Ό 3.6.2 Secure cryptographic key distribution.no data
γ€€γ€€πŸ’Ό 3.6.3 Secure cryptographic key storage.no data
γ€€γ€€πŸ’Ό 3.6.4 Cryptographic key changes for keys that have reached the end of their cryptoperiod, as defined by the associated application vendor or key owner, and based on industry best practices and guidelines.1no data
γ€€γ€€πŸ’Ό 3.6.5 Retirement or replacement of keys as deemed necessary when the integrity of the key has been weakened, or keys are suspected of being compromised.no data
γ€€γ€€πŸ’Ό 3.6.6 If manual clear-text cryptographic key-management operations are used, these operations must be managed using split knowledge and dual control.no data
γ€€γ€€πŸ’Ό 3.6.7 Prevention of unauthorized substitution of cryptographic keys.no data
γ€€γ€€πŸ’Ό 3.6.8 Requirement for cryptographic key custodians to formally acknowledge that they understand and accept their key-custodian responsibilities.no data
γ€€πŸ’Ό 3.7 Ensure that security policies and operational procedures for protecting stored cardholder data are documented, in use, and known to all affected parties.5no data
πŸ’Ό 4 Encrypt transmission of cardholder data across open, public networks.3828no data
γ€€πŸ’Ό 4.1 Use strong cryptography and security protocols to safeguard sensitive cardholder data during transmission over open, public networks.1828no data
γ€€γ€€πŸ’Ό 4.1.1 Ensure wireless networks transmitting cardholder data or connected to the cardholder data environment, use industry best practices to implement strong encryption for authentication and transmission.1no data
γ€€πŸ’Ό 4.2 Never send unprotected PANs by enduser messaging technologies.4no data
γ€€πŸ’Ό 4.3 Ensure that security policies and operational procedures for encrypting transmissions of cardholder data are documented, in use, and known to all affected parties.1no data
πŸ’Ό 5 Protect all systems against malware and regularly update anti-virus software or programs.4413no data
γ€€πŸ’Ό 5.1 Deploy anti-virus software on all systems commonly affected by malicious software.244no data
γ€€γ€€πŸ’Ό 5.1.1 Ensure that anti-virus programs are capable of detecting, removing, and protecting against all known types of malicious software.no data
γ€€γ€€πŸ’Ό 5.1.2 For systems considered to be not commonly affected by malicious software, perform periodic evaluations to identify and evaluate evolving malware threats in order to confirm whether such systems continue to not require anti-virus software.no data
γ€€πŸ’Ό 5.2 Ensure that all anti-virus mechanisms are maintained.9no data
γ€€πŸ’Ό 5.3 Ensure that anti-virus mechanisms are actively running and cannot be disabled or altered by users, unless specifically authorized by management on a case-by-case basis for a limited time period.no data
γ€€πŸ’Ό 5.4 Ensure that security policies and operational procedures for protecting systems against malware are documented, in use, and known to all affected parties.no data
πŸ’Ό 6 Develop and maintain secure systems and applications726no data
γ€€πŸ’Ό 6.1 Establish a process to identify security vulnerabilities, using reputable outside sources for security vulnerability information, and assign a risk ranking to newly discovered security vulnerabilities.2no data
γ€€πŸ’Ό 6.2 Ensure that all system components and software are protected from known vulnerabilities by installing applicable vendor-supplied security patches.7no data
γ€€πŸ’Ό 6.3 Develop internal and external software applications securely.24no data
γ€€γ€€πŸ’Ό 6.3.1 Remove development, test and/or custom application accounts, user IDs, and passwords before applications become active or are released to customers.no data
γ€€γ€€πŸ’Ό 6.3.2 Review custom code prior to release to production or customers in order to identify any potential coding vulnerability.1no data
γ€€πŸ’Ό 6.4 Follow change control processes and procedures for all changes to system components.6no data
γ€€γ€€πŸ’Ό 6.4.1 Separate development/test environments from production environments, and enforce the separation with access controls.no data
γ€€γ€€πŸ’Ό 6.4.2 Separation of duties between development/test and production environments.no data
γ€€γ€€πŸ’Ό 6.4.3 Production data (live PANs) are not used for testing or development.no data
γ€€γ€€πŸ’Ό 6.4.4 Removal of test data and accounts from system components before the system becomes active / goes into production.no data
γ€€γ€€πŸ’Ό 6.4.5 Change control procedures.4no data
γ€€γ€€γ€€πŸ’Ό 6.4.5.1 Documentation of impact.no data
γ€€γ€€γ€€πŸ’Ό 6.4.5.2 Documented change approval by authorized parties.no data
γ€€γ€€γ€€πŸ’Ό 6.4.5.3 Functionality testing to verify that the change does not adversely impact the security of the system.no data
γ€€γ€€γ€€πŸ’Ό 6.4.5.4 Back-out proceduresno data
γ€€γ€€πŸ’Ό 6.4.6 Upon completion of a significant change, all relevant PCI DSS requirements must be implemented on all new or changed systems and networks, and documentation updated as applicable.no data
γ€€πŸ’Ό 6.5 Address common coding vulnerabilities in software-development processes.105no data
γ€€γ€€πŸ’Ό 6.5.1 Injection flaws, particularly SQL injection. Also consider OS Command Injection, LDAP and XPath injection flaws as well as other injection flaws.5no data
γ€€γ€€πŸ’Ό 6.5.2 Buffer overflows.5no data
γ€€γ€€πŸ’Ό 6.5.3 Insecure cryptographic storage.5no data
γ€€γ€€πŸ’Ό 6.5.4 Insecure communications.5no data
γ€€γ€€πŸ’Ό 6.5.5 Improper error handling.5no data
γ€€γ€€πŸ’Ό 6.5.6 All β€œhigh risk” vulnerabilities identified in the vulnerability identification process.5no data
γ€€γ€€πŸ’Ό 6.5.7 Cross-site scripting (XSS).5no data
γ€€γ€€πŸ’Ό 6.5.8 Improper access control.5no data
γ€€γ€€πŸ’Ό 6.5.9 Cross-site request forgery (CSRF).5no data
γ€€γ€€πŸ’Ό 6.5.10 Broken authentication and session management.5no data
γ€€πŸ’Ό 6.6 For public-facing web applications, address new threats and vulnerabilities on an ongoing basis and ensure these applications are protected against known attacks.11no data
γ€€πŸ’Ό 6.7 Ensure that security policies and operational procedures for developing and maintaining secure systems and applications are documented, in use, and known to all affected parties.no data
πŸ’Ό 7 Restrict access to cardholder data by business need to know320no data
γ€€πŸ’Ό 7.1 Limit access to system components and cardholder data to only those individuals whose job requires such access.48no data
γ€€γ€€πŸ’Ό 7.1.1 Define access needs for each role.1no data
γ€€γ€€πŸ’Ό 7.1.2 Restrict access to privileged user IDs to least privileges necessary to perform job responsibilities.5no data
γ€€γ€€πŸ’Ό 7.1.3 Assign access based on individual personnel's job classification and function.5no data
γ€€γ€€πŸ’Ό 7.1.4 Require documented approval by authorized parties specifying required privileges.no data
γ€€πŸ’Ό 7.2 Establish an access control system(s) for systems components that restricts access based on a user's need to know, and is set to β€œdeny all” unless specifically allowed.313no data
γ€€γ€€πŸ’Ό 7.2.1 Coverage of all system components.11no data
γ€€γ€€πŸ’Ό 7.2.2 Assignment of privileges to individuals based on job classification and function.no data
γ€€γ€€πŸ’Ό 7.2.3 Default β€œdeny-all” setting.1no data
γ€€πŸ’Ό 7.3 Ensure that security policies and operational procedures for restricting access to cardholder data are documented, in use, and known to all affected parties.no data
πŸ’Ό 8 Identify and authenticate access to system components8430no data
γ€€πŸ’Ό 8.1 Define and implement policies and procedures to ensure proper user identification management for non-consumer users and administrators on all system components.835no data
γ€€γ€€πŸ’Ό 8.1.1 Assign all users a unique ID before allowing them to access system components or cardholder data.22no data
γ€€γ€€πŸ’Ό 8.1.2 Control addition, deletion, and modification of user IDs, credentials, and other identifier objects.11no data
γ€€γ€€πŸ’Ό 8.1.3 Immediately revoke access for any terminated users.no data
γ€€γ€€πŸ’Ό 8.1.4 Remove/disable inactive user accounts within 90 days.2no data
γ€€γ€€πŸ’Ό 8.1.5 Manage IDs used by third parties to access, support, or maintain system components via remote access.no data
γ€€γ€€πŸ’Ό 8.1.6 Limit repeated access attempts by locking out the user ID after not more than six attempts.no data
γ€€γ€€πŸ’Ό 8.1.7 Set the lockout duration to a minimum of 30 minutes or until an administrator enables the user ID.no data
γ€€γ€€πŸ’Ό 8.1.8 If a session has been idle for more than 15 minutes, require the user to re-authenticate to re-activate the terminal or session.no data
γ€€πŸ’Ό 8.2 In addition to assigning a unique ID, ensure proper user-authentication management for non-consumer users and administrators on all system components.6121no data
γ€€γ€€πŸ’Ό 8.2.1 Using strong cryptography, render all authentication credentials unreadable during transmission and storage on all system components.14no data
γ€€γ€€πŸ’Ό 8.2.2 Verify user identity before modifying any authentication credential.no data
γ€€γ€€πŸ’Ό 8.2.3 Passwords/passphrases must have complexity and strength.13no data
γ€€γ€€πŸ’Ό 8.2.4 Change user passwords/passphrases at least once every 90 days.4no data
γ€€γ€€πŸ’Ό 8.2.5 Do not allow an individual to submit a new password/passphrase that is the same as any of the last four passwords/passphrases he or she has used.13no data
γ€€γ€€πŸ’Ό 8.2.6 Set passwords/passphrases for first-time use and upon reset to a unique value for each user, and change immediately after the first use.no data
γ€€πŸ’Ό 8.3 Secure all individual non-console administrative access and all remote access to the CDE using multi-factor authentication.24no data
γ€€γ€€πŸ’Ό 8.3.1 Incorporate multi-factor authentication for all non-console access into the CDE for personnel with administrative access.3no data
γ€€γ€€πŸ’Ό 8.3.2 Incorporate multi-factor authentication for all remote network access originating from outside the entity's network.1no data
γ€€πŸ’Ό 8.4 Document and communicate authentication policies and procedures to all users.no data
γ€€πŸ’Ό 8.5 Do not use group, shared, or generic IDs, passwords, or other authentication methods.112no data
γ€€γ€€πŸ’Ό 8.5.1 Service providers with remote access to customer premises must use a unique authentication credential for each customer.no data
γ€€πŸ’Ό 8.6 Where other authentication mechanisms are used, use of these mechanisms must be assigned.1no data
γ€€πŸ’Ό 8.7 All access to any database containing cardholder data is restricted.no data
γ€€πŸ’Ό 8.8 Ensure that security policies and operational procedures for identification and authentication are documented, in use, and known to all affected parties.no data
πŸ’Ό 9 Restrict physical access to cardholder data107no data
γ€€πŸ’Ό 9.1 Use appropriate facility entry controls to limit and monitor physical access to systems in the cardholder data environment.3no data
γ€€γ€€πŸ’Ό 9.1.1 Use either video cameras or access control mechanisms (or both) to monitor individual physical access to sensitive areas.no data
γ€€γ€€πŸ’Ό 9.1.2 Implement physical and/or logical controls to restrict access to publicly accessible network jacks.no data
γ€€γ€€πŸ’Ό 9.1.3 Restrict physical access to wireless access points, gateways, handheld devices, networking/communications hardware, and telecommunication lines.no data
γ€€πŸ’Ό 9.2 Develop procedures to easily distinguish between onsite personnel and visitors.no data
γ€€πŸ’Ό 9.3 Control physical access for onsite personnel to sensitive areas.no data
γ€€πŸ’Ό 9.4 Implement procedures to identify and authorize visitors.4no data
γ€€γ€€πŸ’Ό 9.4.1 Visitors are authorized before entering, and escorted at all times within, areas where cardholder data is processed or maintained.no data
γ€€γ€€πŸ’Ό 9.4.2 Visitors are identified and given a badge or other identification that expires and that visibly distinguishes the visitors from onsite personnel.no data
γ€€γ€€πŸ’Ό 9.4.3 Visitors are asked to surrender the badge or identification before leaving the facility or at the date of expiration.no data
γ€€γ€€πŸ’Ό 9.4.4 A visitor log is used to maintain a physical audit trail of visitor activity to the facility as well as computer rooms and data centers where cardholder data is stored or transmitted.no data
γ€€πŸ’Ό 9.5 Physically secure all media.1no data
γ€€γ€€πŸ’Ό 9.5.1 Store media backups in a secure location, preferably an off-site facility.no data
γ€€πŸ’Ό 9.6 Maintain strict control over the internal or external distribution of any kind of media.3no data
γ€€γ€€πŸ’Ό 9.6.1 Classify media so the sensitivity of the data can be determined.no data
γ€€γ€€πŸ’Ό 9.6.2 Send the media by secured courier or other delivery method that can be accurately tracked.no data
γ€€γ€€πŸ’Ό 9.6.3 Ensure management approves any and all media that is moved from a secured area.no data
γ€€πŸ’Ό 9.7 Maintain strict control over the storage and accessibility of media.16no data
γ€€γ€€πŸ’Ό 9.7.1 Properly maintain inventory logs of all media and conduct media inventories at least annuallyno data
γ€€πŸ’Ό 9.8 Destroy media when it is no longer needed for business or legal reasons.2no data
γ€€γ€€πŸ’Ό 9.8.1 Shred, incinerate, or pulp hard-copy materials so that cardholder data cannot be reconstructed.no data
γ€€γ€€πŸ’Ό 9.8.2 Render cardholder data on electronic media unrecoverable so that cardholder data cannot be reconstructed.no data
γ€€πŸ’Ό 9.9 Protect devices that capture payment card data via direct physical interaction with the card from tampering and substitution.31no data
γ€€γ€€πŸ’Ό 9.9.1 Maintain an up-to-date list of devices.1no data
γ€€γ€€πŸ’Ό 9.9.2 Periodically inspect device surfaces to detect tampering, or substitution.no data
γ€€γ€€πŸ’Ό 9.9.3 Provide training for personnel to be aware of attempted tampering or replacement of devices.no data
γ€€πŸ’Ό 9.10 Ensure that security policies and operational procedures for restricting physical access to cardholder data are documented, in use, and known to all affected parties.no data
πŸ’Ό 10 Track and monitor all access to network resources and cardholder data9747no data
γ€€πŸ’Ό 10.1 Implement audit trails to link all access to system components to each individual user.47no data
γ€€πŸ’Ό 10.2 Implement automated audit trails for all system components.7633no data
γ€€γ€€πŸ’Ό 10.2.1 All individual user accesses to cardholder data.414no data
γ€€γ€€πŸ’Ό 10.2.2 All actions taken by any individual with root or administrative privileges.16no data
γ€€γ€€πŸ’Ό 10.2.3 Access to all audit trails.9no data
γ€€γ€€πŸ’Ό 10.2.4 Invalid logical access attempts.414no data
γ€€γ€€πŸ’Ό 10.2.5 Use of and changes to identification and authentication mechanisms.116no data
γ€€γ€€πŸ’Ό 10.2.6 Initialization, stopping, or pausing of the audit logs.9no data
γ€€γ€€πŸ’Ό 10.2.7 Creation and deletion of system level objects.12no data
γ€€πŸ’Ό 10.3 Record audit trail entries for all system components for each event.610no data
γ€€γ€€πŸ’Ό 10.3.1 User identification.no data
γ€€γ€€πŸ’Ό 10.3.2 Type of event.no data
γ€€γ€€πŸ’Ό 10.3.3 Date and time.1no data
γ€€γ€€πŸ’Ό 10.3.4 Success or failure indication.1no data
γ€€γ€€πŸ’Ό 10.3.5 Origination of event.1no data
γ€€γ€€πŸ’Ό 10.3.6 Identity or name of affected data, system component, or resource.1no data
γ€€πŸ’Ό 10.4 Using time-synchronization technology, synchronize all critical system clocks and times.3no data
γ€€γ€€πŸ’Ό 10.4.1 Critical systems have the correct and consistent time.no data
γ€€γ€€πŸ’Ό 10.4.2 Time data is protected.no data
γ€€γ€€πŸ’Ό 10.4.3 Time settings are received from industry-accepted time sources.no data
γ€€πŸ’Ό 10.5 Secure audit trails so they cannot be altered.519no data
γ€€γ€€πŸ’Ό 10.5.1 Limit viewing of audit trails to those with a job-related need.no data
γ€€γ€€πŸ’Ό 10.5.2 Protect audit trail files from unauthorized modifications.14no data
γ€€γ€€πŸ’Ό 10.5.3 Promptly back up audit trail files to a centralized log server or media that is difficult to alter.3no data
γ€€γ€€πŸ’Ό 10.5.4 Write logs for external-facing technologies onto a secure, centralized, internal log server or media device.3no data
γ€€γ€€πŸ’Ό 10.5.5 Use file-integrity monitoring or change-detection software on logs to ensure that existing log data cannot be changed without generating alerts.12no data
γ€€πŸ’Ό 10.6 Review logs and security events for all system components to identify anomalies or suspicious activity.39no data
γ€€γ€€πŸ’Ό 10.6.1 Review security events and critical system component logs at least daily.2no data
γ€€γ€€πŸ’Ό 10.6.2 Review logs of all other system components periodically based on the organization's policies and risk management strategy, as determined by the organization's annual risk assessment.9no data
γ€€γ€€πŸ’Ό 10.6.3 Follow up exceptions and anomalies identified during the review process.2no data
γ€€πŸ’Ό 10.7 Retain audit trail history for at least one year, with a minimum of three months immediately available for analysis.1no data
γ€€πŸ’Ό 10.8 Implement a process for the timely detection and reporting of failures of critical security control systems.1no data
γ€€γ€€πŸ’Ό 10.8.1 Respond to failures of any critical security controls in a timely manner.no data
γ€€πŸ’Ό 10.9 Ensure that security policies and operational procedures for monitoring all access to network resources and cardholder data are documented, in use, and known to all affected parties.no data
πŸ’Ό 11 Regularly test security systems and processes.6120no data
γ€€πŸ’Ό 11.1 Implement processes to test for the presence of wireless access points (802.11), and detect and identify all authorized and unauthorized wireless access points on a quarterly basis.22no data
γ€€γ€€πŸ’Ό 11.1.1 Maintain an inventory of authorized wireless access points including a documented business justification.1no data
γ€€γ€€πŸ’Ό 11.1.2 Implement incident response procedures in the event unauthorized wireless access points are detected.1no data
γ€€πŸ’Ό 11.2 Run internal and external network vulnerability scans at least quarterly and after any significant change in the network.32no data
γ€€γ€€πŸ’Ό 11.2.1 Perform quarterly internal vulnerability scans. Address vulnerabilities and perform rescans to verify all β€œhigh risk” vulnerabilities are resolved in accordance with the entity's vulnerability ranking.2no data
γ€€γ€€πŸ’Ό 11.2.2 Perform quarterly external vulnerability scans, via an Approved Scanning Vendor (ASV) approved by the Payment Card Industry Security Standards Council (PCI SSC).no data
γ€€γ€€πŸ’Ό 11.2.3 Perform internal and external scans, and rescans as needed, after any significant change.no data
γ€€πŸ’Ό 11.3 Implement a methodology for penetration testing.4no data
γ€€γ€€πŸ’Ό 11.3.1 Perform external penetration testing at least annually and after any significant infrastructure or application upgrade or modification.no data
γ€€γ€€πŸ’Ό 11.3.2 Perform internal penetration testing at least annually and after any significant infrastructure or application upgrade or modification.no data
γ€€γ€€πŸ’Ό 11.3.3 Exploitable vulnerabilities found during penetration testing are corrected and testing is repeated to verify the corrections.no data
γ€€γ€€πŸ’Ό 11.3.4 If segmentation is used to isolate the CDE from other networks, perform penetration tests at least annually and after any changes to segmentation controls/methods to verify that the segmentation methods are operational and effective, and isolate all out-of-scope systems from systems in the CDE.1no data
γ€€γ€€γ€€πŸ’Ό 11.3.4.1 If segmentation is used, confirm PCI DSS scope by performing penetration testing on segmentation controls at least every six months and after any changes to segmentation controls/methods.no data
γ€€πŸ’Ό 11.4 Use intrusion-detection and/or intrusion-prevention techniques to detect and/or prevent intrusions into the network.113no data
γ€€πŸ’Ό 11.5 Deploy a change-detection mechanism to alert personnel to unauthorized modification of critical system files, configuration files, or content files.15no data
γ€€γ€€πŸ’Ό 11.5.1 Implement a process to respond to any alerts generated by the change detection solution.1no data
γ€€πŸ’Ό 11.6 Ensure that security policies and operational procedures for security monitoring and testing are documented, in use, and known to all affected parties.no data
πŸ’Ό 12 Maintain a policy that addresses information security for all personnel.111no data
γ€€πŸ’Ό 12.1 Establish, publish, maintain, and disseminate a security policy.1no data
γ€€γ€€πŸ’Ό 12.1.1 Review the security policy at least annually and update the policy when the environment changes.no data
γ€€πŸ’Ό 12.2 Implement a risk-assessment process.no data
γ€€πŸ’Ό 12.3 Develop usage policies for critical technologies and define proper use of these technologies.10no data
γ€€γ€€πŸ’Ό 12.3.1 Explicit approval by authorized parties.no data
γ€€γ€€πŸ’Ό 12.3.2 Authentication for use of the technology.no data
γ€€γ€€πŸ’Ό 12.3.3 A list of all such devices and personnel with access.no data
γ€€γ€€πŸ’Ό 12.3.4 A method to accurately and readily determine owner, contact information, and purpose.no data
γ€€γ€€πŸ’Ό 12.3.5 Acceptable uses of the technology.no data
γ€€γ€€πŸ’Ό 12.3.6 Acceptable network locations for the technologies.no data
γ€€γ€€πŸ’Ό 12.3.7 List of company-approved products.no data
γ€€γ€€πŸ’Ό 12.3.8 Automatic disconnect of sessions for remote-access technologies after a specific period of inactivity.no data
γ€€γ€€πŸ’Ό 12.3.9 Activation of remote-access technologies for vendors and business partners only when needed by vendors and business partners, with immediate deactivation after use.no data
γ€€γ€€πŸ’Ό 12.3.10 For personnel accessing cardholder data via remote-access technologies, prohibit the copying, moving, and storage of cardholder data onto local hard drives and removable electronic media, unless explicitly authorized for a defined business need.no data
γ€€πŸ’Ό 12.4 Ensure that the security policy and procedures clearly define information security responsibilities for all personnel.1no data
γ€€γ€€πŸ’Ό 12.4.1 Executive management shall establish responsibility for the protection of cardholder data and a PCI DSS compliance program.no data
γ€€πŸ’Ό 12.5 Assign to an individual or team information security management responsibilities.5no data
γ€€γ€€πŸ’Ό 12.5.1 Establish, document, and distribute security policies and procedures.no data
γ€€γ€€πŸ’Ό 12.5.2 Monitor and analyze security alerts and information, and distribute to appropriate personnel.no data
γ€€γ€€πŸ’Ό 12.5.3 Establish, document, and distribute security incident response and escalation procedures to ensure timely and effective handling of all situations.no data
γ€€γ€€πŸ’Ό 12.5.4 Administer user accounts, including additions, deletions, and modifications.no data
γ€€γ€€πŸ’Ό 12.5.5 Monitor and control all access to data.no data
γ€€πŸ’Ό 12.6 Implement a formal security awareness program to make all personnel aware of the cardholder data security policy and procedures.2no data
γ€€γ€€πŸ’Ό 12.6.1 Educate personnel upon hire and at least annually.no data
γ€€γ€€πŸ’Ό 12.6.2 Require personnel to acknowledge at least annually that they have read and understood the security policy and procedures.no data
γ€€πŸ’Ό 12.7 Screen potential personnel prior to hire to minimize the risk of attacks from internal sources.no data
γ€€πŸ’Ό 12.8 Maintain and implement policies and procedures to manage service providers with whom cardholder data is shared, or that could affect the security of cardholder data.5no data
γ€€γ€€πŸ’Ό 12.8.1 Maintain a list of service providers including a description of the service provided.no data
γ€€γ€€πŸ’Ό 12.8.2 Maintain a written agreement that includes an acknowledgement that the service providers are responsible for the security of cardholder data the service providers possess or otherwise store, process or transmit on behalf of the customer, or to the extent that they could impact the security of the customer's cardholder data environment.no data
γ€€γ€€πŸ’Ό 12.8.3 Ensure there is an established process for engaging service providers including proper due diligence prior to engagement.no data
γ€€γ€€πŸ’Ό 12.8.4 Maintain a program to monitor service providers' PCI DSS compliance status at least annually.no data
γ€€γ€€πŸ’Ό 12.8.5 Maintain information about which PCI DSS requirements are managed by each service provider, and which are managed by the entity.no data
γ€€πŸ’Ό 12.9 Service providers acknowledge in writing to customers that they are responsible for the security of cardholder data the service provider possesses or otherwise stores, processes, or transmits on behalf of the customer, or to the extent that they could impact the security of the customer's cardholder data environment.no data
γ€€πŸ’Ό 12.10 Implement an incident response plan.61no data
γ€€γ€€πŸ’Ό 12.10.1 Create the incident response plan to be implemented in the event of system breach.no data
γ€€γ€€πŸ’Ό 12.10.2 Review and test the plan at least annually.no data
γ€€γ€€πŸ’Ό 12.10.3 Designate specific personnel to be available on a 24/7 basis to respond to alerts.no data
γ€€γ€€πŸ’Ό 12.10.4 Provide appropriate training to staff with security breach response responsibilities.no data
γ€€γ€€πŸ’Ό 12.10.5 Include alerts from security monitoring systems, including but not limited to intrusion-detection, intrusion-prevention, firewalls, and file-integrity monitoring systems.1no data
γ€€γ€€πŸ’Ό 12.10.6 Develop a process to modify and evolve the incident response plan according to lessons learned and to incorporate industry developments.no data
γ€€πŸ’Ό 12.11 Perform reviews at least quarterly to confirm personnel are following security policies and operational procedures.1no data
γ€€γ€€πŸ’Ό 12.11.1 Maintain documentation of quarterly review process.no data