> 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/triggers/copying.md).

# Copying

Trigger **Copying** is used to monitor data copied by the user to the system clipboard.

It allows controlling the copying of:

* text,
* images,
* file paths.

When an event is detected, the rule can perform configured actions, for example block the ability to continue pasting data, record the event, or display a message to the user.

{% hint style="info" %}
A DLP rule can contain only **one trigger**. However, you can assign multiple actions and multiple notifications to the same trigger.
{% endhint %}

### What does the Copying trigger monitor?

The trigger responds to content placed in the system clipboard.

In the configuration, you can specify one or more data types:

| Data type      | What is monitored                                                               |
| -------------- | ------------------------------------------------------------------------------- |
| **File paths** | Copying file information, for example paths to documents                        |
| **Images**     | Graphics, images, and other graphic data placed in the clipboard                |
| **Text**       | Text fragments copied from documents, websites, applications, and other sources |

<figure><img src="https://3262380731-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdzip3GyvGq5q5J3qckWN%2Fuploads%2FeSIstztsstL1d1KdUkQj%2F56.png?alt=media&amp;token=cb98535e-94f2-436a-b698-95782102f7a6" alt="Konfiguracja wyzwalacza Kopiowanie w eAuditor Cloud z możliwością wyboru ścieżek plików, obrazów i tekstu." width="184"><figcaption><p><em>The Copying trigger allows you to define which types of data placed in the clipboard should be monitored.</em></p></figcaption></figure>

### Trigger configuration

{% stepper %}
{% step %}

#### Open the rule configuration

Create a new rule or open an existing rule for editing.
{% endstep %}

{% step %}

#### Select the Copying trigger

In the **Triggers** section, select:

**Copying**

Remember that one rule can use only one trigger.
{% endstep %}

{% step %}

#### Select the data type

Specify which data placed in the clipboard should be monitored.

You can specify:

* **File paths**,
* **Images**,
* **Text**.

Depending on your needs, you can select more than one data type.
{% endstep %}

{% step %}

#### Configure actions

Go to the **Actions** section and define how the system should respond.

You can add multiple actions to a single trigger.

Depending on the scenario, the rule can, among other things, record the event, block the operation, or display an appropriate message to the user.
{% endstep %}

{% step %}

#### Configure notifications

If event information should be sent to an administrator or another recipient, add the appropriate notifications.

You can assign multiple notifications to one rule.
{% endstep %}

{% step %}

#### Save the rule

After configuration is complete, save the rule and assign it to the appropriate policy.
{% endstep %}

{% step %}

#### Update policies

Click:

**Update policies**

so the current configuration can be delivered to eAgents.
{% endstep %}
{% endstepper %}

### Text copying

After selecting the **Text** type, the system can respond to text copied to the clipboard while the user is working.

This can include text copied from, among other sources:

* documents,
* web pages,
* applications,
* messaging apps,
* terminals and consoles,
* other programs that allow text copying.

An example use case may be controlling the copying of data that, according to the organization's policy, should not be transferred between applications.

{% hint style="info" %}
The trigger responds to the copy-to-clipboard operation. Whether further use of the data is blocked depends on the actions configured in the rule.
{% endhint %}

### Image copying

Type **Images** enables monitoring of graphic data placed in the clipboard.

This can include, among other things:

* copying graphics from applications,
* copying an image from a web page,
* copying graphic fragments,
* graphic data placed in the clipboard as a result of taking a screenshot.

For example, if a user takes a screenshot using the **Print Screen**key, the image may be placed in the clipboard and thus be covered by the trigger.

{% hint style="info" %}
If you want to control the taking of screenshots itself as a separate event, the **Screenshot**. The **Copying** trigger focuses on data located in the clipboard.
{% endhint %}

### Copying file paths

Type **File paths** allows responding to file information placed in the clipboard.

Example:

The user selects the file:

`C:\Dane\Raport.xlsx`

and chooses the **Copy**.

