> For the complete documentation index, see [llms.txt](https://hacking-notes.jord4n.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hacking-notes.jord4n.pro/useful-resources/reporting.md). # Reporting Reporting resources for LaTeX pentest reports, professional deliverables, evidence structure, and example write-up material. Reporting resources for turning technical work into clear deliverables: structure, evidence flow, LaTeX report material, and example report content. ## Reporting Resources


	Professional Reports (LaTeX)	Professional penetration testing report resources and LaTeX templates for clean offensive security writeups.	Professional Reports (LaTeX)
	Report 1 - Presidential LaTeX Write-up	Presidential VulnHub LaTeX report notes for producing professional penetration testing writeups, structuring findings, and documenting exploitation evidence.	Report 1 - Presidential LaTeX Write-up

### Workflow 1. Group evidence by finding, impact, reproduction, and remediation. 2. Keep commands, screenshots, timestamps, and affected assets close to the finding they support. 3. Use templates for consistency, then adjust wording for the target audience. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://hacking-notes.jord4n.pro/useful-resources/reporting.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.

:file-lines:

Professional Reports (LaTeX)

:file-lines:

Report 1 - Presidential LaTeX Write-up