> 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/~/revisions/KY3QqEqZPV6ifxqjwoLa/pentests/starting-an-assessment.md).
# Starting an Assessment
An assessment is the process of preparing and running a pentest on your application. During setup, you’ll define what should be tested, how deep the test should go, and under what conditions it should run.
The setup flow guides you through a few key steps to ensure the pentest runs safely and effectively. Each view in this process focuses on a specific goal:
* **Assessment Details:** Choose the type of pentest you want to run. White box tests use additional context (like repositories or configurations) for deeper coverage, while black box tests simulate an external attacker with no inside knowledge.
* **Scope:** [Define the entry points or domains that are in scope for the test.](/~/revisions/KY3QqEqZPV6ifxqjwoLa/pentests/scope-of-assessment.md) Ownership of each domain must be verified before the assessment can continue.
* **Authentication:** Add login credentials to simulate real-world scenarios for authenticated users and admins. This allows the test to explore protected areas of your app.
* **Attack Resources:** Provide extra context to help the test understand your environment. This can include linked repositories, API specifications, or notes about architecture and frameworks.
* **Confirm:** Review your setup and authorize the test.
{% hint style="danger" %}
**Pentests can run destructive actions**, so they should never be executed on production environments or systems containing customer data.
{% endhint %}
Once confirmed, the assessment runs within the defined scope and timeframe. After completion, you’ll receive a detailed report with findings, prioritized risks, and remediation guidance.
---
# 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://help.aikido.dev/~/revisions/KY3QqEqZPV6ifxqjwoLa/pentests/starting-an-assessment.md?ask=&goal=
```
`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.
