> For the complete documentation index, see [llms.txt](https://help.aikido.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.aikido.dev/docs/docs-ja/pentesuto/coverage-and-findings.md).

# カバレッジと検出結果

Aikido が何をテストするのか、また一般的な種類の指摘結果の読み方を理解する。

このセクションでは、対象範囲とより詳細な例を確認できます。

<table data-view="cards"><thead><tr><th>ガイド</th><th>対象範囲</th><th data-hidden data-card-target data-type="content-ref">対象</th></tr></thead><tbody><tr><td><strong>Aikido Pentestでどのような問題を見つけられますか？</strong></td><td>OWASP、ロジック上の欠陥、ハードニングの不備、インフラ全般をカバーします。</td><td><a href="/docs/docs-ja/pentesuto/coverage-and-findings/what-issues-can-aikido-pentest-find.md">Aikido Pentestでどのような問題を見つけられますか？</a></td></tr><tr><td><strong>ペンテストのカバレッジを理解する</strong></td><td>それが意味することと、意味しないこと。</td><td><a href="/docs/docs-ja/pentesuto/coverage-and-findings/understanding-pentest-coverage.md">ペンテストのカバレッジを理解する</a></td></tr><tr><td><strong>脅威モデル</strong></td><td>偵察結果と攻撃計画の読み方。</td><td><a href="/docs/docs-ja/pentesuto/coverage-and-findings/threat-model.md">脅威モデル</a></td></tr><tr><td><strong>Human in the Loop</strong></td><td>エスカレーションを使うタイミングと、フォローアップ実行で何を期待するか。</td><td><a href="/docs/docs-ja/pentesuto/coverage-and-findings/human-in-the-loop.md">Human in the Loop</a></td></tr><tr><td><strong>ペンテストレポート</strong></td><td>適切なレポート種類の選び方とエクスポート方法。</td><td><a href="/docs/docs-ja/pentesuto/coverage-and-findings/pentest-reports.md">ペンテストレポート</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://help.aikido.dev/docs/docs-ja/pentesuto/coverage-and-findings.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.