Incident to report to a regulator?Incident to report? Intake Line

PCI DSS vs Swift CSP

Where they overlap, where they differ and which asks more, topic by topic, with their deadlines and fines side by side.

PCI DSSEntities that store, process or transmit account data, or can affect its security

Swift CSPSwift users, for their architecture type

At a Glance

They differ on 16 of 20 topics. Each verdict names what it rests on; read the wording before relying on it.

  • PCI DSS Asks more on 5 topics Alone on 5 topics More detailed on 3 topics
  • Swift CSP Asks more on 3 topics Alone on 0 topics More detailed on 0 topics
Requirements per topic and verdict
Topic PCI DSSSwift CSP Verdict
Governance
Management accountability PCI DSS: 1 Swift CSP: – Only PCI DSSno specific requirement on the other side in the acts covered
Security policy PCI DSS: 2 Swift CSP: – Only PCI DSSno specific requirement on the other side in the acts covered
Awareness and training PCI DSS: 2 Swift CSP: 1 Partly overlapfrom the mapping: see the gap notes
Risk management
Risk assessment PCI DSS: 1 Swift CSP: 1 PCI DSS asks morefrom the mapping
Asset management PCI DSS: 1 Swift CSP: – Only PCI DSSno specific requirement on the other side in the acts covered
Protection
Access control PCI DSS: 4 Swift CSP: 2 PCI DSS more detailedmore requirements on this, not necessarily stricter
Authentication PCI DSS: 5 Swift CSP: 4 PCI DSS asks morefrom the mapping
Cryptography and encryption PCI DSS: 3 Swift CSP: 1 PCI DSS asks morebinding, where the other is optional
Data security PCI DSS: 4 Swift CSP: 4 Both cover itread the wording below
Network security PCI DSS: 7 Swift CSP: 4 Partly overlapfrom the mapping: see the gap notes
Secure communications PCI DSS: 2 Swift CSP: 3 PCI DSS asks morefrom the mapping
Secure acquisition and development PCI DSS: 3 Swift CSP: – Only PCI DSSno specific requirement on the other side in the acts covered
Configuration, change and patch management PCI DSS: 1 Swift CSP: – Only PCI DSSno specific requirement on the other side in the acts covered
Vulnerability handling PCI DSS: 4 Swift CSP: 4 Swift CSP asks morefrom the mapping
Human resources security PCI DSS: 1 Swift CSP: 1 PCI DSS asks morefrom the mapping
Physical and environmental security PCI DSS: 5 Swift CSP: 1 PCI DSS more detailedmore requirements on this, not necessarily stricter
Detection and response
Monitoring and detection PCI DSS: 12 Swift CSP: 3 PCI DSS more detailedmore requirements on this, not necessarily stricter
Incident handling PCI DSS: 1 Swift CSP: 1 Swift CSP asks morefrom the mapping
Continuity and resilience
Security testing PCI DSS: 2 Swift CSP: 1 Swift CSP asks morefrom the mapping
Third parties and supply chain
Supplier and third-party risk PCI DSS: 2 Swift CSP: 1 Partly overlapfrom the mapping: see the gap notes

What This Covers

The obligations below are summarised from the acts listed here, grouped by topic. Where a side shows nothing on a topic, the acts covered have no specific requirement on it; an act not yet included, national guidance or a supervisor's expectations may still say more. Use it to see where the regimes differ, not as a compliance checklist.

Included

  • PCI DSS PCI DSS v4.0.1 (June 2024) 63 requirements

Status

Reviewed against the official texts.

Included

  • Swift CSP Swift Customer Security Controls Framework v2026 (CSCF v2026) 32 requirements

Status

Reviewed against the official texts.

Governance

Management accountability

Only PCI DSS no specific requirement on the other side in the acts covered

NIST CSF 2.0 GV.RR, GV.OV · ISO/IEC 27001:2022 Clause 5.1, A.5.4

  • PCI DSS compliance is managed

    PCI DSSPayment Card Industry Data Security Standard compliance is managed.

    PCI DSS, Requirement 12.4

Nothing in the acts covered.

Security policy

Only PCI DSS no specific requirement on the other side in the acts covered

NIST CSF 2.0 GV.PO · ISO/IEC 27001:2022 A.5.1

  • A comprehensive information security policy that governs and provides direction for protection of the entity's information assets is known and current

    A comprehensive information securityProtecting information and the systems that handle it so that only authorised people can access it, it remains accurate and complete, and it is available when needed. These aims are called confidentiality, integrity and availability. Information security combines organisational requirements, staff practices and technical safeguards to reduce risks such as disclosure, alteration, disruption or destruction. policy that governs and provides direction for protection of the entity's information assets is known and current.

    PCI DSS, Requirement 12.1

  • Acceptable use policies for end-user technologies are defined and implemented

    Acceptable use policies for end-user technologies are defined and implemented.

    PCI DSS, Requirement 12.2

Nothing in the acts covered.

Awareness and training

Partly overlap from the mapping: see the gap notes

