> For the complete documentation index, see [llms.txt](https://docs.akto.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.akto.io/test-editor/concepts/dynamic-severity.md).

# Dynamic severity

Akto provides a method to assign severity to a test template dynamically. This means that you can change the severity of a test based on various filter on the API. This helps in providing contextual severity to the test based on the API.

Let's check an example, which is used for severity in Excessive data exposure tests to better understand this.

```yaml
dynamic_severity:
- check:
    api_access_type:
      eq: private
  return: LOW
- check:
    api_access_type:
      eq: public
  return: HIGH
- return: MEDIUM
```

Here, we have three objects in the `dynamic_severity` list. The `check` attribute evaluates some condition on the API, in this case we are checking the access type of an API, and returns the severity based on it. So, in case the API is vulnerable to this test, the issue severity would be low if it's a private API, high if it's a public API and medium would be the default (In case access type is neither of these or not defined).

This helps you to prioritize vulnerabilities in more important APIs and the best part is that you can modify the conditions in `dynamic_severity` according to your needs.

NOTE: It is required to provide a default severity when using `dynamic_severity`. In case it is not defined, default is taken to be `HIGH`.


---

# 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://docs.akto.io/test-editor/concepts/dynamic-severity.md?ask=<question>&goal=<endgoal>
```

`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.