Swift Updated CSP-Assessor Exam Questions and Answers by zaynah

SWIFT Public Key Infrastructure (PKI) certificates are cryptographic credentials used to secure communications over the SWIFT network. Let’s evaluate each option:

•Option A: Asymmetric signing and encryption end to end

This is correct. SWIFT PKI certificates utilize asymmetric cryptography (public and private key pairs) for both signing and encryption. Signing ensures the authenticity and integrity of messages (e.g., verifying the sender), while encryption provides confidentiality end to end—from the sender’s environment to the receiver’s environment across the SWIFT network. This end-to-end security is achieved using PKI certificates managed by Hardware Security Modules (HSMs), as mandated by CSCF Control "1.3 Cryptographic Failover." SWIFT documentation confirms that PKI supports full message security throughout the transmission process.

•Option B: Asymmetric signing and encryption end to SWIFT only

This is incorrect. The security provided by PKI certificates extends beyond just the connection to SWIFT (e.g., to the SWIFT Secure IP Network). It covers the entire message journey, including the recipient’s environment, ensuring end-to-end protection rather than stopping at SWIFT’s boundary.

•Option C: Symmetric encryption only

This is incorrect. SWIFT PKI relies on asymmetric cryptography for key exchange and signing, not symmetric encryption alone. While symmetric encryption may be used internally (e.g., for session keys derived from asymmetric key exchange), the PKI certificates themselves are based on asymmetric algorithms (e.g., RSA), as outlined in SWIFT’s security guidelines.

•Option D: Asymmetric signing only

This is incorrect. PKI certificates are used for both asymmetric signing (for authenticity and integrity) and encryption (for confidentiality), not just signing. The dual purpose is essential for the secure transmission of SWIFT messages.

Summary of Correct Answer:

SWIFT PKI certificates are used for asymmetric signing and encryption end to end (A), ensuring comprehensive security.

References to SWIFT Customer Security Programme Documents:

•SWIFT Customer Security Controls Framework (CSCF) v2024: Control 1.3 specifies the use of PKI for end-to-end security.

•SWIFT Security Guidelines: Details PKI usage for asymmetric signing and encryption.

•SWIFT PKI Documentation: Confirms end-to-end cryptographic protection using PKI certificates.

========

The High-Level Test Plan (HLTP) guidelines, as part of the SWIFT CSP Independent Assessment Framework (IAF), provide instructions for assessing compliance with CSCF controls. The question asks whether selecting only one component (e.g., a SWIFT connector, middleware server, or back-office system) from the SWIFT secure zone is a representative sample for testing:

Step 1: Understand the SWIFT Secure Zone

The SWIFT secure zone is a segregated environment containing all SWIFT-related components critical to transaction processing, including connectors (e.g., SWIFT Alliance Gateway), middleware servers, and back-office systems (CSCF v2024, Control 1.1 –SWIFT Environment Protection). These components collectively form the "SWIFT footprint."

Step 2: HLTP Guidelines on Sampling

The HLTP requires assessors to test a "representative sample" of systems to verify compliance. However, the guidelines emphasize that the sample must cover the "full scope of the SWIFT environment" to ensure all critical components and their interactions are assessed (IAF, Section 3 – Assessment Methodology). Selecting only one component (e.g., just the connector) ignores the others (middleware and back-office), which may have different security configurations or risks.

Step 3: Application to the Scenario

In this case, the secure zone comprises three distinct components. Testing only one (e.g., the connector) would not provide a comprehensive view of the secure zone’s compliance with controls like 1.1 (environment protection), 2.1 (system hardening), or 4.2 (MFA). The HLTP expects a sample that reflects the diversity and interdependence of these components, not a single point.

Conclusion: No, selecting only one component is not a representative sample per HLTP guidelines, as it fails to address the full scope and complexity of the SWIFT secure zone.

Bridging servers facilitate data exchange between the back-office systems (e.g., Treasury Management Systems) and the SWIFT infrastructure (e.g., Alliance Access or Gateway). The CSCF scope includes components that handle SWIFT-related data or connectivity. Let’s evaluate:

•The "Swift Customer Security Controls Framework v2025" defines the secure zone and includes internal data transmission components. Bridging servers, as part of the data flow between back-office and SWIFT infrastructure, are considered in scope, particularly under Control "2.1 Internal Data Transmission Security" (mandatory) and related advisory controls (e.g., 2.3 System Hardening).

•The "CSP Architecture Type - Decision tree" includes such servers when they are part of the SWIFT environment, even if some controls are advisory depending on the architecture (e.g., A1 or A2).

•The "Assessment template for Advisory controls" applies to bridging servers for non-mandatory measures, while mandatory controls ensure secure data exchange.

Summary of Correct Answer:

Bridging servers are in scope of CSCF security controls, with some being advisory (TRUE).

References to SWIFT Customer Security Programme Documents:

•Swift Customer Security Controls Framework v2025: Control 2.1 includes bridging servers.

•CSP_controls_matrix_and_high_test_plan_2025: Lists applicable controls.

•Assessment template for Advisory controls: Applies to bridging servers.

========

This question examines whether an internal audit department can submit and approve a Swift user’s attestation on the KYC-SA Swift portal.

Step 1: Understand Attestation Process

TheIndependent Assessment FrameworkandCSCF v2024require attestations to be submitted by an independent party or authorized user representative, not the internal audit department, to ensure objectivity.

Step 2: Evaluate Each Option

A. Yes, providing this is agreed by the head of IT operations and the CISOInternal audit cannot submit or approve attestations, regardless of internal agreements, per theIndependent Assessment Framework.Conclusion: Incorrect.

B. No, this is never an optionTheCSCF v2024andSwift CSP Compliance Guidelinesprohibit internal audit from submitting or approving attestations, as they lack independence from the audited entity.Conclusion: Correct.

C. Yes, an internal auditor can submit the attestation for approval provided they have the appropriate credentials for swift.com. The CISO remains in charge of the approval of the attestationIncorrect. Internal auditors cannot submit or approve, even with credentials, due to independence requirements.Conclusion: Incorrect.

D. Yes, with approval from the Chief auditorIncorrect. Chief auditor approval does not override the independence requirement.Conclusion: Incorrect.

Step 3: Conclusion and Verification

The correct answer isB, as theCSCF v2024andIndependent Assessment Frameworkprohibit internal audit from submitting or approving attestations.

References

Swift Customer Security Controls Framework (CSCF) v2024, Section: Independent Assessment.

Swift Independent Assessment Framework, Section: Attestation Submission.

Swift CSP Compliance Guidelines, Section: Independence Requirements.