Requirements & evidence
PCI 3DS Core Security Standard
PCI SSC's security requirements for 3-D Secure environments (issuer/ACS, 3DS Server, and DS components) that support cardholder authentication.
- Edition on record
- v1.0
- Issuing authority
- PCI Security Standards Council — 3DS Core (opens in a new tab)
- Edition published
- Source last checked
Understand the scope
What the framework covers.
The library records this framework for payments, across global. The issuing authority determines applicability; your assessment scope should identify the organization, systems, services, and edition being assessed.
Areas of requirement
- 3DS environment security
- Cryptography and key management
- Access control
- Physical security
The library tracks the authority and edition. A normalized requirement catalog is not available for this framework, so a requirement count is not stated here.
Source access and licensing
Freely downloadable from PCI SSC; PCI SSC's terms permit identifiers and structure, not verbatim requirement text, without a separate license.
Prepare with context
The evidence behind
the requirements.
Evidence needs to demonstrate how a requirement is met within the assessment scope. Keep the source requirement, collection context, responsible owner, review decision, and period of applicability together.
A framework-specific collection workflow has not been activated. The reference material on this page can inform scoping and preparation; it does not establish evidence collection or assessment readiness.
ControlFrame availability
Framework reference available
Authority and version facts, with a parsed public catalog when available; no tenant blueprint or executable evidence method is activated.
How availability is determined
PCI 3DS Core Security Standard is tracked in the registry — authority, version ledger, verification — and nothing else is modelled for it yet. Import its catalog to begin.
Catalog status: Planned. Tracked metadata: we record the regime and its issuing authority for review. Registry presence does not mean automated monitoring is active. No control or requirement model is implemented.
Named and tracked only; requirements not modelled as a control catalog.
Follow the source
Editions and transitions.
These are the editions recorded in the library, checked September 6, 2026. Confirm the applicable edition with the authority before beginning an assessment.
Announced transition
A v2.0 revision has been under discussion for years with no publication date announced; v1.0 remains the current, effective standard.
Authority’s stated timing: Unannounced
Read the authority’s announcement (opens in a new tab)- v1.0Current edition on record
Check the basis
Sources you can follow.
Corroborated through independent sources; direct verification with the authority was unavailable. Source verification was recorded on September 6, 2026.
- PCI Security Standards Council — 3DS Core (opens in a new tab)
Issuing authority and framework publication.
- Edition reference: v1.0 (opens in a new tab)
The publication used to establish the recorded edition.
Catalog provenance and record details
Framework record: pci-3ds-core-1-0.
Source artifact: acquisition required.
Parsed catalog: Not ingested.
Control families as published: 3DS environment security · Cryptography and key management · Access control · Physical security.
Record last updated: September 6, 2026.
Common questions
A closer look.
What is PCI 3DS Core Security Standard?
PCI SSC's security requirements for 3-D Secure environments (issuer/ACS, 3DS Server, and DS components) that support cardholder authentication.
Who does PCI 3DS Core Security Standard apply to?
PCI 3DS Core Security Standard applies to payments, global, per PCI Security Standards Council — 3DS Core.
What is the current version of PCI 3DS Core Security Standard?
The current edition is v1.0, issued by PCI Security Standards Council — 3DS Core and published 2017-10-01. Source: https://www.pcisecuritystandards.org/standards/pci-3ds-core/.
What does an assessment under PCI 3DS Core Security Standard require?
No control catalog has been ingested for PCI 3DS Core Security Standard yet — the registry tracks it as planned (Tracked metadata: we record the regime and its issuing authority for review. Registry presence does not mean automated monitoring is active. No control or requirement model is implemented), so an assessment under this framework currently requires the authority's own catalog rather than a ControlFrame-parsed one.
At a glance
PCI 3DS Core Security Standard
v1.0
- Framework reference
- Authority and edition tracked
- Evidence preparation
- Framework reference available
- Source confidence
- Independent corroboration
A framework reference describes requirements. Evidence decisions belong to a scoped assessment and a named reviewer.
Make the requirements
part of the work.
Explore how ControlFrame can organize PCI 3DS Core Security Standard requirements, evidence preparation, and review for your assessment scope.