--- title: "Alert details" slug: "alert-details" updated: 2026-09-11T11:05:49Z published: 2026-09-11T11:05:49Z canonical: "docs.trellix.com/alert-details" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # Alert details [Skip to main content](/docs/_content-wrapper) When you select a single AMSI alert on the **Alerts** page, the details of the alert are shown on the **Hosts** page of the Endpoint Security Web UI. ![hx_amsi_alerts_host_page.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-ff297f7a-c5c6-ec73-e745-79e53bb56c01.png?sv=2026-02-06&spr=https&st=2026-11-20T23%3A50%3A34Z&se=2026-11-21T00%3A50%3A34Z&sr=c&sp=r&sig=hh4QWD6QWMuBYqrJiVz0ei4XJO4E2qG6%2F6wfm3W0SMc%3D) The Endpoint Security server provides a raw view of the alert details in JSON format. Most of the information available in the AMSI home page is reformatted to generalize the alerts data coming from various modules. The following table shows notable alert fields that the AMSI module generates. | **Alert Fields** | **Description** | | --- | --- | | `Event_at` | Time when the script was executed. | | `Content_name` | The script name if the file is on the disk. This field can also be used to indicate when a `DotNet` assembly is dynamically loaded. | | `matched_rule` | Contains the rule name and additional metadata, such as `MetaData` and `MatchedStrings`, that help analyze the detection. | | `Intel_version` | Version of the intel package that includes the AMSI rules. | | `Rules_version` | AMSI rules package version. | | `Amsi_data` | Suspicious data scanned by AMSI. | | `Arguments` | Command-line arguments passed to the source process. | | `Attributes` | Scan metadata. | | `Account_name` | User account that the scripting engine targeted. |