NIST CSF 2.0 PR.AT · ISO/IEC 27001:2022 A.6.3

  • Anti-phishing mechanisms protect users against phishing attacks

    Anti-phishing mechanisms protect users against phishingAn attack that impersonates a trusted person or organisation through electronic communications, often an email or a fake website, to trick someone into revealing information such as passwords or bank details. The attacker uses apparent familiarity or credibility to persuade the person to respond. Training simulations practise recognising these deceptive requests. attacks.

    PCI DSS, Requirement 5.4

  • Security awareness education is an ongoing activity

    Security awareness education is an ongoing activity.

    PCI DSS, Requirement 12.6

  • Security Training and Awareness

    Applies to: All types

    Train staff with access to SwiftSociety for Worldwide Interbank Financial Telecommunication on security, including role-specific training for privileged users.

    Swift CSP, Control 7.2

How these map: 1 link
  • Swift CSP Control 7.2 Partial PCI DSS Requirement 12.6

    PCI DSS requires a formal awareness programme on hire and at least annually, including phishing and social engineering, but not specific training for privileged users.

Risk management

Risk assessment

PCI DSS asks more from the mapping

NIST CSF 2.0 ID.RA · ISO/IEC 27001:2022 Clauses 6.1.2, 8.2

  • Risks to the cardholder data environment are formally identified, evaluated, and managed

    Risks to the cardholder data environmentThe system components, people and processes that store, process or transmit cardholder data or sensitive authentication data, plus components with unrestricted connectivity to them. Defining the CDE sets the scope of a PCI DSS assessment. are formally identified, evaluated, and managed.

    PCI DSS, Requirement 12.3

  • Scenario-based Risk Assessment (advisory) Recommended

    Applies to: All types (advisory)

    Assess the risk of SwiftSociety for Worldwide Interbank Financial Telecommunication-related attack scenarios regularly.

    Swift CSP, Control 7.4A

How these map: 1 link
  • Swift CSP Control 7.4A Supports PCI DSS Requirement 12.3

    PCI DSS requires targeted risk analyses for specific requirements rather than scenario-based assessments of cyber-attack readiness.

Asset management

Only PCI DSS no specific requirement on the other side in the acts covered

NIST CSF 2.0 ID.AM · ISO/IEC 27001:2022 A.5.9 to A.5.13

  • PCI DSS scope is documented and validated

    PCI DSSPayment Card Industry Data Security Standard scope is documented and validated.

    PCI DSS, Requirement 12.5

Nothing in the acts covered.

Protection

Access control

PCI DSS more detailed more requirements on this, not necessarily stricter

NIST CSF 2.0 PR.AA · ISO/IEC 27001:2022 A.5.15, A.5.18, A.8.2, A.8.3

  • Processes and mechanisms for restricting access to system components and cardholder data by business need to know are defined and understood

    Processes and mechanisms for restricting access to system components and cardholder dataUnder PCI DSS, the payment card data that must be protected: at a minimum the full primary account number, which may be accompanied by the cardholder name, expiration date or service code. Where cardholder data is stored, processed or transmitted defines the scope of a PCI DSS assessment. by business need to know are defined and understood.

    PCI DSS, Requirement 7.1

  • Access to system components and data is appropriately defined and assigned

    Access to system components and data is appropriately defined and assigned.

    PCI DSS, Requirement 7.2

  • Access to system components and data is managed via an access control system(s)

    Access to system components and data is managed via an access controlRequirements and safeguards that decide who or what may use information, systems or facilities, and what actions they may perform. Access control can grant or refuse access to people, software or devices. Examples include restricting a user account to permitted systems and limiting its privileges. In the plural, access controls are the measures used to enforce these requirements. system(s).

    PCI DSS, Requirement 7.3

  • User identification and related accounts for users and administrators are strictly managed throughout an account's lifecycle

    User identification and related accounts for users and administrators are strictly managed throughout an account's lifecycle.

    PCI DSS, Requirement 8.2

  • Operating System Privileged Account Control

    Applies to: A1, A2, A3, A4; advisory for B

    Restrict and control the use of administrator accounts on the operating systems of in-scope components.

    Swift CSP, Control 1.2

  • Logical Access Control

    Applies to: All types

    Grant access on need-to-know, least privilegeThe principle that a security architecture gives each user, process or other entity only the system authorisations and resources it needs to perform its function. It limits the damage a compromised account or component can do. and segregation of duties, and review it regularly.

    Swift CSP, Control 5.1

How these map: 3 links
  • Swift CSP Control 1.2 Partial PCI DSS Requirement 7.2

    PCI DSS requires privileged access to be assigned on least privilege but does not restrict administrator accounts to named activities such as installation, maintenance and emergencies.

  • Swift CSP Control 5.1 Partial PCI DSS Requirement 7.2

    PCI DSS requires access based on job function and least privilege with periodic review, but does not name separation of duties for operator accounts.

  • Swift CSP Control 5.1 Partial PCI DSS Requirement 8.2

    PCI DSS adds account lifecycle rules such as immediate revocation for terminated users and removal or disabling of inactive accounts within 90 days.

Authentication

PCI DSS asks more from the mapping

