> 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/api-inventory/concepts/threat-issues.md).

# Threat Issues

## Overview

The **Threat Issues** section presents security findings associated with a specific API endpoint. The view helps you understand active and historical security risks detected by Akto for the selected API.

<figure><img src="/files/1TehSqh8IWYOiORqkDda" alt="" width="563"><figcaption></figcaption></figure>

## How Akto Populates Threat Issues

Akto continuously analyzes API traffic and test results to identify security issues. Each detected issue is recorded as a discrete threat entry and linked directly to the API endpoint where the behavior was observed.

## Information Shown for Each Issue

Each row in the Threat Issues table represents a single security issue and includes clearly scoped attributes:

* **Severity**: Risk level assigned by Akto based on exploitability and impact.
* **Issue Name**: Security condition or weakness detected.
* **Category**: Classification of the issue based on Akto’s threat taxonomy.
* **Domains**: Affected security domains, when applicable.
* **Compliance**: Mapped compliance standards, when relevant.
* **Discovered**: Date when Akto first identified the issue.

## Value for Your Security Workflow

The Threat Issues view allows you to:

* Correlate security findings directly with API endpoints.
* Track issue recurrence and discovery timelines.
* Prioritise remediation using severity and category context.
* Validate security posture changes as APIs evolve.

This section is designed to provide focused, API-level security visibility without requiring navigation across multiple testing or reporting views.


---

# 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/api-inventory/concepts/threat-issues.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.