> 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-protection/concepts/threat-ignored-events.md).

# Configure Ignored Events

**Ignored Malicious Events Policy**

Customizable filters that mark detected security threats by Akto's Runtime Threat Protection as ignored in the Threat Activity dashboard.

**How to configure**

Go to **API Threat Detection → Threat Activity** in the left sidebar. Click **More Actions → Configure Ignored Events**.

**Note:** Policies must use category name `IgnoredEvent`

**Syntax Reference:** For detailed syntax on how to define API selection filters, see [API Selection Filters](https://docs.akto.io/test-editor/concepts/test-yaml-syntax-detailed/api-selection-filters).

<figure><img src="/files/6aXz34zrNkyohgKyVX4q" alt=""><figcaption></figcaption></figure>

**Example Ignored Events Policy**

Marks all threats as ignored when when the URL contains `test`.

```
id: IgnoredEvent
filter:
  url:
    contains_all:
      - "test"

info:
  name: "IgnoredEvent"
  description: "Marks threats as ignored events"
  details: "Identifies which threat activities to ignore"
  impact: "Sets the events status as ignored."
  category:
    name: "IgnoredEvent"
    displayName: "IgnoredEvent"
  subCategory: "IgnoredEvent"
  severity: HIGH
```

<figure><img src="/files/WfKENJPCuDFc0pnJ4l69" alt=""><figcaption></figcaption></figure>


---

# 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-protection/concepts/threat-ignored-events.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.