NIST CSF 2.0 PR.AA · ISO/IEC 27001:2022 A.5.17, A.8.5

  • Processes and mechanisms for identifying users and authenticating access to system components are defined and understood

    Processes and mechanisms for identifying users and authenticating access to system components are defined and understood.

    PCI DSS, Requirement 8.1

  • Strong authentication for users and administrators is established and managed

    Strong authenticationThe process of checking that a user, device or software process is who or what it claims to be before allowing access to a system. A system may check evidence such as a password or a security credential. Authentication establishes identity; access requirements then determine what that identity may do. Multi-factor authentication is one approach to authentication, using more than one kind of evidence. for users and administrators is established and managed.

    PCI DSS, Requirement 8.3

  • Multi-factor authentication (MFA) is implemented to secure access into the CDE

    Multi-factor authenticationAuthentication through verification of at least two different types of factor: something a person knows, such as a password; something they have, such as a token; or something they are, such as a biometric. NIS2, PCI DSS, the NYDFS regulation and the FTC Safeguards Rule call for it. (MFA) is implemented to secure access into the CDECardholder Data Environment.

    PCI DSS, Requirement 8.4

  • Multi-factor authentication (MFA) systems are configured to prevent misuse

    Multi-factor authenticationAuthentication through verification of at least two different types of factor: something a person knows, such as a password; something they have, such as a token; or something they are, such as a biometric. NIS2, PCI DSS, the NYDFS regulation and the FTC Safeguards Rule call for it. (MFA) systems are configured to prevent misuse.

    PCI DSS, Requirement 8.5

  • Use of application and system accounts and associated authentication factors is strictly managed

    Use of application and system accounts and associated authenticationThe process of checking that a user, device or software process is who or what it claims to be before allowing access to a system. A system may check evidence such as a password or a security credential. Authentication establishes identity; access requirements then determine what that identity may do. Multi-factor authentication is one approach to authentication, using more than one kind of evidence. factors is strictly managed.

    PCI DSS, Requirement 8.6

  • Password Policy

    Applies to: All types

    Make passwords resistant to common attacks through an enforced password policy.

    Swift CSP, Control 4.1

  • Multi-Factor Authentication

    Applies to: All types

    Require multi-factor authenticationAuthentication through verification of at least two different types of factor: something a person knows, such as a password; something they have, such as a token; or something they are, such as a biometric. NIS2, PCI DSS, the NYDFS regulation and the FTC Safeguards Rule call for it. for interactive access to SwiftSociety for Worldwide Interbank Financial Telecommunication-related applications and operating system administration.

    Swift CSP, Control 4.2

  • Token Management

    Applies to: All types

    Manage hardware authenticationThe process of checking that a user, device or software process is who or what it claims to be before allowing access to a system. A system may check evidence such as a password or a security credential. Authentication establishes identity; access requirements then determine what that identity may do. Multi-factor authentication is one approach to authentication, using more than one kind of evidence. tokens and keep them under the control of their owners.

    Swift CSP, Control 5.2

  • Password Repository Protection

    Applies to: All types

    Protect stored passwords, physical and logical, against disclosure.

    Swift CSP, Control 5.4

How these map: 5 links
  • Swift CSP Control 4.1 Partial PCI DSS Requirement 8.3

    PCI DSS sets specific password parameters, such as at least 12 characters and lockout after no more than ten failed attempts, but does not cover PINs on personal tokens.

  • Swift CSP Control 4.2 Partial PCI DSS Requirement 8.4

    PCI DSS requires multi-factor authentication for all non-console access into the CDE and all remote access, while Swift also covers operating system accounts and individual Swift applications.

  • Swift CSP Control 4.2 Partial PCI DSS Requirement 8.5

    PCI DSS requires multi-factor authentication systems to resist replay and bypass and to need at least two different factor types.

  • Swift CSP Control 5.2 Supports PCI DSS Requirement 8.3

    PCI DSS covers management of authentication factors in general and does not address the assignment, distribution, revocation and storage of tokens.

  • Swift CSP Control 5.4 Partial PCI DSS Requirement 8.3

    PCI DSS requires authentication factors to be unreadable with strong cryptography in storage and transmission, but does not address physical password records.

Cryptography and encryption

PCI DSS asks more binding, where the other is optional

NIST CSF 2.0 PR.DS · ISO/IEC 27001:2022 A.8.24

  • Primary account number (PAN) is secured wherever it is stored

    Primary account numberThe unique payment card number that identifies the card issuer and the cardholder account, used on credit, debit and prepaid cards. Under PCI DSS the full PAN is the minimum element of cardholder data, so where it is stored, processed or transmitted drives the scope of an assessment. (PAN) is secured wherever it is stored.

    PCI DSS, Requirement 3.5

  • Cryptographic keys used to protect stored account data are secured

    Cryptographic keys used to protect stored account dataThe PCI DSS umbrella term for cardholder data, sensitive authentication data or both. PCI DSS requirements apply to every system component that stores, processes or transmits account data, or that could affect its security. are secured.

    PCI DSS, Requirement 3.6

  • Where cryptography is used to protect stored account data, key management processes and procedures covering all aspects of the key lifecycle are defined and implemented

    Where cryptographyThe use of mathematical methods to protect information and provide evidence that it can be trusted. Cryptography can hide information, detect changes and help verify where information came from. Encryption, which makes readable information unintelligible without the means to decrypt it, is one use of cryptography. The broader discipline also supports integrity checks and digital signatures. is used to protect stored account dataThe PCI DSS umbrella term for cardholder data, sensitive authentication data or both. PCI DSS requirements apply to every system component that stores, processes or transmits account data, or that could affect its security., key management processes and procedures covering all aspects of the key lifecycle are defined and implemented.

    PCI DSS, Requirement 3.7

  • External Transmission Data Protection (advisory) Recommended

    Applies to: A1, A2, A3, A4 (advisory)

    Protect SwiftSociety for Worldwide Interbank Financial Telecommunication-related data sent or stored outside the secure zone, such as back-ups or files moved to other sites.

    Swift CSP, Control 2.5A

