> For the complete documentation index, see [llms.txt](https://docs.xygeni.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xygeni.io/xygeni-products/anomaly-detection/anomaly-detection-user-interface-guide.md).
# Anomalous Activity Detection User Interface Guide
## Real-Time Protection Against Exploits in Your Software Supply Chain
Xygeni’s **Anomaly Detection** provides robust security by actively monitoring and addressing vulnerabilities and risks as they are detected. Our real-time analytics ensure that any attempt to exploit these vulnerabilities is identified and mitigated quickly, protecting the integrity and security of your software operations.
**Anomaly Detection** platform provides an additional layer of security by *continuously monitoring and analyzing activities within your SCM and CI/CD infrastructure to identify and respond to unusual behavior quickly*. Xygeni detects anomalies that indicate unauthorized modifications, access, or exploitations in real time. This proactive approach ensures that potential security breaches are addressed before they can escalate into serious threats.
{% hint style="info" %}
Anomaly Detection UI can be found under **Products >> Anomalous Activity**
{% endhint %}
The **Anomalous Activity** page displays the following information:
* Timeline Chart of number of issues created (differentiating between Critical File Changes and Suspicious Behavior)
* Charts for # of events by severity, by type and top-5 users with anomalous activities
* A table with the events (as well as filters ):
* Severity of the event.
* Timestamp of the event.
* Category. (Critical File Changes or Suspicious Behavior)
* Event type. (catalogued depending on the Unusual Activity detectors; read [Unusual Activity detectors available](https://docs.xygeni.io/xydocs/unusual_activity/detectors/index.html) for the full list)
* User that produced the event.
* Inventory asset associated with the event.
* Etc
In the events table, by clicking on the  icon of any event, you will see the details of the event.
As an example, the below image shows that a commit has been pushed to a repository after the branch protection was disabled.
{% hint style="info" %}
See [Code Tampering](/xygeni-products/anomaly-detection/code-tampering-scanner.md) Scanner for further information on code tampering scanner.
See [Xygeni Sensors](/xygeni-products/anomaly-detection/xygeni-sensors.md) for a full description and supported platforms of sensors.
{% endhint %}
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.xygeni.io/xygeni-products/anomaly-detection/anomaly-detection-user-interface-guide.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
