Process/Application Started
Trigger Process/application launched
Trigger Process/application launched enables monitoring and management of activities related to process execution in the system. Through detailed configuration, it is possible to precisely block selected processes or applications, which supports enforcement of the organization's security policies.
Trigger configuration
Process mask
Defining processes to monitor: Specify any number of processes to be monitored or blocked. Each process must be entered individually, e.g.
chrome.exe, which will block only that process.Using wildcards: Patterns such as the following can be used:
chr*.exe– blocks all processes starting with “chr” (e.g.chrome.exe,chr123.exe).*abcd.exe– blocks all processes ending with “abcd.exe” (e.g. 123abcd.exe, testabcd.exe)
Multiple processes: Within a single rule, multiple parameters can be entered (e.g., domain masks, paths, file names, or process names). There is no need to create a separate rule for each of them.
Each parameter must be entered on a separate line, separating successive entries only with the ENTERkey. Commas, semicolons, or other separators must not be used.
In this case, the logic is OR. This means that the rule will be applied if any of the specified conditions is met.
Example:
chrome.exe
opera.exe
*abcd.exe
NOTE: It is not possible to define a rule that blocks all processes (e.g. *) and at the same time exclude individual ones (e.g. chrome.exe). Such a configuration would completely block the system from functioning and is not supported.
Example use case
Blocking access to the CRM application for selected users
Goal: Prevent selected users from using the CRM application, which is normally launched on every computer. Configuration:
Process mask: Enter the process name of the CRM application, e.g.
crmapp.exe.Scope: Restrict the rule to selected users or groups.
Result: Selected users will not be able to launch the CRM application, while others will retain access to it.
Summary
Trigger Process/application launched enables effective management of access to applications and processes in the system. With flexible configuration options such as process masks and patterns, rules can be precisely tailored to the specific needs of the organization while minimizing the risk of security breaches.
Last updated
Was this helpful?