Before investing GPU time, an assessor reviews a municipal capture in Wireshark to validate handshake quality. What should that QA step confirm?
Select an answer to reveal the explanation.
Short Explanation
Wireshark QA is checking you filmed the whole handshake scene with the right AP in frame—not a teaser trailer of beacons only. Confirm EAPOL completeness and BSSID before lighting up the GPU. Bad captures waste good wordlists.
Full Explanation
Offline cracking time is expensive relative to capture validation. Analysts should verify that the relevant EAPOL messages for a usable handshake are present and that frames map to the in-scope BSSID/ESSID before launching large candidate runs. An SSID string without handshake material is insufficient, and WEP myths or imagined cleartext PMKID passphrases are not substitutes. Capture QA is a core process control in WPA Personal recovery workflows.