ESET Online Help

Search English
Select the topic

Operations

The operations part defines which operations executed by a process raise the detection. If empty, the detection is triggered when the process generates an event.

Operations are defined using an operation element with a type attribute and an expression element.

<operation type="WriteFile">Expression</operation>

 

The following components are supported by all operation.

DateTime

EnterpriseInspector

SystemInfo

 

CodeInjection

A process was subject to some form of code injection.

Supported components:

ClientProcessInfo

CodeInjectionInfo

Enterprise

FileItem

LiveGrid

Module

ProcessInfo

 

CreateNamedPipe

A named pipe was created.

Supported components:

FileItem

 

CreateProcess

A process was created.

Supported components:

Enterprise

FileItem

LiveGrid

Module

ProcessInfo

 

DeleteFile

A file was deleted.

Supported components:

FileItem

 

Detection

This operation can be used in two different ways:

Used in a regular rule—an event was triggered on client-side antivirus

Used in a sequence rule—only detections triggered by Inspect

Supported components:

Endpoint

InspectDetection

Network

 

DnsRequest

A DNS request was made (usually IP > domain, domain > IP).

Supported components:

DnsInfo

 

HttpRequest

A HTTP request was made.

Supported components:

Network

 

LoadDLL

A DLL was loaded.

Supported components:

Enterprise

FileItem

LiveGrid

Module

ProcessInfo

 

LoadDriver

A driver or kernel module was loaded.

Supported components:

FileItem

 

ModuleDrop

An executable was dropped.

Supported components:

FileItem

 

MultipleFilesChanged

Process modified multiple files.

Supported components:

ProcessBehavior

 

OpenProcess

Added a new rule attribute, which triggers when a process is opened. Only the open process to lsass.exe is monitored.

Supported components:

FileItem

OpenProcess

 

ReadFile

Triggered when a monitored file was read. Monitored files refer to those which contain either sensitive information or stored credentials, for example, stored browser passwords, stored FTP clients passwords, AD database and so on.

Supported components:

FileItem

 

RegDeleteKey

A registry key was deleted.

Supported components:

RegistryItem

 

RegDeleteValue

The value of the registry was deleted.

Supported components:

RegistryItem

 

RegRenameKey

A registry key was renamed.

Supported components:

RegistryItem

 

RegSetValue

A registry key was altered.

Supported components:

RegistryItem

 

RenameFile

A file was renamed.

Supported components:

FileItem

DestFileItem

 

Scripts

A script exposed by AMSI was executed.

Supported components:

Scripts

 

SetFileAttribute

A file attribute was set.

Supported components:

FileAttribute

FileItem

 

SystemApiCall

A system function was called.

Supported components:

ApiCall

 

TcpIpAccept

An incoming TCP/IP connection was accepted.

Supported components:

Network

 

TcpIpConnect

An outbound TCP/IP connection was made.

Supported components:

Network

 

TcpIpProtocolIdentified

On top of TCP/IP connection, describes the protocol used.

Supported components:

Network

 

TruncateFile

A file was truncated, this operation is reported only on Posix systems

Supported components:

FileItem

 

UserActivate

The user was activated.

Supported components:

TargetUser

DoneByUser

UserGroupData

 

UserAddToGroup

The user was added to the group.

Supported components:

TargetUser

DoneByUser

UserGroupData

 

UserCreate

A new user was created.

Supported components:

TargetUser

DoneByUser

UserGroupData

 

UserDisable

The user was disabled.

Supported components:

TargetUser

DoneByUser

UserGroupData

 

UserLogin

The user logged in.

Supported components:

TargetUser

DoneByUser

UserGroupData

UserLogonData

 

UserLogout

The user logged out.

Supported components:

TargetUser

DoneByUser

UserGroupData

UserLogonData

 

UserRemove

The user was removed.

Supported components:

TargetUser

DoneByUser

UserGroupData

 

UserRemoveFromGroup

The user was removed from the group.

Supported components:

TargetUser

DoneByUser

UserGroupData

 

WmiExecution

WMI execution event was triggered.

Supported components:

ClientEnterprise

ClientFileItem

ClientLiveGrid

ClientModule

ClientProcessInfo

FileItem

WmiExecutionInfo

 

WmiPersistence

The event is generated when consumer binds to a filter.

Supported components:

WmiPersistenceInfo

 

WmiQuery

WMI query was executed on a computer.

Supported components:

ClientEnterprise

ClientFileItem

ClientLiveGrid

ClientModule

ClientProcessInfo

WmiQueryInfo

 

WriteFile

A file was written to.

Supported components:

FileItem

 


important

Earlier versions of Windows do not produce WMI events. This functionality has been available since Windows 10 version 1803.

Some of the events provide only partial information:

File write events—only the first file change is recorded (This is per process. If two processes change the same file, both changes are recorded)

Registry related events—only the first registry key change is recorded (first time by a process)

DLLLoad—only DLLs that are not whitelisted by AV are recorded

TcpIp events—only the first connection is recorded (first time by a process)

Http events—only the first request is recorded (first time by a process)

ModuleDrop (a.k.a PEDrop)—it is reported only for the first drop of a given module (first time on a computer)

AmsiTriggerEvent—only the first execution is recorded (first time on a computer)