SWIFT Customer Security Controls Framework

SWIFT issues the SWIFT Customer Security Controls Framework for the community

The SWIFT Customer Security Controls Framework describes a set of mandatory and advisory security controls for SWIFT customers.

Mandatory security controls establish a security baseline for the entire community, and must be implemented by all users on their local SWIFT infrastructure. SWIFT has chosen to prioritise these mandatory controls to set a realistic goal for near-term, tangible security gain and risk reduction.
Advisory controls are based on good practice that SWIFT recommends users to implement. Over time, mandatory controls may change due to the evolving threat landscape, and some advisory controls may become mandatory.

All controls are articulated around three overarching objectives: 'Secure your Environment', 'Know and Limit Access', and 'Detect and Respond'. The controls have been developed based on SWIFT's analysis of cyber threat intelligence and in conjunction with industry experts and user feedback. The control definitions are also intended to be in line with existing information security industry standards.

The SWIFT Customer Security Controls Framework Detailed Description is available on swift.com. Customers must log in to mySWIFT with their swift.com credentials to access the document. (swift.com > Ordering & Support > User Handbook home > A-Z > Customer Security Programme).

To ensure adoption, and to complement the Swift Customer Security Controls Framework, SWIFT has now published  further details of the related attestation policy and process in the SWIFT Customer Security Controls Policy document

The document contains further information on:

  • the requirement to self-attest against SWIFT’s mandatory security controls.
  • the process and timelines for submitting self- attestation data to The KYC Registry Security Attestation application.
  • the process for viewing counterparties’ attestation data via the KYC Registry Security Attestation application
  • follow-up actions in cases of non-compliance according to the reporting timelines.

We strongly urge customers to consult this document and to begin preparing . Customers must log in to mySWIFT with their swift.com credentials to access the document. (swift.com > Ordering & Support > User Handbook home > A-Z > Customer Security Programme).

The KYC registry Security Attestation Application will be open for the submission of self-attestation data from July 2017 onwards, and all SWIFT users must have submitted a self-attestation by end of December 2017. 

Customers are also encouraged to explore the new suite of SWIFTSmart training modules which include an overview of the SWIFT Customer Security Controls Framework and an introduction to the 16 mandatory security controls.

 

CSP security controls

 

Mandatory Security Controls Control Objective

1. Restrict Internet Access and Protect Critical Systems from General IT Environment

1.1 SWIFT Environment Protection Ensure the protection of the user's local SWIFT infrastructure from potentially compromised elements of the general IT environment and external environment.

1.2 Operating System Privileged Account Control

Restrict and control the allocation and usage of administrator-level operating system accounts.

2. Reduce Attack Surface and Vulnerabilities
2.1 Internal Data Flow Security

Ensure the confidentiality, integrity, and authenticity of data flows between local SWIFT-related applications and their link to the operator PC.

2.2 Security Updates Minimize the occurrence of known technical vulnerabilities within the local SWIFT infrastructure by ensuring vendor support, applying mandatory software updates, and applying timely security updates aligned to the assessed risk.
2.3 System Hardening Reduce the cyber attack surface of SWIFT-related components by performing system hardening.
3. Physically Secure the Environment
3.1 Physical Security Prevent unauthorised physical access to sensitive equipment, workplace environments, hosting sites, and storage.
4. Prevent Compromise of Credentials
4.1 Password Policy Ensure passwords are sufficiently resistant against common password attacks by implementing and enforcing an effective password policy.
4.2 Multi-factor Authentication Prevent that a compromise of a single authentication factor allows access into SWIFT systems, by implementing multi-factor authentication.
5. Manage Identities and Segregate Privileges
5.1 Logical Access Control Enforce the security principles of need-to-know access, least privilege, and segregation of duties for operator accounts.
5.2 Token Management Ensure the proper management, tracking, and use of connected hardware authentication tokens (if tokens are used).
6. Detect Anomalous Activity to Systems or Transaction Records
6.1 Malware Protection Ensure that local SWIFT infrastructure is protected against malware.
6.2 Software Integrity Ensure the software integrity of the SWIFT-related applications.

6.3 Database Integrity

Ensure the integrity of the database records for the SWIFT messaging interface.
6.4 Logging and Monitoring Record security events and detect anomalous actions and operations within the local SWIFT environment.
7. Plan for Incident Response and Information Sharing
7.1 Cyber Incident Response Planning Ensure a consistent and effective approach for the management of cyber incidents.
7.2 Security Training and Awareness Ensure all staff are aware of and fulfil their security responsibilities by performing regular security training and awareness activities.

 

Advisory Security Controls Control objective
2. Reduce Attack Surface and Vulnerabilities
2.4 A Back Office Data Flow Security Ensure the confidentiality, integrity, and mutual authenticity of data flows between back office (or middleware) applications and connecting SWIFT infrastructure components.

2.5 A External Transmission Data Protection

Protect the confidentiality of SWIFT-related data transmitted and residing outside of the secure zone.

2.6 A Operator Session Confidentiality and Integrity

Protect the confidentiality and integrity of interactive operator sessions connecting to the local SWIFT infrastructure.
2.7 A Vulnerability Scanning

Identify known vulnerabilities within the local SWIFT environment by implementing a regular vulnerability scanning process.

2.8 A Critical Activity Outsourcing

Ensure protection of the local SWIFT infrastructure from risks exposed by the outsourcing of critical activities.

2.9 A Transaction Business Controls

Restrict transaction activity to validated and approved counterparties and within the expected bounds of normal business.

5. Manage Identities and Segregate Privileges

5.3 A Personnel Vetting Process

Ensure the trustworthiness of staff operating the local SWIFT environment by performing personnel vetting.

5.4 A Physical and Logical Password Storage

Protect physically and logically recorded passwords.

6. Detect Anomalous Activity to Systems or Transaction Records
6.5 A Intrusion Detection

Detect and prevent anomalous network activity into and within the local SWIFT environment.

7. Plan for Incident Response and Information Sharing
7.3 A Penetration Testing

Validate the operational security configuration and identify security gaps by performing penetration testing.

7.4 A Scenario Risk Assessment

Evaluate the risk and readiness of the organization based on plausible cyber attack scenarios.