Alert Detail for a MITRE-Mapped Alert
- Click 'Security' > 'Endpoint Security' > 'Alerts' > 'Alert Search', find a row whose 'Mitre ID' column holds a value, and click the arrow at the start of that row.
When the alert policy that raised an alert maps it to a MITRE ATT&CK technique, the 'Mitre ID' column of the row is filled in and the detail panel gains two extra summary rows naming the tactic and the technique. Everything else about the panel is the same as a plain alert.
You can read which tactic and technique the activity belongs to, read the event fields that carry the mapping, and close the alert.

The summary
| Field | Description |
| Component: | The security component that raised the alert, for example 'Antivirus'. |
| Device Name: | The managed device the event happened on. |
| Event Type: | The kind of event that triggered the alert, for example 'Antivirus Quarantine' or 'Antivirus Restore from Quarantine'. |
| Event Time: | The date and time of the event itself. |
| Tactic: | The MITRE ATT&CK tactic, with its identifier in brackets, for example 'Execution (TA0002)'. Shown only when the alert has a mapping. |
| Technique: | The MITRE ATT&CK technique, with its identifier in brackets, for example 'User Execution (T1204)' or 'Malicious File (T1204.002)'. It is shown as a link. Shown only when the alert has a mapping. |
The event fields that carry the mapping
The same four values appear again among the event fields in the right-hand column, so a rule or an export can read them:
| Field | Description |
| tactic | The name of the tactic, for example 'Execution'. |
| tacticID | The identifier of the tactic, for example 'TA0002'. |
| technique | The name of the technique, for example 'User Execution'. |
| techniqueID | The identifier of the technique, for example 'T1204'. This is the value shown in the 'Mitre ID' column of the list. |
The other event fields
An Antivirus alert carries, in addition to the fields described in Alert Detail:
| Field | Description |
| prcsHash | The hash of the process that performed the action. |
| prcsPID | The process identifier on the device. |
| prcsPath | The full path of that process, for example the security client's own service. |
| prcsVerdict | The file verdict held for that process, for example 'Absent'. |
| parent_process_hash | The hash of the parent process. |
| parent_process_logged_on_user | The user the parent process was running as, for example 'SYSTEM'. |
| parent_process_path | The full path of the parent process. |
| parent_process_user_domain | The domain of that user, for example 'NT AUTHORITY'. |
| parent_process_user_name | The user name of that user. |
| parent_process_verdict | The file verdict held for the parent process. |
| process_parent_tree | The chain of processes above this one, shown collapsed as '[ ... ]'. Click the mark to expand it. |
The buttons
Only 'Close Alert' is shown, at the top right of the panel, and only while the alert is not already closed. The extra 'Add Suppression Rule' and 'Report False Positive' buttons belong to 'EXDR' alerts.
Find the alerts that carry a mapping
- Choose a tactic in the 'Mitre Tactic' drop-down of the filter bar.
- Choose a technique in 'Mitre Technique' if you want to narrow it further. The list fills with the techniques of the tactic you chose.
- Click 'Apply'. Every alert in the result carries a value in its 'Mitre ID' column.
Note: an alert with no mapping shows a hyphen in 'Mitre ID' and has no 'Tactic' or 'Technique' row in its detail panel. Which alerts are mapped is decided by the alert policy — the 'Tactic' and 'Technique' of each condition are set in the condition editor. See The Condition Editor.
