A software development team is building an automated third-party API webhook receiver to process incoming transaction status updates. The security specification requires that the receiver must verify both the data integrity and origin authenticity of each incoming payload using a shared secret key, while avoiding the processing overhead associated with public key cryptography. Which cryptographic mechanism should the team implement to meet these requirements?
- Hash-based Message Authentication Code (HMAC)Cevap
- BAsymmetric digital signatures using RSA with SHA-256
- CStandalone cryptographic hashing using SHA-256
- DKey derivation and stretching using PBKDF2
Cevap
The team should implement Hash-based Message Authentication Code (HMAC) to fulfill the integrity and origin authenticity requirements using a shared secret key.
Hash-based Message Authentication Code (HMAC) combines a symmetric shared secret key with a cryptographic hash function (such as SHA-256) to ensure both message integrity and sender origin authenticity. Because HMAC relies on symmetric shared secrets rather than public key infrastructure, it provides fast processing speeds suitable for high-throughput API webhooks.
Adım Adım Çözüm
Anahtar Kavram
Hash-based Message Authentication Code (HMAC)