SWIFT Architecture Discovery & Control Scoping

ScreenSWIFT CSP › Scope·step 1

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

• Assessment Name (required)

  scopeName

  Search and open an existing assessment, or enter a name and choose Use to continue this intake.

• Primary SWIFT BIC Code (required)

  entityId

  Select the primary 8 or 11-character SWIFT BIC from the directory.

• Legal Entity Name (required)

  legalEntityName

  Full registered legal name of the assessed institution.e.g. Deutsche Bank AG

• SWIFT Registration Status (required)

  registrationStatus

  Your registration category with SWIFT (direct user, supervised, or service bureau).

• Is this a Group Assessment covering multiple BICs?optional

  isGroupAssessment

  Check if this assessment covers multiple BICs under a single legal entity.

• Subsidiary BICs in Scopeoptional

  relatedBics

  Add each subsidiary BIC covered by this assessment. Each entry must be a valid 8 or 11-character SWIFT BIC (uppercase letters and digits).

ScreenSWIFT CSP › Scope·step 2

Complete the Architecture & Policy Scope fields. Each value is validated against the schema before the next step unlocks.

• Overall Architecture Type (required)

  archType

  Select the SWIFT architecture type that matches how your institution connects to SWIFT; the in-scope controls and requirements are resolved by the OPA policy server.

ScreenSWIFT CSP › Scope·step 3

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

• SWIFT Environments › Environment Type (required)

  environments.environmentType

  Identify whether this is a production, disaster-recovery or backup environment.

• Secure Zones › Zone Name (required)

  zones.zoneName

  Short unique zone name — components reference the zone by it.e.g. SWIFT-SECURE-VLAN10

• In-Scope Components › Component Name (required)

  components.componentName

  Use a unique component name referenced by connections and providers.

• SWIFT Environments › Environment Name (required)

  environments.environmentName

  Name it by tier and site — e.g. "Production - London". Components and providers reference this name.

• Secure Zones › Environment (required)

  zones.environmentName

  The declared environment this zone belongs to.

• In-Scope Components › Component Type (required)

  components.componentType

  Select the component's role in the SWIFT topology.

• Secure Zones › Demarcation (Firewalls/VLANs) (required)

  zones.demarcation

  Describe the firewalls, VLAN IDs and rules enforcing this zone.

• In-Scope Components › Environment Name (required)

  components.environmentName

  Enter the exact name of a declared SWIFT environment.

• In-Scope Components › Network / Security Zone (required)

  components.zone

  Name the network or security zone containing the component.

• In-Scope Components › Component Owner (required)

  components.ownerType

  Identify the party that owns or operates the component.

• In-Scope Components › Product / Platformoptional

  components.product

  Optional vendor and product or platform identifier.

• In-Scope Components › Runtime IP Addressoptional

  components.ipAddress

  Bind this component to its observed network address. Leave blank until the address is known.

• In-Scope Components › RMA Key Storage Typeoptional

  components.rmaStorageType

  Enter rma key storage type.

• In-Scope Components › Active RMA Keys Managedoptional

  components.rmaKeyCount

  Enter active rma keys managed.

• SWIFT Environments (required)

  environments

  Declare every production, disaster-recovery and backup environment in the assessment boundary.

• Secure Zonesoptional

  zones

  Declare every secure zone (VLAN / firewall segment) that isolates SWIFT components.

• In-Scope Componentsoptional

  components

  Inventory the systems inside the declared environments; architecture policy determines the minimum required component types.

• SWIFT Environments › Hosting Model (required)

  environments.hostingModel

  Select on-premise, co-location, public cloud, or managed service.

• SWIFT Environments › Site Country (required)

  environments.siteCountry

  Select the ISO 3166-1 alpha-2 country for this environment.

• SWIFT Environments › Smart Site Address (required)

  environments.siteAddress

  Search, review and confirm the operating address for this environment.

ScreenSWIFT CSP › Scope·step 4

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

• In-Scope Connections › Connection Name (required)

  connections.connectionName

  Use a unique name for this data or administration flow.

• In-Scope Connections › Source Component (required)

  connections.sourceComponent

  Enter the exact name of the declared source component.

• In-Scope Connections › Destination Component (required)

  connections.destinationComponent

  Enter the exact name of the declared destination component.

• In-Scope Connections › Traffic Direction (required)

  connections.direction

  Direction of traffic relative to the source and destination.

• In-Scope Connections › Protocol / Port (required)

  connections.protocol

  Protocol and port used by this connection.

• In-Scope Connections › Connection Protection (required)

  connections.protection

  Describe encryption, authentication and network controls protecting the flow.

• In-Scope Connections › Does this connection cross a trust boundary? (required)

  connections.crossesTrustBoundary

  Select Yes when the flow crosses zones, organizations or responsibility boundaries.

• In-Scope Connections › Connected Market Infrastructureoptional

  connections.marketInfrastructure

  Optional market infrastructure reached by this connection, such as TARGET2 or CHIPS.

• In-Scope Connections › Destination Portoptional

  connections.destinationPort

  The destination port used to match this declared flow to network traffic.

• In-Scope Connections › Expected Encryption Protocoloptional

  connections.encryption

  Select the expected protocol for runtime comparison, or Unknown when it is not established.

• Are there connections between in-scope components or adjoining systems? (required)

  hasAdjoiningConnections

  Answer Yes to map each traffic path between declared components, including flows that cross a trust boundary. Answer No only if no such connections exist.

• In-Scope Connectionsoptional

  connections

  Map traffic paths between declared components, including trust-boundary crossings.

ScreenSWIFT CSP › Scope·step 5

Complete the Third-Party Risk fields. Each value is validated against the schema before the next step unlocks.

• Third-Party Providers › Provider Legal Name (required)

  providers.providerName

  Full legal name of the service provider.

• Third-Party Providers › Provider Type (required)

  providers.providerType

  Select the provider's role in the SWIFT service chain.

• Third-Party Providers › Services Provided (required)

  providers.services

  Describe the in-scope services delivered by this provider.

• Third-Party Providers › Supported Environments (required)

  providers.environmentNames

  Add the exact names of all environments supported by this provider.

• Third-Party Providers › Supported Componentsoptional

  providers.componentNames

  Add the exact names of any components supported by this provider.

• Third-Party Providers › Control Responsibility (required)

  providers.responsibility

  Record whether the user, provider or both share control responsibility.

• Third-Party Providers › Provider KYC-SA BIC Codeoptional

  providers.providerKycSaBic

  Enter provider kyc-sa bic code. An example value is "SWFTUS33XXX".

• Third-Party Providers › Provider Attestation Postureoptional

  providers.attestationStatus

  Enter provider attestation posture.

• Third-Party Providers › Provider Attestation Yearoptional

  providers.attestationYear

  Enter provider attestation year.

• Are you using a Third-Party Service Provider (TPSP)? (required)

  usesTpsp

  Toggle if any Third-Party Service Provider operates in scope.

• Third-Party Providersoptional

  providers

  Declare providers that host, operate, connect or monitor any in-scope environment or component.

ScreenSWIFT CSP › Scope·step 6

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

• I confirm the accuracy of this A-Z SWIFT ecosystem scopeoptional

  reviewSignOff

  I confirm this is an accurate end-to-end scope statement of my SWIFT ecosystem.