hostapd-mana appears in Enterprise and rogue-AP coursework for a municipal purple-team lab. What mana-class purpose should the assessor state—without diving into configs?
Select an answer to reveal the explanation.
Short Explanation
Mana-class tooling is about making a hungry rogue AP that answers what clients are looking for and sets up credential-capture style exercises—in a lab with a green light. It is not your PCI paperwork robot, a citywide WPA3 demolisher, or a chatbot for banned one-liners.
Full Explanation
hostapd-mana appears in Enterprise and rogue-AP coursework for a municipal purple-team lab as a mana-class capability: help operate rogue APs that attract clients and facilitate credential-capture classes under authorization. Assessors should state that purpose without diving into banned exam wrappers or config dumps. Civic framing keeps the technique inside written RoE.
'Generate PCI SAQs automatically from ceiling heat-map surveys' fails because mana-class tooling is not for generating PCI SAQs from ceiling heat-map surveys. 'Convert every WPA3-SAE network into open authentication citywide' fails because it does not convert every WPA3-SAE network into open authentication citywide by existing. 'Serve only as a banned exam chatbot that writes deauth one-liners' fails because it is not merely a banned exam chatbot that writes deauth one-liners.
Exam caveat: know which automations exam culture disallows even if coursework mentions the class. Operational check: if the city purple team uses mana-class capabilities, confine them to authorized lab SSIDs, prohibit production credential misuse, and document educational objectives. Prefer manual methodology literacy where exam rules ban wrappers. 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.