
Cybersecurity & IT
Ethical Hacking: Reporting Findings That Get Fixed
A Practical Guide to Evidence, Risk, Remediation, and Clear Communication
by Todd Michael
Available nowA security finding is only useful when the people receiving it can understand what happened and decide what to do next. This practical guide helps ethical hacking students and working professionals turn authorized test results into clear, credible reports that support remediation.
Learn how to identify affected assets, select persuasive evidence, describe reproduction conditions, and explain impact without exaggeration. Develop recommendations that account for ownership, constraints, and verification. Worked examples show how to distinguish observation from inference, acknowledge uncertainty, and present the same issue to technical teams and managers at the right level of detail.
From first notes through final review and retesting, each chapter builds a repeatable reporting skill. Templates, annotated sample findings, and exercises help you practice writing reports that readers can verify, prioritize, and act on.
Designed for certification candidates and early-career practitioners, this book focuses on the communication work that turns testing into useful security improvements.
Contents
- 1. The Finding as a Path to Action
- 2. Scope, Authorization, and Reporting Boundaries
- 3. Identify the Affected Assets
- 4. Collect and Protect Useful Evidence
- 5. Write Reproduction Conditions
- 6. Separate Observation, Inference, and Uncertainty
- 7. Explain Impact Without Alarmism
- 8. Prioritize Findings in Context
- 9. Recommend Fixes That Can Be Owned
- 10. Build the Technical Finding
- 11. Write for Managers and Decision-Makers
- 12. Review, Deliver, and Discuss the Report
- 13. Track Remediation and Retest
- 14. Practice with Complete Sample Reports
- A Reusable Report Structure
- Sample Report One: Customer Portal Authorization
- Sample Report Two: Administrative Service Exposure
- Compare the Two Findings
- Practice: Draft Before Reading the Model
- From Practice to Delivery
- Other Books by Todd Michael
Read a sample: 1. The Finding as a Path to Action
A security test can reveal a genuine weakness and still leave an organization unsure what to do next. Perhaps the tester found that an ordinary account could view another user’s document. The report says “broken access control,” includes a screenshot, and assigns a high severity. The technical team opens the ticket and immediately has questions: Which application? Which account? What kind of document? Did the tester actually see someone else’s information, or only a page that suggested access might be possible? Does the proposed fix apply to the affected service?
Until those questions are answered, a finding may be accurate but difficult to act on. The team may spend its first meeting reconstructing the test instead of correcting the condition. A manager may see a serious label without understanding what decision is needed. The tester may be asked to repeat work that was already performed.
A useful finding is a path from an observed condition to an informed action. It identifies what was tested, shows enough evidence to support the claim, explains why the condition matters, and recommends a practical next step. It also marks the edge of the tester’s knowledge. The reader should be able to distinguish what happened during the assessment from what might happen under other circumstances.
This chapter establishes a reporting standard you can use throughout the book. The standard is not a rigid demand that every issue occupy the same number of pages. A simple configuration error may need only a concise record; a complex authorization failure may require several pieces of evidence and careful explanation. In both cases, the finding should make the next responsible action easier.
Technical labels are useful. They help readers recognize patterns, group similar issues, and connect a finding to established concepts. But a label alone does not tell a team where to work or what was established.
“Broken access control” could describe many different conditions. An unauthenticated visitor might reach an administrative page. A customer might view another customer’s invoice. A support employee might perform an action beyond the permissions intended for that role. Each situation calls for different evidence, has different prerequisites, and may require a different fix.
A finding turns a general concept into an engagement-specific account. It answers questions such as:
- Where is the condition? Identify the affected application, host, endpoint, feature, account type, or other asset precisely enough for the responsible team to locate it.
- What was observed? State the behavior the tester actually saw.
- How was it observed? Describe the relevant access, environment, inputs, and evidence.
- Why does it matter? Connect the condition to a plausible security consequence, with its limitations.
- What should happen next? Recommend a corrective action and describe how the result can be verified.
These questions serve different readers. An engineer may focus first on the endpoint and reproduction conditions. A manager may look for affected service, impact, priority, and ownership. A reviewer may check whether the evidence supports the claim. All three should be able to follow the same chain of reasoning.
A report is not an instruction to trust the tester’s confidence. It is a record that lets other people understand the basis for that confidence and decide what to do with it.
Most findings benefit from a predictable structure. The headings need not be identical in every organization, but the essential information should be easy to locate.
Title and summary. Give the issue a specific, neutral title. “Users can access another account’s invoice by changing the invoice identifier” tells the reader more than “Critical vulnerability.” The summary should describe the condition and its immediate significance without trying to include every test detail.
Affected assets. Name the system and the part of it where the behavior was observed. Include the environment when it matters: a staging application is not automatically evidence that production behaves the same way. Asset details are facts about the test target, not proof of who owns or operates it. If ownership is unknown, say so or leave the assignment for the organization to confirm.
Evidence and reproduction conditions. Evidence supports the observation; reproduction conditions explain how the observation was obtained. A response showing a test invoice is evidence. The fact that the tester used an authenticated customer account and substituted a known test invoice identifier is part of the reproduction context. Together, they help a reviewer evaluate and, where authorized, repeat the test.
Impact and uncertainty. Explain the consequence that follows from the observed condition. Then distinguish it from broader outcomes that are plausible but not demonstrated. If a test account accessed one other test account’s invoice, the report should not claim that every customer invoice was exposed. It can explain that similar unauthorized access may be possible for other records if the same control is used, while recommending that the organization assess the scope.
Recommendation and verification. Describe the change that addresses the condition, not merely the desired outcome. “Fix access control” names a goal; “check on the server that the requesting account is authorized to access the requested invoice before returning it” points toward a control. Verification should test the behavior after the change, including both legitimate access and denial of unauthorized access.
A severity or priority can help organize work, but it does not replace these elements. A rating is a conclusion based on facts and assumptions. If those are missing, the label gives readers little basis…