How these map: 1 link
  • Swift CSP Control 2.5A Partial PCI DSS Requirement 3.5

    PCI DSS requires stored PAN to be rendered unreadable but does not cover other Swift-related data such as business transactions and credentials.

Data security

Both cover it read the wording below

NIST CSF 2.0 PR.DS · ISO/IEC 27001:2022 A.5.12, A.8.10 to A.8.12

  • Processes and mechanisms for protecting stored account data are defined and understood

    Processes and mechanisms for protecting stored account dataThe PCI DSS umbrella term for cardholder data, sensitive authentication data or both. PCI DSS requirements apply to every system component that stores, processes or transmits account data, or that could affect its security. are defined and understood.

    PCI DSS, Requirement 3.1

  • Storage of account data is kept to a minimum

    Storage of account dataThe PCI DSS umbrella term for cardholder data, sensitive authentication data or both. PCI DSS requirements apply to every system component that stores, processes or transmits account data, or that could affect its security. is kept to a minimum.

    PCI DSS, Requirement 3.2

  • Sensitive authentication data (SAD) is not stored after authorization

    Sensitive authentication dataSecurity-related information used to authenticate cardholders or authorise payment card transactions, such as card verification codes, full track data, PINs and PIN blocks. Together with cardholder data it makes up account data under PCI DSS. (SAD) is not stored after authorization.

    PCI DSS, Requirement 3.3

  • Access to displays of full PAN and ability to copy PAN are restricted

    Access to displays of full PANPrimary Account Number and ability to copy PANPrimary Account Number are restricted.

    PCI DSS, Requirement 3.4

  • Transaction Business Controls

    Applies to: All types

    Restrict transaction activity to what is expected for your business, such as hours, counterparties and value limits, and detect deviations.

    Swift CSP, Control 2.9

  • RMA Business Controls (advisory) Recommended

    Applies to: All types (advisory)

    Review Relationship Management Application relationships regularly and remove those no longer needed.

    Swift CSP, Control 2.11A

  • Software Integrity

    Applies to: A1, A2, A3; advisory for A4

    Check the integrity of the SwiftSociety for Worldwide Interbank Financial Telecommunication-related software you run.

    Swift CSP, Control 6.2

  • Database Integrity

    Applies to: A1, A2; advisory for A4

    Check the integrity of the database records of the messaging interface.

    Swift CSP, Control 6.3

Network security

Partly overlap from the mapping: see the gap notes

NIST CSF 2.0 PR.IR · ISO/IEC 27001:2022 A.8.20 to A.8.22

  • Processes and mechanisms for installing and maintaining network security controls are defined and understood

    Processes and mechanisms for installing and maintaining network security controls are defined and understood.

    PCI DSS, Requirement 1.1

  • Network security controls (NSCs) are configured and maintained

    Network security controls (NSCs) are configured and maintained.

    PCI DSS, Requirement 1.2

  • Network access to and from the cardholder data environment is restricted

    Network access to and from the cardholder data environmentThe system components, people and processes that store, process or transmit cardholder data or sensitive authentication data, plus components with unrestricted connectivity to them. Defining the CDE sets the scope of a PCI DSS assessment. is restricted.

    PCI DSS, Requirement 1.3

  • Network connections between trusted and untrusted networks are controlled

    Network connections between trusted and untrusted networks are controlled.

    PCI DSS, Requirement 1.4

  • Risks to the CDE from computing devices that are able to connect to both untrusted networks and the CDE are mitigated

    Risks to the CDECardholder Data Environment from computing devices that are able to connect to both untrusted networks and the CDECardholder Data Environment are mitigated.

    PCI DSS, Requirement 1.5

  • Wireless environments are configured and managed securely

    Wireless environments are configured and managed securely.

    PCI DSS, Requirement 2.3

  • Wireless access points are identified and monitored, and unauthorized wireless access points are addressed

    Wireless access points are identified and monitored, and unauthorized wireless access points are addressed.

    PCI DSS, Requirement 11.2

  • Swift Environment Protection

    Applies to: A1, A2, A3

    Place the SwiftSociety for Worldwide Interbank Financial Telecommunication infrastructure in a secure zone, separated from the general ITInformation Technology environment, with controlled access into and out of it.

    Swift CSP, Control 1.1

  • Virtualisation or Cloud Platform Protection

    Applies to: A1, A2, A3, A4; advisory for B

    Secure the virtualisation or cloud platform that hosts in-scope components to the same level as the components themselves.

    Swift CSP, Control 1.3

  • Restriction of Internet Access

    Applies to: All types

    Limit internet access from operator PCs and in-scope systems to what is needed, and control it.

    Swift CSP, Control 1.4

  • Customer Environment Protection

    Applies to: A4

    For users with a customer connector, protect that environment in a dedicated, separated zone.

    Swift CSP, Control 1.5

