Replay Attack Explained: Customer-Banker Scenario

The described scenario involves an attacker positioned between a customer and a banker. This attacker intercepts information, modifies it, and then sends it on to the banker. The key actions are capturing the data and then retransmitting it, potentially with alterations.

Identifying the Correct Attack Type

This type of attack, where captured data is maliciously replayed or retransmitted, is known as a Replay Attack. The attacker essentially intercepts a communication, keeps a copy, and then later re-sends the communication to trick the recipient into believing it's a fresh, legitimate message. While the question mentions altering the information, retransmission of captured data is the core characteristic defining a replay attack, and modifications can be part of the malicious retransmission.

Evaluating Other Attack Options

Let's look at why the other options don't fit as well:

• Masquerade Attack: This involves the attacker pretending to be a different user or system. The scenario focuses on intercepting and retransmitting, not impersonation.
• Passive Attack: This type of attack only involves monitoring or eavesdropping on communications without changing or interfering with them. The described attacker actively alters and retransmits data.
• Denial of Service (DoS) Attack: The goal here is to make a system or resource unavailable to its intended users. The scenario describes data manipulation and retransmission, not disruption of service availability.

Therefore, based on the act of capturing and retransmitting information, the attack described is best classified as a Replay Attack.