Step 1 of 8: Identity
SWIFT Customer Security Programme
Phase 3 · Evidence & auditReal-time drift detection, architecture delta monitoring, and automated baseline re-basing.
Basis: Operations
/swift-driftSWIFT Customer Security Controls Framework (CSCF v2025/v2026)
8 steps, completed in order. Each step is validated against the schema before the next unlocks.
Step 1 of 8
Complete the Identity fields. Each value is validated against the schema before the next step unlocks.
Drift Report Name (required)
driftNameEnter drift report name. An example value is "Weekly Compliance Drift Q2".
SWIFT BIC Code (required)
entityIdThe BIC of the entity this record is about — 8 or 11 characters, e.g. DEUTDEFF or DEUTDEFF500. Pick one you have used before, or type a new BIC to add it.
Step 2 of 8
Complete the Trigger fields. Each value is validated against the schema before the next step unlocks.
Baseline Snapshot Date (Last Known Good)optional
baselineSnapshotDateEnter baseline snapshot date (last known good).
Current Snapshot Dateoptional
currentSnapshotDateEnter current snapshot date.
Drift Trigger Eventoptional
driftTriggerEventSelect trigger.
Step 3 of 8
Complete the Tooling fields. Each value is validated against the schema before the next step unlocks.
Configuration Monitoring Tool (e.g., AWS Config)optional
configMonitoringToolEnter configuration monitoring tool (e.g., aws config).
File Integrity Monitoring Tool (Control 6.2)optional
fileIntegrityToolEnter file integrity monitoring tool (control 6.2).
SIEM Logging Platform (Control 6.4)optional
siemToolEnter siem logging platform (control 6.4).
Step 4 of 8
No manual input is captured here: this step is completed from the preceding sections or by the platform.
No manual inputs in this step.
Step 5 of 8
Complete the Accountability fields. Each value is validated against the schema before the next step unlocks.
Remediation SLA Deadlineoptional
remediationSlaDateEnter remediation sla deadline.
I acknowledge the compliance drift and commit to the SLAoptional
driftAcknowledgmentEnter i acknowledge the compliance drift and commit to the sla.
Step 6 of 8
Complete the Risk fields. Each value is validated against the schema before the next step unlocks.
Risk likelihood (0-10) (required)
riskLikelihoodEnter risk likelihood (0-10).
Risk impact (0-10) (required)
riskImpactEnter risk impact (0-10).
Step 7 of 8
No manual input is captured here: this step is completed from the preceding sections or by the platform.
No manual inputs in this step.
Step 8 of 8
No manual input is captured here: this step is completed from the preceding sections or by the platform.
No manual inputs in this step.
Continue with the next guide in this framework's table of contents.
Immutable compliance evidence storage, SHA-256 chain-of-custody verification, and audit locking.
Read guide Phase 3 · Evidence & auditSWIFT-issued CSP security advisory acknowledgment, mandatory action tracking, and tenant impact scoring.
Read guide Phase 1 · Scoping & architecturePhysical and logical boundary definition, architecture typing (A1-A4, B), and in-scope control baseline mapping.
Read guide