An intern wants to use wifiphisher-class automation on an OSWP-style exam-culture question for the city's practice drills. What policy stance should leadership reinforce?
Select an answer to reveal the explanation.
Short Explanation
OSWP culture is 'drive the tools yourself,' not 'launch the wizard and grab coffee.' Leave wifiphisher-class automators out of exam-minded practice and learn the manual method. Automation is not mandatory, not a substitute for RoE, and not the only way to talk about proof concepts.
Full Explanation
OffSec OSWP exam culture disallows certain automated wireless attack wrappers; leadership should reinforce learning manual methodology instead of depending on wifiphisher-class automation for city practice drills that mirror exam expectations. Municipal training can teach the technique class conceptually while forbidding banned wrappers in exam-prep environments. Authorization letters remain mandatory regardless of tooling.
'Banned automators are required for every municipal finding to be valid' fails because banned automators are not required for every municipal finding to be valid. 'Wifiphisher-class tools replace the need for authorization letters' fails because wifiphisher-class tools do not replace the need for authorization letters. 'Automation wrappers are the only accepted way to document proof.txt concepts' fails because automation wrappers are not the only accepted way to document proof.txt concepts.
Exam caveat: course mentions of a tool class ≠ permission to use banned wrappers in exam conditions. Operational check: publish an allowed-tool list for civic OSWP-style drills, confiscate or uninstall banned wrappers from lab laptops, and grade manual process evidence. Align practice RoE with exam culture expectations. In municipal wireless operations, record the rationale in the engagement notes so future assessors know which control or technique class was chosen and which failure modes the rejected options would create for city services.