Editing and Assignments

After creating a policy and rules, you can change their configuration and scope of operation at any time.

You can, among other things:

• change the rule settings,

• modify triggers, actions, and notifications,

• change the devices covered by the policy,

• change the users covered by the policy,

• exclude selected users,

• activate or disable the policy.

Changing a policy assignment does not change the configuration of the rules it contains. It does, however, change their scope of operation, that is, the users and devices to which they will be applied.

Editing a rule

An existing rule can be changed without having to create it again.

1

Find the policy

Go to:

Data Leak Prevention -> DLP Policies and Rules -> Policies

Click the policy name to display the rules assigned to it.

2

Open the rule

For the selected rule, click the icon Edit.

The rule will open in a separate tab.

Editing an existing rule can be started directly from the policy view.

3

Change the configuration

Depending on your needs, modify:

• the rule name,

• triggers,

• trigger parameters,

• actions,

• notifications.

4

Save the changes

After finishing the edit, save the rule.

The modified configuration will be saved in the console.

5

Update the policies

After saving the changes, go to the policy view and click:

Update the policies

Only after the current configuration is deployed can eAgents begin using the modified rule.

Before changing an active rule, verify how broad the scope of the policy it belongs to is. Changing the rule may affect all users and all devices covered by that policy.

Editing policy assignments

Assignments define, where the policy is to apply.

After creating a policy, you can change the devices and users assigned to it without having to create a new policy.

1

Open policy editing

In the Policies find the policy whose scope you want to change.

Click the icon Edit.

2

Check target objects

In the target objects section, review the devices covered by the policy.

Depending on the configuration, you can leave a broad scope or specify selected devices.

Target objects define the devices on which the policy rules apply.

3

Check target users

In the users section, specify the people who are to be covered by the policy.

You can change existing assignments and specify users who should not be covered by the policy.

User assignments define which people the policy rules apply to.

4

Save the changes

Review the configuration scope and save the policy.

5

Update the policies

After changing the assignments, click:

Update the policies

Until the current configuration is deployed, eAgents can continue using the previous assignments.

How do assignments work?

A policy assignment defines the scope in which the rules it contains will be applied.

Example:

Policy DLP - Accounting includes:

• USB storage control,

• file sending control,

• blocking specific operations.

If the policy is assigned to the accounting department's computers and its users, the rules contained in it will be applied within that scope.

Changing the assignment does not require recreating the rules.

Objects and users

When defining the scope of a policy, pay attention to two independent elements:

Assignment	What it defines
Target objects	Devices covered by the policy
Target users	Users covered by the policy

This makes it possible to build policies tailored both to devices and to the people using the environment.

It is advisable to define a policy's scope as precisely as possible. The more restrictive the rule, the more important it is to verify that it does not include devices or users for whom it was not intended.

Excluding users

If a policy is intended to cover a broad group of users but should not apply to specific individuals, you can use exclusions.

Example:

A policy that blocks the use of specific media applies to all users of selected computers, but the IT administrator performing maintenance tasks should be excluded from it.

In this situation, there is no need to create a separate policy just for the remaining users - an appropriate exclusion can be applied.

Excluding a user means that the rules resulting from a given policy will not be applied to that user within the configured scope. Use exclusions deliberately and periodically check whether they are still needed.

Changing assignments for an existing policy

Changing the scope of a policy can have two effects:

Adding new assignments

If you add new devices or new users, they will be covered by the rules in the policy after the current configuration is deployed.

Removing assignments

If you remove a device or user from the policy's scope, the rules of that policy will stop being applied to it after the modified configuration is deployed.

Before expanding the scope of an active policy, review all rules contained in it. Blocking actions require particular attention, because after assignments are changed, they may begin to apply to new devices or new users.

Safely changing an active policy

When changing a policy already in use in the environment, we recommend the following sequence:

1

Check the current scope

Before making changes, review the devices and users currently covered by the policy.

2

Review the rules

Verify which triggers and actions are in the policy.

Pay special attention to rules that cause operations to be blocked.

3

Make the change

Modify the rule or the policy assignments.

4

Save the configuration

Review the modified settings and save the configuration.

5

Update the policies

Click Update the policies, to deploy the latest configuration to eAgents.

6

Check the result

After deploying the change, perform a controlled test and review events in:

Data Leak Prevention -> DLP Logs

Copying and moving rules

If you do not want to modify an existing rule, you can also:

• create a copy of it,

• move it to another policy.

These operations are described in detail in the section Rules.

If the existing configuration works correctly, but you need a similar rule for another group of users, it is often safer to copy it and modify the copy rather than change the active rule.

FAQ

After creating a policy, can I change the assigned devices?

Yes. Open policy editing and change the target objects configuration.

After saving the changes, use the option Update the policies.

Can I change the users covered by an existing policy?

Yes. User assignments can also be edited after the policy is created.

Do I need to create a new policy after changing its scope?

No. The scope of an existing policy can be changed by editing the assigned devices and users.

Does changing the assignment also change the rule configuration?

No. The rules remain configured the same way.

Only the scope of the devices or users to which they are applied changes.

Can I exclude a single user from a policy?

Yes. Policy configuration supports user exclusions; you can specify the individuals to whom the policy should not be applied.

Why is the assignment change not yet visible on the computer?

After changing the configuration, use the option Update the policies.

Until the current configuration is deployed, eAgent may use the previous version of the assignments.