Resposta de referência
I structure my reports in layers. The executive summary is the top layer—it's one page, no technical jargon, and focuses on business impact. Instead of saying 'SQL injection vulnerability in authentication mechanism,' I say something like 'We found a way to bypass your login system and access customer data without credentials.' I include a risk rating, potential business impact, and what the client should do first. Below that is the technical section with all the details—the vulnerability type, the exact location, reproduction steps, and remediation guidance. I include screenshots and proof-of-concept code when it helps clarify. I've also started using a dashboard-style visual for high-level metrics—number of findings by severity, which systems were tested, timeline. I find that executives respond to metrics. Recently, I presented findings to a client's board and focused on 'this vulnerability could expose 10,000 customer records in under an hour,' which resonated more than 'insecure direct object reference in the API endpoint.' The goal is always to make it easy for them to understand what's wrong and why it matters.