> For the complete documentation index, see [llms.txt](https://blog.s1rn3tz.ovh/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://blog.s1rn3tz.ovh/pentest-et-bug-bounty/bug-bounty-methodology.md).

# Bug Bounty Methodology

Mindmap pour ne rien oublier:

1. Trouver des [sous-domaines](/osint-recon/domaines-et-sous-domaines.md).
2. Vérifier les enregistrements [CNAME](/pentest-web/one-liners.md#enregistrements-cname) de ces sous-domaines (possibilité de [subdomain takeover](/pentest-web/prise-de-controle-de-sous-domaine.md) ?) et rassembler des urls.
3. Utiliser [masscan](/osint-recon/scan-de-ports-web.md#masscan), [nmap](/osint-recon/scan-de-ports-web.md#nmap), Shodan... pour faire un [scan de ports](/osint-recon/scan-de-ports-web.md) de la cible.
4. Tenter de retrouver des informations sensibles sur la cible à l'aide de dorks [Github](/osint-recon/manuel-dorks.md#github-dorks), [Google](/osint-recon/manuel-dorks.md#google-bing-yahoo-dorks), [Shodan](/osint-recon/manuel-dorks.md#reconnaissance-et-recherche-de-leaks-avec-shodan-et-github)...

Sur les applications web:

1.  Tester les [CORS](/pentest-web/sop-bypass/cors.md) (Cross-origin ressource sharing)
2. Tester les injections de header dans les emails des [fonctions de remplacement de mot de passe](/pentest-web/mot-de-passe-oublie.md).
3. Tester les serveurs SMTP et les [HOST header injection](/pentest-web/injections.md#host-header)
4. Tester les iframe (pour le [clickjacking](/pentest-web/clickjacking.md))
5. Tester les [contrôles d'accès incorrects](/pentest-web/idor.md) et tenter de modifier les paramètres
6. Vérifier l'historique de Burp Suite et récolter les endpoints
7. Tenter de trouver d'autres endpoints
8. Chercher des failles [CSRF](/pentest-web/csrf.md)
9. Chercher des failles SSRF ([upload features](/pentest-web/upload-features.md#ssrf), [open redirect](/pentest-web/open-redirect.md#ssrf-via-open-redirect), [XXE](/pentest-web/injections/xxe.md))
10. Chercher des failles [SSTI](/pentest-web/injections/ssti.md) et [XSS](/pentest-web/injections/xss.md) ([upload features](/pentest-web/upload-features.md#xss), [broken authent](/pentest-web/broken-authentication-register.md#xss)...)
11. Chercher des failles [XXE](/pentest-web/injections/xxe.md)
12. Vérifier la robustesse des fonctions [OAuth](/pentest-web/oauth.md), [Tokens JSON](/pentest-web/json-web-token.md) et [autres](/pentest-web/insecure-deserialization.md)
13. Tester les injections unicode dans les paramètres email
14. Tester le rate limit des fonctions de [mot de passe oubliés](/pentest-web/mot-de-passe-oublie.md)
15. Tester les différentes méthodes de la section Bug Bounty Tips sur les fonctions de[ mot de passe oublié](/pentest-web/mot-de-passe-oublie.md)
16. [Bruteforce](/pentest-web/brute-force-fuzzing.md) des repertoires
17. Tester les [HTTP resquest smuggling](/pentest-web/http-smuggling.md)
18. Chercher des failles [open redirect](/pentest-web/open-redirect.md)
19. Essayer de [bypass](/pentest-web/bypass.md) les accès restreints
20. Chercher des [insecure deserializtion](/pentest-web/insecure-deserialization.md)
21. Rédaction d'un [rapport](/pentest-et-bug-bounty/bug-bounty-methodology/ecrire-un-bon-rapport.md) pour chaque faille trouvée


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://blog.s1rn3tz.ovh/pentest-et-bug-bounty/bug-bounty-methodology.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.