GSLC · Question #411
Which of the following are the countermeasures against WEP cracking? Each correct answer represents a part of the solution. Choose all that apply.
The correct answer is A. Changing keys often. B. Using the longest key supported by hardware. D. Using a non-obvious key.. Effective WEP security countermeasures focus on key management and key strength, but SSID length is not a WEP-related countermeasure because the SSID is a network identifier independent of the WEP encryption mechanism.
Question
Which of the following are the countermeasures against WEP cracking? Each correct answer represents a part of the solution. Choose all that apply.
Options
- AChanging keys often.
- BUsing the longest key supported by hardware.
- CUsing a 16 bit SSID.
- DUsing a non-obvious key.
How the community answered
(49 responses)- A92% (45)
- C8% (4)
Why each option
Effective WEP security countermeasures focus on key management and key strength, but SSID length is not a WEP-related countermeasure because the SSID is a network identifier independent of the WEP encryption mechanism.
Changing WEP keys frequently limits the window of time an attacker has to capture enough initialization vectors (IVs) to statistically crack the key, since WEP's weakness is rooted in IV reuse and small IV space.
Using the longest key supported by hardware - typically 104-bit WEP instead of 40-bit - increases the key space and makes brute-force and statistical attacks significantly more difficult and time-consuming.
The SSID is a network name broadcast to identify the wireless network and is entirely separate from the WEP encryption key and IV mechanism, so changing its bit length has no effect on WEP cracking resistance.
Using a non-obvious, complex key reduces the effectiveness of dictionary-based and brute-force attacks against the shared WEP key, since weak or default keys are trivially guessed.
Concept tested: WEP vulnerability countermeasures and key management
Source: https://csrc.nist.gov/publications/detail/sp/800-97/final
Topics
Community Discussion
No community discussion yet for this question.