If you are parsing the notifications sent through email, script, or pager, Trellix recommends that you define your custom message template. Default template may change in newer releases and it may break your parsing algorithms.
The following tables describe the variables used in the various message templates.
Note
“%” "/” and "$" are reserved characters. Do not use them as a delimiter in custom templates.
Variable name | Description |
|---|---|
| Unique ID assigned to an alert by the Manager |
| The type of the attack that triggered the alert. The value, for example, can be exploit, host sweep, or port scan. |
| Time when the attack was detected |
| Name of the attack that triggered the alert |
| The Trellix IPS ID for the attack |
| System impact severity posed by the attack: high, medium, low, or informational |
| Signature that matched the attack traffic (applicable only to signature-based attacks) |
| Higher the confidence, the lower is the chance for the attack to be a false-positive. |
| The admin domain to which the Sensor that detected the attack belongs |
| The number of times the attack was detected within the throttle duration |
| The Sensor that detected the attack |
| The Sensor's interface where the attack was detected |
| The Sensor in a fail-over pair that detected the attack |
| IP address of the host from where the attack originated |
| The source port number of the attack traffic |
| IP address of the targeted host |
| The destination port number of the attack traffic |
| General attack type |
| Within the attack type, a specific classification such as virus and Trojan horse |
| Whether the traffic was inbound or outbound |
| Whether the attack was successful, blocked, or a failed attempt |
| The method used to detect the attack. Each method relates to a specific attack category. Some of these methods are signature, threshold, statistical anomaly, and flow correlation. |
| The application protocol found in the attack traffic |
| The transport protocol used for the attack traffic |
| Information whether the attack is relevant for the targeted host |
| Time when an attacking host will be out of quarantine |
| Unique ID assigned to an alert by the Sensor |
| The VMware ESX server that hosts the VMware from which the attack traffic originated |
| The VMware host from which the attack traffic originated |
| The targeted VMware host for the attack |
| The VMware ESX server that hosts the targeted VMware |
| The URI found in the attack traffic |
| The VLAN tagged with the attack traffic |
| Applicable only to attacks targeted at data-enabled mobile equipments such as a mobile phone or a tablet PC. The Access Point Name (APN) of the targeted mobile equipment |
| Applicable only to attacks targeted at data-enabled mobile equipments such as a mobile phone or a tablet PC. The International Mobile Subscriber Identity (IMSI) of the targeted mobile equipment |
| Applicable only to attacks targeted at data-enabled mobile equipments such as a mobile phone or a tablet PC. The phone number of the targeted mobile equipment |
| Applicable only to attacks from data-enabled mobile equipments such as a mobile phone or a tablet PC. The Access Point Name (APN) of the mobile equipment that is the source of the attack traffic |
| Applicable only to attacks from data-enabled mobile equipments such as a mobile phone or a tablet PC. The International Mobile Subscriber Identity (IMSI) ID of the source mobile equipment |
| Applicable only to attacks from data-enabled mobile equipments such as a mobile phone or a tablet PC. The phone number of the source mobile equipment |
| The application-layer data found in the attack traffic |
| Zone from which the alert was raised; applicable only for NTBA alerts |
| Source OS name |
| Destination OS name |
| Malware file type |
| Malware file length |
| Malware file name |
| Malware file MD5 hash |
| Malware virus name |
| Malware confidence |
| Malware detection engine |
The following table describes the fault template variables.
Name | Description |
|---|---|
| The admin domain associated with the fault message |
| Name of the fault |
| The state of the fault, whether it is created, acknowledged, or cleared |
| The Sensor ID where the fault occurred. This field is not applicable to Manager faults. |
| The user-defined name of the Sensor where the fault occurred. For Manager fault, the value is 'Manager.' |
| The level of the fault. Whether it occurred at the Manager system level, Sensor level, or Sensor interface level. |
| Timestamp of when the fault occurred |
| Whether the fault was sent by the Sensor to the Manager or it was generated by the Manager |
| The component where the fault occurred |
| Whether the fault is critical, an error, warning, informational, or unknown |
| The description as found in the faultNameAndText.properties file |
| If true, the fault has been acknowledged by someone. |
| The user-defined name of the Sensor where the fault occurred |
The following table describes Firewall access rule template variables.
Name | Description |
|---|---|
| The Sensor that parsed the traffic matching the Firewall access rule |
| The admin domain to which the Sensor belongs |
| The interface where the matching traffic was detected |
| Whether the traffic was inspected, dropped, denied, or ignored |
| The IP address of the host from which the traffic originated |
| The source port number of the traffic that matched the Firewall access rule |
| The IP address of the destination host for the traffic |
| The destination port number of the traffic that matched the Firewall access rule |
| The layer 7 protocol associated with the traffic that matched the Firewall access rule |
| The IP protocol that matched |
| The number of Firewall syslog messages that were suppressed |
| The number of Firewall syslog messages that were forwarded |
| Whether the traffic that matched was inbound or outbound |
| The layer 7 application associated with the matched traffic |
| The user-entered description of the Firewall policy |
| The host DNS name from which the traffic originated |
| The host DNS name to which the traffic is destined |
| The country from which the traffic originated |
| The country to which the traffic is destined to |
| The name of the Firewall policy |
| The order of the rule in the effective list of Firewall access rules |