A financial organization is implementing a centralized enterprise API gateway to handle high-value B2B fund transfers with external corporate partners. The security team must ensure that once a corporate partner transmits a payment request, they cannot plausibly claim the request was forged or sent by an unauthorized party. Which of the following technical controls directly support non-repudiation for these payment requests? (Select TWO.)
- Requiring senders to digitally sign payment payloads using their organization's private cryptographic keyAnswer
- Validating sender digital certificates against a mutually trusted Public Key Infrastructure (PKI) Certificate AuthorityAnswer
- CComputing a SHA-256 message digest of the incoming transaction payload to verify data integrity upon arrival
- DEncrypting API requests with AES-256 GCM using a pre-shared key shared between the gateway and the partner
Answer
Non-repudiation for payment transactions is directly supported by requiring senders to digitally sign payment payloads using their asymmetric private key and by validating sender certificates against a trusted Public Key Infrastructure (PKI) Certificate Authority.
Non-repudiation ensures that a sender cannot dispute the authenticity of a message or transaction they originated. This security goal requires combining proof of origin with proof of integrity. Digitally signing payloads with an asymmetric private key guarantees that only the key owner could have signed the request. Validating the sender's identity certificate via a trusted Public Key Infrastructure (PKI) binds that key to a verified identity, completing the non-repudiation chain.
Step-by-Step Solution
Key Concept
Non-Repudiation and Asymmetric Cryptography