A company needs to obscure its traffic between remote offices without heavy certificate-based overhead. The team wants short-lived keys for each session so attackers cannot reuse captured data to access future sessions. Which arrangement achieves these goals?
Relying on one certificate to safeguard all data flows across the offices
Applying a hash function to data before sending it
A method that generates short-lived keys for every session
Generating a new session key for each connection limits the impact of intercepted traffic. This technique, often used in protocols supporting Perfect Forward Secrecy, ensures that even if one session key is compromised, past and future sessions remain secure. Reusing a static certificate or long-term key creates risk, and hashing alone doesn’t encrypt data — it only verifies integrity. Temporary session keys are ideal for protecting sensitive traffic between remote offices.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What is Perfect Forward Secrecy (PFS)?
Open an interactive chat with Bash
Why is hashing not sufficient for securing data traffic?
Open an interactive chat with Bash
What are the drawbacks of using static certificates or long-term keys?