Which of the following authentication methods prevents authentication replay?
Click on the arrows to vote for the correct answer
A. B. C. D.B.
A challenge/response mechanism prevents replay attacks by sending a different random challenge in each authentication event.
The response is linked to that challenge.
Therefore, capturing the authentication handshake and replaying it through the network will not work.
Using hashes by itself will not prevent a replay.
A WEP key will not prevent sniffing (it just takes a few more minutes to break the WEP key if the attacker does not already have it) and therefore will not be able to prevent recording and replaying an authentication handshake.
Out of the four authentication methods given, the method that prevents authentication replay is the Challenge/Response mechanism, so option B is the correct answer.
Here is an explanation of each option and why it does or doesn't prevent authentication replay:
A. Password hash implementation: Password hash implementation is a method of storing passwords in a hashed form in a database. When a user enters their password, the system hashes the password and compares it to the hashed value in the database. While password hash implementation can provide secure authentication, it does not prevent authentication replay. If an attacker intercepts the hashed password, they can use it to authenticate themselves to the system.
B. Challenge/response mechanism: The challenge/response mechanism is an authentication method where the system challenges the user with a random value, and the user responds with a computed value based on a secret key and the random value. The system verifies the response, and if it matches the expected value, the user is authenticated. This method prevents authentication replay because the challenge is unique each time, making it difficult for an attacker to intercept and reuse the response.
C. Wired Equivalent Privacy (WEP) encryption usage: WEP encryption is an outdated encryption standard used to secure wireless networks. It has been widely demonstrated to be vulnerable to attacks and is not considered a secure encryption method. While WEP encryption can provide secure authentication, it does not prevent authentication replay.
D. HTTP Basic Authentication: HTTP Basic Authentication is a simple authentication method that uses a username and password to authenticate the user. While it can be secure when used over HTTPS, it does not prevent authentication replay. If an attacker intercepts the username and password, they can use them to authenticate themselves to the system.
In summary, the only authentication method out of the given options that prevents authentication replay is the Challenge/Response mechanism.