How these map: 6 links
  • Swift CSP Control 1.1 Partial PCI DSS Requirement 1.3

    PCI DSS restricts network access to and from the cardholder data environment rather than a secure zone around Swift components.

  • Swift CSP Control 1.1 Partial PCI DSS Requirement 1.4

    PCI DSS controls connections between trusted and untrusted networks but does not cover segregation from the wider enterprise network unless it is outside the CDE.

  • Swift CSP Control 1.4 Partial PCI DSS Requirement 1.3

    PCI DSS restricts outbound traffic from the CDE to what is necessary, but does not address internet access from operator PCs outside the CDE.

  • Swift CSP Control 1.4 Partial PCI DSS Requirement 1.5

    PCI DSS requires controls on devices that connect to both untrusted networks and the CDE but does not restrict their internet access to business need.

  • Swift CSP Control 1.5 Partial PCI DSS Requirement 1.3

    PCI DSS restricts network access to and from the CDE rather than requiring a separated secure zone for customer connectivity components.

  • Swift CSP Control 1.5 Partial PCI DSS Requirement 1.4

    PCI DSS controls connections between trusted and untrusted networks but does not prescribe a dedicated zone for customer connectors.

Secure communications

PCI DSS asks more from the mapping

NIST CSF 2.0 PR.DS · ISO/IEC 27001:2022 A.5.14

  • Processes and mechanisms for protecting cardholder data with strong cryptography during transmission over open, public networks are defined and understood

    Processes and mechanisms for protecting cardholder dataUnder PCI DSS, the payment card data that must be protected: at a minimum the full primary account number, which may be accompanied by the cardholder name, expiration date or service code. Where cardholder data is stored, processed or transmitted defines the scope of a PCI DSS assessment. with strong cryptographyThe use of mathematical methods to protect information and provide evidence that it can be trusted. Cryptography can hide information, detect changes and help verify where information came from. Encryption, which makes readable information unintelligible without the means to decrypt it, is one use of cryptography. The broader discipline also supports integrity checks and digital signatures. during transmission over open, public networks are defined and understood.

    PCI DSS, Requirement 4.1

  • PAN is protected with strong cryptography during transmission

    PANPrimary Account Number is protected with strong cryptographyThe use of mathematical methods to protect information and provide evidence that it can be trusted. Cryptography can hide information, detect changes and help verify where information came from. Encryption, which makes readable information unintelligible without the means to decrypt it, is one use of cryptography. The broader discipline also supports integrity checks and digital signatures. during transmission.

    PCI DSS, Requirement 4.2

  • Internal Data Flow Security

    Applies to: A1, A2, A3

    Protect the confidentialityThe information-security property of keeping information from being disclosed to people, organisations or systems that are not authorised to receive it. Access restrictions and encryption help preserve confidentiality when information is stored, sent or processed. It concerns who can see information; it does not by itself ensure that the information is accurate or that a service remains available., integrity and authenticity of data flows between SwiftSociety for Worldwide Interbank Financial Telecommunication-related components.

    Swift CSP, Control 2.1

  • Back Office Data Flow Security

    Applies to: A1, A2, A3, A4

    Protect data flows between the back office and the secure zone, starting with bridging servers. Mandatory since v2026; legacy direct flows tentatively from 2028.

    Swift CSP, Control 2.4

  • Operator Session Confidentiality and Integrity

    Applies to: All types

    Protect interactive operator sessions to SwiftSociety for Worldwide Interbank Financial Telecommunication-related applications against eavesdropping and tampering.

    Swift CSP, Control 2.6

How these map: 2 links
  • Swift CSP Control 2.1 Supports PCI DSS Requirement 4.2

    PCI DSS requires strong cryptography only for PAN sent over open, public networks, whereas Swift requires protection of all internal data flows between Swift components.

  • Swift CSP Control 2.4 Supports PCI DSS Requirement 4.2

    PCI DSS protects only PAN over open, public networks, whereas Swift requires confidentiality, integrity and authentication on all back-office flows.

Secure acquisition and development

Only PCI DSS no specific requirement on the other side in the acts covered

NIST CSF 2.0 PR.PS · ISO/IEC 27001:2022 A.8.25 to A.8.31

  • Processes and mechanisms for developing and maintaining secure systems and software are defined and understood

    Processes and mechanisms for developing and maintaining secure systems and software are defined and understood.

    PCI DSS, Requirement 6.1

  • Bespoke and custom software are developed securely

    Bespoke and custom software are developed securely.

    PCI DSS, Requirement 6.2

  • Public-facing web applications are protected against attacks

    Public-facing web applications are protected against attacks.

    PCI DSS, Requirement 6.4

