PCI SSF
The PCI Software Security Framework (PCI Security Standards Council) replaces PA-DSS with the Secure Software Standard, which sets the security requirements payment software must meet under its core requirements and its modules (account data protection, terminal software, web software), and the Secure Software Lifecycle Standard for vendors' development practices, validated by SSF assessors and listed by the Council. The graph models the Secure Software Standard's 76 requirements under 23 control objectives with the errata recorded.
PCI SSF is a compliance framework from Global (PCI Security Standards Council; payment software vendors seeking validation and listing) with 4 domains and 76 controls that map to 180 other frameworks. The largest domains are Secure Software Standard: core requirements (Control Objectives 1 to 12) – PCI SSF (37 controls), Module B: Terminal Software Requirements – PCI SSF (18 controls), Module C: Web Software Requirements – PCI SSF (17 controls). Every control below carries what it requires and what an assessor expects to see.
Framework summaries on this platform are interpretations grounded in the published source, 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 (4)
Module A: Account Data Protection Requirements – PCI SSF
| Code | Title |
|---|---|
| pci-ssf::A.1.1 | Secure Software Standard A.1.1 (Sensitive Authentication Data) |
| pci-ssf::A.2.1 | Secure Software Standard A.2.1 (Cardholder Data Protection) |
| pci-ssf::A.2.2 | Secure Software Standard A.2.2 (Cardholder Data Protection) |
| pci-ssf::A.2.3 | Secure Software Standard A.2.3 (Cardholder Data Protection) |
Module B: Terminal Software Requirements – PCI SSF
| Code | Title |
|---|---|
| pci-ssf::B.1.1 | Secure Software Standard B.1.1 (Terminal Software Documentation) |
| pci-ssf::B.1.2 | Secure Software Standard B.1.2 (Terminal Software Documentation) |
| pci-ssf::B.1.3 | Secure Software Standard B.1.3 (Terminal Software Documentation) |
| pci-ssf::B.2.1 | Secure Software Standard B.2.1 (Terminal Software Design) |
| pci-ssf::B.2.2 | Secure Software Standard B.2.2 (Terminal Software Design) |
| pci-ssf::B.2.3 | Secure Software Standard B.2.3 (Terminal Software Design) |
| pci-ssf::B.2.4 | Secure Software Standard B.2.4 (Terminal Software Design) |
| pci-ssf::B.2.5 | Secure Software Standard B.2.5 (Terminal Software Design) |
| pci-ssf::B.2.6 | Secure Software Standard B.2.6 (Terminal Software Design) |
| pci-ssf::B.2.7 | Secure Software Standard B.2.7 (Terminal Software Design) |
| pci-ssf::B.2.8 | Secure Software Standard B.2.8 (Terminal Software Design) |
| pci-ssf::B.2.9 | Secure Software Standard B.2.9 (Terminal Software Design) |
| pci-ssf::B.3.1 | Secure Software Standard B.3.1 (Terminal Software Attack Mitigation) |
| pci-ssf::B.3.2 | Secure Software Standard B.3.2 (Terminal Software Attack Mitigation) |
| pci-ssf::B.3.3 | Secure Software Standard B.3.3 (Terminal Software Attack Mitigation) |
| pci-ssf::B.4.1 | Secure Software Standard B.4.1 (Terminal Software Security Testing) |
| pci-ssf::B.5.1 | Secure Software Standard B.5.1 (Terminal Software Implementation Guidance) |
| pci-ssf::B.5.2 | Secure Software Standard B.5.2 (Terminal Software Implementation Guidance) |
Module C: Web Software Requirements – PCI SSF
| Code | Title |
|---|---|
| pci-ssf::C.1.1 | Secure Software Standard C.1.1 (Web Software Components & Services) |
| pci-ssf::C.1.2 | Secure Software Standard C.1.2 (Web Software Components & Services) |
| pci-ssf::C.1.3 | Secure Software Standard C.1.3 (Web Software Components & Services) |
| pci-ssf::C.1.4 | Secure Software Standard C.1.4 (Web Software Components & Services) |
| pci-ssf::C.1.5 | Secure Software Standard C.1.5 (Web Software Components & Services) |
| pci-ssf::C.1.6 | Secure Software Standard C.1.6 (Web Software Components & Services) |
| pci-ssf::C.1.7 | Secure Software Standard C.1.7 (Web Software Components & Services) |
| pci-ssf::C.2.1 | Secure Software Standard C.2.1 (Web Software Access Controls) |
| pci-ssf::C.2.2 | Secure Software Standard C.2.2 (Web Software Access Controls) |
| pci-ssf::C.2.3 | Secure Software Standard C.2.3 (Web Software Access Controls) |
| pci-ssf::C.3.1 | Secure Software Standard C.3.1 (Web Software Attack Mitigation) |
| pci-ssf::C.3.2 | Secure Software Standard C.3.2 (Web Software Attack Mitigation) |
| pci-ssf::C.3.3 | Secure Software Standard C.3.3 (Web Software Attack Mitigation) |
| pci-ssf::C.3.4 | Secure Software Standard C.3.4 (Web Software Attack Mitigation) |
| pci-ssf::C.3.5 | Secure Software Standard C.3.5 (Web Software Attack Mitigation) |
| pci-ssf::C.3.6 | Secure Software Standard C.3.6 (Web Software Attack Mitigation) |
| pci-ssf::C.4.1 | Secure Software Standard C.4.1 (Web Software Communications) |
Secure Software Standard: core requirements (Control Objectives 1 to 12) – PCI SSF
| Code | Title |
|---|---|
| pci-ssf::1.1 | Secure Software Standard 1.1 (Critical Asset Identification) |
| pci-ssf::1.2 | Secure Software Standard 1.2 (Critical Asset Identification) |
| pci-ssf::1.3 | Secure Software Standard 1.3 (Critical Asset Identification) |
| pci-ssf::10.1 | Secure Software Standard 10.1 (Threat and Vulnerability Management) |
| pci-ssf::10.2 | Secure Software Standard 10.2 (Threat and Vulnerability Management) |
| pci-ssf::11.1 | Secure Software Standard 11.1 (Secure Software Updates) |
| pci-ssf::11.2 | Secure Software Standard 11.2 (Secure Software Updates) |
| pci-ssf::12.1 | Secure Software Standard 12.1 (Software Vendor Implementation Guidance) |
| pci-ssf::2.1 | Secure Software Standard 2.1 (Secure Defaults) |
| pci-ssf::2.2 | Secure Software Standard 2.2 (Secure Defaults) |
| pci-ssf::2.3 | Secure Software Standard 2.3 (Secure Defaults) |
| pci-ssf::2.4 | Secure Software Standard 2.4 (Secure Defaults) |
| pci-ssf::2.5 | Secure Software Standard 2.5 (Secure Defaults) |
| pci-ssf::3.1 | Secure Software Standard 3.1 (Sensitive Data Retention) |
| pci-ssf::3.2 | Secure Software Standard 3.2 (Sensitive Data Retention) |
| pci-ssf::3.3 | Secure Software Standard 3.3 (Sensitive Data Retention) |
| pci-ssf::3.4 | Secure Software Standard 3.4 (Sensitive Data Retention) |
| pci-ssf::3.5 | Secure Software Standard 3.5 (Sensitive Data Retention) |
| pci-ssf::3.6 | Secure Software Standard 3.6 (Sensitive Data Retention) |
| pci-ssf::4.1 | Secure Software Standard 4.1 (Critical Asset Protection) |
| pci-ssf::4.2 | Secure Software Standard 4.2 (Critical Asset Protection) |
| pci-ssf::5.1 | Secure Software Standard 5.1 (Authentication and Access Control) |
| pci-ssf::5.2 | Secure Software Standard 5.2 (Authentication and Access Control) |
| pci-ssf::5.3 | Secure Software Standard 5.3 (Authentication and Access Control) |
| pci-ssf::5.4 | Secure Software Standard 5.4 (Authentication and Access Control) |
| pci-ssf::6.1 | Secure Software Standard 6.1 (Sensitive Data Protection) |
| pci-ssf::6.2 | Secure Software Standard 6.2 (Sensitive Data Protection) |
| pci-ssf::6.3 | Secure Software Standard 6.3 (Sensitive Data Protection) |
| pci-ssf::7.1 | Secure Software Standard 7.1 (Use of Cryptography) |
| pci-ssf::7.2 | Secure Software Standard 7.2 (Use of Cryptography) |
| pci-ssf::7.3 | Secure Software Standard 7.3 (Use of Cryptography) |
| pci-ssf::7.4 | Secure Software Standard 7.4 (Use of Cryptography) |
| pci-ssf::8.1 | Secure Software Standard 8.1 (Activity Tracking) |
| pci-ssf::8.2 | Secure Software Standard 8.2 (Activity Tracking) |
| pci-ssf::8.3 | Secure Software Standard 8.3 (Activity Tracking) |
| pci-ssf::8.4 | Secure Software Standard 8.4 (Activity Tracking) |
| pci-ssf::9.1 | Secure Software Standard 9.1 (Attack Detection) |
Your Compliance Coverage
If you comply with PCI SSF, you already cover:
PSD2 SCA
13%
16 controls mapped
Compare →PCI P2PE
13%
16 controls mapped
Compare →FFIEC IT Examination Handbook
13%
16 controls mapped
Compare →+ 177 more: PCI PIN Security (13%), Singapore Government Instruction Manual on ICT&SS Management (IM8) (11%)
See all 180 mapped frameworks ↓Maps to 180 other frameworks
Coverage is not the same as your position
This page shows what PCI SSF overlaps with in general. Where your organisation actually stands, against the standard you are going for and the certifications you already hold, is a different question. Same graph and the same recorded refutations, scoped to you rather than to a pair.
The Compliance Position Diagnostic, $5,000 fixed, ten business daysWhat is PCI SSF and who does it apply to?
PCI SSF is a compliance framework from Global (PCI Security Standards Council; payment software vendors seeking validation and listing) with 4 domains and 76 controls. The PCI Software Security Framework (PCI Security Standards Council) replaces PA-DSS with the Secure Software Standard, which sets the security requirements payment software must meet under its core requirements and its modules (account data protection, terminal software, web software), and the Secure Software Lifecycle Standard for vendors' development practices, validated by SSF assessors and listed by the Council. The graph models the Secure Software Standard's 76 requirements under 23 control objectives with the errata recorded. It is used by organisations to establish and maintain compliance with industry standards and regulatory requirements.
What does PCI SSF actually require?
PCI SSF has 76 controls organised across 4 domains. The largest domains are Secure Software Standard: core requirements (Control Objectives 1 to 12) – PCI SSF (37 controls), Module B: Terminal Software Requirements – PCI SSF (18 controls), Module C: Web Software Requirements – PCI SSF (17 controls). Each control defines specific requirements that organisations must implement to achieve compliance.
If I already comply with another framework, how much of PCI SSF do I already cover?
PCI SSF maps to 180 other compliance frameworks. The top mapping partners are PSD2 SCA (13% coverage), PCI P2PE (13% coverage), FFIEC IT Examination Handbook (13% coverage). Use our comparison tool to explore control-level mappings between frameworks.
How do I implement PCI SSF?
Start your PCI SSF 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 SSF 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 76 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 1,120 frameworks.
Get Started Free →Free forever, no credit card required