SWIFT PKI certificates are critical for securing communications and require a formal request process to SWIFT for issuance or renewal. Let’s evaluate each option:
•Option A: Using both online and offline methods
This is correct. SWIFT provides multiple channels for submitting PKI certificate requests to accommodate different customer needs and security requirements. The online method involves submitting requests through the SWIFT Alliance Web Platform or SWIFT’s customer portal, where users can generate and upload certificate signing requests (CSRs). The offline method involves physical submission, such as sending a signed request via secure mail or courier, often used for initial setups or high-security environments. SWIFT documentation confirms both methods are supported, aligning with CSCF Control "1.3 Cryptographic Failover" for secure certificate management.
•Option B: Using an online method
This is incorrect as a standalone answer. While the online method is available and widely used, it is not the only method. Excluding the offline option does not reflect SWIFT’s flexible process.
•Option C: Using an offline method
This is incorrect as a standalone answer. The offline method is an option, but it is not the only method. SWIFT supports both approaches depending on the customer’s infrastructure and security policies.
•Option D: None of the above
This is incorrect. Both online and offline methods are valid, making this option invalid.
Summary of Correct Answer:
PKI certificate requests can be submitted to SWIFT using both online and offline methods (A), providing flexibility and security.
References to SWIFT Customer Security Programme Documents:
•SWIFT Customer Security Controls Framework (CSCF) v2024: Control 1.3 supports secure certificate request processes.
•SWIFT PKI Management Guide: Details online and offline submission methods for certificate requests.
•SWIFT Alliance Documentation: Confirms dual submission channels for PKI certificates.
