A new assessor opens bettercap and feels overwhelmed by the module list on a municipal engagement. What is the professional approach?
Select an answer to reveal the explanation.
Short Explanation
Bettercap is a toolbox, not a slot machine. Pick the module that answers the question you came to ask—survey, watch, capture—then stop. Random module spam on a city network is unprofessional and risky.
Full Explanation
When overwhelmed by bettercap’s module list on a municipal engagement, the professional approach is to select modules purposefully against a clear recon goal rather than enabling features at random. Tool breadth is not a substitute for methodology: define the question (inventory, portal detection, specific MITM test), map one or two modules to that question, and keep everything else off. Civic assessments reward intentionality. Enabling every wireless-related module at once fails by concept: shotgun enablement increases noise, risk, and confusion without guaranteeing coverage quality. Treating module quantity as a substitute for written scope and RoE review fails by concept: more modules do not create authorization. Running modules at random until an alert appears fails by concept: undocumented experimentation is poor evidence practice and may violate RoE. Exam caveat: if bettercap is not on the approved municipal tool list, do not use it—fall back to the aircrack-ng suite and analyzers the playbook names. Operational check: write the recon goal in one sentence, pick the minimum modules that answer it, verify RoE allows those actions, run them, then disable modules and archive logs with the engagement notes.