A municipal PMO asks when reporting work should start during a multi-week penetration test. What timing is preferred?
Select an answer to reveal the explanation.
Short Explanation
Reporting is not a Sunday night essay after the adventure. Capture evidence and draft findings as you go so the story stays accurate. Last-day panic reports read like last-day panic reports.
Full Explanation
On a multi-week municipal penetration test, reporting work should start early: draft findings and evidence continuously rather than scrambling on the final day. Waiting until systems are wiped so screenshots stay minimal destroys the evidence trail the city needs. Dictating the entire report from memory in the last hour produces errors and weak remediation guidance. Outsourcing reporting to an uninvolved intern who never saw the testing notes breaks chain-of-custody for technical claims. Exam caveat: continuous drafting also supports mid-engagement critical notifications required by many civic RoEs. Operational check: after each meaningful finding, write the title, affected asset, evidence path, impact draft, and remediation sketch the same day; review the living draft with the engagement lead at weekly municipal check-ins. Document the rationale in the municipal engagement notes so later civic responders know which boundary was honored and which failure modes the rejected options would create for public services. Document the rationale in the municipal engagement notes so later civic responders know which boundary was honored and which failure modes the rejected options would create for public services.