> For the complete documentation index, see [llms.txt](https://eaclouddoc.eauditor.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://eaclouddoc.eauditor.eu/eacloud-docs-en/features/data-loss-prevention/dlp-policies-and-rules/triggers/process-application-started..md).
# Process/application started.
## Trigger Process/Application Launched
Trigger **Process/Application Launched** allows monitoring and management of actions related to launching processes in the system. With detailed configuration it is possible to precisely block selected processes or applications, supporting 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.
* **Use of wildcards:**\
You can use patterns such as:
* `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:**\
It is possible to specify several processes at once. To configure the policy this way, each parameter must be entered on a separate line. Parameters must be separated by ENTER, e.g.:
```
chrome.exe
opera.exe
abcd.exe
```
{% hint style="danger" %}
**NOTE:** You cannot enter a rule that blocks all processes (e.g. `*`) and at the same time exclude individual ones (e.g. `chrome.exe`). Such a configuration would result in complete system shutdown and is not supported.
{% endhint %}
### Example use
#### Blocking access to the CRM application for selected users
**Objective:** Prevent selected users from using the CRM application, which is normally launched on every computer.\
**Configuration:**
* **Process mask:** Enter the CRM application process name, e.g. `crmapp.exe`.
* **Scope of action:** Limit the rule to selected users or groups.
**Effect:** 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 organization's specific needs while minimizing the risk of security breaches.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://eaclouddoc.eauditor.eu/eacloud-docs-en/features/data-loss-prevention/dlp-policies-and-rules/triggers/process-application-started..md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.