SWIFT CSCF Framework Version Management

ScreenSWIFT Customer Security Programme·step 1

Complete the Identity fields. Each value is validated against the schema before the next step unlocks.

• Assessment Name (required)

  assessmentName

  Enter assessment name. An example value is "SWIFT CSCF 2026 Migration Review".

• SWIFT BIC Code (required)

  entityId

  The 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.

ScreenSWIFT Customer Security Programme·step 2

Complete the Migration fields. Each value is validated against the schema before the next step unlocks.

• Current Framework Version (Source)optional

  sourceVersion

  Select version.

• Target Framework Versionoptional

  targetVersion

  Select version.

• Impacted Architecture Typeoptional

  impactedArchType

  Select architecture.

ScreenSWIFT Customer Security Programme·step 3

Complete the Controls fields. Each value is validated against the schema before the next step unlocks.

• Have control gaps been formally identified against the target version?optional

  hasIdentifiedGaps

  Enter have control gaps been formally identified against the target version?.

• Operational Impact Leveloptional

  operationalImpactLevel

  Enter operational impact level.

• Infrastructure/Systems requiring upgrade or replacementoptional

  systemsRequiringUpgrade

  Enter infrastructure/systems requiring upgrade or replacement.

ScreenSWIFT Customer Security Programme·step 4

Complete the Governance fields. Each value is validated against the schema before the next step unlocks.

• Migration Strategyoptional

  migrationStrategy

  Enter migration strategy.

• Project Owneroptional

  projectOwner

  Search manager.

• Has necessary budget been secured?optional

  budgetApproved

  Enter has necessary budget been secured?.

• Target Completion Dateoptional

  targetCompletionDate

  Enter target completion date.

ScreenSWIFT Customer Security Programme·step 5

Complete the Exceptions fields. Each value is validated against the schema before the next step unlocks.

• Do you have existing out-of-scope exemptions or compensating controls?optional

  carryoverExceptionsExist

  Enter do you have existing out-of-scope exemptions or compensating controls?.

• Have existing exceptions been reviewed against target version controls?optional

  exceptionsReviewed

  Enter have existing exceptions been reviewed against target version controls?.

• Previous exceptions no longer valid under new versionoptional

  invalidatedExceptions

  Enter previous exceptions no longer valid under new version.

ScreenSWIFT Customer Security Programme·step 6

Complete the Testing fields. Each value is validated against the schema before the next step unlocks.

• Have net-new mandatory controls been successfully tested?optional

  newControlsTested

  Enter have net-new mandatory controls been successfully tested?.

• Evidence Repository Link (Test Results/Diagrams)optional

  evidenceRepositoryLink

  Enter evidence repository link (test results/diagrams).

ScreenSWIFT Customer Security Programme·step 7

Complete the Regulatory fields. Each value is validated against the schema before the next step unlocks.

• Has an Independent Assessor been engaged (IAF)?optional

  iafAssessorEngaged

  Enter has an independent assessor been engaged (iaf)?.

• Target IAF Completion Dateoptional

  iafCompletionTarget

  Enter target iaf completion date.

• Critical Control Remediation Status (e.g., Control 2.4)optional

  criticalControlRemediationStatus

  Enter critical control remediation status (e.g., control 2.4).

• Planned KYC-SA Portal Submission Dateoptional

  plannedKycSaSubmissionDate

  Enter planned kyc-sa portal submission date.

ScreenSWIFT Customer Security Programme·step 8

Complete the Sign Off fields. Each value is validated against the schema before the next step unlocks.

• I confirm the accuracy of this version migration scope and planoptional

  reviewSignOff

  Enter i confirm the accuracy of this version migration scope and plan.

ScreenSWIFT Customer Security Programme·step 9

Complete the Deadlines fields. Each value is validated against the schema before the next step unlocks.

• Trigger date (starts the clock) (required)

  triggerAt

  Enter trigger date (starts the clock).

ScreenSWIFT Customer Security Programme·step 10

No manual input is captured here: this step is completed from the preceding sections or by the platform.

No manual inputs in this step.