The information about the copied file is placed in the clipboard and can be detected by the DLP rule.

Depending on the configured actions, the event can be recorded or the further operation can be restricted.

### Copying vs. File Operations

Triggers **Copying** and **File Operations** do not mean the same thing.

#### Copying

It focuses on data sent to the **system clipboard**, for example:

* text,
* image,
* information about the copied file.

#### File Operations

It is used to control specific operations performed directly on files.

{% hint style="warning" %}
If the goal is to control a specific action performed on a file, do not automatically assume that the correct trigger is **Copying**. The Copying trigger applies primarily to clipboard content. Detailed file operations are described in the section [**File Operations**](/eacloud-docs-en/features/data-loss-prevention/triggers/file-operations.md).
{% endhint %}

### Use case example

#### Goal

The organization wants to block the ability to copy text to the clipboard on computers covered by a specific policy.

#### Configuration

**Trigger:**

**Copying**

**Data type:**

**Text**

**Actions:**

* blocking the unauthorized operation,
* displaying a message to the user informing them of a security policy violation.

<figure><img src="https://3262380731-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdzip3GyvGq5q5J3qckWN%2Fuploads%2FASB5dkc7Rpktk4LNRNmN%2Fimage.png?alt=media&amp;token=a7b9ebdd-337e-4722-a1e0-59a2bb922865" alt="Przykładowa reguła DLP wykorzystująca wyzwalacz Kopiowanie dla danych tekstowych oraz akcję blokującą." width="375"><figcaption><p><em>Example of a rule controlling copying text to the clipboard.</em></p></figcaption></figure>

After the rule is deployed, an attempt to copy text on a computer covered by the policy will cause the configured actions to be executed.

### Testing the rule

{% stepper %}
{% step %}

#### Limit the scope of the test

Assign the policy to a test computer or a small group of devices.
{% endstep %}

{% step %}

#### Update policies

Click **Update policies** and make sure eAgent has downloaded the current configuration.
{% endstep %}

{% step %}

#### Perform the copy operation

Copy data corresponding to the configured type.

For example, for the type **Text** copy a text fragment from a document or web page.
{% endstep %}

{% step %}

#### Check the response

Verify that the configured actions were performed.

If the rule is to block the operation, also test the attempt to paste the copied content.
{% endstep %}

{% step %}

#### Check DLP Logs

Go to:

**Data Loss Prevention -> DLP Logs**

and verify that the event was recorded correctly.
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
Rules that block copying can affect basic operations performed by users. Before broad deployment, always test their behavior on a test device.
{% endhint %}

### FAQ

<details>

<summary><strong>Does the Copying trigger monitor only text?</strong></summary>

No. You can control:

* text,
* images,
* file paths.

</details>

<details>

<summary><strong>Can I add Copying and USB device connection in one rule?</strong></summary>

No. One rule can contain only one trigger.

If you want to control two different types of events, create separate rules.

</details>

<details>

<summary><strong>Can one rule perform several actions after detecting copying?</strong></summary>

Yes. A rule can have one trigger and many assigned actions.

</details>

<details>

<summary><strong>Can I monitor text and images at the same time?</strong></summary>

Yes. In the trigger configuration, you can select more than one supported data type.

</details>

<details>

<summary><strong>Can Print Screen be detected as image copying?</strong></summary>

If taking a screenshot causes an image to be placed in the clipboard, the graphic data can be covered by the monitoring of the trigger **Copying**.

To control the taking of screenshots itself, a separate trigger is also available [**Screenshot**.](/eacloud-docs-en/features/data-loss-prevention/triggers/screenshot.md)

</details>

<details>

<summary><strong>Is Copying used to control all operations performed on files?</strong></summary>

No. The trigger **Copying** focuses on data placed in the clipboard.

For detailed control of operations performed on files, use the trigger [**File Operations**](/eacloud-docs-en/features/data-loss-prevention/triggers/file-operations.md).

</details>


---

# 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/triggers/copying.md?ask=<question>&goal=<user_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.