Research index
Reporting
18 May 2017
NobleIDark:/48914/w1/20260515/63BC6739DOI10.1002/9781119419358.ch10
The full text is at the publisher
You can read the abstract here, or open it at the publisher.
Abstract
This chapter offers guidance on how to figure out what to include in the report, add supporting documentation, and make sure the report is free of typos. The document may borrow heavily from one's initial interactions and interviews with the client. The pen testing report may be read by a wide range of individuals. Classification of the project and report should be discussed with a contact person at the beginning of the project in order to make sure that no classified information is given to an unauthorized person. The pen-tester should also discuss how classified information should be documented in the report. Screenshots that show error messages as well as other outputs are also useful because they can be presented to the client and technical or other personnel to illustrate specific issues they need to address.