The CSCF applies to all SWIFT users and components that handle SWIFT-related data or connectivity, including customer connectors and interfaces. The scope is defined by the "Swift Customer Security Controls Framework v2025" and the "CSP Architecture Type - Decision tree." Let’s evaluate the scenario and options:

•The application uses the SWIFT API for reporting and gpi basic tracker calls (e.g., tracking payment statuses via the SWIFT gpi Tracker) through a tailored account that does not allow business transaction management (e.g., creating or sending MT messages like MT103). This limits its functionality to read-only or monitoring activities.

•CSCF Scope: The CSCF applies to components that process or manage SWIFT business transactions (e.g., payment messages) or provide connectivity to the SWIFT network. The "CSP Architecture Type - Decision tree" classifies components into architecture types (A1-A4), with customer connectors and interfaces in scope if they handle transactional data or enable SWIFT connectivity. Reporting and tracking via APIs, without transaction management, do not constitute business transaction processing.

•Option A: Yes, it is in scope and considered a customer connector because it reads business transaction data

This is incorrect. While the application reads transaction data (e.g., via gpi Tracker), the CSCF scope is primarily focused on components that manage or transmit business transactions (e.g., creating or sending messages). Reading data for reporting purposes does not classify it as a customer connector requiring full CSCF compliance unless it also handles transactional flows. The "Swift_CSP_Assessment_Report_Template" focuses on transactional interfaces.

•Option B: No, it can be descoped because there is no business transaction management being performed

This is correct. Since the application does not manage business transactions (e.g., it cannot initiate or modify payments), it falls outside the primary scope of the CSCF. The "Independent Assessment Framework" allows for descoping of components that do not process transactional data, provided they are isolated from the SWIFT secure zone. This aligns with the "CSP Architecture Type - Decision tree," which excludes non-transactional reporting tools from mandatory assessment.

•Option C: No, it is not in scope because the API connection method is not in scope of the CSP

This is incorrect. The SWIFT API connection method is within the CSP scope if it interacts with SWIFT services (e.g., gpi Tracker), but the key factor is the lack of transaction management, not the API itself.

•Option D: Yes, it is in scope because the API connection method is less secure than SWIFT interfaces

This is incorrect. Security of the connection method (e.g., API vs. traditional interfaces) does not determine CSCF scope. The scope is based on functionality (transaction management), and the statement’s premise about security is not a valid criterion per CSCF guidelines.

Summary of Correct Answer:

The application is not in scope of the CSCF and can be descoped because it does not perform business transaction management (B).

References to SWIFT Customer Security Programme Documents:

•Swift Customer Security Controls Framework v2025: Defines scope based on transaction management.

•CSP Architecture Type - Decision tree: Guides descoping of non-transactional components.

•Independent Assessment Framework: Allows descoping of reporting-only applications.

========