GIAC Foundational Cybersecurity Technologies Practice Test

In a web application configured to validate a unique token value for each submitted user request, which threat is being mitigated?

1. Local file inclusion

2. Cross site request forgery

3. Drive-by downloads

4. Command injection

The correct answer is: Cross site request forgery

Validating a unique token value for each submitted user request is primarily aimed at mitigating the risk of Cross-Site Request Forgery (CSRF). CSRF is a type of attack where an unauthorized command is transmitted from a user that the web application trusts. In CSRF attacks, the attacker tricks the user's browser into sending a request that performs an action (like transferring funds or changing user settings) without the user's consent. By implementing a unique token for each request, the application ensures that every submitted request originates from the legitimate user. This token usually takes the form of a cryptographic value that is unique to the session and is validated with each request. If a request does not contain the correct token, or if the token does not match the user’s session, the server can reject the request, effectively thwarting potential CSRF attacks. This method is not as effective against other threats listed, such as local file inclusion, drive-by downloads, and command injection, which involves different vectors of attack not directly related to the authenticity of user requests on a website. The focus on validating a token mainly safeguards against CSRF, thus ensuring the integrity of user interactions with the application.