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

Standard and framework

Swift CSP: Swift Customer Security Programme

The Swift Customer Security ProgrammeA customer security programme from Swift for organisations using its services. It combines a Customer Security Controls Framework with customer attestations and an independent assessment framework. (CSP) requires every SwiftSociety for Worldwide Interbank Financial Telecommunication user to attest each year, between July and 31 December, that it meets the mandatory controls of the Customer Security Controls FrameworkSwift's framework of mandatory and advisory security controls for its users' environments. Users must implement the mandatory controls applicable to their architecture, while advisory controls are recommended best practices. Compliance is attested annually and independently assessed under the Customer Security Programme. (CSCF) for its architecture type.

  • 32 controls in CSCF v2026: 26 mandatory and 6 advisory
  • 31 December deadline for the yearly KYC-SAKYC-Security Attestation attestation
  • Independent assessment behind every attestation

Last updated 6 November 2026 · Reviewed yearly

What Is Swift CSP?

The CSP exists to protect the SwiftSociety for Worldwide Interbank Financial Telecommunication community as a whole: a weak user puts its counterparties at risk. The controls aim to prevent unauthorised or altered transactions, business with an unauthorised counterparty, and breaches of 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. or integrity. They build on NISTNational Institute of Standards and Technology, ISO 27000 and PCI DSSPayment Card Industry Data Security Standard, and SwiftSociety for Worldwide Interbank Financial Telecommunication publishes a mapping to NIST CSFCybersecurity Framework, ISO 27002Information Security, Cybersecurity and Privacy Protection: Information Security Controls, PCI DSS 4.0Payment Card Industry Data Security Standard and SOC 2SOC for Service Organizations: Trust Services Criteria.

The 32 controls sit under three objectives and seven principles. Secure your environment: restrict internet access and protect critical systems from the general ITInformation Technology environment (controls 1.x), reduce the attack surface and 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. (2.x), physically secure the environment (3.1). Know and limit access: prevent compromise of credentials (4.x), manage identities and separate privileges (5.x). Detect and respond: detect anomalous activity (6.x), plan for incident responseThe coordinated work an organisation carries out to deal with a cybersecurity incident and limit its consequences. An incident is an event that compromises, or threatens to compromise, the security of systems or information. Response can include investigating what happened, containing the problem, removing its cause and restoring affected services. It helps reduce damage and return operations to a controlled state. and information sharing (7.x).

SwiftSociety for Worldwide Interbank Financial Telecommunication does not check or certify compliance itself. It sets the standard, requires an independent assessment behind every attestation, and makes the result visible, so that each user can judge the cyber risk of the institutions it does business with.

SwiftSociety for Worldwide Interbank Financial Telecommunication launched the Customer Security Programme in 2016, after cyber attacks on SwiftSociety for Worldwide Interbank Financial Telecommunication users, to keep a common level of security hygiene across the community and limit the damage of fraudulent payments. It is not a law: it is part of every user’s contract with SwiftSociety for Worldwide Interbank Financial Telecommunication. Users protect their own environment; SwiftSociety for Worldwide Interbank Financial Telecommunication sets the controls and makes each user’s compliance visible to its counterparties and supervisors.

GRC+ carries out Swift CSPSwift Customer Security Programme independent assessments for banks and every other Swift user, and has done so every year since 2021, on architecture types A4 and B. The gaps we find most often are 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 the application that reaches SwiftSociety for Worldwide Interbank Financial Telecommunication (4.2), an 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. without SwiftSociety for Worldwide Interbank Financial Telecommunication-specific steps or a test (7.1), logging and monitoring without a defined process (6.4) and missing periodic access reviews (5.1).

Full title
Swift Customer Security Programme (Swift CSP)
Official reference
Swift Customer Security Controls Framework v2026 (CSCF v2026)
Type
Industry scheme
Issued by
Swift (Society for Worldwide Interbank Financial Telecommunication)
Applies from
1 July 2026
Status
In force and applicable
Countries
Worldwide

Official text

Verified by

Ahmet Ucar

Principal Consultant (CISSPCertified Information Systems Security Professional, CISMCertified Information Security Manager, CISACertified Information Systems Auditor, CIPP/ECertified Information Privacy Professional/Europe)

Last updated 6 November 2026

Get regulatory updates

One email a week when something changes in the countries you choose, Swift CSP included.

Countries
Choose one or more countries

Pick one or more

