This question asks whether a Swift user can implement security controls (e.g., logging and monitoring) in systems not directly in scope of the CSCF. Let’s analyze this based on Swift CSP guidelines.

Step 1: Define CSCF Scope and Security Controls

TheSwift Customer Security Controls Framework (CSCF) v2024defines its scope as the Swift-related infrastructure, including messaging interfaces, communication interfaces, and operator systems (asdetailed in Question 4). Security controls likelogging and monitoringare mandated underControl Objective 6: Detect Anomalous Activity, specifically in controls likeControl 6.1: Security Event Logging.

Step 2: Analyze the Question

The question focuses on whether a Swift user can apply CSCF security controls (e.g., logging and monitoring) to systemsnot directly in scopeof the CSCF. Systems not in scope include back-office systems, general-purpose servers, or other infrastructure that does not directly process Swift messages or connect to the Swift network.

Step 3: Evaluate Swift CSP Guidance

The CSCF mandates that security controls must be applied to in-scope systems to ensure the security of the Swift environment. However, Swift also encourages adefense-in-depthapproach, as outlined in theSwift Customer Security Programme – Security Best Practices. This approach recommends extending security practices beyond the minimum scope to enhance overall security.

Control 6.1: Security Event Loggingrequires logging and monitoring for in-scope systems to detect anomalous activity. While this control is mandatory for in-scope systems, the CSCF does not prohibit applying similar controls to out-of-scope systems. In fact, theSwift CSP FAQ(available on swift.com) clarifies that users may implement additional security measures on out-of-scope systems to reduce risks to the Swift environment (e.g., monitoring back-office systems that interact with Swift middleware).

Implementing logging and monitoring on out-of-scope systems can help detect threats that might indirectly affect the Swift environment, such as lateral movement from a compromised back-office system to a Swift-related system.

Step 4: Conclusion and Verification

A Swift usercanchoose to implement security controls like logging and monitoring on systems not directly in scope of the CSCF. This is not mandatory but is considered a best practice under Swift’s defense-in-depth strategy. The CSCF does not restrict users from applying additional security measures beyond its defined scope, and such actions align with the broader goal of enhancing cybersecurity across the user’s environment.

References

Swift Customer Security Controls Framework (CSCF) v2024, Control 6.1: Security Event Logging.

Swift Customer Security Programme – Security Best Practices, Section: Defense-in-Depth.

Swift CSP FAQ, Section: Scope and Applicability of Security Controls.