> 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/issues/concepts/values.md).
# Evidence
The Evidence tab in the Issue details provides in-depth information about the specific API interactions associated with the detected vulnerability. When examining an issue, the evidence tab offers detailed insights into the API calls that triggered the security concern.
This includes both the requests sent to the API and the responses received, allowing for a comprehensive analysis of the vulnerability context.
### Request
The request section typically displays:
* HTTP method used
* Endpoint path
* Headers sent with the request
* Any data or parameters included in the request body
This information helps in understanding how the API was called and what data was sent, which is crucial for identifying the root cause of the security issue.
### Response
The response section usually shows:
* HTTP status code
* Response headers
* Body of the response
Analysing the response data is essential for understanding how the API reacted to the potentially vulnerable request and what information may have been exposed.
{% hint style="info" %}
**Change Legend in Evidence**
The legend under the Evidence tab explains how Akto highlights differences between compared requests and responses.
* **Added**
Marks fields or values that appear in the current request or response but were not present earlier.
* **Removed**
Marks fields or values that were present earlier but are missing in the current request or response.
* **Updated**
Marks fields or values that exist in both comparisons but have different values.
{% endhint %}
### Usage
Examining the Evidence tab allows you to:
1. Understand the exact nature of the vulnerability by seeing the raw data exchanged.
2. Identify specific headers or payload elements that may be causing the security issue.
3. Verify the severity and impact of the vulnerability based on the actual data exposed or manipulated.
4. Guide the development of precise fixes by pinpointing the problematic parts of the request or response.
The Evidence tab is a crucial to gain a detailed understanding of each detected vulnerability, facilitating more effective and targeted remediation efforts.
---
# 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/issues/concepts/values.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.