> 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/pentests/configure-a-pentest/scope-of-assessment.md). # Scope of Assessment ## What is Scope Scope defines the exact parts of your application or infrastructure that a pentest is allowed to test. Defining your scope clearly is one of the most important steps before running a pentest. * **Safety**: prevents testing systems that are not prepared for scanning * **Accuracy**: keeps agents focused on the right domains, APIs, or apps * **Compliance**: provides proof of what was tested and what was excluded * **Consistency**: allows retests to follow the same boundaries every time {% hint style="warning" %} Run assessments on a testing environment that does not contain real customer data. [Why use a testing environment?](/pentests/prepare-a-pentest/why-use-a-testing-environment.md) {% endhint %} Only the targets listed in the scope are scanned. Anything not included is ignored and will not be tested. ## What to include in the Scope A scope can contain one or more of the following: * Primary domain such as app.example.com * Subdomains or environments like staging.example.com or api.example.com * Connected systems that belong to the same application Each target must be owned or controlled by your organization. ### Domain ownership verification Before a domain can be tested, ownership must be verified. This step ensures that Aikido only tests systems you control. Verification must be completed for every domain included in the scope. --- # 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/pentests/configure-a-pentest/scope-of-assessment.md?ask=&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.