A municipal enterprise-style assessment produced a lucky path to Domain Admin early. What else should the engagement still demonstrate?
Select an answer to reveal the explanation.
Short Explanation
Getting DA on Tuesday is not a free pass to skip the rest of the map. A solid engagement still shows coverage across the process and reports residual risk honestly.
Full Explanation
A municipal enterprise-style assessment that luckily reaches Domain Admin early should still demonstrate broad methodology coverage from recon through reporting—not only a single privileged path. Clients pay for systematic assurance, not a speedrun screenshot.
Methodology does not end the moment Domain Admin is reached. One DA screenshot is not full commercial delivery. Further testing is not unethical after high privilege; it should continue within RoE to map attack surface and hardening gaps.
Exam caveat: after DA, prefer low-impact enumeration and agreed objectives over noisy persistence sprawl.
Operational check: continue scoped domain hygiene review, document alternate paths and missing detections, and deliver a full-phase report for the city—not only the lucky path. In municipal operations, record the rationale in the engagement notes so future assessors know which control was chosen and which failure modes the rejected options would create for city services. Re-validate after the next maintenance window that the same finding class still applies under the estate's current patch and configuration baseline. In municipal operations, record the rationale in the engagement notes so future assessors know which control was chosen and which failure modes the rejected options would create for city services.