4 minute read 22 Dec 2020
Buildings in a busy street at sunset .

Why the SWIFT Customer Security Programme should be a CISO priority

By Tom Schmidt

Partner, Financial Services Cybersecurity Competency Leader | EMEIA, Cybersecurity Leader, Financial Services | EY Switzerland

Focusing on all aspects of Information Security, Cybersecurity, and IT risk management. Passionate about traveling the world and engaging in various sports.

4 minute read 22 Dec 2020
Related topics Consulting Digital Technology

The pressure is on CISOs of SWIFT member organizations to perform independent Community Standard Assessments by 31 December 2021.

In brief

  • SWIFT member organizations must meet new compliance requirements, which includes an independent assessment, by 31 December 2021.
  • The new requirements impact SWIFT members as well as their ITOs and BPOs.
  • Independent assessments require time, know-how and resources, and can be complex and challenging.

After the infamous “Bangladesh Bank cyber heist” in 2016, the Society for Worldwide Interbank Financial Telecommunication (SWIFT) introduced its Customer Security Programme (CSP) to deepen its support to members in more than 200 countries. This CSP heightened security of global banking and payment systems by providing information and tools for integrating cybersecurity into a risk-based decision framework for counterparty relationships.

Each year, SWIFT publishes an update of its Customer Security Controls Framework (CSCF), and requires members to verify their adherence to these controls annually based on a self-attestation. In July 2019, SWIFT released the “SWIFT CSP Independent Assessment Framework” indicating that from mid-2020, all SWIFT members would be obliged to perform “Community Standard Assessments” that required independent assessments, either by an internal second line of defense (e.g. operational risk) or third line of defense (e.g. internal audit) function or by an external auditor/assessor.

The global economic impact of the COVID-19 pandemic resulted in SWIFT postponing the new requirement of an independent SWIFT CSP assessment by one year. Consequently, many SWIFT members paused or slowed their SWIFT CSP 2020 activities as well.

Now, with the revised 31 December 2021 deadline once again looming, this topic has become an urgent issue for many CISOs and cybersecurity teams in SWIFT member organizations, which range from banks, stock exchanges, brokerage houses and other companies.

The implementation of the new 2021 SWIFT CSP requirements can be very challenging, as it not only impacts SWIFT members but also the ITOs and BPOs that support them.

Understanding SWIFT architecture types and the CSP assessment

The SWIFT 2021 assessment comprises a maximum of 22 mandatory and nine advisory controls with comprehensive implementation guidelines. The total number of controls is determined by the “SWIFT architecture type”, defined by how SWIFT members connect the SWIFT network. SWIFT distinguishes between five possible architecture types (types A1-A4 and type B) with all 31 controls in scope for architecture types A1 and A2, and only a subset of 22 controls in scope for architecture type B.

Implementation of SWIFT CSP requirements tends to be challenging

An increasingly number of SWIFT members have outsourced part of their IT infrastructure and/or business processes to IT Outsourcing (ITO) and Business Process Outsourcing (BPO) providers. However, the ultimate responsibility for SWIFT CSP compliance remains with SWIFT members (namely, the organizations that own the SWIFT Business Identifier Code (BIC)). Therefore, increasingly more SWIFT members expect to receive SWIFT CSP compliance assurance reports (e.g. ISAE 3000 reports) from their ITOs and BPOs. As such, it is not only the SWIFT members but also ITOs and BPOs that support them, that need to prepare for compliance with the new requirements in 2021.

The implementation of the SWIFT CSP requires time, know-how and resources, and can be complex and challenging. The following six steps are crucial for SWIFT members as well as ITO and BPO providers:

  1. Set up a cross-functional team to oversee implementation, including IT, risk and compliance
  2. Analyze past IT and information security audits to identify critical gaps which need to be addressed as part of the SWIFT CSP implementation project
  3. Conduct readiness assessments for mandatory and advisory controls
  4. Evaluate to what extent SWIFT CSP control requirements can be automated by technological solutions (e.g. continuous monitoring of SWIFT logs regarding possible anomalies) instead of purely manually driven control activities
  5. Understand how the implementation of the SWIFT CSP can be aligned with broader cybersecurity initiatives
  6. Determine the extent to which existing ISAE 3000 or similar Service Organization Control reports are already addressing SWIFT CSP controls to understand what needs to be in place in addition

The pressure is on

SWIFT members are required to submit their SWIFT CSP attestation based on an independent SWIFT CSP assessment report by 31 December 2021. The pressure is on, and there’s no time to waste to kick off planning as early as Q1 2021.

The consequences for non-compliance are high. If a SWIFT member fails to comply, SWIFT will inform other SWIFT members and may report deficiencies to local supervisory authorities in the respective operating countries of those members. Not only can this directly jeopardize business operations, but it may incur untold reputational damage and stakeholder trust. On the other hand, proactive planning and a reliable delivery provider of the necessary assessments will help organizations to remain focused on their primary cybersecurity mandate without compromising on critical compliance.

Summary

Member organizations of the SWIFT network are required to submit their SWIFT CSP attestation by 31 December 2021 based on an independent assessment. The pressure is now on CISOs to plan for and undertake the necessary steps for compliance. This can be both complex and time consuming if not well planned and executed.

About this article

By Tom Schmidt

Partner, Financial Services Cybersecurity Competency Leader | EMEIA, Cybersecurity Leader, Financial Services | EY Switzerland

Focusing on all aspects of Information Security, Cybersecurity, and IT risk management. Passionate about traveling the world and engaging in various sports.

Related topics Consulting Digital Technology