Control Definition
Control Objective: Reduce the attack surface of SWIFT-related components by performing application hardening on the SWIFT-compatible messaging and communication interfaces, the SWIFT connector and related applications.
In-scope components:
- messaging interface
- communication interface
- GUI
- SWIFTNet Link
- SWIFT connector
Risk Drivers:
- excess attack surface
- exploitation of insecure application configuration
Implementation Guidance
Control Statement:
All messaging interfaces and communication interfaces products within the SWIFT secure zone are SWIFT compatible. Application security hardening is conducted and maintained on all in-scope components.
Control Context:
Application hardening applies the security concept of “least privilege” to an application by disabling features and services that are not required for normal operations. This process reduces the application capabilities, features, and protocols that may be used during an attack. The process also makes sure that potential default credentials
are changed.
In addition, SWIFT runs a Compatible Interface Programme to make sure interfaces are aligned with current practices and to give the customer additional assurance, guarantees, and better visibility regarding individual product capabilities. Upon the successful validation of the test results by the SWIFT Test Authority, the interface
is published in the Compatible Register. As per the SWIFT General Terms and Conditions, customers must use a SWIFT-compatible interface.
Implementation Guidelines:
The implementation guidelines are common methods to apply the relevant control. The guidelines are a helpful way to begin an assessment, but should never be considered as an "audit checklist" as each user’s implementation may vary. Therefore, in cases where some implementation guidelines elements are not present or partially covered, mitigations as well as particular environment specificities must be considered to properly assess the overall compliance adherence level (as per the suggested guidelines
or as per the alternatives).
- Make sure the messaging and communication interfaces are SWIFT-compatible (the list of compatible interfaces is published in the Compatible Register on www.swift.com).
- The SWIFT-compatible interface should meet all the security conformance requirements (mandatory and advisory) defined in the SWIFT Compatible Interface Programme.
- If some security conformance requirements are yet to be met, then the user should upgrade to a SWIFT-compatible interface by implementing at least the minimum mandatory security conformance requirements.
- The interface provider should be contacted in case of doubts regarding the availability of some security functionalities or their proper configuration and usage.
- • All in-scope applications are hardened considering one or more of the following:
- vendor security, operational or configuration guidance (such as the Alliance Security Guidance)
- a local or a regulator's standard security configuration, or controls set of the same rigour as the vendor guidance
- • At a minimum, the application hardening process should do the following:
- Change default existing passwords.
- Disable or remove unnecessary user accounts.
- Disable or restrict unnecessary components, adaptors, or connectivity methods.
- Securely configure the adapters, connectivity methods, or remote connections.
- Remove unnecessary packages.
- Adjust any default configurations known to be vulnerable.
- Deviations from the selected hardening configuration (that is, a set of rules) are documented along with the justification for the deviation.
Optional Enhancements:
Additional applications installed on the systems that host in-scope components and handle SWIFT-related data are also subject to considered application hardening as per the vendor recommendations.
