Architecture type and scope
Confirm your architecture type (A1, A2, A3, A4 or B), the secure zone, operator PCs and in-scope components, so the right controls are assessed.
I've run the full SWIFT Customer Security Programme lifecycle for eight financial institutions, from architecture scoping and control walkthroughs to evidence validation and attestation support.
Confirm your architecture type (A1, A2, A3, A4 or B), the secure zone, operator PCs and in-scope components, so the right controls are assessed.
Assessment of every mandatory control and the advisory controls you choose to attest to, backed by interviews, evidence review and testing.
With control 2.4 now mandatory, map flows between the secure zone and back office, identify bridging servers and confirm protection.
Middleware, API clients and file transfer tools are now in mandatory scope for many controls. Check whether this changes your architecture type.
An assessment report and evidence mapping that support an accurate attestation in the KYC Security Attestation application.
A repeatable review and validation method, so each annual assessment is consistent and quicker to complete.
Confirm the architecture type, in-scope components and the CSCF version you are attesting against.
Interview control owners and understand how each control operates in practice, not just on paper.
Review configurations, logs and records, and test controls where evidence alone is not enough.
Document compliance status per control, agree fixes for gaps and support an accurate attestation before the deadline.
SWIFT CSCF client engagements per country. Client names stay confidential.
Tell me your architecture type and timeline. I'll tell you honestly what the assessment involves.