> ## Documentation Index
> Fetch the complete documentation index at: https://docs.axottle.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Incidents and evidence

> How to Open an Incident, Update Evidence, and Close an Investigation in the Panel

Incidents are in **Security → Incidents**.

## Open an incident

Click the incident card. The sidebar shows:

* Purpose and seriousness;
* chronology;
* snapshot of evidence;
* associated nodes and Flow;
* active deceleration;
* proposed actions.

## Update the evidence

Click **Update the evidence of** in the Incident Card. The panel will re-assemble available metrics, signals, events and fragments of authorized logs.

If the source is unavailable, the card shows the reason for the skip.

## Action by the operator

From the card, you can apply an available offer, create a temporary slowdown or complete an investigation.

To close, select:

* **Resolved**;
* **False operation**.

The reason for the closure is mandatory and is stored in the chronology and the Audit journal.

## Signal without a clear user

Some network signals refer to a node, but do not allow you to identify a single subscription. In this case, see the reason for the incomplete attribution and confirming data. An absent user is not a reason to choose an arbitrary subscription for the restriction; for several candidates, first specify the source.

## Verification

1. Make sure the card contains a fresh snapshot of the evidence.
2. Check the action in the tab **Journal** or in the **Audit-magazine**.
3. To check notifications, use **Settings → Telegram → Send test**.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.