SWIFT Service Bureau Connectivity Governance

ScreenSWIFT Customer Security Programme·step 1

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

• Service Bureau Name (required)

  sbName

  Enter service bureau name. An example value is "Acme SWIFT Services".

• Service Bureau BICoptional

  sbBic

  The BIC of the service bureau operating the connection on your behalf — 8 or 11 characters, e.g. DEUTDEFF or DEUTDEFF500.

• Service Bureau LEIoptional

  sbLei

  Enter service bureau lei.

• Service Bureau Legal Nameoptional

  sbLegalName

  Enter service bureau legal name.

• Contract Referenceoptional

  contractId

  Enter contract reference.

• Contract Startoptional

  contractStartDate

  Enter contract start.

• Contract Endoptional

  contractEndDate

  Enter contract end.

ScreenSWIFT Customer Security Programme·step 2

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

• Hosting Services Providedoptional

  hostingServices

  Enter hosting services provided.

• Messaging Interfaces Hostedoptional

  messagingInterfacesHosted

  Enter messaging interfaces hosted.

• GPI Support?optional

  gpiSupport

  Enter gpi support?.

• SCORE Access?optional

  scoreAccess

  Enter score access?.

• Support Leveloptional

  supportLevel

  Select support level.

ScreenSWIFT Customer Security Programme·step 3

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

• Service bureau provided their own KYC-SA?optional

  sbAttestationProvided

  Enter service bureau provided their own kyc-sa?.

• SB Attestation SHA-256optional

  sbAttestationSha256

  Enter sb attestation sha-256.

• SB Attestation Expires Atoptional

  sbAttestationExpiresAt

  Enter sb attestation expires at.

• CSCF Controls Covered by SBoptional

  sbCscfControlsCovered

  Enter cscf controls covered by sb.

ScreenSWIFT Customer Security Programme·step 4

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

• Our Authorizing Officer Nameoptional

  ourAuthorizingOfficer

  Enter our authorizing officer name.

• Authorizing Officer Titleoptional

  ourAuthorizingOfficerTitle

  Select title.

• Authorizing Officer Emailoptional

  ourAuthorizingOfficerEmail

  Enter authorizing officer email.

• Authorization Dateoptional

  authorizationDate

  Enter authorization date.

• Due diligence completed?optional

  dueDiligenceCompleted

  Enter due diligence completed?.

• Due Diligence Notesoptional

  dueDiligenceNotes

  Enter due diligence notes.

ScreenSWIFT Customer Security Programme·step 5

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

• Last Audit Dateoptional

  lastAuditDate

  Enter last audit date.

• Last Audit Report SHA-256optional

  lastAuditReportSha256

  Enter last audit report sha-256.

• Next Audit Dueoptional

  nextAuditDueDate

  Enter next audit due.

• Open Audit Findingsoptional

  auditFindingsCount

  Enter open audit findings.

ScreenSWIFT Customer Security Programme·step 6

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

No manual inputs in this step.