Nothing in the acts covered.

Configuration, change and patch management

Only PCI DSS no specific requirement on the other side in the acts covered

NIST CSF 2.0 PR.PS · ISO/IEC 27001:2022 A.8.9, A.8.19, A.8.32

  • Changes to all system components are managed securely

    Changes to all system components are managed securely.

    PCI DSS, Requirement 6.5

Nothing in the acts covered.

Vulnerability handling

Swift CSP asks more from the mapping

NIST CSF 2.0 ID.RA · ISO/IEC 27001:2022 A.8.8

  • Processes and mechanisms for applying secure configurations to all system components are defined and understood

    Processes and mechanisms for applying secure configurations to all system components are defined and understood.

    PCI DSS, Requirement 2.1

  • System components are configured and managed securely

    System components are configured and managed securely.

    PCI DSS, Requirement 2.2

  • Security vulnerabilities are identified and addressed

    Security vulnerabilitiesA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. are identified and addressed.

    PCI DSS, Requirement 6.3

  • External and internal vulnerabilities are regularly identified, prioritized, and addressed

    External and internal vulnerabilitiesA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. are regularly identified, prioritized, and addressed.

    PCI DSS, Requirement 11.3

  • Security Updates

    Applies to: All types

    Install vendor security updates on in-scope hardware and software within a risk-based time frame.

    Swift CSP, Control 2.2

  • System Hardening

    Applies to: All types

    Harden operating systems, databases and network devices of the SwiftSociety for Worldwide Interbank Financial Telecommunication environment against attack.

    Swift CSP, Control 2.3

  • Vulnerability Scanning

    Applies to: A1, A2, A3, A4; advisory for B

    Scan in-scope components for vulnerabilitiesA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. and act on the results.

    Swift CSP, Control 2.7

  • Application Hardening

    Applies to: A1, A2, A3

    Harden the SwiftSociety for Worldwide Interbank Financial Telecommunication messaging and communication interfaces and related applications.

    Swift CSP, Control 2.10

How these map: 4 links
  • Swift CSP Control 2.10 Partial PCI DSS Requirement 2.2

    PCI DSS requires secure configuration of system components but does not require Swift-compatible interfaces or application-specific hardening.

  • Swift CSP Control 2.2 Partial PCI DSS Requirement 6.3

    PCI DSS requires vulnerabilities to be identified and patched within defined timeframes but does not require all hardware and software to remain within the vendor support life cycle.

  • Swift CSP Control 2.3 Partial PCI DSS Requirement 2.2

    PCI DSS requires configuration standards based on industry-accepted hardening guidance, closely aligned with Swift's hardening requirement but scoped to the CDE.

  • Swift CSP Control 2.7 Stricter PCI DSS Requirement 11.3

    PCI DSS is more prescriptive, requiring at least quarterly internal scans, external scans by an Approved Scanning Vendor and rescans to confirm fixes.

Human resources security

PCI DSS asks more from the mapping

NIST CSF 2.0 GV.RR · ISO/IEC 27001:2022 A.6.1 to A.6.6

  • Personnel are screened to reduce risks from insider threats

    Personnel are screened to reduce risks from insider threats.

    PCI DSS, Requirement 12.7

  • Staff Screening Process (advisory) Recommended

    Applies to: All types (advisory)

    Screen staff who operate or administer the SwiftSociety for Worldwide Interbank Financial Telecommunication environment before and during employment, where local law allows.

    Swift CSP, Control 5.3A

How these map: 1 link
  • Swift CSP Control 5.3A Supports PCI DSS Requirement 12.7

    PCI DSS requires screening only before hire, whereas Swift also requires periodic re-screening of staff operating the Swift infrastructure.

Physical and environmental security

PCI DSS more detailed more requirements on this, not necessarily stricter

NIST CSF 2.0 PR.IR · ISO/IEC 27001:2022 A.7.1 to A.7.14

  • Processes and mechanisms for restricting physical access to cardholder data are defined and understood

    Processes and mechanisms for restricting physical access to cardholder dataUnder PCI DSS, the payment card data that must be protected: at a minimum the full primary account number, which may be accompanied by the cardholder name, expiration date or service code. Where cardholder data is stored, processed or transmitted defines the scope of a PCI DSS assessment. are defined and understood.

    PCI DSS, Requirement 9.1

  • Physical access controls manage entry into facilities and systems containing cardholder data

    Physical access controls manage entry into facilities and systems containing cardholder dataUnder PCI DSS, the payment card data that must be protected: at a minimum the full primary account number, which may be accompanied by the cardholder name, expiration date or service code. Where cardholder data is stored, processed or transmitted defines the scope of a PCI DSS assessment..

    PCI DSS, Requirement 9.2

  • Physical access for personnel and visitors is authorized and managed

    Physical access for personnel and visitors is authorized and managed.

    PCI DSS, Requirement 9.3

  • Media with cardholder data is securely stored, accessed, distributed, and destroyed

    Media with cardholder dataUnder PCI DSS, the payment card data that must be protected: at a minimum the full primary account number, which may be accompanied by the cardholder name, expiration date or service code. Where cardholder data is stored, processed or transmitted defines the scope of a PCI DSS assessment. is securely stored, accessed, distributed, and destroyed.

    PCI DSS, Requirement 9.4

  • Point-of-interaction (POI) devices are protected from tampering and unauthorized substitution

    Point-of-interaction (POI) devices are protected from tampering and unauthorized substitution.

    PCI DSS, Requirement 9.5

  • Physical Security

    Applies to: All types

    Prevent unauthorised physical access to sensitive equipment, workplaces, tokens and storage media.

    Swift CSP, Control 3.1

