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

SecNumCloud vs Swift CSP

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

SecNumCloud

Swift CSPSwift users, for their architecture type

At a Glance

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

  • SecNumCloud Asks more on 0 topics Alone on 0 topics More detailed on 0 topics
  • Swift CSP Asks more on 0 topics Alone on 15 topics More detailed on 0 topics
Requirements per topic and verdict
Topic SecNumCloudSwift CSP Verdict
Governance
Awareness and training SecNumCloud: – Swift CSP: 1 Only Swift CSPno specific requirement on the other side in the acts covered
Risk management
Risk assessment SecNumCloud: – Swift CSP: 1 Only Swift CSPno specific requirement on the other side in the acts covered
Protection
Access control SecNumCloud: – Swift CSP: 2 Only Swift CSPno specific requirement on the other side in the acts covered
Authentication SecNumCloud: – Swift CSP: 4 Only Swift CSPno specific requirement on the other side in the acts covered
Cryptography and encryption SecNumCloud: – Swift CSP: 1 Only Swift CSPno specific requirement on the other side in the acts covered
Data security SecNumCloud: – Swift CSP: 4 Only Swift CSPno specific requirement on the other side in the acts covered
Network security SecNumCloud: – Swift CSP: 4 Only Swift CSPno specific requirement on the other side in the acts covered
Secure communications SecNumCloud: – Swift CSP: 3 Only Swift CSPno specific requirement on the other side in the acts covered
Vulnerability handling SecNumCloud: – Swift CSP: 4 Only Swift CSPno specific requirement on the other side in the acts covered
Human resources security SecNumCloud: – Swift CSP: 1 Only Swift CSPno specific requirement on the other side in the acts covered
Physical and environmental security SecNumCloud: – Swift CSP: 1 Only Swift CSPno specific requirement on the other side in the acts covered
Detection and response
Monitoring and detection SecNumCloud: – Swift CSP: 3 Only Swift CSPno specific requirement on the other side in the acts covered
Incident handling SecNumCloud: – Swift CSP: 1 Only Swift CSPno specific requirement on the other side in the acts covered
Continuity and resilience
Security testing SecNumCloud: – Swift CSP: 1 Only Swift CSPno specific requirement on the other side in the acts covered
Third parties and supply chain
Supplier and third-party risk SecNumCloud: – Swift CSP: 1 Only Swift CSPno specific requirement on the other side in the acts covered

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

  • SecNumCloud SecNumCloud requirements framework v3.2 (8 March 2022), approved by order of 12 August 2026; Law No. 2024-449 of 21 May 2024 (SREN), Article 31; Decree No. 2026-272 of 14 April 2026 5 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

Awareness and training

Only Swift CSP no specific requirement on the other side in the acts covered

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

Nothing in the acts covered.

  • 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

Risk management

Risk assessment

Only Swift CSP no specific requirement on the other side in the acts covered

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

Nothing in the acts covered.

  • 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

Protection

Access control

Only Swift CSP no specific requirement on the other side in the acts covered

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

Nothing in the acts covered.

  • 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

Authentication

Only Swift CSP no specific requirement on the other side in the acts covered

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

Nothing in the acts covered.

  • 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

Cryptography and encryption

Only Swift CSP no specific requirement on the other side in the acts covered

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

Nothing in the acts covered.

  • 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

Data security

Only Swift CSP no specific requirement on the other side in the acts covered

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

Nothing in the acts covered.

  • 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

Only Swift CSP no specific requirement on the other side in the acts covered

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

Nothing in the acts covered.

  • 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

Secure communications

Only Swift CSP no specific requirement on the other side in the acts covered

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

Nothing in the acts covered.

  • 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

Vulnerability handling

Only Swift CSP no specific requirement on the other side in the acts covered

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

Nothing in the acts covered.

  • 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

Human resources security

Only Swift CSP no specific requirement on the other side in the acts covered

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

Nothing in the acts covered.

  • 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

Physical and environmental security

Only Swift CSP no specific requirement on the other side in the acts covered

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

Nothing in the acts covered.

  • Physical Security

    Applies to: All types

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

    Swift CSP, Control 3.1

Detection and response

Monitoring and detection

Only Swift CSP no specific requirement on the other side in the acts covered

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

Nothing in the acts covered.

  • 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

Incident handling

Only Swift CSP no specific requirement on the other side in the acts covered

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

Nothing in the acts covered.

  • 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

Continuity and resilience

Security testing

Only Swift CSP no specific requirement on the other side in the acts covered

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

Nothing in the acts covered.

  • 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

Third parties and supply chain

Supplier and third-party risk

Only Swift CSP no specific requirement on the other side in the acts covered

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

Nothing in the acts covered.

  • 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

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.

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…