A candidate wants to run wifite to save time on an OffSec wireless exam culture question. What policy judgment is correct?
Select an answer to reveal the explanation.
Short Explanation
Wifite-class wizards are on the do-not-fly list for OSWP. Manual PEN-210 methods are the culture. Renaming binaries or letting a chatbot drive the wrapper still breaks the rule.
Full Explanation
On an OffSec wireless exam culture question, automated wireless attack wrappers such as wifite are prohibited; candidates should use manual PEN-210 methods instead. Wifite is not mandatory because manual aircrack-ng use is obsolete. Renaming an automator binary does not make it allowed. AI chatbots driving wifite while screenshots look manual still violates policy themes. Exam caveat: prohibition of wrappers is about demonstrating understanding under exam rules, not a claim that automation never exists in industry—civic engagements still require RoE and skill, but this item tests exam policy judgment. Operational check: prepare a manual toolchain checklist for practice labs, avoid wrapper dependencies in exam prep, and document manual steps clearly in the report as required. 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. Document the decision in the municipal engagement notes so the next assessor inherits both the technical rationale and the civic constraints that shaped it.