One email a week, only when something changed. Each email has an unsubscribe link. Privacy notice

What Swift CSP Requires

Control 1.1

Swift Environment Protection

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.

+3 more in the full mapping

Control 1.2

Operating System Privileged Account Control

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

+2 more in the full mapping

Control 1.3

Virtualisation or Cloud Platform Protection

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

+1 more in the full mapping

Control 1.4

Restriction of Internet Access

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

+3 more in the full mapping
Show All 32 Requirements

Control 1.5

Customer Environment Protection

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

+3 more in the full mapping

Control 2.1

Internal Data Flow Security

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.

+3 more in the full mapping

Control 2.2

Security Updates

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

+2 more in the full mapping

Control 2.5A

External Transmission Data Protection (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.

+5 more in the full mapping

Control 2.7

Vulnerability Scanning

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.

+2 more in the full mapping

Control 2.8

Outsourced Critical Activity Protection

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

+7 more in the full mapping

Control 2.9

Transaction Business Controls

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

Control 2.11A

RMA Business Controls (advisory)

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

Control 3.1

Physical Security

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

+3 more in the full mapping

Control 4.2

Multi-Factor Authentication

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.

+2 more in the full mapping

Control 5.1

Logical Access Control

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.

+4 more in the full mapping

Control 5.2

Token Management

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.

+1 more in the full mapping

Control 6.1

Malware Protection

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..

+2 more in the full mapping

Control 6.4

Logging and Monitoring

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

+4 more in the full mapping

Control 6.5A

Intrusion Detection (advisory)

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

+3 more in the full mapping

Control 7.1

Cyber Incident Response Planning

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..

DORA Article 17ISO 27001 A.5.24ISO 27001 A.5.26
+7 more in the full mapping

Control 7.2

Security Training and Awareness

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

+1 more in the full mapping

Control 7.3A

Penetration Testing (advisory)

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

+2 more in the full mapping

Control 7.4A

Scenario-based Risk Assessment (advisory)

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

+4 more in the full mapping

Reference framework: Swift Customer Security Controls Framework (CSCF) v2026, with Swift's High-Level Test Plan and controls matrix www2.swift.com/knowledgecentre/rest/v1/publications/cscf_dd/70.0/CSCF_v2026_202507015.pdf

Latest Swift CSP Updates

Swift CSP Milestones Since 2025
  1. CSCF v2027 published: clarifications only, no new or promoted controlsNo new controls to build, but check the clarifications before you plan your 2027 assessment.
  2. Attestation window for CSCF v2026 opensFrom here, attestations in KYC-SAKYC-Security Attestation are made against v2026, supported by an independent assessment.
  3. CSCF v2026 published: 2.4 Back Office Data Flow Security becomes mandatorySwift publishes each framework about a year before attestation against it starts, so you have time to close gaps.

Questions

Swift CSP FAQ: Common Questions Answered

What is the Swift Customer Security Programme?

SwiftSociety for Worldwide Interbank Financial Telecommunication‘s programme, launched in 2016, that sets the security controls every SwiftSociety for Worldwide Interbank Financial Telecommunication user must meet and makes each user’s compliance visible. The controls are in the Customer Security Controls FrameworkSwift's framework of mandatory and advisory security controls for its users' environments. Users must implement the mandatory controls applicable to their architecture, while advisory controls are recommended best practices. Compliance is attested annually and independently assessed under the Customer Security Programme. (CSCF), updated every July: CSCF v2026 has 32 controls, 26 mandatory and 6 advisory. Each user attests its compliance once a year in the KYC Security Attestation application (KYC-SA).

Who must comply with the Swift CSP?

Every SwiftSociety for Worldwide Interbank Financial Telecommunication user, for each connected 8-character BICBusiness Identifier Code, whatever its architecture type, including users that connect through a service bureau, a Group Hub or an outsourcing agent. New users and new BICsBusiness Identifier Code must attest before going live. Non-connected BICsBusiness Identifier Code are out of scope, and receiving-only BICsBusiness Identifier Code may rely on a self-assessment.

When is the Swift CSP attestation due?

Every year between July and 31 December, against the CSCFCustomer Security Controls Framework version of that year: in 2026 against CSCF v2026, in 2027 against CSCF v2027Customer Security Controls Framework V2027. An attestation published between July and December 2026 stays valid until the end of 2027. A change of architecture type, provider or a mandatory control calls for a new attestation within three months.

What changed in CSCF v2026 and v2027?

In v2026, control 2.4 Back Office Data Flow Security became mandatory, and customer client connectors came into scope of 14 controls, so some users moved from architecture type B to A4. CSCF v2027Customer Security Controls Framework V2027 adds no new or promoted controls: it clarifies existing ones, names the secrets and keys vault as an in-scope component and requires users who work through an outsourcing agent to choose A4.

Which architecture type applies to us?

It depends on which SwiftSociety for Worldwide Interbank Financial Telecommunication-related components you own or licence. A1: you own the communication interface. A2: you own the messaging interface only. A3: a SwiftSociety for Worldwide Interbank Financial Telecommunication connector in your environment. A4: a customer connector such as file transfer or middleware, without SwiftSociety for Worldwide Interbank Financial Telecommunication software. B: operators use a provider’s or SwiftSociety for Worldwide Interbank Financial Telecommunication‘s interface from a normal PC. The type decides how many controls apply: from 16 for B to 25 for A1 and A2.

What happens if we do not attest or are not compliant?

SwiftSociety for Worldwide Interbank Financial Telecommunication does not fine users. It may report to your supervisors a late or missing attestation, non-compliance with a mandatory control, a missing independent assessment or a non-compliant provider. Counterparties see your status in KYC-SAKYC-Security Attestation and may limit their business with you, an expired attestation turns amber, and a new BICBusiness Identifier Code cannot go live without a valid attestation.

Does every attestation need an independent assessment?

Yes. Every attestation must be supported by an independent assessment of at least all mandatory controls for your architecture type, with a report from the same year. A self-assessment by the team that runs the controls shows as not compliant. SwiftSociety for Worldwide Interbank Financial Telecommunication also selects some users each year for an external assessment by a different assessor.

Who can carry out the independent assessment?

An internal function that is independent of the first line, such as internal audit or risk, or an external organisation with recent cyber-security assessment experience. The lead assessor needs a recognised certification, such as CISSPCertified Information Systems Security Professional, CISACertified Information Systems Auditor or ISO 27001 Lead Auditor. Using a Swift CSP Certified AssessorAn individual certified through Swift's Customer Security Programme assessor certification process to assess a Swift user's security controls. The process includes passing an examination and maintaining relevant knowledge. Swift offers external and internal assessor tracks. External certified assessors work through registered assessment providers and can be listed in Swift's directory. Certification is optional for carrying out an independent assessment, which must still satisfy Swift's assessment requirements. is optional; SwiftSociety for Worldwide Interbank Financial Telecommunication does not endorse any assessor.

Who approves the attestation in KYC-SA?

The CISOChief Information Security Officer approves it; without a CISOChief Information Security Officer, the CIOChief Information Officer, CRO, chief auditor or an officer of similar seniority, and failing those the CEOChief Executive Officer. The submitter is usually the Head of SwiftSociety for Worldwide Interbank Financial Telecommunication Operations, and the default four-eyes setting needs two different people. The approver’s name and function are shown to counterparties.

Can the assessment be done remotely?

Yes. SwiftSociety for Worldwide Interbank Financial Telecommunication allows remote assessments if they give the same comfort as on site, for example through documents, screenshots, interviews and video for physical controls. GRC+ runs its Swift CSPSwift Customer Security Programme assessments remotely as a rule: a kick-off, a few working sessions and a closing meeting.

What do we receive at the end of the assessment?

An assessment report with the result per control, how each conclusion was reached and what to fix, a completion letter signed by the lead assessor (the only document SwiftSociety for Worldwide Interbank Financial Telecommunication may ask for), and SwiftSociety for Worldwide Interbank Financial Telecommunication‘s completed assessment templates. You keep these documents for five years; nothing is uploaded to KYC-SAKYC-Security Attestation.

Which controls do organisations most often fail?

In GRC+’s assessments since 2021: 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 the application that reaches SwiftSociety for Worldwide Interbank Financial Telecommunication (4.2), an incident response plan without SwiftSociety for Worldwide Interbank Financial Telecommunication-specific steps or a test (7.1), logging and monitoring without a defined process (6.4), and periodic access reviews (5.1).

Attesting Before 31 December? Plan Your Swift CSP Assessment

Thirty minutes with a GRC+ Swift CSPSwift Customer Security Programme assessor: we confirm your architecture type, the controls in scope and how long the assessment takes, so your attestation is published before the deadline.

Loading the form…