How these map: 2 links
  • Swift CSP Control 3.1 Partial PCI DSS Requirement 9.2

    PCI DSS requires entry controls to facilities and systems with cardholder data but does not specifically address operator PCs, HSMs or tokens.

  • Swift CSP Control 3.1 Partial PCI DSS Requirement 9.3

    PCI DSS adds personnel and visitor access authorisation and badge management that the Swift control does not detail.

Detection and response

Monitoring and detection

PCI DSS more detailed more requirements on this, not necessarily stricter

NIST CSF 2.0 DE.CM, DE.AE · ISO/IEC 27001:2022 A.8.15, A.8.16

  • Processes and mechanisms for protecting all systems and networks from malicious software are defined and understood

    Processes and mechanisms for protecting all systems and networks from malicious softwareSoftware or firmware deliberately designed to harm a computer system or the information it holds. Malware can steal or destroy data, change information without permission, spy on activity or stop systems working. Examples include viruses, worms and spyware. Screening email or uploads for malware means looking for this harmful code before it can affect people or systems. are defined and understood.

    PCI DSS, Requirement 5.1

  • Malicious software (malware) is prevented, or detected and addressed

    Malicious software (malware) is prevented, or detected and addressed.

    PCI DSS, Requirement 5.2

  • Anti-malware mechanisms and processes are active, maintained, and monitored

    Anti-malwareSoftware designed to find malicious software, prevent it from infecting computers and, in some cases, remove an existing infection. Malicious software, or malware, includes programs such as viruses and spyware that can damage systems, steal information or disrupt operations. In security requirements, anti-malware refers to this protective capability rather than a particular product. mechanisms and processes are active, maintained, and monitored.

    PCI DSS, Requirement 5.3

  • Processes and mechanisms for logging and monitoring all access to system components and cardholder data are defined and understood

    Processes and mechanisms for logging and monitoring all access to system components and cardholder dataUnder PCI DSS, the payment card data that must be protected: at a minimum the full primary account number, which may be accompanied by the cardholder name, expiration date or service code. Where cardholder data is stored, processed or transmitted defines the scope of a PCI DSS assessment. are defined and understood.

    PCI DSS, Requirement 10.1

  • Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events

    Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events.

    PCI DSS, Requirement 10.2

  • Audit logs are protected from destruction and unauthorized modifications

    Audit logs are protected from destruction and unauthorized modifications.

    PCI DSS, Requirement 10.3

  • Audit logs are reviewed to identify anomalies or suspicious activity

    Audit logs are reviewed to identify anomalies or suspicious activity.

    PCI DSS, Requirement 10.4

  • Audit log history is retained and available for analysis

    Audit log history is retained and available for analysis.

    PCI DSS, Requirement 10.5

  • Time-synchronization mechanisms support consistent time settings across all systems

    Time-synchronization mechanisms support consistent time settings across all systems.

    PCI DSS, Requirement 10.6

  • Failures of critical security control systems are detected, reported, and responded to promptly

    Failures of critical security control systems are detected, reported, and responded to promptly.

    PCI DSS, Requirement 10.7

  • Network intrusions and unexpected file changes are detected and responded to

    Network intrusions and unexpected file changes are detected and responded to.

    PCI DSS, Requirement 11.5

  • Unauthorized changes on payment pages are detected and responded to

    Unauthorized changes on payment pages are detected and responded to.

    PCI DSS, Requirement 11.6

  • Malware Protection

    Applies to: All types

    Protect in-scope components with up-to-date anti-malwareSoftware designed to find malicious software, prevent it from infecting computers and, in some cases, remove an existing infection. Malicious software, or malware, includes programs such as viruses and spyware that can damage systems, steal information or disrupt operations. In security requirements, anti-malware refers to this protective capability rather than a particular product..

    Swift CSP, Control 6.1

  • Logging and Monitoring

    Applies to: All types

    Record security events and monitor them to detect anomalous activity and operations.

    Swift CSP, Control 6.4

  • Intrusion Detection (advisory) Recommended

    Applies to: A1, A2, A3, A4 (advisory)

    Detect and contain anomalous network activity inside and towards the secure zone.

    Swift CSP, Control 6.5A

