350-901 · Question #4
Which two countermeasures help reduce the risk of playback attacks? (Choose two.)
The correct answer is B. Implement message authentication (HMAC). E. Use short-lived access tokens. To mitigate playback attacks, implementing message authentication (HMAC) can verify message freshness and integrity, while using short-lived access tokens limits the window of opportunity for replayed credentials.
Question
Options
- AStore data in a NoSQL database.
- BImplement message authentication (HMAC).
- CEnable end-to-end encryption.
- DRemove stack traces from errors.
- EUse short-lived access tokens.
How the community answered
(29 responses)- B93% (27)
- C3% (1)
- D3% (1)
Why each option
To mitigate playback attacks, implementing message authentication (HMAC) can verify message freshness and integrity, while using short-lived access tokens limits the window of opportunity for replayed credentials.
Storing data in a NoSQL database relates to data persistence and architecture, which does not directly prevent or mitigate playback attacks on network communication.
Implementing message authentication codes (HMACs) allows for the inclusion of nonces, timestamps, or sequence numbers within messages, which can be used by the receiver to detect and reject replayed messages, ensuring message freshness.
End-to-end encryption protects the confidentiality of messages but does not inherently prevent an attacker from replaying an encrypted message if other mechanisms like nonces or timestamps are not also employed.
Removing stack traces from errors is a security measure to prevent information disclosure, but it does not address the issue of an attacker re-transmitting captured valid messages.
Using short-lived access tokens significantly reduces the effectiveness of a playback attack because intercepted tokens quickly expire, rendering them useless for unauthorized re-transmission.
Concept tested: Playback attack countermeasures
Source: https://learn.microsoft.com/en-us/azure/architecture/patterns/security-anti-patterns#replay-attack
Topics
Community Discussion
No community discussion yet for this question.