PCI P2PE
PCI Point-to-Point Encryption Standard
Framework summaries on this platform are AI-assisted interpretations for educational and compliance planning purposes. They do not reproduce or replace the official standards. Refer to the authoritative source for the definitive text. Framework names and trademarks belong to their respective organisations.
Framework Domains (19)
Application Security
| Code | Title |
|---|---|
| Domain-2.1 | POI Application Security |
Compliance Management
| Code | Title |
|---|---|
| Domain-6.2 | Annual Reassessment and Change Management |
Decryption Environment
| Code | Title |
|---|---|
| Domain-4.1 | Decryption Environment Logical Security |
Deployment
| Code | Title |
|---|---|
| Domain-3.2 | Merchant POI Device Deployment |
Device Approval
| Code | Title |
|---|---|
| Domain-1.1 | POI Device Approval Status |
Device Identity
| Code | Title |
|---|---|
| Domain-2.2 | POI Device Authentication |
Device Lifecycle
| Code | Title |
|---|---|
| Domain-3.1 | POI Device Management |
Documentation
| Code | Title |
|---|---|
| Domain-6.1 | P2PE Solution Documentation |
Encryption
| Code | Title |
|---|---|
| Domain-1.2 | Account Data Encryption at POI |
Key Distribution
| Code | Title |
|---|---|
| Annex-A | Symmetric Key Distribution Using Asymmetric Techniques |
Key Injection
| Code | Title |
|---|---|
| Annex-B | Key Injection Facility Requirements |
Key Management
| Code | Title |
|---|---|
| Domain-5.1 | Key Generation |
| Domain-5.2 | Key Distribution and Injection |
| Domain-5.3 | Key Storage |
| Domain-5.4 | Key Usage and Cryptoperiods |
| Domain-5.5 | Key Destruction |
Merchant Enablement
| Code | Title |
|---|---|
| Domain-6.3 | Merchant Self-Assessment Support |
PCI P2PE: Cybersecurity Controls
Technical cybersecurity measures (PCI P2PE)
| Code | Title |
|---|---|
| PCI-P2PE-06 | Network security and segmentation |
| PCI-P2PE-07 | Endpoint protection and detection |
| PCI-P2PE-08 | Application security controls |
| PCI-P2PE-09 | Encryption and key management |
| PCI-P2PE-10 | Secure configuration standards |
PCI P2PE: Incident Management & Reporting
Incident handling for financial services (PCI P2PE)
| Code | Title |
|---|---|
| PCI-P2PE-21 | Incident detection and classification |
| PCI-P2PE-22 | Incident response and containment |
| PCI-P2PE-23 | Regulatory reporting requirements |
| PCI-P2PE-24 | Customer notification procedures |
| PCI-P2PE-25 | Post-incident review and improvement |
PCI P2PE: Information Security Governance
IT governance for financial institutions (PCI P2PE)
| Code | Title |
|---|---|
| PCI-P2PE-01 | Information security program management |
| PCI-P2PE-02 | Board and management oversight |
| PCI-P2PE-03 | Risk appetite and tolerance for IT risk |
| PCI-P2PE-04 | Security policy framework |
| PCI-P2PE-05 | Roles and responsibilities definition |
PCI P2PE: Operational Resilience
Business continuity and resilience (PCI P2PE)
| Code | Title |
|---|---|
| PCI-P2PE-11 | Business continuity planning and testing |
| PCI-P2PE-12 | Disaster recovery procedures |
| PCI-P2PE-13 | Third-party dependency management |
| PCI-P2PE-14 | Critical service identification |
| PCI-P2PE-15 | Communication and escalation procedures |
PCI P2PE: Third-Party Risk Management
Managing vendor and supplier risks (PCI P2PE)
| Code | Title |
|---|---|
| PCI-P2PE-16 | Due diligence and onboarding |
| PCI-P2PE-17 | Contractual security requirements |
| PCI-P2PE-18 | Ongoing monitoring and assessment |
| PCI-P2PE-19 | Concentration risk management |
| PCI-P2PE-20 | Exit strategy and transition planning |
Physical Security
| Code | Title |
|---|---|
| Domain-1.3 | POI Device Tampering Protection |
| Domain-4.2 | Decryption Environment Physical Security |
Your Compliance Coverage
If you comply with PCI P2PE, you already cover:
OSFI B-13
34%
15 controls mapped
Compare →DORA
34%
15 controls mapped
Compare →FFIEC IT Examination Handbook
34%
15 controls mapped
Compare →+ 624 more: BCBS 239 (34%), APRA CPS 234 (34%)
See all 627 mapped frameworks ↓Maps to 627 other frameworks
Frequently Asked Questions
What is PCI P2PE?
PCI P2PE is a compliance framework from International with 19 domains and 44 controls. PCI Point-to-Point Encryption Standard It is used by organisations to establish and maintain compliance with industry standards and regulatory requirements.
How many controls does PCI P2PE have?
PCI P2PE has 44 controls organised across 19 domains. The largest domains are Key Management (5 controls), PCI P2PE: Cybersecurity Controls (5 controls), PCI P2PE: Incident Management & Reporting (5 controls). Each control defines specific requirements that organisations must implement to achieve compliance.
What frameworks does PCI P2PE map to?
PCI P2PE maps to 627 other compliance frameworks. The top mapping partners are OSFI B-13 (34% coverage), DORA (34% coverage), FFIEC IT Examination Handbook (34% coverage). Use our comparison tool to explore control-level mappings between frameworks.
How do I get started with PCI P2PE compliance?
Start your PCI P2PE compliance journey by running a self-assessment on our platform to identify your current compliance posture. Our AI advisory can answer specific questions about PCI P2PE requirements, and cross-framework mapping helps you leverage existing controls from other frameworks you may already comply with. Create a free account to access all 44 controls and track your progress.
Start Your Compliance Journey
Create a free account to run self-assessments, get AI advisory, and track your compliance progress across 700 frameworks.
Get Started Free →Free forever — no credit card required