> 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-1/dlp-policies-and-rules/triggers/process-application-started.md).
# 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 **ENTER**key. 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
```
{% hint style="danger" %}
**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.
{% endhint %}
### 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.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://eaclouddoc.eauditor.eu/eacloud-docs-en/features/data-loss-prevention-1/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 what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
