An intern enables verbose frame injection during early recon 'to be thorough' on a live city WLAN. What guidance should the lead give?
Select an answer to reveal the explanation.
Short Explanation
Recon is mostly ears, not a bullhorn. Do not spray inject frames just to look busy—city users feel that. Stay quiet unless the RoE says noisier tricks are on the menu.
Full Explanation
During early recon on a live city WLAN, the lead should tell the intern to minimize injected traffic unless RoE explicitly allows noisier techniques. Thoroughness in discovery is achieved primarily by listening and careful tooling—not by verbose frame injection that can disrupt civic users and trip detection. Professional municipal recon defaults to quiet. Saying injection volume during recon is always required to populate accurate SSID lists fails by concept: passive beacon/probe listening populates inventories without injection. Claiming verbose injection is harmless because monitor mode cannot affect production clients fails by concept: injection transmits; monitor mode receive capability does not make transmits harmless. Replacing all passive listening with continuous injection to finish faster fails by concept: speed via noise violates low-impact recon norms and often RoE. Exam caveat: some later phases may allow directed probes or deauth—those are separate, written permissions, not recon defaults. Operational check: keep phase-one tooling receive-focused, disable unnecessary inject modules, review RoE language before any transmit, and log any authorized active frames with timestamps for the city SOC.