> 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/ja/hacking-tools/exploitation/bug-bounty-and-research-resources.md).

# バグバウンティおよび調査リソース

公開された書き起こし、脆弱性データベース、エクスプロイト参照、手法メモ、ペイロード調査のためのバグバウンティおよびセキュリティ調査リソース。

脆弱性調査、公開レポート、エクスプロイトの参照、手法の着想にはこれらのリソースを活用してください。技術的な証明手順は、該当する脆弱性またはレポートのページにまとめてください。

## リソース

<table data-card-size="large" data-column-title-hidden data-view="cards" data-full-width="false" data-search="false"><thead><tr><th>名前</th><th>説明</th><th>公式リンク</th><th data-hidden data-card-cover data-type="image">カバー画像</th></tr></thead><tbody><tr><td><strong>Pentester Land</strong></td><td>公開バグバウンティのレポートとセキュリティ研究の参考資料。</td><td><a href="https://pentester.land/">https://pentester.land/</a></td><td><a href="https://2001299964-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-3a8f02fe6c7236f00cde1130ced9b2d2d98c7f39%2Fimage.png?alt=media">image.png</a></td></tr><tr><td><strong>Rapid7 脆弱性データベース</strong></td><td>CVE、脆弱性の詳細、エクスプロイトの参照、Metasploit モジュールの背景情報を検索できます。</td><td><a href="https://www.rapid7.com/db/">https://www.rapid7.com/db/</a></td><td><a href="https://2001299964-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-4c9c5842623d6e3642e160cf1c82d9c258833ba8%2FScreenshot%202026-07-20%20155200.png?alt=media">Screenshot 2026-07-20 155200.png</a></td></tr><tr><td><strong>Exploit-DB</strong></td><td>公開エクスプロイト、PoCコード、論文、Google Hacking Database の参照を閲覧できます。</td><td><a href="https://www.exploit-db.com/">https://www.exploit-db.com/</a></td><td><a href="https://2001299964-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-b3b1beb4fe63cbea67b9cf15fe8665cace9d40a4%2FScreenshot%202026-07-20%20155602.png?alt=media">Screenshot 2026-07-20 155602.png</a></td></tr><tr><td><strong>HackTricks</strong></td><td>さまざまな技術や環境にわたるプレイブックや攻撃経路を活用してください。</td><td><a href="https://book.hacktricks.xyz/">https://book.hacktricks.xyz/</a></td><td><a href="https://2001299964-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-238315153dff778af12e75f13052d2add28bfd63%2FScreenshot%202026-07-20%20155648.png?alt=media">Screenshot 2026-07-20 155648.png</a></td></tr></tbody></table>


---

# 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/ja/hacking-tools/exploitation/bug-bounty-and-research-resources.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.
