A student proposes RF jamming to force municipal clients onto a lab rogue AP. What is the correct OSWP-aligned response?
Select an answer to reveal the explanation.
Short Explanation
Jamming is not a clever deauth cousin—it is yelling into the radio until everyone falls over. That is usually illegal and never the OSWP lesson. Force association with authorization and brains, not a noise bomb.
Full Explanation
Proposing RF jamming to force municipal clients onto a lab rogue AP must be rejected: intentional RF denial is typically illegal, outside professional rules of engagement, and not an OSWP technique class to practice. Authorized assessment culture focuses on recon, crypto weakness analysis, WPS concepts, and carefully controlled rogue or portal scenarios—not spectrum denial against city users. Matching the rogue SSID to production does not legalize jamming. Jamming does not encrypt client traffic and is not preferred over captive portals as a technique class. Regulatory constraints are not suspended on 6 GHz merely by band choice. Exam caveat: teach refusal skills—candidates must recognize denied techniques even when they appear efficient for association forcing in a timed lab mindset. Operational check: if a student or junior assessor suggests jamming in a civic engagement, cite RoE and applicable law, document the refusal, and select authorized alternatives such as waiting for natural reconnects when deauthentication is also banned. For municipal and campus engagements, keep the finding language tied to authorized scope, name the building or SSID class affected, and state the residual risk to residents or staff if the rejected option had been chosen. Re-validate after the next change window that the selected control still matches inventory, monitoring, and RoE abort criteria used by the city wireless program.