> 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/high-risk-recommended-and-deeper-coverage.md).

# What the Coverage Levels Mean

What high risk only, recommended coverage, and deeper coverage change on a Rightsized Pentest.

On a Rightsized Pentest, the coverage slider sets how much of your application Aikido tests. Aikido shows the credit total before you start.

<div data-with-frame="true"><figure><img src="https://3149773201-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyKbzcQGrx7UtrG0nPZZ7%2Fuploads%2Fgit-blob-f14bd55dd068cfe98cfd0c571f639826e19cc714%2Frightsized-coverage-selection.png?alt=media" alt="Choose Your Coverage dialog with the coverage slider and a credit estimate broken down by repository"><figcaption><p>Move the slider to change the coverage level. The credit total updates before you confirm.</p></figcaption></figure></div>

## How it works

Use the slider to decide how thoroughly Aikido tests your application. Optimize for a lower cost, or for a more thorough test.

### High risk only

Aikido focuses on the areas most likely to expose serious vulnerabilities. Some areas get less testing, or none.

Choose this for a quick check between fuller tests. It costs less.

### Recommended coverage

Aikido covers the security-sensitive parts of your application and APIs.

Aikido recommends this level. It balances cost and thoroughness.

### Deeper coverage

Aikido tests everything in recommended coverage, then goes further. That includes complex workflows and less common attack paths.

Choose this when you want a broader test, for example ahead of a major new release. It costs more.

Every level includes a compliance-ready report, retesting, and [AutoFix](/autofix-and-remediation/overview-aikido-autofix.md). Aikido looks for the same kinds of issues at each level. The slider changes how much of the application gets tested.

## Related

{% content-ref url="/pages/hCQQM8nd9Zl8tsJuMP5g" %}
[Pentest Pricing](/pentests/pentest-pricing.md)
{% endcontent-ref %}

{% content-ref url="/pages/mtmHG9iZYyNQJ2bwM1sn" %}
[How to Setup a Pentest](/pentests/configure-a-pentest/starting-an-assessment.md)
{% endcontent-ref %}


---

# 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/high-risk-recommended-and-deeper-coverage.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.