> 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/fr/useful-resources/reporting.md).

# Reporting

Ressources de reporting pour les rapports pentest LaTeX, les livrables professionnels, la structure des preuves et du matériel d’exemple de rédaction.

Ressources de reporting pour transformer un travail technique en livrables clairs : structure, flux de preuves, matériel de rapport LaTeX et exemple de contenu de rapport.

## Ressources de reporting

<table data-view="cards" data-full-width="false" data-search="false"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h3><i class="fa-file-lines" style="color:$primary;">:file-lines:</i></h3></td><td><h4>Rapports professionnels (LaTeX)</h4></td><td>Ressources de rapports professionnels de test d’intrusion et modèles LaTeX pour des comptes rendus clairs de sécurité offensive.</td><td><a href="/fr/useful-resources/reporting/professional-reports-latex.md">Rapports professionnels (LaTeX)</a></td></tr><tr><td><h3><i class="fa-file-lines" style="color:$primary;">:file-lines:</i></h3></td><td><h4>Rapport 1 - Rédaction LaTeX présidentielle</h4></td><td>Notes de rapport LaTeX Presidential VulnHub pour produire des comptes rendus professionnels de test d’intrusion, structurer les constats et documenter les preuves d’exploitation.</td><td><a href="/fr/useful-resources/reporting/report-1-presidential-writeup-latex.md">Rapport 1 - Write-up LaTeX présidentiel</a></td></tr></tbody></table>

### Flux de travail

1. Regroupez les preuves par constat, impact, reproduction et remédiation.
2. Gardez les commandes, captures d’écran, horodatages et actifs affectés à proximité du constat qu’ils étayent.
3. Utilisez des modèles pour assurer la cohérence, puis adaptez le wording au public cible.


---

# 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/fr/useful-resources/reporting.md?ask=<question>&goal=<user_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.