APPX-A | Compensating controls (the standard's Appendix A-1) | 0 |
ASSESS | Assessment and reporting: 3DS Assessors, the ROC and the AOC | 0 |
DATA-MATRIX | PCI 3DS Data Matrix v1.3 (September 2026): 3DS sensitive data and HSM keys | 0 |
P1-1.1 | P1-1.1 Maintain security policies | 0 |
P1-1.1.1 | P1-1.1.1 Organisation-wide security policy exists and reaches everyone concerned | 1 |
P1-1.1.2 | P1-1.1.2 Policy revised when business aims or risks change | 1 |
P1-1.1.3 | P1-1.1.3 Policy changes communicated to the people affected | 1 |
P1-1.1.4 | P1-1.1.4 Management approval of the security policy | 2 |
P1-1.1.5 | P1-1.1.5 Personnel confirm they have read and understood the policy | 1 |
P1-1.2 | P1-1.2 Evaluate risk | 0 |
P1-1.2.1 | P1-1.2.1 Written risk-assessment process | 1 |
P1-1.2.2 | P1-1.2.2 Risk assessment run yearly and after significant change | 1 |
P1-1.3 | P1-1.3 Educate personnel | 0 |
P1-1.3.1 | P1-1.3.1 Security awareness programme in operation | 1 |
P1-1.3.2 | P1-1.3.2 Awareness training at set intervals, fitted to the role | 1 |
P1-1.3.3 | P1-1.3.3 Staff know the policy and their own security duties | 1 |
P1-1.4 | P1-1.4 Screen personnel | 0 |
P1-1.4.1 | P1-1.4.1 Background screening before 3DE access | 2 |
P1-1.4.2 | P1-1.4.2 Screening criteria and decision process defined | 1 |
P1-2.1 | P1-2.1 Protect 3DS systems from untrusted systems and networks | 0 |
P1-2.1.1 | P1-2.1.1 Boundary-protection policy and procedures for the 3DE | 1 |
P1-2.1.2 | P1-2.1.2 Current network and data-flow records for every 3DS path | 1 |
P1-2.1.3 | P1-2.1.3 Physical or logical limits between trusted and untrusted zones | 2 |
P1-2.1.4 | P1-2.1.4 Only necessary 3DS traffic permitted, rest denied | 1 |
P1-2.1.5 | P1-2.1.5 Network controls monitored or reviewed for effectiveness | 1 |
P1-2.2 | P1-2.2 Protect 3DS systems from network threats | 0 |
P1-2.2.1 | P1-2.2.1 Detection or blocking of known and unknown network attacks | 2 |
P1-2.2.2 | P1-2.2.2 Suspicious traffic blocked or alerted and acted upon | 1 |
P1-3.1 | P1-3.1 Secure application development | 0 |
P1-3.1.1 | P1-3.1.1 Secure development lifecycle policy and procedures | 2 |
P1-3.1.2 | P1-3.1.2 Developers trained in secure development | 1 |
P1-3.1.3 | P1-3.1.3 Development procedures address common coding weaknesses | 1 |
P1-3.1.4 | P1-3.1.4 Security testing during development using documented methods | 1 |
P1-3.1.5 | P1-3.1.5 Testing surfaces defects and vulnerabilities | 1 |
P1-3.1.6 | P1-3.1.6 Defects and vulnerabilities fixed before release | 1 |
P1-3.1.7 | P1-3.1.7 Management signs off test results before release | 1 |
P1-3.2 | P1-3.2 Configuration standards | 0 |
P1-3.2.1 | P1-3.2.1 Build and configuration management policy and procedures | 1 |
P1-3.2.2 | P1-3.2.2 Current inventory of 3DS system components | 2 |
P1-3.2.3 | P1-3.2.3 Configuration standards defined and applied to every 3DS system type | 1 |
P1-3.2.4 | P1-3.2.4 Standards cover known weaknesses and follow hardening benchmarks | 1 |
P1-3.2.5 | P1-3.2.5 Build standards remove defaults, excess functions and mixed trust levels | 1 |
P1-3.3 | P1-3.3 Change management | 0 |
P1-3.3.1 | P1-3.3.1 Change-control procedures for all changes, including emergencies | 2 |
P1-3.3.2 | P1-3.3.2 Changes authorised with security impact understood first | 1 |
P1-3.3.3 | P1-3.3.3 Changes tested outside production | 2 |
P1-3.3.4 | P1-3.3.4 Rollback prepared for every change | 1 |
P1-3.3.5 | P1-3.3.5 Unauthorised configuration changes prevented or detected and handled | 1 |
P1-4.1 | P1-4.1 Protect against malicious software | 0 |
P1-4.1.1 | P1-4.1.1 Malware-protection policy and procedures | 1 |
P1-4.1.2 | P1-4.1.2 Anti-malware controls active and maintained | 2 |
P1-4.2 | P1-4.2 Address vulnerabilities and security weaknesses | 0 |
P1-4.2.1 | P1-4.2.1 Vulnerability-management policy and procedures | 1 |
P1-4.2.2 | P1-4.2.2 Quarterly internal and external vulnerability scans | 1 |
P1-4.2.3 | P1-4.2.3 Scans run by qualified parties, external by an ASV | 1 |
P1-4.2.4 | P1-4.2.4 Vulnerabilities ranked by criticality | 2 |
P1-4.2.5 | P1-4.2.5 Annual penetration testing | 1 |
P1-4.2.6 | P1-4.2.6 Penetration tests by qualified personnel | 1 |
P1-4.2.7 | P1-4.2.7 High-risk findings fixed within a month, others promptly | 1 |
P1-5.1 | P1-5.1 Access management | 0 |
P1-5.1.1 | P1-5.1.1 Access-assignment policy and procedures | 1 |
P1-5.1.2 | P1-5.1.2 Roles and responsibilities defined for groups and accounts | 1 |
P1-5.1.3 | P1-5.1.3 Least privilege by job function, reviewed periodically | 1 |
P1-5.2 | P1-5.2 Account management | 0 |
P1-5.2.1 | P1-5.2.1 Account-management policy and procedures | 1 |
P1-5.2.2 | P1-5.2.2 Unique account ID per individual | 2 |
P1-5.2.3 | P1-5.2.3 Accounts and credentials kept confidential and intact | 1 |
P1-5.2.4 | P1-5.2.4 Account misuse prevented | 1 |
P1-5.2.5 | P1-5.2.5 Third-party access identified, controlled and monitored | 1 |
P1-5.3 | P1-5.3 Authentication | 0 |
P1-5.3.1 | P1-5.3.1 Strong authentication for all access to 3DS systems | 1 |
P1-6.1 | P1-6.1 Restrict physical access | 0 |
P1-6.1.1 | P1-6.1.1 Physical-access policy and procedures for 3DS systems | 1 |
P1-6.1.2 | P1-6.1.2 Entry controls limit and monitor physical access | 1 |
P1-6.1.3 | P1-6.1.3 Physical access authorised by job function | 1 |
P1-6.1.4 | P1-6.1.4 Physical access removed immediately on termination | 1 |
P1-6.2 | P1-6.2 Secure media | 0 |
P1-6.2.1 | P1-6.2.1 Strict control over media storage and access | 2 |
P1-7.1 | P1-7.1 Incident response plan | 0 |
P1-7.1.1 | P1-7.1.1 Incident-management policy and procedures | 1 |
P1-7.1.2 | P1-7.1.2 Incident response plan with its required elements | 2 |
P1-7.1.3 | P1-7.1.3 Plan reviewed and tested every year | 1 |
P1-7.2 | P1-7.2 Audit logs | 0 |
P1-7.2.1 | P1-7.2.1 Audit-logging policy and procedures | 1 |
P1-7.2.2 | P1-7.2.2 Logs tie access to individuals and record security events | 1 |
P1-7.2.3 | P1-7.2.3 Clocks synchronised on 3DS systems | 2 |
P1-7.2.4 | P1-7.2.4 Logs and security events monitored or reviewed | 1 |
P1-7.2.5 | P1-7.2.5 Audit logs protected from alteration | 1 |
P1-7.2.6 | P1-7.2.6 Log retention of one year, three months at hand | 1 |
P2-1.1 | P2-1.1 Scoping | 0 |
P2-1.1.1 | P2-1.1.1 In-scope networks and components identified | 1 |
P2-1.1.2 | P2-1.1.2 Out-of-scope networks justified with their segmentation | 1 |
P2-1.1.3 | P2-1.1.3 Connected entities with 3DE access identified | 1 |
P2-2.1 | P2-2.1 Security governance | 0 |
P2-2.1.1 | P2-2.1.1 Security objectives aligned with business objectives | 1 |
P2-2.1.2 | P2-2.1.2 Security responsibility and accountability formally assigned | 1 |
P2-2.1.3 | P2-2.1.3 Responsibility for evolving risks assigned | 1 |
P2-2.2 | P2-2.2 Manage risk | 0 |
P2-2.2.1 | P2-2.2.1 Formal risk-management strategy defined | 1 |
P2-2.2.2 | P2-2.2.2 Risk strategy approved and kept current | 1 |
P2-2.3 | P2-2.3 Business as usual (BAU) | 0 |
P2-2.3.1 | P2-2.3.1 Periodic checks that staff follow security policies | 1 |
P2-2.3.2 | P2-2.3.2 Security control failures detected and responded to | 1 |
P2-2.4 | P2-2.4 Manage third-party relationships | 0 |
P2-2.4.1 | P2-2.4.1 Third-party relationship policies and procedures | 1 |
P2-2.4.2 | P2-2.4.2 Due diligence before engaging a third party | 1 |
P2-2.4.3 | P2-2.4.3 Security responsibilities defined per engagement | 1 |
P2-2.4.4 | P2-2.4.4 Third parties' agreed responsibilities verified periodically | 2 |
P2-2.4.5 | P2-2.4.5 Written agreements maintained | 2 |
P2-3.1 | P2-3.1 Protect boundaries | 0 |
P2-3.1.1 | P2-3.1.1 ACS and DS traffic limited to 3DS functions | 1 |
P2-3.1.2 | P2-3.1.2 ACS and DS reachable only through approved interfaces | 1 |
P2-3.2 | P2-3.2 Protect baseline configurations | 0 |
P2-3.2.1 | P2-3.2.1 Configurations and security documentation protected | 1 |
P2-3.3 | P2-3.3 Protect applications and application interfaces | 0 |
P2-3.3.1 | P2-3.3.1 Production applications protected from unauthorised change | 1 |
P2-3.3.2 | P2-3.3.2 Application protection mechanisms monitored and maintained | 1 |
P2-3.3.3 | P2-3.3.3 APIs to the 3DE identified, defined and tested | 1 |
P2-3.3.4 | P2-3.3.4 APIs exposed to untrusted networks protected | 1 |
P2-3.4 | P2-3.4 Secure web configurations | 0 |
P2-3.4.1 | P2-3.4.1 Only required HTTP methods accepted | 1 |
P2-3.4.2 | P2-3.4.2 HTTPS enforced everywhere | 1 |
P2-3.4.3 | P2-3.4.3 External content rejected by default | 1 |
P2-3.4.4 | P2-3.4.4 Framing by untrusted sites prevented | 1 |
P2-3.4.5 | P2-3.4.5 Native framework protections enabled | 1 |
P2-3.5 | P2-3.5 Maintain availability of 3DS operations | 0 |
P2-3.5.1 | P2-3.5.1 Availability mechanisms against loss of 3DS processing | 2 |
P2-3.5.2 | P2-3.5.2 Availability mechanisms monitored and maintained | 1 |
P2-4.1 | P2-4.1 Secure connections for issuer and merchant customers | 0 |
P2-4.1.1 | P2-4.1.1 Issuer and merchant user access to their own interfaces | 1 |
P2-4.2 | P2-4.2 Secure internal network connections | 0 |
P2-4.2.1 | P2-4.2.1 Multi-factor for all non-console personnel access | 1 |
P2-4.3 | P2-4.3 Secure remote access | 0 |
P2-4.3.1 | P2-4.3.1 Multi-factor for remote access into the 3DE | 1 |
P2-4.3.2 | P2-4.3.2 Remote access controlled and documented | 2 |
P2-4.3.3 | P2-4.3.3 Rules for personally owned devices used remotely | 2 |
P2-4.3.4 | P2-4.3.4 Remote access privileges reviewed at least quarterly | 1 |
P2-4.4 | P2-4.4 Restrict wireless exposure | 0 |
P2-4.4.1 | P2-4.4.1 No wireless use by 3DS components | 2 |
P2-4.5 | P2-4.5 Secure VPNs | 0 |
P2-4.5.1 | P2-4.5.1 VPNs into the 3DE securely configured | 1 |
P2-5.1 | P2-5.1 Data lifecycle | 0 |
P2-5.1.1 | P2-5.1.1 3DS data lifecycle policies and procedures | 1 |
P2-5.1.2 | P2-5.1.2 3DS data kept only as long as needed, then purged securely | 2 |
P2-5.2 | P2-5.2 Data transmission | 0 |
P2-5.2.1 | P2-5.2.1 Strong cryptography for 3DS sensitive data in transit | 1 |
P2-5.2.2 | P2-5.2.2 No fallback to insecure protocols | 1 |
P2-5.3 | P2-5.3 TLS configuration | 0 |
P2-5.3.1 | P2-5.3.1 TLS between 3DS components uses only allowed cipher suites | 1 |
P2-5.3.2 | P2-5.3.2 No EMVCo-unsupported cipher suites offered | 1 |
P2-5.3.3 | P2-5.3.3 No rollback to unapproved algorithms or key sizes | 1 |
P2-5.3.4 | P2-5.3.4 TLS configurations monitored for change | 1 |
P2-5.4 | P2-5.4 Data storage | 0 |
P2-5.4.1 | P2-5.4.1 Stored 3DS sensitive data limited to permitted elements | 2 |
P2-5.4.2 | P2-5.4.2 Strong cryptography for stored 3DS sensitive data | 1 |
P2-5.5 | P2-5.5 Monitor 3DS transactions | 0 |
P2-5.5.1 | P2-5.5.1 3DS transactions monitored for anomalies | 1 |
P2-5.5.2 | P2-5.5.2 Anomalous transaction activity investigated promptly | 1 |
P2-6.1 | P2-6.1 Key management | 0 |
P2-6.1.1 | P2-6.1.1 Cryptography and key-management policies and procedures | 1 |
P2-6.1.10 | P2-6.1.10 Incident response covers key-related issues | 1 |
P2-6.1.2 | P2-6.1.2 HSM for specified keys at ACS and DS | 3 |
P2-6.1.3 | P2-6.1.3 HSM deployed according to its security policy | 1 |
P2-6.1.4 | P2-6.1.4 Documented cryptographic architecture | 1 |
P2-6.1.5 | P2-6.1.5 Keys managed securely through their whole lifecycle | 1 |
P2-6.1.6 | P2-6.1.6 Key management follows recognised standards | 1 |
P2-6.1.7 | P2-6.1.7 Keys used only for their intended purpose | 2 |
P2-6.1.8 | P2-6.1.8 Trusted CA for all 3DS certificates | 2 |
P2-6.1.9 | P2-6.1.9 Audit logs for key-management and clear-text component activity | 1 |
P2-6.2 | P2-6.2 Secure logical access to HSMs (ACS and DS only) | 0 |
P2-6.2.1 | P2-6.2.1 Logical HSM access at the console or through an evaluated solution | 1 |
P2-6.2.2 | P2-6.2.2 Non-console HSM access originates only from the 3DE | 1 |
P2-6.2.3 | P2-6.2.3 Devices used for non-console HSM access secured | 1 |
P2-6.2.4 | P2-6.2.4 No clear-text key loading or export over non-console links | 1 |
P2-6.2.5 | P2-6.2.5 Non-console activity meets all other HSM and key rules | 0 |
P2-6.3 | P2-6.3 Secure physical access to HSMs (ACS and DS only) | 0 |
P2-6.3.1 | P2-6.3.1 HSMs kept in dedicated areas | 1 |
P2-6.3.2 | P2-6.3.2 Physical HSM access restricted and under dual control | 1 |
P2-7.1 | P2-7.1 Data-centre physical security for ACS and DS | 0 |
P2-7.1.1 | P2-7.1.1 ACS and DS hosted in data centres | 1 |
P2-7.1.2 | P2-7.1.2 Single-entry portal with positive authentication | 2 |
P2-7.1.3 | P2-7.1.3 Electronic access control on internal doors to 3DS areas | 1 |
P2-7.1.4 | P2-7.1.4 Multi-factor entry to telecom rooms outside the data centre | 1 |
P2-7.1.5 | P2-7.1.5 Anti-piggybacking entry controls | 1 |
P2-7.1.6 | P2-7.1.6 Intrusion detection linked to the alarm system | 1 |
P2-7.1.7 | P2-7.1.7 Physical connection points into the 3DE controlled at all times | 1 |
P2-7.2 | P2-7.2 CCTV | 0 |
P2-7.2.1 | P2-7.2.1 CCTV at every entrance and emergency exit | 1 |
P2-7.2.2 | P2-7.2.2 CCTV recordings time-stamped | 1 |
PART1-DSS | Part 1 and PCI DSS: leveraging a PCI DSS assessment (the standard's Appendix B) | 0 |
SCOPE | Applicability: 3DS components, the 3DS environment and third parties | 0 |
TECH-FAQ | Technical FAQs for v1.x (September 2023): mandatory interpretations | 0 |