> 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/website-visited.md).

# Website Visited

## Trigger Website Visited

Trigger **Website Visited** enables management of access to websites and monitoring of user activity in web browsers. This management is supported by advanced artificial intelligence **BTC Web Classification**, using machine learning and deep learning technologies for precise website classification.

## Trigger Configuration

{% stepper %}
{% step %}

### Website Masks

* **Website Mask:**
  * Defines the websites that are to be monitored.
  * Works in the same way as path masks, for example:
    * `www.test.pl`
    * `www.test/test*.com`.
* **Excluded Website Mask:**
  * Specifies exceptions that will not be monitored.

<div align="left"><figure><img src="https://3262380731-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdzip3GyvGq5q5J3qckWN%2Fuploads%2FvvSJRdxs0JynKPlnx0jf%2F67.png?alt=media&amp;token=331ce415-fbfb-40c5-9f14-3a6fedacba97" alt="" width="95"><figcaption></figcaption></figure></div>

[How to add/edit a mask?](/eacloud-docs-en/features/data-loss-prevention-1/dlp-policies-and-rules/triggers/file-operations/masks.md)

{% hint style="warning" %}
The website mask should include the protocol **(https\://)** or start with a wildcard character **\***, which replaces any string of characters located before the specified address.

Examples of valid masks:

* **<https://www.facebook.com/>**
* **\*[www.facebook.com/](http://www.facebook.com/)**

By using the **\*** character, the rule will match regardless of the address prefix, for example **https\://, http\://** or others occurring before the domain name.
{% endhint %}
{% endstep %}

{% step %}

### Process Masks

* **Process Mask:**
  * Limits monitoring to specific web browsers.
  * Example: `chrome.exe`, `firefox.exe`.
  * Optionally monitor all, that is `*` and exclude selected ones.
* **Excluded Process Mask:**
  * Allows selected browser processes to be excluded from monitoring.

<div align="left"><figure><img src="https://3262380731-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdzip3GyvGq5q5J3qckWN%2Fuploads%2F0QsprMAxGOagAsTZsht8%2F68.png?alt=media&amp;token=db64a503-bf57-4ff2-8182-1711ababc62a" alt="" width="96"><figcaption></figcaption></figure></div>

[How to add/edit a mask?](/eacloud-docs-en/features/data-loss-prevention-1/dlp-policies-and-rules/triggers/file-operations/masks.md)
{% endstep %}

{% step %}

### Website Categories

* **Website Categories:**
  * A multi-select list containing various types of websites (for example, "Games", "Finance and Banking", "Social Media").
  * If no category is selected, the policy applies regardless of category.
* **Excluded Website Categories:**
  * Allows you to specify categories to be excluded from monitoring.
* **Three-position switch:**
  * Makes it easier to choose between the "include" and "exclude" options.
  * **Left (exclude):** The switch turns black.
  * **Right (include):** The switch turns green.

<div align="left"><figure><img src="https://3262380731-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdzip3GyvGq5q5J3qckWN%2Fuploads%2FmXbYONCNzBunssrJSVRH%2F69.png?alt=media&amp;token=c6d085ae-f64f-4a8a-86ec-a19b834f33cf" alt="" width="94"><figcaption></figcaption></figure></div>
{% endstep %}
{% endstepper %}

{% hint style="warning" %}

#### Entering multiple parameters in a single rule

Within a single rule, you can enter multiple parameters (for example, domain, path, file, or process masks). There is no need to create a separate rule for each one.

Each parameter should be entered **on a separate line**, separating consecutive 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 - domain masks**

```
*.facebook.com
*.youtube.com
*.tiktok.com*
```

The rule will be applied if the user visits **Facebook OR YouTube OR TikTok**.
{% endhint %}

### List of supported website categories

Sample categories available in the system:

* Finance, Banking, and Insurance
* Games
* Gambling
* Career, Education, and Religion
* Computers, Software, and Electronics
* Culinary and Restaurants
* People and Social Media
* Malware
* Media, News, and Weather
* Automotive and Transportation
* Unsafe Page Structure
* Unrecognized Language
* Real Estate, Home, and Garden
* Politics, Law, and Government Institutions
* Pornography
* Industry, Business, and Services
* Entertainment
* Sports
* Login Page
* Art and Culture

The full list of categories contains several dozen items, allowing precise policy customization.

## Use case

**Objective:** Restrict access to gossip websites for the sales department during working hours.

* **Configuration:**
  * Select the "Entertainment" category and set the switch to **include** (green).
  * Set the process mask to the browsers used in the company, for example `chrome.exe`.
  * Define the actions in the next step — block.

**Result:**

* Users in the sales department will not have access to gossip websites.
* Every attempt to access such a website will be recorded in the system logs.

## Summary

Trigger **Website Visited** enables effective management of access to websites, supporting security and productivity policies across the organization. Thanks to advanced configuration features such as masks, categories, and intelligent website classification, the tool provides precise control over user activity in browsers.


---

# 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-1/dlp-policies-and-rules/triggers/website-visited.md?ask=<question>&goal=<endgoal>
```

`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.