How these map: 5 links
  • Swift CSP Control 6.1 Partial PCI DSS Requirement 5.2

    PCI DSS requires anti-malware on all system components except those assessed as not at risk, closely aligned with Swift but scoped to the CDE.

  • Swift CSP Control 6.1 Partial PCI DSS Requirement 5.3

    PCI DSS adds requirements to keep anti-malware current, run periodic scans and prevent users from disabling it.

  • Swift CSP Control 6.4 Partial PCI DSS Requirement 10.2

    PCI DSS specifies the events and log content to be captured, which is more prescriptive than Swift.

  • Swift CSP Control 6.4 Partial PCI DSS Requirement 10.4

    PCI DSS requires daily review of security event logs, which is more prescriptive than Swift's requirement to keep and review logs.

  • Swift CSP Control 6.5A Partial PCI DSS Requirement 11.5

    PCI DSS requires intrusion detection or prevention at the CDE perimeter and critical points, which is closely aligned but scoped to the CDE.

Incident handling

Swift CSP asks more from the mapping

NIST CSF 2.0 RS.MA, RS.AN, RS.MI · ISO/IEC 27001:2022 A.5.24 to A.5.28

  • Suspected and confirmed security incidents that could impact the CDE are responded to immediately

    Suspected and confirmed security incidents that could impact the CDECardholder Data Environment are responded to immediately.

    PCI DSS, Requirement 12.10

  • Cyber Incident Response Planning

    Applies to: All types

    Keep and test a cyber incident response planA written set of instructions for detecting and handling cybersecurity incidents and limiting their consequences. It gives the organisation a prepared approach to follow when systems or information are attacked. In practice, it should make clear who acts, how decisions and communications are handled, and how the response is coordinated. The plan supports the people doing the response work. that covers SwiftSociety for Worldwide Interbank Financial Telecommunication, including informing SwiftSociety for Worldwide Interbank Financial Telecommunication and using its threat intelligenceInformation about cyber threats that has been collected, combined and analysed to help people make security decisions. It adds context to facts about attackers, their methods or signs of an attack, helping an organisation judge what matters to its systems. It can guide monitoring, incident response, information sharing and realistic attack simulations..

    Swift CSP, Control 7.1

How these map: 1 link
  • Swift CSP Control 7.1 Stricter PCI DSS Requirement 12.10

    PCI DSS requires the incident response plan to be reviewed and tested at least annually, more often than Swift, but does not require notification of Swift.

Continuity and resilience

Security testing

Swift CSP asks more from the mapping

NIST CSF 2.0 ID.IM · ISO/IEC 27001:2022 A.5.35, A.8.29, A.8.34

  • Processes and mechanisms for regularly testing security of systems and networks are defined and understood

    Processes and mechanisms for regularly testing security of systems and networks are defined and understood.

    PCI DSS, Requirement 11.1

  • External and internal penetration testing is regularly performed, and exploitable vulnerabilities and security weaknesses are corrected

    External and internal penetration testingA security assessment in which authorised testers simulate attacks on an application, system or network to find weaknesses that could actually be exploited. Testing takes place within agreed limits, such as the systems included and the techniques permitted. It can reveal how several weaknesses combine to give an attacker greater access, helping an organisation understand and correct the resulting exposure. is regularly performed, and exploitable vulnerabilitiesA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. and security weaknesses are corrected.

    PCI DSS, Requirement 11.4

  • Penetration Testing (advisory) Recommended

    Applies to: All types (advisory)

    Test the security of the SwiftSociety for Worldwide Interbank Financial Telecommunication environment through penetration tests.

    Swift CSP, Control 7.3A

How these map: 1 link
  • Swift CSP Control 7.3A Stricter PCI DSS Requirement 11.4

    PCI DSS requires internal and external penetration testing at least annually and after significant changes, plus segmentation testing, which is more prescriptive than Swift.

Third parties and supply chain

Supplier and third-party risk

Partly overlap from the mapping: see the gap notes

NIST CSF 2.0 GV.SC · ISO/IEC 27001:2022 A.5.19, A.5.21 to A.5.23

  • Risk to information assets associated with third-party service provider (TPSP) relationships is managed

    Risk to information assets associated with third-party service provider (TPSP) relationships is managed.

    PCI DSS, Requirement 12.8

  • Third-party service providers (TPSPs) support their customers' PCI DSS compliance

    Third-party service providers (TPSPs) support their customers' PCI DSSPayment Card Industry Data Security Standard compliance.

    PCI DSS, Requirement 12.9

  • Outsourced Critical Activity Protection

    Applies to: All types

    Ensure that critical activities outsourced to third parties are protected to the same standard.

    Swift CSP, Control 2.8

How these map: 1 link
  • Swift CSP Control 2.8 Partial PCI DSS Requirement 12.8

    PCI DSS requires third-party service providers to be listed, contracted, monitored and checked before engagement, but not to meet the CSCF.

Requirements are summarised in plain words; the official text prevails. Verdicts compare what the acts covered state, not how a supervisor applies them. Most topics are cross-referenced to NIST CSF 2.0 and ISO/IEC 27001:2022.

Full Mapping

Get the Complete Table as a Spreadsheet

All 42 links, ready to filter, extend with your own controls and use as the starting point of a gap analysis.

We e-mail you a download link. Your details go to our CRM so a consultant can follow up about the mapping. Privacy notice

Subject to more than one?

We run one control set for both, without doing the work twice. Ask what that saves you.

Loading the form…