A municipal assessment's rules of engagement forbid credential-harvesting portals. What should the assessor do regarding those techniques on that engagement?
Select an answer to reveal the explanation.
Short Explanation
RoE is the referee, not a suggestion box. If harvesting portals are banned on this city job, you leave that play in the textbook—even if class taught the concept. Midnight, automation wrappers, or hiding loot in the report do not create a hall pass.
Full Explanation
If a municipal assessment's rules of engagement forbid credential-harvesting portals, the assessor must not use those techniques on that engagement even if they are taught conceptually elsewhere. RoE is engagement law. Quiet hours, automation swaps, or omitting loot from the report do not create compliance.
'Use them quietly after midnight because RoE pauses overnight' fails because RoE does not pause overnight to allow quiet forbidden portal harvests. 'Swap in wifiphisher automation so the ban applies only to manual portals' fails because wifiphisher automation does not exempt the technique from a portal ban. 'Harvest credentials but omit them from the report to stay compliant' fails because harvesting credentials but omitting them from the report is still a RoE violation.
Exam caveat: conceptual knowledge ≠ authorization to execute on a constrained engagement. Operational check: highlight forbidden techniques in the city kickoff checklist, choose alternate allowed tests (inventory, WPS-off verification, awareness tabletop), and have the lead assessor attest RoE compliance daily. Stop immediately if scope pressure appears. 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.