IOA tags—Information about the results of file analysis using the Targeted Attack Analyzer technology: name of the TAA (IOA) rule that was used to create the alert.
Click the link to display information about the TAA (IOA) rule. If the rule was provided by Kaspersky experts, it contains information about the triggered MITRE technique as well as recommendations for reacting to the event.
The MITRE ATT&CK (Adversarial Tactics, Techniques & Common Knowledge) database contains descriptions of hacker behavior based on the analysis of real attacks. It is a structured list of known hacker techniques represented as a table.
The field is displayed if a TAA (IOA) rule was triggered when the event was created.
File—Name of the loaded module file.
MD5—MD5 hash of the loaded module file.
SHA256—SHA256 hash of the loaded module file.
Size—Size of the loaded module.
Event time—Time when the module was loaded.
Program name—For example, name of the operating system.
Vendor—For example, vendor of the operating system.
File description—For example, Example File.
Original file name—For example, Example File.
Signature subject—Organization that issued the digital certificate of the file.
Signature validation result—For example, "Signature invalid" or "Signature OK".
Time created—Creation time of the loaded module.
Time modified—Date of last modification of the loaded module.
Next DLL in bypass path—The field contains the path to the DLL library that could have been loaded instead of the existing library.
The field is displayed if the following conditions are satisfied:
The source of the loaded DLL is not trusted.
A folder in the standard search path contains a library with the same name but a different hash.
Kaspersky Anti Targeted Attack Platform receives the data required to populate the Next DLL in bypass path field only when Kaspersky Anti Targeted Attack Platform is integrated with the Kaspersky Endpoint Agent for Windows program version 3.10. When integrating the program with older versions of the Kaspersky Endpoint Agent program, the field is not displayed in the event information.
Event initiator section:
File—Path to the parent process file.
MD5—MD5 hash of the parent process file.
SHA256—SHA256 hash of the parent process file.
System info section:
Host name—Name of the host on which the module was loaded.
User name—Name of the user that loaded the module.
OS name—Version of the operating system being used on the host.
Clicking the link with the file name or file path opens a list in which you can select one of the following actions: