> 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/prepare-a-pentest.md).

# ペンテストの準備

アセスメントを開始する前に、環境を準備してください。

これらのガイドを使って、環境を準備し、プロジェクトを整理し、安全にアクセスを許可してください。

<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>ペンテストの準備</strong></td><td>完全な事前チェックリスト。</td><td><a href="/docs/docs-ja/pentesuto/prepare-a-pentest/preparing-for-a-pentest.md">ペンテストの準備</a></td></tr><tr><td><strong>テスト環境を使う理由</strong></td><td>一部のテストでデータが変更される理由と、それがテスト環境にあるべき理由。</td><td><a href="/docs/docs-ja/pentesuto/prepare-a-pentest/why-use-a-testing-environment.md">テスト環境を使う理由</a></td></tr><tr><td><strong>ペンテスト用のIPアドレス</strong></td><td>エージェントのトラフィックに対する許可リストの要件。</td><td><a href="/docs/docs-ja/pentesuto/prepare-a-pentest/ip-addresses-for-pentest.md">ペンテスト用のIPアドレス</a></td></tr><tr><td><strong>アセスメントをグループ化するためのプロジェクトの使用</strong></td><td>繰り返し行う、または関連するペンテストをどのように整理するか。</td><td><a href="/docs/docs-ja/pentesuto/prepare-a-pentest/using-projects-to-group-assessments.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/prepare-a-pentest.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.
