---
title: "Swift Customer Security Programme (Swift CSP)"
url: "https://grc.plus/regulation/swift-customer-security-program-swift-csp/"
type: "Regulation"
updated: "2026-11-21"
publisher: "GRC+"
---

# Swift Customer Security Programme (Swift CSP)

Swift launched the Customer Security Programme in 2016, after cyber attacks on Swift 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 Swift. Users protect their own environment; Swift sets the controls and makes each user’s compliance visible to its counterparties and supervisors.

GRC+ carries out Swift CSP 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 authentication for the application that reaches Swift (4.2), an incident response plan without Swift-specific steps or a test (7.1), logging and monitoring without a defined process (6.4) and missing periodic access reviews (5.1).

**Ahmet Ucar**Principal Consultant

- [Book a call](https://meetings-eu1.hubspot.com/ahmet-ucar)
- [+31 20 241 66 00](tel:+31202416600)
- [sales@grc.plus](mailto:sales@grc.plus)

## Review Info

- Last Update: 11 June 2026
- Review Cycle: Annually

Do you want to receive updates on Swift CSP?

No spam. No advertising. Regulatory updates only.

[Subscribe to updates](https://meetings-eu1.hubspot.com/ahmet-ucar)

## Quick Facts on Swift CSP

## Reference

- Official reference: SWIFT-CSP

[Read the official text](https://www2.swift.com/knowledgecentre/rest/v1/publications/cscf_dd/70.0/CSCF_v2026_202507015.pdf)

## Purpose

The CSP exists to protect the Swift 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 confidentiality or integrity. They build on NIST, ISO 27000 and PCI DSS, and Swift publishes a mapping to NIST CSF, ISO 27002, PCI DSS 4.0 and SOC 2.

The 32 controls sit under three objectives and seven principles. Secure your environment: restrict internet access and protect critical systems from the general IT environment (controls 1.x), reduce the attack surface and vulnerabilities (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 response and information sharing (7.x).

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

## Key Requirements

### Swift Environment Protection

Place the Swift infrastructure in a secure zone, separated from the general IT environment, with controlled access into and out of it.

### Operating System Privileged Account Control

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

### Virtualisation or Cloud Platform Protection

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

### Restriction of Internet Access

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

### Customer Environment Protection

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

### Internal Data Flow Security

Protect the confidentiality, integrity and authenticity of data flows between Swift-related components.

### Security Updates

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

### System Hardening

Harden operating systems, databases and network devices of the Swift environment against attack.

### Back Office Data Flow Security

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

### External Transmission Data Protection (advisory)

Protect Swift-related data sent or stored outside the secure zone, such as back-ups or files moved to other sites.

### Operator Session Confidentiality and Integrity

Protect interactive operator sessions to Swift-related applications against eavesdropping and tampering.

### Vulnerability Scanning

Scan in-scope components for vulnerabilities and act on the results.

### Outsourced Critical Activity Protection

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

### Transaction Business Controls

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

### Application Hardening

Harden the Swift messaging and communication interfaces and related applications.

### RMA Business Controls (advisory)

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

### Physical Security

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

### Password Policy

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

### Multi-Factor Authentication

Require multi-factor authentication for interactive access to Swift-related applications and operating system administration.

### Logical Access Control

Grant access on need-to-know, least privilege and segregation of duties, and review it regularly.

### Token Management

Manage hardware authentication tokens and keep them under the control of their owners.

### Staff Screening Process (advisory)

Screen staff who operate or administer the Swift environment before and during employment, where local law allows.

### Password Repository Protection

Protect stored passwords, physical and logical, against disclosure.

### Malware Protection

Protect in-scope components with up-to-date anti-malware.

### Software Integrity

Check the integrity of the Swift-related software you run.

### Database Integrity

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

### Logging and Monitoring

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

### Intrusion Detection (advisory)

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

### Cyber Incident Response Planning

Keep and test a cyber incident response plan that covers Swift, including informing Swift and using its threat intelligence.

### Security Training and Awareness

Train staff with access to Swift on security, including role-specific training for privileged users.

### Penetration Testing (advisory)

Test the security of the Swift environment through penetration tests.

### Scenario-based Risk Assessment (advisory)

Assess the risk of Swift-related attack scenarios regularly.

## Related

Regulation

### [ISO/IEC 27001: Information Security Management Systems (ISO 27001)](https://grc.plus/regulation/iso-27001-information-security-cybersecurity-and-privacy-protection/)

Specifies requirements for a risk-based information security management system that organisations of any size and sector can certify against.

Regulation

### [Payment Card Industry Data Security Standard (PCI DSS)](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/)

Specifies security requirements for any organisation that stores, processes or transmits card data, validated by a ROC or self-assessment.

Regulation

### [NIST Cybersecurity Framework (NIST CSF)](https://grc.plus/regulation/nist-cybersecurity-framework-nist-csf/)

Organises cybersecurity outcomes into six functions, from govern to recover, that organisations use to assess and improve their security.

## Talk to a Principal Consultant

Thirty minutes, no slides. You leave knowing which requirements apply to you and what it takes to meet them.

[Book a Scoping Call](https://meetings-eu1.hubspot.com/ahmet-ucar)
