Rule

In the first tile, you can find the following details:

Name—the name of the triggered rule is shown here

Occurred—date and time of occurrence

Triggering process—shows the name of the triggering process with its integrity level

Command Line—shows command line that the triggering process used

Username—shows the name of the user that was logged when the event happened

User Role—if available, show the role of the user that is listed in the Username

 

In the second tile, you can find the following details:

Triggering Executable—the executable that triggered the detection. By clicking the name of the executable, you are redirected to the Executable details tab

SHA-1—hash of the executable. By clicking the down arrow next to the hash, the context menu shows up, where you can use two options:

oHere you will see the preferred virus search page that you can define in the Server Settings tab. By default Virus Total search page

oCopy to clipboard—As the name says it will copy the hash to your clipboard for further use

Signature Type—information whether the file is signed or not and how it is signed (Trusted/Valid/None/Invalid/Unknown)

Signer Name—if the file is signed, here you can see the signer of the file

Seen on—the number of computers on which the file was discovered. After clicking on it, you are redirected to the Computers view, with filtered Computers list

First Seen—when an executable was first seen on any computer in a monitored network

Last Executed—when an executable was last executed on any computer in a monitored network

 

In the third tile, you can find the following details:

Reputation (LiveGrid®)—is the number from 1 to 9, indicating how safe the file is. 1-2 Red is malicious, 3-7 Yellow is suspicious, 8-9 Green is safe

Popularity (LiveGrid®)—how many computers reported an executable to LiveGrid®. For a detailed description, click here

First Seen (LiveGrid®)—when an executable was first seen on any computer connected to LiveGrid®

 

In the fourth tile, you can find the following details:

Computer—shows the name of the computer, where the detection triggered. After clicking the computer name, you are redirected to Computer details

Parent Group—the name of a group of computers where this particular computer is assigned. Computer’s group can be changed in ESET PROTECT

Last connected—permanent connection created to listen on notification about blocked hashes, requests to download some file, kill the process, etc. Refresh interval is 90 seconds

 

The process tree on the right side—the process tree reflects the parent-child relationship between processes where child processes are shown directly beneath their parent and right-indented. Processes that are left-justified are orphans, and their parent has exited.

 

Each detection includes the following details:

Category—show the Category name that u can find between Category tag in Edit Rule section

Explanation—explanation of behavior of the file

Malicious Causes—what can be a result if the file was executed

Benign Causes—what could be an unharmful approach to the file. Shown only if rule does

Recommended Actions—steps to be made to clarify whether the file is Malicious or Benign

MITRE ATT&CK™ TECHNIQUES—if the rule contains an ID of the MITRE ATT&CK™ TECHNIQUE it is shown here, otherwise none

Detection Type

oRule—this filters Detections that were triggered based on rules

oBlocked—this shows Detections that were triggered by matching the blocked hashes listed in the Admin section

oAntivirus—this shows Detections that were triggered by ESET Endpoint Security itself, after Scan or after Real-time detection

oFirewall—this shows Detections that were triggered by ESET Endpoint Security itself, for example, if some Firewall rule was triggered

oHIPS—this shows Detections that were triggered by ESET Endpoint Security itself when HIPS protection detects intrusion

oFiltered Websites—this shows Detections that were triggered by ESET Endpoint Security itself if the website is from (PUA, Internal or Anti-Phishing) blacklist

Source Rule—whether it was the detection triggered by the rule or ESET Endpoint Security. After clicking on it, you are redirected to the specific Edit Rule section if it was triggered by the rule

Occurred—date and time of occurrence of the process

Triggered—date and time when the detection was triggered

Priority—the priority of the detection. This can be changed via Priority buttons at the bottom

Severity—shows the severity of the detection.Threat Alarm_Severity_Threat Warning Alarm_Severity_Warning Info Alarm_Severity_Info

Severity Score—more precise definition of severity. 1-39 > Info Alarm_Severity_Info 40-69 > Warning Alarm_Severity_Warning 70 - 100 > Threat Alarm_Severity_Threat

Resolved—shows whether the detection is marked as Resolved Alarms_Details_Resolved. This status can be changed via Priority buttons at the bottom of the window Alarms_Details_Resolved_Unresolved

Note—the place where the user can put his note for this detection. You can add the note by clicking the Set note blue string on the right side of the window

Triggering Process—the name of the process (with corresponding Process ID) that triggered the detection. After clicking the name you are redirected to the Process Details

Command Line—show the name of Command Line file name

Path—appears when the detection was triggered by the blocked hash or ESET Endpoint Security

Integrity Level—Represented by the arrow in process tree, the grid of Detections tab, and everywhere where the process name is present
These levels are present:

oUntrusted—Blue arrow downIntegrity_blue, blocks most write access to a majority of objects

oLow—Blue arrow downIntegrity_blue, blocks most write access to registry keys and file objects

oMedium—No icon, this is the default setting for most processes when UAC has been enabled on the system

oHigh—Red icon upIntegrity_red, most processes will have this setting if UAC is disabled and the currently logged on user is the administrator

oSystem—Red icon upIntegrity_red, this is a setting reserved for system level components

oProtected process—Red icon upIntegrity_red, is used by some anti-malware services, only allows trusted, signed code to load and has built-in defense against code injection attacks

Compromised—if available shows if the process is compromised

Compromised by rule—if available shows the name of the rule that compromised the process

Compromised by event—if available shows the event that triggered the action in the rule

Event—event that triggered that particular detection. By clicking the name of event, the user is redirected to the raw event view

Computer—shows the name of the computer, where the detection triggered. After clicking the computer name, you are redirected to Computer details. You can also click "View detections on this computer" located on the right side from the name of the computer and you are redirected to the detection list of this particular Computer

Triggering Executable—the executable that triggered the detection. After clicking the name you are redirected to the Executable Details

SHA-1—hash of the executable. By clicking the down arrow next to the hash, the context menu shows up, where you can use two options:

oHere you will see the preferred virus search page that you can define in the Server Settings tab. By default Virus Total search page

oCopy to clipboard—As the name says it will copy the hash to your clipboard for further useSignature Type—information whether the file is signed or not and how it is signed (Trusted/Valid/None/Invalid/Unknown)

Signature Type—information whether the file is signed or not and how it is signed (Trusted/Valid/None/Invalid/Unknown)

Signer Name—if the file is signed, here you can see the signer of the file

File Description—The full description of the file, for example, "Keyboard Driver for AT-Style Keyboards"

Seen on—the number of computers on which the file was discovered. After clicking on it, you are redirected to the Computers view, with filtered computers list

First Seen—when an executable was first seen on any computer in a monitored network

Inspected—if the executable is marked as inspected by the user

Reputation (LiveGrid®)—Is number from 1 to 9, indicating how safe the file is. 1-2 Red is malicious, 3-7 Yellow is suspicious, 8-9 Green is safe

Popularity (LiveGrid®)—how many computers reported an executable to LiveGrid®. For a detailed description, click here

First Seen (LiveGrid®)—when an executable was first seen on any computer connected to LiveGrid®

Username—the name of the user/account that was logged in when the detection was raised

Full name—users full name, if available from Active Directory

Job Position—users job position, if available from Active Directory

User Department—users department, if available from Active Directory

User Description—users description, if available from Active Directory

Audit Log—here, you see actions that were taken on this detection. At the moment Resolved, Unresolved, Commented and Priority Changed

Comments—the place where the user can put his comments for this detection. You can add the comment by clicking the Add comment blue string

 

At the bottom of the page, there are several action buttons available.