Guides for Swift users preparing an attestation: running a gap analysis, implementing controls, choosing an internal, external or certified assessor, what drives assessment cost, obligations when connecting through a service bureau, and reading counterparties' attestations.
How a Swift user runs a CSCF gap analysis before implementing controls: identifying the architecture type, mapping controls with Swift's Security Guidance documents, comparing the current posture, and planning for advisory controls that will become mandatory.
What implementing the CSCF involves for a Swift user: who sits on the implementation team, how far Swift's implementation guidance binds you, the kinds of technical work involved, the records to keep for the assessor and the yearly update cycle.
How a Swift user picks who performs its CSP independent assessment: certified and non-certified external assessors, internal second and third line teams, mixed teams, the qualifications Swift expects, what certification adds and what the attestation must disclose.
What drives the cost of a SWIFT CSP independent assessment and attestation when Swift publishes no prices: scope set by architecture type and connectivity, internal versus external assessors, Swift's standardized effort estimates, reliance on last year's assessment and the cost of remediation.
What a Swift user that connects through a service bureau, L2BA or Business Connect provider still has to do under the CSP: its own footprint, the architecture decision, attestation and assessment duties, and the risk of being reported for using a non-compliant provider.
How Swift users use counterparties' CSP attestations in third-party risk management: what KYC-SA shows when access is granted, what the certified assessor flag and assessor name tell you, how remediation dates appear, and where Swift's policy on viewing attestations sits.
Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.