1.1.1 | 1.1.1 Requirement 1 policies and procedures governed | 17 |
1.1.2 | 1.1.2 Requirement 1 roles and responsibilities assigned | 18 |
1.2.1 | 1.2.1 Ruleset configuration standards for NSCs | 18 |
1.2.2 | 1.2.2 Network connection and NSC changes under change control | 19 |
1.2.3 | 1.2.3 Accurate network diagram of CDE connections | 18 |
1.2.4 | 1.2.4 Accurate data-flow diagram for account data | 15 |
1.2.5 | 1.2.5 Allowed services, protocols and ports justified | 22 |
1.2.6 | 1.2.6 Security features for insecure services in use | 17 |
1.2.7 | 1.2.7 Six-monthly review of NSC configurations | 18 |
1.2.8 | 1.2.8 NSC configuration files secured and consistent | 15 |
1.3.1 | 1.3.1 Inbound CDE traffic restricted | 20 |
1.3.2 | 1.3.2 Outbound CDE traffic restricted | 19 |
1.3.3 | 1.3.3 NSCs between wireless networks and the CDE | 13 |
1.4.1 | 1.4.1 NSCs between trusted and untrusted networks | 24 |
1.4.2 | 1.4.2 Restricting traffic entering trusted networks from outside | 19 |
1.4.3 | 1.4.3 Anti-spoofing measures at trusted boundary | 8 |
1.4.4 | 1.4.4 Cardholder data stores not reachable from untrusted networks | 19 |
1.4.5 | 1.4.5 Internal IP and routing disclosure limited | 10 |
1.5.1 | 1.5.1 Security controls on dual-connected devices | 16 |
10.1.1 | 10.1.1 Requirement 10 policies and procedures maintained and in use | 17 |
10.1.2 | 10.1.2 Roles for logging and monitoring assigned and understood | 12 |
10.2.1 | 10.2.1 Audit logging enabled on all system components | 24 |
10.2.1.1 | 10.2.1.1 Logs capture individual user access to cardholder data | 17 |
10.2.1.2 | 10.2.1.2 Logs capture all administrative actions | 18 |
10.2.1.3 | 10.2.1.3 Access to the audit logs is itself logged | 16 |
10.2.1.4 | 10.2.1.4 Logs capture invalid logical access attempts | 17 |
10.2.1.5 | 10.2.1.5 Logs capture changes to identification and authentication credentials | 18 |
10.2.1.6 | 10.2.1.6 Logs capture initialization and stopping of audit logs | 13 |
10.2.1.7 | 10.2.1.7 Logs capture creation and deletion of system-level objects | 14 |
10.2.2 | 10.2.2 Required details recorded for each auditable event | 19 |
10.3.1 | 10.3.1 Audit log read access limited to job need | 15 |
10.3.2 | 10.3.2 Audit log files protected from modification | 21 |
10.3.3 | 10.3.3 Audit logs promptly backed up to central secure storage | 16 |
10.3.4 | 10.3.4 File integrity monitoring on audit logs | 14 |
10.4.1 | 10.4.1 Daily review of security-relevant logs | 26 |
10.4.1.1 | 10.4.1.1 Automated mechanisms used for audit log review | 17 |
10.4.2 | 10.4.2 Periodic review of all other system component logs | 17 |
10.4.2.1 | 10.4.2.1 Periodic log review frequency set by targeted risk analysis | 9 |
10.4.3 | 10.4.3 Exceptions and anomalies from log review addressed | 24 |
10.5.1 | 10.5.1 Keep logs 12 months, latest three months online | 21 |
10.6.1 | 10.6.1 System clocks synchronized with time-sync technology | 15 |
10.6.2 | 10.6.2 Systems configured to correct and consistent time | 13 |
10.6.3 | 10.6.3 Time sync configuration and time data protected | 15 |
10.7.1 | 10.7.1 Service providers detect critical control failures (superseded) | 16 |
10.7.2 | 10.7.2 Detect and alert on critical security control failures | 25 |
10.7.3 | 10.7.3 Respond promptly to critical security control failures | 21 |
11.1.1 | 11.1.1 Requirement 11 policies and procedures managed | 19 |
11.1.2 | 11.1.2 Roles for security testing assigned and understood | 12 |
11.2.1 | 11.2.1 Detect authorized and rogue wireless access points | 14 |
11.2.2 | 11.2.2 Inventory of authorized wireless access points | 12 |
11.3.1 | 11.3.1 Quarterly internal vulnerability scans | 29 |
11.3.1.1 | 11.3.1.1 Lower-risk vulnerabilities handled per risk analysis | 20 |
11.3.1.2 | 11.3.1.2 Authenticated internal vulnerability scanning | 15 |
11.3.1.3 | 11.3.1.3 Internal scans after significant change | 18 |
11.3.2 | 11.3.2 Quarterly ASV external vulnerability scans | 22 |
11.3.2.1 | 11.3.2.1 External scans after significant change | 14 |
11.4.1 | 11.4.1 Penetration testing methodology defined and implemented | 22 |
11.4.2 | 11.4.2 Internal penetration testing annually and after change | 22 |
11.4.3 | 11.4.3 External penetration testing annually and after change | 24 |
11.4.4 | 11.4.4 Correct exploitable findings from penetration tests | 28 |
11.4.5 | 11.4.5 Annual segmentation penetration testing | 18 |
11.4.6 | 11.4.6 Service provider segmentation testing every six months | 9 |
11.4.7 | 11.4.7 Multi-tenant providers support customer penetration testing | 7 |
11.5.1 | 11.5.1 IDS/IPS monitoring of CDE traffic | 22 |
11.5.1.1 | 11.5.1.1 Service providers detect covert malware channels | 15 |
11.5.2 | 11.5.2 Change detection on critical files | 21 |
11.6.1 | 11.6.1 Payment page tamper detection | 10 |
12.1.1 | 12.1.1 Overall information security policy established and disseminated | 26 |
12.1.2 | 12.1.2 Security policy reviewed annually and updated as needed | 22 |
12.1.3 | 12.1.3 Security roles defined and acknowledged by all personnel | 21 |
12.1.4 | 12.1.4 Executive ownership of information security formally assigned | 21 |
12.10.1 | 12.10.1 Incident response plan ready for activation | 29 |
12.10.2 | 12.10.2 Annual review and testing of the incident response plan | 27 |
12.10.3 | 12.10.3 Incident response personnel available 24/7 | 19 |
12.10.4 | 12.10.4 Periodic training for incident response personnel | 20 |
12.10.4.1 | 12.10.4.1 Responder training frequency set by targeted risk analysis | 12 |
12.10.5 | 12.10.5 Plan covers alerts from security monitoring systems | 25 |
12.10.6 | 12.10.6 Plan evolved from lessons learned and industry developments | 24 |
12.10.7 | 12.10.7 Response procedures for PAN found in unexpected locations | 16 |
12.2.1 | 12.2.1 Rules for acceptable use of end-user technology | 20 |
12.3.1 | 12.3.1 Targeted risk analysis for flexible-frequency requirements | 25 |
12.3.2 | 12.3.2 Targeted risk analysis for each customized-approach requirement | 18 |
12.3.3 | 12.3.3 Cryptographic cipher suite and protocol inventory reviewed annually | 19 |
12.3.4 | 12.3.4 Annual review of hardware and software technologies | 23 |
12.4.1 | 12.4.1 Executive responsibility for a PCI DSS compliance program | 17 |
12.4.2 | 12.4.2 Quarterly reviews that personnel follow security procedures | 24 |
12.4.2.1 | 12.4.2.1 Documentation of quarterly operational reviews | 19 |
12.5.1 | 12.5.1 Inventory of in-scope system components | 25 |
12.5.2 | 12.5.2 Annual and change-driven scope confirmation | 28 |
12.5.2.1 | 12.5.2.1 Six-monthly scope confirmation for service providers | 12 |
12.5.3 | 12.5.3 Scope review after significant organisational change | 17 |
12.6.1 | 12.6.1 Formal security awareness program | 26 |
12.6.2 | 12.6.2 Awareness program reviewed annually and updated | 18 |
12.6.3 | 12.6.3 Security awareness training on hire and annually with acknowledgment | 28 |
12.6.3.1 | 12.6.3.1 Awareness training covers phishing and social engineering | 19 |
12.6.3.2 | 12.6.3.2 Awareness training covers acceptable use of end-user technologies | 18 |
12.7.1 | 12.7.1 Pre-hire screening of personnel with CDE access | 23 |
12.8.1 | 12.8.1 List of third-party service providers | 22 |
12.8.2 | 12.8.2 TPSP contracts acknowledging account data responsibility | 26 |
12.8.3 | 12.8.3 Due diligence before engaging TPSPs | 26 |
12.8.4 | 12.8.4 Annual monitoring of TPSP compliance status | 26 |
12.8.5 | 12.8.5 Responsibility allocation between entity and TPSPs | 25 |
12.9.1 | 12.9.1 TPSP written acknowledgments to customers | 10 |
12.9.2 | 12.9.2 TPSP support for customer information requests | 14 |
2.1.1 | 2.1.1 Requirement 2 policies and procedures governed | 34 |
2.1.2 | 2.1.2 Requirement 2 roles and responsibilities assigned | 31 |
2.2.1 | 2.2.1 System configuration standards maintained | 25 |
2.2.2 | 2.2.2 Vendor default accounts managed | 184 |
2.2.3 | 2.2.3 Primary functions with different security levels managed | 17 |
2.2.4 | 2.2.4 Only necessary functionality enabled | 23 |
2.2.5 | 2.2.5 Insecure services, protocols or daemons secured | 15 |
2.2.6 | 2.2.6 System security parameters configured against misuse | 20 |
2.2.7 | 2.2.7 Non-console administrative access encrypted | 19 |
2.3.1 | 2.3.1 Wireless vendor defaults changed or confirmed secure | 13 |
2.3.2 | 2.3.2 Wireless encryption keys changed on triggers | 14 |
3.3.1.1 | 3.3.1.1 Full track data not retained after authorization | 8 |
3.3.1.2 | 3.3.1.2 Card verification code not retained after authorization | 3 |
3.3.1.3 | 3.3.1.3 PIN and PIN block not retained after authorization | 5 |
3.3.2 | 3.3.2 Pre-authorization SAD stored electronically is strongly encrypted | 12 |
3.3.3 | 3.3.3 Issuer SAD storage limited, justified and encrypted | 9 |
3.4.2 | 3.4.2 Remote access blocks copying or relocating PAN | 14 |
3.5.1 | 3.5.1 Stored PAN rendered unreadable | 20 |
3.5.1.1 | 3.5.1.1 PAN hashes are keyed cryptographic hashes | 8 |
3.5.1.2 | 3.5.1.2 Disk or partition encryption only on removable media | 15 |
3.5.1.3 | 3.5.1.3 Disk encryption access independent of OS authentication | 14 |
3.6.1.1 | 3.6.1.1 Service provider cryptographic architecture documented | 14 |
3.6.1.2 | 3.6.1.2 Permitted storage forms for secret and private keys | 14 |
3.6.1.3 | 3.6.1.3 Cleartext key component access limited to minimum custodians | 15 |
3.6.1.4 | 3.6.1.4 Cryptographic keys kept in fewest locations | 12 |
3.7.2 | 3.7.2 Secure distribution of cryptographic keys | 15 |
3.7.3 | 3.7.3 Secure storage of cryptographic keys | 15 |
3.7.4 | 3.7.4 Key changes at end of cryptoperiod | 14 |
3.7.5 | 3.7.5 Retirement, replacement or destruction of keys | 13 |
3.7.6 | 3.7.6 Split knowledge and dual control for manual key operations | 9 |
3.7.7 | 3.7.7 Prevent unauthorized substitution of keys | 11 |
3.7.8 | 3.7.8 Key custodians formally acknowledge responsibilities | 11 |
3.7.9 | 3.7.9 Key guidance for service provider customers | 8 |
4.1.1 | 4.1.1 Requirement 4 policies and procedures maintained and communicated | 16 |
4.1.2 | 4.1.2 Requirement 4 roles and responsibilities assigned | 15 |
4.2.1 | 4.2.1 Strong cryptography safeguards PAN over public networks | 22 |
4.2.1.1 | 4.2.1.1 Inventory of trusted transmission keys and certificates | 16 |
4.2.1.2 | 4.2.1.2 Wireless networks use strong cryptography | 15 |
4.2.2 | 4.2.2 PAN secured when sent by end-user messaging | 18 |
5.1.1 | 5.1.1 Requirement 5 policies and procedures maintained and communicated | 16 |
5.1.2 | 5.1.2 Requirement 5 roles and responsibilities assigned | 14 |
5.2.3.1 | 5.2.3.1 Targeted risk analysis sets evaluation frequency | 12 |
5.3.2.1 | 5.3.2.1 Targeted risk analysis sets malware scan frequency | 12 |
5.3.4 | 5.3.4 Anti-malware audit logs enabled and retained | 16 |
5.3.5 | 5.3.5 Users cannot disable or alter anti-malware | 17 |
5.4.1 | 5.4.1 Mechanisms detect and protect against phishing | 17 |
6.1.1 | 6.1.1 Requirement 6 policies and procedures maintained and communicated | 17 |
6.1.2 | 6.1.2 Requirement 6 roles and responsibilities assigned | 15 |
6.2.1 | 6.2.1 Secure development of bespoke and custom software | 23 |
6.2.2 | 6.2.2 Annual secure software training for developers | 22 |
6.2.3 | 6.2.3 Code review before release | 20 |
6.2.3.1 | 6.2.3.1 Manual code review independence and approval | 19 |
6.2.4 | 6.2.4 Engineering techniques against common software attacks | 18 |
6.4.1 | 6.4.1 Public web application review or automated protection | 20 |
6.4.2 | 6.4.2 Automated web attack detection and prevention | 15 |
6.5.5 | 6.5.5 No live PANs in pre-production | 11 |
6.5.6 | 6.5.6 Remove test data and accounts before production | 12 |
7.1.1 | 7.1.1 Requirement 7 policies and procedures maintained | 17 |
7.1.2 | 7.1.2 Requirement 7 roles and responsibilities assigned | 13 |
7.2.1 | 7.2.1 Access control model defined | 25 |
7.2.2 | 7.2.2 User access assigned by job function and least privilege | 27 |
7.2.3 | 7.2.3 Privileges approved by authorized personnel | 20 |
7.2.5.1 | 7.2.5.1 Application and system account access reviewed periodically | 15 |
7.3.2 | 7.3.2 Access control system enforces role-based permissions | 17 |
7.3.3 | 7.3.3 Access control default deny all | 18 |
8.2.1 | 8.2.1 Unique ID assigned to every user | 23 |
8.2.2 | 8.2.2 Shared and generic IDs only by exception | 21 |
8.2.3 | 8.2.3 Service provider unique factors per customer | 9 |
8.2.4 | 8.2.4 User ID lifecycle changes authorized | 19 |
8.2.5 | 8.2.5 Terminated users' access revoked immediately | 21 |
8.2.6 | 8.2.6 Inactive accounts removed within 90 days | 18 |
8.2.7 | 8.2.7 Third-party remote access accounts controlled | 19 |
8.2.8 | 8.2.8 Re-authentication after 15 minutes idle | 14 |
8.3.1 | 8.3.1 Access authenticated with at least one factor | 24 |
8.3.10 | 8.3.10 Service provider customer password guidance | 10 |
8.3.10.1 | 8.3.10.1 Service provider customer passwords 90 days or dynamic | 6 |
8.3.11 | 8.3.11 Tokens, smart cards and certificates individually assigned | 11 |
8.3.2 | 8.3.2 Authentication factors unreadable with strong cryptography | 21 |
8.3.3 | 8.3.3 Identity verified before factor changes | 12 |
8.3.4 | 8.3.4 Lockout after 10 attempts for 30 minutes | 17 |
8.3.5 | 8.3.5 Initial and reset passwords unique and changed | 14 |
8.3.6 | 8.3.6 Password minimum length 12 and complexity | 20 |
8.3.7 | 8.3.7 No reuse of last four passwords | 12 |
8.3.8 | 8.3.8 Authentication policies communicated to users | 18 |
8.3.9 | 8.3.9 Single-factor passwords changed every 90 days or dynamic analysis | 12 |
8.4.1 | 8.4.1 MFA for non-console administrative CDE access | 23 |
8.4.2 | 8.4.2 MFA for all non-console CDE access | 24 |
8.4.3 | 8.4.3 MFA for remote access that could reach CDE | 22 |
8.5.1 | 8.5.1 MFA system resistant to replay and bypass | 20 |
9.1.1 | 9.1.1 Requirement 9 policies and procedures maintained | 16 |
9.1.2 | 9.1.2 Requirement 9 roles and responsibilities assigned | 15 |
9.2.1 | 9.2.1 Facility entry controls for CDE systems | 19 |
9.2.1.1 | 9.2.1.1 Monitoring of entry to sensitive areas | 18 |
9.2.2 | 9.2.2 Controls on publicly accessible network jacks | 17 |
9.2.3 | 9.2.3 Physical protection of network hardware and lines | 20 |
9.2.4 | 9.2.4 Locking of consoles in sensitive areas | 10 |
9.3.1 | 9.3.1 Personnel physical access procedures for the CDE | 19 |
9.3.1.1 | 9.3.1.1 Personnel access to sensitive areas controlled | 16 |
9.3.2 | 9.3.2 Visitor access procedures for the CDE | 15 |
9.3.3 | 9.3.3 Visitor badges returned or deactivated | 12 |
9.3.4 | 9.3.4 Visitor logs for facility and sensitive areas | 12 |
9.4.1 | 9.4.1 Physical security of all media | 18 |
9.4.1.1 | 9.4.1.1 Secure storage location for offline backups | 19 |
9.4.1.2 | 9.4.1.2 Annual review of offline backup location security | 15 |
9.4.2 | 9.4.2 Classification of media by data sensitivity | 17 |
9.4.3 | 9.4.3 Securing media sent outside the facility | 16 |
9.4.4 | 9.4.4 Management approval for media leaving facility | 14 |
9.4.5 | 9.4.5 Inventory logs of electronic media | 16 |
9.4.5.1 | 9.4.5.1 Annual inventories of electronic media | 15 |
9.4.6 | 9.4.6 Destruction of hard-copy materials | 15 |
9.4.7 | 9.4.7 Destruction of electronic media | 19 |
9.5.1 | 9.5.1 Protection of POI devices from tampering | 11 |
9.5.1.1 | 9.5.1.1 Current register of POI devices | 12 |
9.5.1.2 | 9.5.1.2 Periodic inspection of POI device surfaces | 8 |
9.5.1.3 | 9.5.1.3 Training for personnel in POI environments | 14 |
1.1 | 1.1 Governance of network security control processes | 0 |
1.2 | 1.2 Configuration and maintenance of NSCs | 0 |
1.3 | 1.3 Restriction of CDE network access | 0 |
1.4 | 1.4 Control of trusted and untrusted network connections | 0 |
1.5 | 1.5 Risk from dual-connected computing devices | 0 |
10.1 | 10.1 Logging and monitoring governance defined | 0 |
10.2 | 10.2 Audit logs support anomaly detection and forensics | 0 |
10.3 | 10.3 Audit logs protected from destruction and tampering | 0 |
10.4 | 10.4 Audit logs reviewed for anomalies | 0 |
10.5 | 10.5 Audit log history retained | 0 |
10.6 | 10.6 Time synchronization across systems | 0 |
10.7 | 10.7 Critical security control failures handled promptly | 0 |
11.1 | 11.1 Governance of security testing activities | 0 |
11.2 | 11.2 Wireless access point detection | 0 |
11.3 | 11.3 Vulnerability scanning | 0 |
11.4 | 11.4 Penetration testing | 0 |
11.5 | 11.5 Intrusion and change detection | 0 |
11.6 | 11.6 Payment page change detection | 0 |
12.1 | 12.1 Overall information security policy | 0 |
12.10 | 12.10 Security incident response | 0 |
12.2 | 12.2 Acceptable use of end-user technologies | 0 |
12.3 | 12.3 Risk identification and management for the CDE | 0 |
12.4 | 12.4 PCI DSS compliance management | 0 |
12.5 | 12.5 PCI DSS scope documentation and validation | 0 |
12.6 | 12.6 Security awareness education | 0 |
12.7 | 12.7 Personnel screening | 0 |
12.8 | 12.8 Third-party service provider risk management | 0 |
12.9 | 12.9 TPSP support for customer compliance | 0 |
2.1 | 2.1 Governance of secure configuration processes | 0 |
2.2 | 2.2 Secure configuration and management of system components | 0 |
2.3 | 2.3 Secure wireless configuration and management | 0 |
3.1 | 3.1 Governance of stored account data protection | 0 |
3.1.1 | 3.1.1 Requirement 3 policies and procedures maintained and in use | 17 |
3.1.2 | 3.1.2 Assigned duties for Requirement 3 activities | 16 |
3.2 | 3.2 Minimising account data storage | 0 |
3.2.1 | 3.2.1 Data retention and disposal minimise stored account data | 23 |
3.3 | 3.3 No SAD retained after authorization | 0 |
3.3.1 | 3.3.1 SAD not retained after authorization, even encrypted | 10 |
3.4 | 3.4 Restricting PAN display and copying | 0 |
3.4.1 | 3.4.1 PAN masked on display except for authorized roles | 11 |
3.5 | 3.5 PAN protected wherever stored | 0 |
3.6 | 3.6 Securing cryptographic keys | 0 |
3.6.1 | 3.6.1 Procedures protect keys against disclosure and misuse | 19 |
3.7 | 3.7 Key lifecycle management | 0 |
3.7.1 | 3.7.1 Generation of strong cryptographic keys | 18 |
4.1 | 4.1 Governance for encrypting PAN in transit | 0 |
4.2 | 4.2 PAN encrypted while in transit | 0 |
5.1 | 5.1 Governance for malware protection | 0 |
5.2 | 5.2 Malware prevented or detected and addressed | 0 |
5.2.1 | 5.2.1 Anti-malware deployed on all system components | 24 |
5.2.2 | 5.2.2 Anti-malware detects and handles all known malware | 22 |
5.2.3 | 5.2.3 Periodic evaluation of components not at risk from malware | 14 |
5.3 | 5.3 Anti-malware kept active, current and monitored | 0 |
5.3.1 | 5.3.1 Anti-malware kept current through automatic updates | 21 |
5.3.2 | 5.3.2 Periodic and real-time scans or continuous behavioural analysis | 18 |
5.3.3 | 5.3.3 Anti-malware covers removable electronic media | 18 |
5.4 | 5.4 Anti-phishing protection for personnel | 0 |
6.1 | 6.1 Governance of secure systems and software processes | 0 |
6.2 | 6.2 Secure development of bespoke and custom software | 0 |
6.3 | 6.3 Identifying and addressing security vulnerabilities | 0 |
6.3.1 | 6.3.1 Vulnerability identification and risk ranking | 26 |
6.3.2 | 6.3.2 Inventory of bespoke software and components | 21 |
6.3.3 | 6.3.3 Timely installation of security patches | 27 |
6.4 | 6.4 Protection of public-facing web applications | 0 |
6.4.3 | 6.4.3 Payment page script management | 15 |
6.5 | 6.5 Secure management of changes | 0 |
6.5.1 | 6.5.1 Change control procedure for production | 21 |
6.5.2 | 6.5.2 Confirm PCI DSS controls after significant change | 20 |
6.5.3 | 6.5.3 Separate pre-production from production | 21 |
6.5.4 | 6.5.4 Separate roles between production and pre-production | 19 |
7.1 | 7.1 Governance of need-to-know access restriction | 0 |
7.2 | 7.2 Access defined and assigned appropriately | 0 |
7.2.4 | 7.2.4 User accounts and privileges reviewed every six months | 24 |
7.2.5 | 7.2.5 Application and system accounts least privilege | 19 |
7.2.6 | 7.2.6 Query access to stored cardholder data restricted | 15 |
7.3 | 7.3 Access managed through access control systems | 0 |
7.3.1 | 7.3.1 Need-to-know access control system covers all components | 20 |
8.1 | 8.1 Governance of identification and authentication | 0 |
8.1.1 | 8.1.1 Requirement 8 policies and procedures maintained | 17 |
8.1.2 | 8.1.2 Requirement 8 roles and responsibilities assigned | 15 |
8.2 | 8.2 User identification and account lifecycle | 0 |
8.3 | 8.3 Strong user and administrator authentication | 0 |
8.4 | 8.4 MFA for access into the CDE | 0 |
8.5 | 8.5 MFA systems configured against misuse | 0 |
8.6 | 8.6 Application and system account management | 0 |
8.6.1 | 8.6.1 Interactive use of system accounts controlled | 15 |
8.6.2 | 8.6.2 No hard-coded passwords for interactive system accounts | 18 |
8.6.3 | 8.6.3 System account passwords protected against misuse | 18 |
9.1 | 9.1 Physical access governance defined and understood | 0 |
9.2 | 9.2 Physical entry controls for facilities and CDE systems | 0 |
9.3 | 9.3 Authorization and management of personnel and visitor access | 0 |
9.4 | 9.4 Secure storage, access, distribution and destruction of media | 0 |
9.5 | 9.5 POI devices protected from tampering and substitution | 0 |
9.5.1.2.1 | 9.5.1.2.1 Risk-based frequency and type of POI inspections | 0 |
A1.1 | A1.1 Separation and protection of customer environments | 0 |
A1.1.1 | A1.1.1 Logical separation between provider and customer environments | 0 |
A1.1.2 | A1.1.2 Customers limited to their own cardholder data and CDE | 0 |
A1.1.3 | A1.1.3 Customers restricted to their allocated resources | 0 |
A1.1.4 | A1.1.4 Penetration testing of tenant separation every six months | 0 |
A1.2 | A1.2 Per-customer logging and incident support | 0 |
A1.2.1 | A1.2.1 Per-customer audit logging consistent with Requirement 10 | 0 |
A1.2.2 | A1.2.2 Support for prompt forensic investigation of any customer | 0 |
A1.2.3 | A1.2.3 Customer reporting and remediation of incidents and vulnerabilities | 0 |
A2.1 | A2.1 SSL/early TLS POI terminals free of known exploits | 0 |
A2.1.1 | A2.1.1 Confirm SSL/early TLS POS POI devices resist known exploits | 0 |
A2.1.2 | A2.1.2 Risk Mitigation and Migration Plan for SSL/early TLS connections | 0 |
A2.1.3 | A2.1.3 Service providers offer a secure protocol option | 0 |
A3.1 | A3.1 PCI DSS compliance program | 0 |
A3.1.1 | A3.1.1 Executive management responsibility for the PCI DSS compliance program | 0 |
A3.1.2 | A3.1.2 Formal PCI DSS compliance program elements | 0 |
A3.1.3 | A3.1.3 Defined and assigned PCI DSS compliance roles | 0 |
A3.1.4 | A3.1.4 Annual PCI DSS training for compliance personnel | 0 |
A3.2 | A3.2 Scope documentation and validation | 0 |
A3.2.1 | A3.2.1 Quarterly and change-driven scope documentation and validation | 0 |
A3.2.2 | A3.2.2 Scope impact of every system or network change | 0 |
A3.2.2.1 | A3.2.2.1 Post-change confirmation that PCI DSS controls are in place | 0 |
A3.2.3 | A3.2.3 Scope review after organizational structure changes | 0 |
A3.2.4 | A3.2.4 Six-monthly penetration testing of segmentation controls | 0 |
A3.2.5 | A3.2.5 Data-discovery methodology for cleartext PAN | 0 |
A3.2.5.1 | A3.2.5.1 Annual confirmation of data-discovery effectiveness | 0 |
A3.2.5.2 | A3.2.5.2 Response procedures when cleartext PAN is found outside the CDE | 0 |
A3.2.6 | A3.2.6 Mechanisms to detect and block cleartext PAN leaving the CDE | 0 |
A3.2.6.1 | A3.2.6.1 Response procedures for attempted removal of cleartext PAN | 0 |
A3.3 | A3.3 PCI DSS in business-as-usual activities | 0 |
A3.3.1 | A3.3.1 Prompt detection and alerting of critical security control failures | 0 |
A3.3.1.1 | A3.3.1.1 Prompt response to critical security control failures | 0 |
A3.3.2 | A3.3.2 Annual review of hardware and software technologies | 0 |
A3.3.3 | A3.3.3 Quarterly review that BAU activities are followed | 0 |
A3.4 | A3.4 Control of logical access to the CDE | 0 |
A3.4.1 | A3.4.1 Six-monthly review of user accounts and access privileges | 0 |
A3.5 | A3.5 Identification and response to suspicious events | 0 |
A3.5.1 | A3.5.1 Methodology for prompt detection of attack patterns | 1 |
APPENDIX-A1 | Appendix A1 Extra requirements for multi-tenant service providers | 0 |
APPENDIX-A2 | Appendix A2 SSL and early TLS on card-present POS POI terminals | 0 |
APPENDIX-A3 | Appendix A3 DESV supplemental validation for designated entities | 0 |
APPLICABILITY | Who PCI DSS applies to and which data it protects | 0 |
APPROACHES | Defined approach, customized approach and compensating controls (Appendices B to E) | 0 |
ASSESSMENT | How PCI DSS is assessed: sampling, testing methods, reporting and protected artefacts | 0 |
SCOPE | Scope of the requirements: the cardholder data environment, segmentation and third-party service providers | 0 |
STANDARD | PCI DSS v4.0.1: the standard and its edition | 0 |
TIMEFRAMES | Timeframes, business-as-usual practice and missed activities | 0 |