> 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/network-connection.md).
# Network Connection
## Network Connection Trigger
Trigger **Network Connection** allows for monitoring and managing access to wireless networks. The user can define rules regarding the types of networks that are permitted for connection, as well as exception settings, ensuring a high level of network connection security.
## Trigger Configuration
{% stepper %}
{% step %}
### Network Type
The user can specify the types of networks to be monitored by selecting one or both options:
* **Open:** Unsecured networks that do not require a password or other authentication mechanisms.
* **Secured:** Networks that require a password or use security mechanisms (e.g., WPA2, WPA3).
**Operating principle:**
* If only the “Open” option is selected, the rule actions will apply exclusively to connections to unsecured networks.
* If both options are selected, the rule will cover both open and secured networks.
{% endstep %}
{% step %}
### Network masks
Network mask configuration works analogously to process, path, and file masks:
* **Network mask:** Defining the networks to be monitored. Specific SSIDs or their patterns can be specified (e.g. `Hotel_WiFi`, `HomeNetwork_*`).
* **Excluded network mask:** Defining networks that will be ignored by the monitoring system (e.g. `Trusted_Network`, `OfficeWiFi`).
{% endstep %}
{% endstepper %}
## Use case
**Purpose:** Protection against connecting to unsecured networks while working remotely or on a business trip.
* **Configuration:**
* Network type: Select “Open”.
* Masks: Exclude corporate Wi-Fi networks (`OfficeWiFi`), to allow connections only to them.
* **Result:**
* Users will not be able to connect to unsecured networks (e.g., in hotels or at airports).
* Connection to corporate networks will remain available.
{% hint style="warning" %}
#### Entering multiple parameters in a single rule
Within a single rule, multiple parameters can be entered (e.g., domain masks, paths, file names, or processes). There is no need to create a separate rule for each one.
Each parameter should be entered **on a separate line**, separating successive entries only with the **ENTER**key. Do not use commas, semicolons, or other separators.
In this case, the **OR**logic applies. This means that the rule will be applied if **any** of the specified conditions is met.
**Example - network masks**
```
*officeWiFi*
*WIFI_COMPANY*
NETWORK_ABCD
```
The rule will be applied if the user attempts to connect, for example, to the network **TESTofficeWiFi OR WIFI\_COMPANY123 OR NETWORK\_ABCD**
{% endhint %}
## Summary
Trigger **Network Connection** provides effective monitoring and management of access to wireless networks. Thanks to the ability to select network types, SSID masks, and define exceptions, this tool supports organizations in enforcing security and data protection policies when using Wi-Fi connections.
---
# 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/network-connection.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.
