Global (PCI Security Standards Council; applied through the payment brands' compliance programmes, e.g. listed in the Visa Core Rules of 18 April 2026 for all regions)

PCI 3DS Core Security Standard

192 controls. 5 other frameworks in our corpus share controls with it. Here is all of it, and how much of it you are already doing.

Page built . This page is derived from the framework corpus, which changes when the corpus is extended rather than daily.

192 controls 5 frameworks share controls with it Global (PCI Security Standards Council; applied through the payment brands' compliance programmes, e.g. listed in the Visa Core Rules of 18 April 2026 for all regions) verified against its source document

Every control below is one this framework asks for. The right hand column counts how many other frameworks in our corpus carry the same control, which is the difference between doing this work once and doing it again for the next standard.

There is no implementation kit for this framework yet. The control list and the overlap above are free and complete.

What you already have

Frameworks whose controls overlap this one, most first. If you run any of them, the count is roughly what you have already evidenced.

Every control

CodeControlAlso in
APPX-ACompensating controls (the standard's Appendix A-1)0
ASSESSAssessment and reporting: 3DS Assessors, the ROC and the AOC0
DATA-MATRIXPCI 3DS Data Matrix v1.3 (September 2026): 3DS sensitive data and HSM keys0
P1-1.1P1-1.1 Maintain security policies0
P1-1.1.1P1-1.1.1 Organisation-wide security policy exists and reaches everyone concerned1
P1-1.1.2P1-1.1.2 Policy revised when business aims or risks change1
P1-1.1.3P1-1.1.3 Policy changes communicated to the people affected1
P1-1.1.4P1-1.1.4 Management approval of the security policy2
P1-1.1.5P1-1.1.5 Personnel confirm they have read and understood the policy1
P1-1.2P1-1.2 Evaluate risk0
P1-1.2.1P1-1.2.1 Written risk-assessment process1
P1-1.2.2P1-1.2.2 Risk assessment run yearly and after significant change1
P1-1.3P1-1.3 Educate personnel0
P1-1.3.1P1-1.3.1 Security awareness programme in operation1
P1-1.3.2P1-1.3.2 Awareness training at set intervals, fitted to the role1
P1-1.3.3P1-1.3.3 Staff know the policy and their own security duties1
P1-1.4P1-1.4 Screen personnel0
P1-1.4.1P1-1.4.1 Background screening before 3DE access2
P1-1.4.2P1-1.4.2 Screening criteria and decision process defined1
P1-2.1P1-2.1 Protect 3DS systems from untrusted systems and networks0
P1-2.1.1P1-2.1.1 Boundary-protection policy and procedures for the 3DE1
P1-2.1.2P1-2.1.2 Current network and data-flow records for every 3DS path1
P1-2.1.3P1-2.1.3 Physical or logical limits between trusted and untrusted zones2
P1-2.1.4P1-2.1.4 Only necessary 3DS traffic permitted, rest denied1
P1-2.1.5P1-2.1.5 Network controls monitored or reviewed for effectiveness1
P1-2.2P1-2.2 Protect 3DS systems from network threats0
P1-2.2.1P1-2.2.1 Detection or blocking of known and unknown network attacks2
P1-2.2.2P1-2.2.2 Suspicious traffic blocked or alerted and acted upon1
P1-3.1P1-3.1 Secure application development0
P1-3.1.1P1-3.1.1 Secure development lifecycle policy and procedures2
P1-3.1.2P1-3.1.2 Developers trained in secure development1
P1-3.1.3P1-3.1.3 Development procedures address common coding weaknesses1
P1-3.1.4P1-3.1.4 Security testing during development using documented methods1
P1-3.1.5P1-3.1.5 Testing surfaces defects and vulnerabilities1
P1-3.1.6P1-3.1.6 Defects and vulnerabilities fixed before release1
P1-3.1.7P1-3.1.7 Management signs off test results before release1
P1-3.2P1-3.2 Configuration standards0
P1-3.2.1P1-3.2.1 Build and configuration management policy and procedures1
P1-3.2.2P1-3.2.2 Current inventory of 3DS system components2
P1-3.2.3P1-3.2.3 Configuration standards defined and applied to every 3DS system type1
P1-3.2.4P1-3.2.4 Standards cover known weaknesses and follow hardening benchmarks1
P1-3.2.5P1-3.2.5 Build standards remove defaults, excess functions and mixed trust levels1
P1-3.3P1-3.3 Change management0
P1-3.3.1P1-3.3.1 Change-control procedures for all changes, including emergencies2
P1-3.3.2P1-3.3.2 Changes authorised with security impact understood first1
P1-3.3.3P1-3.3.3 Changes tested outside production2
P1-3.3.4P1-3.3.4 Rollback prepared for every change1
P1-3.3.5P1-3.3.5 Unauthorised configuration changes prevented or detected and handled1
P1-4.1P1-4.1 Protect against malicious software0
P1-4.1.1P1-4.1.1 Malware-protection policy and procedures1
P1-4.1.2P1-4.1.2 Anti-malware controls active and maintained2
P1-4.2P1-4.2 Address vulnerabilities and security weaknesses0
P1-4.2.1P1-4.2.1 Vulnerability-management policy and procedures1
P1-4.2.2P1-4.2.2 Quarterly internal and external vulnerability scans1
P1-4.2.3P1-4.2.3 Scans run by qualified parties, external by an ASV1
P1-4.2.4P1-4.2.4 Vulnerabilities ranked by criticality2
P1-4.2.5P1-4.2.5 Annual penetration testing1
P1-4.2.6P1-4.2.6 Penetration tests by qualified personnel1
P1-4.2.7P1-4.2.7 High-risk findings fixed within a month, others promptly1
P1-5.1P1-5.1 Access management0
P1-5.1.1P1-5.1.1 Access-assignment policy and procedures1
P1-5.1.2P1-5.1.2 Roles and responsibilities defined for groups and accounts1
P1-5.1.3P1-5.1.3 Least privilege by job function, reviewed periodically1
P1-5.2P1-5.2 Account management0
P1-5.2.1P1-5.2.1 Account-management policy and procedures1
P1-5.2.2P1-5.2.2 Unique account ID per individual2
P1-5.2.3P1-5.2.3 Accounts and credentials kept confidential and intact1
P1-5.2.4P1-5.2.4 Account misuse prevented1
P1-5.2.5P1-5.2.5 Third-party access identified, controlled and monitored1
P1-5.3P1-5.3 Authentication0
P1-5.3.1P1-5.3.1 Strong authentication for all access to 3DS systems1
P1-6.1P1-6.1 Restrict physical access0
P1-6.1.1P1-6.1.1 Physical-access policy and procedures for 3DS systems1
P1-6.1.2P1-6.1.2 Entry controls limit and monitor physical access1
P1-6.1.3P1-6.1.3 Physical access authorised by job function1
P1-6.1.4P1-6.1.4 Physical access removed immediately on termination1
P1-6.2P1-6.2 Secure media0
P1-6.2.1P1-6.2.1 Strict control over media storage and access2
P1-7.1P1-7.1 Incident response plan0
P1-7.1.1P1-7.1.1 Incident-management policy and procedures1
P1-7.1.2P1-7.1.2 Incident response plan with its required elements2
P1-7.1.3P1-7.1.3 Plan reviewed and tested every year1
P1-7.2P1-7.2 Audit logs0
P1-7.2.1P1-7.2.1 Audit-logging policy and procedures1
P1-7.2.2P1-7.2.2 Logs tie access to individuals and record security events1
P1-7.2.3P1-7.2.3 Clocks synchronised on 3DS systems2
P1-7.2.4P1-7.2.4 Logs and security events monitored or reviewed1
P1-7.2.5P1-7.2.5 Audit logs protected from alteration1
P1-7.2.6P1-7.2.6 Log retention of one year, three months at hand1
P2-1.1P2-1.1 Scoping0
P2-1.1.1P2-1.1.1 In-scope networks and components identified1
P2-1.1.2P2-1.1.2 Out-of-scope networks justified with their segmentation1
P2-1.1.3P2-1.1.3 Connected entities with 3DE access identified1
P2-2.1P2-2.1 Security governance0
P2-2.1.1P2-2.1.1 Security objectives aligned with business objectives1
P2-2.1.2P2-2.1.2 Security responsibility and accountability formally assigned1
P2-2.1.3P2-2.1.3 Responsibility for evolving risks assigned1
P2-2.2P2-2.2 Manage risk0
P2-2.2.1P2-2.2.1 Formal risk-management strategy defined1
P2-2.2.2P2-2.2.2 Risk strategy approved and kept current1
P2-2.3P2-2.3 Business as usual (BAU)0
P2-2.3.1P2-2.3.1 Periodic checks that staff follow security policies1
P2-2.3.2P2-2.3.2 Security control failures detected and responded to1
P2-2.4P2-2.4 Manage third-party relationships0
P2-2.4.1P2-2.4.1 Third-party relationship policies and procedures1
P2-2.4.2P2-2.4.2 Due diligence before engaging a third party1
P2-2.4.3P2-2.4.3 Security responsibilities defined per engagement1
P2-2.4.4P2-2.4.4 Third parties' agreed responsibilities verified periodically2
P2-2.4.5P2-2.4.5 Written agreements maintained2
P2-3.1P2-3.1 Protect boundaries0
P2-3.1.1P2-3.1.1 ACS and DS traffic limited to 3DS functions1
P2-3.1.2P2-3.1.2 ACS and DS reachable only through approved interfaces1
P2-3.2P2-3.2 Protect baseline configurations0
P2-3.2.1P2-3.2.1 Configurations and security documentation protected1
P2-3.3P2-3.3 Protect applications and application interfaces0
P2-3.3.1P2-3.3.1 Production applications protected from unauthorised change1
P2-3.3.2P2-3.3.2 Application protection mechanisms monitored and maintained1
P2-3.3.3P2-3.3.3 APIs to the 3DE identified, defined and tested1
P2-3.3.4P2-3.3.4 APIs exposed to untrusted networks protected1
P2-3.4P2-3.4 Secure web configurations0
P2-3.4.1P2-3.4.1 Only required HTTP methods accepted1
P2-3.4.2P2-3.4.2 HTTPS enforced everywhere1
P2-3.4.3P2-3.4.3 External content rejected by default1
P2-3.4.4P2-3.4.4 Framing by untrusted sites prevented1
P2-3.4.5P2-3.4.5 Native framework protections enabled1
P2-3.5P2-3.5 Maintain availability of 3DS operations0
P2-3.5.1P2-3.5.1 Availability mechanisms against loss of 3DS processing2
P2-3.5.2P2-3.5.2 Availability mechanisms monitored and maintained1
P2-4.1P2-4.1 Secure connections for issuer and merchant customers0
P2-4.1.1P2-4.1.1 Issuer and merchant user access to their own interfaces1
P2-4.2P2-4.2 Secure internal network connections0
P2-4.2.1P2-4.2.1 Multi-factor for all non-console personnel access1
P2-4.3P2-4.3 Secure remote access0
P2-4.3.1P2-4.3.1 Multi-factor for remote access into the 3DE1
P2-4.3.2P2-4.3.2 Remote access controlled and documented2
P2-4.3.3P2-4.3.3 Rules for personally owned devices used remotely2
P2-4.3.4P2-4.3.4 Remote access privileges reviewed at least quarterly1
P2-4.4P2-4.4 Restrict wireless exposure0
P2-4.4.1P2-4.4.1 No wireless use by 3DS components2
P2-4.5P2-4.5 Secure VPNs0
P2-4.5.1P2-4.5.1 VPNs into the 3DE securely configured1
P2-5.1P2-5.1 Data lifecycle0
P2-5.1.1P2-5.1.1 3DS data lifecycle policies and procedures1
P2-5.1.2P2-5.1.2 3DS data kept only as long as needed, then purged securely2
P2-5.2P2-5.2 Data transmission0
P2-5.2.1P2-5.2.1 Strong cryptography for 3DS sensitive data in transit1
P2-5.2.2P2-5.2.2 No fallback to insecure protocols1
P2-5.3P2-5.3 TLS configuration0
P2-5.3.1P2-5.3.1 TLS between 3DS components uses only allowed cipher suites1
P2-5.3.2P2-5.3.2 No EMVCo-unsupported cipher suites offered1
P2-5.3.3P2-5.3.3 No rollback to unapproved algorithms or key sizes1
P2-5.3.4P2-5.3.4 TLS configurations monitored for change1
P2-5.4P2-5.4 Data storage0
P2-5.4.1P2-5.4.1 Stored 3DS sensitive data limited to permitted elements2
P2-5.4.2P2-5.4.2 Strong cryptography for stored 3DS sensitive data1
P2-5.5P2-5.5 Monitor 3DS transactions0
P2-5.5.1P2-5.5.1 3DS transactions monitored for anomalies1
P2-5.5.2P2-5.5.2 Anomalous transaction activity investigated promptly1
P2-6.1P2-6.1 Key management0
P2-6.1.1P2-6.1.1 Cryptography and key-management policies and procedures1
P2-6.1.10P2-6.1.10 Incident response covers key-related issues1
P2-6.1.2P2-6.1.2 HSM for specified keys at ACS and DS3
P2-6.1.3P2-6.1.3 HSM deployed according to its security policy1
P2-6.1.4P2-6.1.4 Documented cryptographic architecture1
P2-6.1.5P2-6.1.5 Keys managed securely through their whole lifecycle1
P2-6.1.6P2-6.1.6 Key management follows recognised standards1
P2-6.1.7P2-6.1.7 Keys used only for their intended purpose2
P2-6.1.8P2-6.1.8 Trusted CA for all 3DS certificates2
P2-6.1.9P2-6.1.9 Audit logs for key-management and clear-text component activity1
P2-6.2P2-6.2 Secure logical access to HSMs (ACS and DS only)0
P2-6.2.1P2-6.2.1 Logical HSM access at the console or through an evaluated solution1
P2-6.2.2P2-6.2.2 Non-console HSM access originates only from the 3DE1
P2-6.2.3P2-6.2.3 Devices used for non-console HSM access secured1
P2-6.2.4P2-6.2.4 No clear-text key loading or export over non-console links1
P2-6.2.5P2-6.2.5 Non-console activity meets all other HSM and key rules0
P2-6.3P2-6.3 Secure physical access to HSMs (ACS and DS only)0
P2-6.3.1P2-6.3.1 HSMs kept in dedicated areas1
P2-6.3.2P2-6.3.2 Physical HSM access restricted and under dual control1
P2-7.1P2-7.1 Data-centre physical security for ACS and DS0
P2-7.1.1P2-7.1.1 ACS and DS hosted in data centres1
P2-7.1.2P2-7.1.2 Single-entry portal with positive authentication2
P2-7.1.3P2-7.1.3 Electronic access control on internal doors to 3DS areas1
P2-7.1.4P2-7.1.4 Multi-factor entry to telecom rooms outside the data centre1
P2-7.1.5P2-7.1.5 Anti-piggybacking entry controls1
P2-7.1.6P2-7.1.6 Intrusion detection linked to the alarm system1
P2-7.1.7P2-7.1.7 Physical connection points into the 3DE controlled at all times1
P2-7.2P2-7.2 CCTV0
P2-7.2.1P2-7.2.1 CCTV at every entrance and emergency exit1
P2-7.2.2P2-7.2.2 CCTV recordings time-stamped1
PART1-DSSPart 1 and PCI DSS: leveraging a PCI DSS assessment (the standard's Appendix B)0
SCOPEApplicability: 3DS components, the 3DS environment and third parties0
TECH-FAQTechnical FAQs for v1.x (September 2023): mandatory interpretations0

Tell me when PCI 3DS Core Security Standard files something new

One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.

What this page is

A control-level reference for PCI 3DS Core Security Standard, drawn from our framework corpus. Control codes and titles are references to the standard, not reproductions of it. The overlap counts and the auditor artefacts are our own work and are the part you will not find elsewhere.

Measure this against what you already run · All frameworks · Today's edition