When you discover a significant finding during testing, what should you do?

• A. Write it up immediately
• B. Wait until details are verified
• C. Archive it privately
• D. Share only with team

Answer: (A)

Prompt documentation of significant findings is essential because it creates an accurate, auditable trail and enables timely remediation. When you encounter a meaningful vulnerability or misconfiguration, capture all critical details while they’re fresh: what was found, where, potential impact, how to reproduce, evidence (screenshots, logs, files), affected assets, and an initial severity estimate. Then share with the appropriate stakeholders per the engagement rules so remediation can begin and the client or team can validate and prioritize. Waiting for verification risks information loss or changes in the environment that could alter impact. Archiving privately delays action, and sharing only with the team may not meet governance and reporting obligations. So the best approach is to write it up immediately and refine the report as more details are confirmed.