Swift Customer Security Programme
Swift CSP Assessment
Swift accepts your yearly KYC-SA attestation as compliant only when an independent assessment from the same year supports it. We carry out that assessment and hand you the report and the signed completion letter, so you can attest with confidence before 31 December 2026, this year's deadline. There is still time: we start within two to five working days of your go-ahead.
- Listed in Swift's directory of CSP assessment providers. Check the Listing on swift.com
- Led and signed by a Swift CSP Certified Assessor, who also runs the working sessions
- We never assess a control we helped design or run
- Professional indemnity insurance on every engagement
WHY YOU NEED AN ASSESSMENT
No independent assessment, no compliant attestation
Every Swift user attests each year in KYC-SA. Swift only counts that attestation as compliant when an independent assessment from the same year backs it up.
The problem
You cannot vouch for your own controls
A self-assessment by the team that runs the controls shows as not compliant. Without an independent report, your attestation works against you, and the window closes on 31 December.
- Counterparties you give access to in KYC-SA may see your status and limit business with you
- Swift can report a late or non-compliant attestation to your supervisor
- A new BIC cannot go live without a valid attestation
The solution
An independent assessment, scoped to your architecture
A Swift CSP Certified Assessor tests every mandatory control that applies to your architecture type, against the CSCF version you attest to, and relies on your providers' assurance where Swift allows.
- Scope confirmed for A1, A2, A3, A4 or B, with your BICs and environments
- An evidence list mapped to each control, and short remote sessions
- Draft findings you can answer before anything is final
The outcome
You attest with confidence, on time
You receive the report, Swift's completed templates and the signed completion letter, and publish your attestation before the deadline.
- A KYC-SA attestation your counterparties and supervisor can rely on
- Each gap fixed or planned, with how other Swift users closed it
- A lighter assessment next year for controls that did not change
Does a requirement ask for it?
What asks for it in Sweden
We scope the work to what your requirement asks for, so the result serves that audit or supervisor too.
What we check
What we assess
For each requirement we review the evidence and check that the control works, so you know exactly where you stand.
Your architecture type and scope
We confirm A1, A2, A3, A4 or B from what you own or licence, and list the BICs, environments (live, back-up and disaster recovery) and components in scope.
Every mandatory control that applies
From 16 mandatory controls for type B to 25 for A1 and A2 under CSCF v2027, plus the advisory controls you want in your attestation.
What your providers cover
Where a service bureau, cloud or treasury platform runs part of the set-up, we split the responsibilities and rely on its assurance where Swift allows.
Each finding with a recommendation
Every gap comes with its risk and a practical recommendation, so your team can close it or plan a compliance date before you attest.
The Swift control framework
Three objectives. Seven security principles.
The CSCF groups controls around protecting your environment, limiting access and responding to threats. Your architecture and components determine which controls apply to the assessment.
Secure your environment
Protect the systems and surroundings used for Swift operations.
- 1. Separate critical systems from general IT and restrict internet access
- 2. Reduce attack surface and vulnerabilities
- 3. Secure the physical environment
Know and limit access
Control who can access systems and what they can do.
- 4. Protect credentials from compromise
- 5. Manage identities and separate privileges
Detect and respond
Recognise suspicious activity and prepare an effective response.
- 6. Detect unusual system or transaction activity
- 7. Plan incident response and information sharing
Adapted from Swift CSCF v2027, Framework Objectives and Principles, page 9: 32 controls, 26 mandatory and 6 advisory. Principle descriptions are shortened for readability; the CSCF remains the assessment reference. View source
YOUR ASSESSMENT, PHASE BY PHASE
From kick-off to completion letter
The phases are the same for every architecture; their length is not. A single BIC on type B usually takes two to three weeks from kick-off. With more components, interfaces or environments (A1 to A4), evidence and sessions take longer, and your proposal gives the dates.
-
Kick-off
Kick-off and evidence request
Within two to five working days of your go-ahead: the plan, the dates and an evidence list mapped to each control.
-
Kick-off – Evidence
Evidence upload and review
A few days for type B; longer where more components and environments are in scope.
-
Evidence – Sessions
Working sessions with control owners
Short online sessions, usually one a day; their number follows the components in scope.
-
Findings
Draft findings and your factual review
You see every conclusion before it is final and can add evidence.
-
Close
Report and completion letter
The documents your attestation rests on: report, Swift templates, executive summary, signed letter.
-
Close
You publish your attestation in KYC-SA
Once you have the final report, before 31 December; we answer your questions while you fill it in.
A guide, not a fixed promise: the length of each phase depends on your architecture type and on how quickly evidence and people are available.
WHEN TO START
Attest by 31 December 2026, then plan for 2027
This year you attest against CSCF v2026, and the deadline is 31 December 2026. There is still time: we start within two to five working days of your go-ahead, and for type B your report usually follows two to three weeks after kick-off. In 2027 you attest against CSCF v2027, which Swift has already published: the window opens in July 2027 and closes on 31 December 2027. Either way, your assessment report has to be ready before you attest.
-
Jan–Jun
Check what CSCF v2027 changes for you
No new or promoted mandatory controls, but clarifications: the secrets and keys vault is an in-scope component, and users working through an outsourcing agent attest as A4, not B.
-
Jan–Jun – Aug
Scope and book the assessment
Agree architecture type, scope and dates early: assessor diaries fill up after the summer.
-
Jul
Attestation window opens
From July 2027 you can attest against CSCF v2027.
-
Jul – Oct
Independent assessment
About two to three weeks for type B; for A1 to A4 the proposal gives the dates, sized on Swift's effort guide.
-
Sep – Nov
Fix gaps, if any
Close findings before you attest, or record a planned compliance date in KYC-SA.
-
Aug – Dec
Publish your attestation in KYC-SA
Once you have the final report, approved by your CISO or an equally senior officer.
-
Dec
Deadline: 31 December 2027
Last year's attestations expire at the end of 2027; late or missing attestations can be reported to your supervisor.
Based on Swift's Customer Security Controls Framework v2027, the Customer Security Controls Policy and the Independent Assessment Framework. Starting in October or November? Ask early: we can usually still plan an assessment before the deadline. View source
YOUR 2026 ATTESTATION
Still time to attest by 31 December 2026
Tell us how you connect to Swift. We confirm your architecture type and send a written proposal with scope, dates and a fixed fee within two working days, and start within two to five working days of your go-ahead. For 2027 the attestation window opens in July, and we also run out-of-cycle assessments for a new connection, a major change or a supervisor's request.
WORKING WITH US
What it takes from your side
Your team's time, how quickly we start, and what makes the assessment lighter.
Of your team's time, in total
From about 8 hours for a single BIC on type B to about 32 for A1 or A2: a coordinator who gathers evidence and arranges sessions, and an hour or two with each control owner in treasury or payments, IT and security.
From your go-ahead to kick-off
We start within two to five working days, so a late decision in the year does not cost you the deadline.
From kick-off to your report, for type B
Then you attest. For types A1 to A4 with more components, the proposal gives the dates, in line with Swift's effort guide above.
No travel costs
Swift allows remote assessments: video calls, screen-share demonstrations and documents, with physical controls shown on camera. On-site days only when you want them.
Your provider's assurance counts
Where a service bureau, cloud or treasury platform runs part of your set-up, we rely on its assurance reports and test only the controls you run.
A lighter following year
Swift lets an unchanged control rely on the previous conclusion for one following cycle, when neither the control nor your set-up changed; the year after needs a full assessment. In that year we focus on what changed and on this year's findings.
Delivered Work on the Same Topic
Clients are described, never named.
What you receive, and what it lets you do
The assessment report
Scope, architecture type, method and a conclusion for every control, with the evidence behind it and what to fix. It is what your attestation must match, and what you keep for five years.
The signed completion letter
Confirms that an independent assessment of the CSCF version was carried out. It is the one document Swift may ask you for.
PDF, signed by the Certified CSP Assessor
Swift's completed control templates
The mandatory and, where agreed, advisory control workbooks, so your team can fill in KYC-SA control by control.
Excel, Swift templates
An executive summary and walkthrough
The overall result and the decisions management needs to take, presented to your stakeholders.
Presentation and a closing call
Why Swift users choose GRC+
Certified and listed by Swift
Every assessment is led and signed by a Swift CSP Certified Assessor, and GRC+ is listed in Swift's directory of CSP assessment providers. The certified assessor runs the working sessions; the work is not handed down.
Findings that hold up to scrutiny
Each conclusion records the test performed and the evidence behind it, on Swift's templates, so your internal auditors, external auditors and supervisors can rely on it.
We know where the gaps usually are
Across our assessments the same controls fall short most often: multi-factor authentication for the application that reaches Swift (4.2), an incident plan without Swift-specific steps (7.1), logging and monitoring (6.4) and access reviews (5.1). We look there first and tell you how others closed them.
At home in treasury and cloud set-ups
Many Swift users connect through a cloud treasury platform, a service bureau or another provider (types A4 and B). We know which evidence those providers can supply and which controls stay with you.
Ready for CSCF v2027
We follow Swift's yearly changes and tell you at scoping what the version you attest to means for your architecture, such as the secrets and keys vault now in scope, or the move from B to A4 for users of an outsourcing agent.
One set of evidence, more frameworks
Our mappings link the Swift controls to DORA and its technical standards, ISO 27001 and PCI DSS, so the evidence you collect for Swift also serves those audits.
Credentials
Who does the work
Certified practitioners
Every engagement is led by a senior, certified practitioner.
25+
years in regulated sectors
Banks, insurers, payments, healthcare and the public sector across the globe.
Insured
Professional indemnity cover on every engagement.
FAQ
Swift CSP assessment: frequently asked questions
Something else? Ask us in a 30-minute call.
Who can carry out the assessment?
SwiftSociety for Worldwide Interbank Financial Telecommunication accepts an appropriately independent internal team, an external assessor or a mixed team that meets its competence and independence requirements. GRC+ provides external independent assessments and is listed in SwiftSociety for Worldwide Interbank Financial Telecommunication’s CSP Certified Assessors directory.
Can GRC+ assess controls it helped to fix?
No. SwiftSociety for Worldwide Interbank Financial Telecommunication requires the assessment to be independent. Where we have helped design or run a control, we do not assess that control: another independent assessor does, or you choose one.
When is the Swift CSP attestation due?
By 31 December 2026 for this year’s cycle, against CSCF v2026, for every connected BICBusiness Identifier Code. There is still time: we start within two to five working days of your go-ahead, and for type B the report usually follows two to three weeks after kick-off. The 2027 cycle runs from July to 31 December 2027, against CSCF v2027Customer Security Controls Framework V2027. Each attestation must rest on an independent assessment from the same year, so you attest once you have the final report. Plan the assessment early enough for evidence, your factual review and any fixes; we confirm the timetable at scoping.
Do you implement the changes in our systems?
No. We report each gap with a recommendation; your team or your provider designs and makes the fix. If you want us to help design a fix, another independent assessor assesses that control.
How long will it take, and can it be remote?
It depends on your architecture type. For a single BICBusiness Identifier Code on type B, or A4Swift Architecture Type A4 with only a customer client connector, the report usually follows two to three weeks after kick-off, and we start within two to five working days of your go-ahead. SwiftSociety for Worldwide Interbank Financial Telecommunication‘s own guide puts the assessor effort at about 7 days for those types, 17 to 18 for A3 and A4Swift Architecture Type A4 with a customer connector, and 23 for A1 and A2; for those, the proposal gives the dates. Assessments are remote by default, as SwiftSociety for Worldwide Interbank Financial Telecommunication allows; on-site days are possible.
What if a gap cannot be closed before the deadline?
You can attest with a planned compliance date for that control in KYC-SAKYC-Security Attestation. We help you set a date you can keep and the steps to get there.
Show 7 More Questions
Do we have to include the advisory controls?
The assessment must cover the mandatory controls applicable to your architecture and components. Advisory controls are recommended and can be included in the agreed scope. Applicability and control status can change between CSCFCustomer Security Controls Framework versions, so we confirm both against the version for your attestation cycle.
What will we receive?
You receive completed control workbooks, a full assessment report, an executive presentation and a signed completion letter. We discuss the conclusions and exceptions with your stakeholders. Advisory-control coverage, report formats and any KYC-SAKYC-Security Attestation preparation support are confirmed in the proposal. Your organisation owns the attestation and submission.
How is the fee determined?
It is a fixed fee, set in your written proposal before any work starts. It follows your architecture type, the BICsBusiness Identifier Code and infrastructures in scope, whether you include advisory controls, and whether you want on-site days. There are no day rates or open-ended hours, and the fee does not change unless the scope does.
Do you cover service bureaus and other third parties?
Where third parties host, operate or maintain in-scope components, we establish the responsibilities and evidence needed from each party. Relevant independent reports may support the assessment when their scope, timing and coverage meet SwiftSociety for Worldwide Interbank Financial Telecommunication’s criteria; outsourcing does not remove the SwiftSociety for Worldwide Interbank Financial Telecommunication user’s responsibility for its attestation.
Can we attest before the report is ready?
Not as a compliant attestation. SwiftSociety for Worldwide Interbank Financial Telecommunication requires the attestation to be consistent with the findings of an independent assessment and supported by a report from the same year, so you attest once you have the final report. An attestation without an independent assessment shows as not compliant to the supervisor and to the counterparties that can see it.
What happens if the assessment finds gaps?
You see each finding in the draft and can add evidence before the report is final. For a gap that remains, you either fix it before you attest or attest that control as “I will comply by” a planned date; until then your attestation does not count as fully compliant. We tell you which gaps matter most and how other SwiftSociety for Worldwide Interbank Financial Telecommunication users closed them.
Do we need a full assessment every year?
Every yearly attestation needs an independent assessment, but it does not always start from zero. SwiftSociety for Worldwide Interbank Financial Telecommunication lets a control conclusion be relied on for one following cycle when neither the control nor the CSCFCustomer Security Controls Framework requirement has changed. In that year we focus on changes, new requirements and last year’s findings, and re-confirm the rest on a sample; the year after needs a full assessment again.
Want to know more about Swift CSP?
Our guide to Swift CSP explains who it applies to, what it requires, the deadlines and what happens if you do not comply. Swift Customer Security Programme (Swift CSP) →
Let’s scope the assessment you need
Tell us who you are and when you need to attest. We will help clarify the scope and the information needed for a written proposal. You can share technical details and documents after confidentiality arrangements are agreed. sales@grc.plus +46 72 349 99 00


