08 Nov 2026 By CISO Consulting team 40 views 5 min read

SWIFT CSCF New Version: Which Changes Apply to You

Each CSCF release moves some advisory controls to mandatory and adjusts scope, and the effect depends on your architecture type. This article explains how to compare versions, sort the changes and build a dated gap list before the attestation deadline.

A compliance officer reviewing two versions of a control framework document side by side at a desk in a modern office.
In this article
  1. Why each release deserves a structured review
  2. Step 1: Fix your baseline
  3. Step 2: Compare the versions control by control
  4. Step 3: Sort the changes by architecture type
  5. Step 4: Test where you stand today
  6. Step 5: Turn the findings into a dated gap list
  7. Signs it is time for an independent review
  8. What a good outcome looks like
  9. How we run this
  10. Next step

Every year, the SWIFT Customer Security Controls Framework is revised, and every year some institutions discover the revisions late. For teams searching for what a SWIFT CSCF new version changes in mandatory controls, the useful question is not only what changed, but which changes apply to your own environment and by when you must act. This article sets out a practical method for answering that.

Why each release deserves a structured review

A new CSCF version typically does three things. It may promote controls from advisory to mandatory, it may adjust the scope or wording of existing controls, and it may add or retire controls. The effect on any one institution depends on its architecture type, because the controls that apply differ between architecture A, architecture B and other types.

For Saudi banks and financial institutions, the framework sits alongside domestic expectations. SWIFT sets the CSCF and requires an annual attestation. The Saudi Central Bank (SAMA) sets the Cyber Security Framework that regulated institutions also work to. A change in one does not remove the need to check the other, so a version review is best kept as a repeatable exercise rather than a one-off reaction.

Step 1: Fix your baseline

Before comparing anything, confirm exactly what you attested against last time. Gather:

  • The CSCF version and the architecture type recorded in your last attestation.
  • The list of in-scope components, including interfaces, connectors, operator workstations and any service provider connections.
  • The control-by-control results, with the evidence behind each one.
  • Any open items or accepted exceptions carried forward.

Architecture type is the point most often assumed rather than checked. Infrastructure changes, such as moving an interface to a service provider or adding a connector, can change your type without anyone formally deciding that it has. If your type has shifted, your applicable control set has shifted with it.

Step 2: Compare the versions control by control

Take the published control set for the new version and the one for the version you attested against, and compare them line by line. Record each difference under one of these headings:

  1. Newly mandatory: a control that was advisory and now must be met.
  2. New control: a control that did not exist before.
  3. Scope change: a control whose applicability, components or wording has changed.
  4. Clarification only: guidance that was reworded without altering what is expected.
  5. Removed or merged: a control that no longer stands alone.

Use the official SWIFT documentation as the source for this comparison. Summaries from other places can be useful for orientation, but the attestation is made against the framework text itself.

Step 3: Sort the changes by architecture type

For each difference, ask whether it applies to your architecture type and to the components you have in scope. Place each change in one of three groups:

  • Applies and is mandatory: you must meet it for the next attestation.
  • Applies and is advisory: not required yet, but worth planning, since advisory controls are the usual candidates for later promotion.
  • Does not apply: record the reason, so that the decision can be reviewed if your architecture changes.

Writing down the reason for each "does not apply" is important. It turns a silent assumption into a documented scoping decision, which is easier to defend to an assessor and to your own audit function.

Step 4: Test where you stand today

For every change in the first two groups, assess your current position against the control and note what evidence you hold. Be honest about evidence. A control may be operating in practice but without records that an assessor could rely on, and that is a gap in attestation terms even if it is not a gap in security terms.

Typical outcomes are: met with evidence, met without evidence, partly met, and not met. Each calls for a different kind of work, from collecting records to changing a technical configuration or a procedure.

Step 5: Turn the findings into a dated gap list

A gap list is only useful if it can be managed. For each gap, record:

  • The control and the version change that created it.
  • The architecture component affected.
  • The action required and the named owner.
  • A target date, working back from the attestation deadline and leaving time for evidence to accumulate.
  • Any dependency, such as a vendor change window or budget approval.

Controls that need a technical change or a recurring activity should be started first, because evidence of operation takes time to build. Documentation gaps can be closed later. Sorting by lead time rather than by control number is what prevents a last-minute scramble.

Signs it is time for an independent review

Internal teams can run this comparison, but several situations suggest outside support is worth considering:

  • Your architecture has changed since the last attestation and you are unsure of your type.
  • The people who prepared the last attestation have moved on.
  • Evidence is held in several places and has not been consolidated.
  • Your internal audit function wants independent assurance before you attest.
  • The new version affects components you have not assessed before.

What a good outcome looks like

By the time you reach the attestation window, you should have a confirmed architecture type, a documented list of what changed and what applies, evidence stored control by control, and a gap list in which every item has an owner and a date. Most items should already be closed, and the remainder should be known, scheduled and explainable. Nothing about the new mandatory controls should be a surprise.

How we run this

Our SWIFT CSCF Assessment & Attestation service is built around this sequence. We independently assess your SWIFT environment against the current Customer Security Controls Framework, identify gaps and support remediation and your annual attestation. The work follows four stages: scope the architecture type and in-scope components, assess each control with evidence, support gap closure, and prepare the final report for the attestation.

The service includes architecture type confirmation and an assessment of both mandatory and advisory controls, so the version differences described above are sorted against your actual setup. The assessment phase takes 3–5 weeks. You receive an independent assessment report, a control-by-control evidence file and a gap remediation plan. The framework coverage is SWIFT CSCF and SAMA CSF.

Next step

If you are planning this year's attestation, the best time to compare versions is before remediation windows close. Speak to CISO Consulting about a SWIFT CSCF assessment, and we will confirm your architecture type, sort the new requirements and give you a dated plan to work from.

Tags: SWIFT CSCF Attestation Mandatory controls Architecture type Regulatory updates Saudi banking
Readiness self-check

How ready are you? Find out in two minutes

Answer a few questions for your framework. You get a score, your biggest gaps and — if you want it — a detailed assessment from our team.

Ready to talk about your compliance?

Tell us where you stand. We will show you the shortest path to what your regulator expects.

Regulatory updates in your inbox

SAMA, NCA and SDAIA changes and what they mean for your institution — once a month.

E-mails in

We confirm by e-mail; unsubscribe any time. Manage your subscription · Past issues

Schedule a Free Assessment