Rules
The rule defines what the system is to detect and how it is to respond to a specific event.
Each rule belongs to a DLP policy and can include:
one trigger,
configured actions (multiple),
notifications (multiple).
A sample rule can detect the connection of a specific USB device, block an unauthorized operation, and send a notification to the administrator.
Where are the rules located?
Go to:
Data Protection -> Rules -> Policies
Rules are displayed within the policies to which they have been assigned.
To view the rules belonging to the selected policy, click its name.

What does a rule consist of?
Rule configuration is based on three basic elements:
Trigger
Defines the event or condition that starts the rule
Action
Defines the action performed when the conditions are met
Notification
Defines whether and to whom information about the event is to be sent
Example:
Trigger: the user connects a USB device that meets specified conditions.
Action: the system blocks the unauthorized operation.
Notification: the administrator receives information about the event.
Adding a rule
You can create a new rule within an existing policy.
Saving a new rule in the console does not yet mean that computers are using its latest version. After completing the configuration, remember to use the option Update policies.
Working with rule tabs
When creating or editing a rule, its configuration opens in a separate tab at the top of the view.
You can have several rule tabs open at the same time.
The tab name corresponds to the name of the rule currently being edited and may change after the changes are saved.

If you start creating a new rule, save the configuration before closing its tab. Unsaved work may be lost.
Editing a rule
You can modify an existing rule without creating it from scratch.
Before changing an active rule, check the scope of the policy to which it belongs. The change may affect all devices and users covered by that policy.
Copying a rule
If a similar configuration is to be used in another policy, you do not need to create the rule from scratch.
Function Copy creates a copy of an existing rule in the selected policy. The original rule remains in the current policy.
Moving a rule
Function Move allows you to change the policy to which an existing rule belongs.
Unlike copying, no second rule is created - the existing configuration is removed from the current policy and assigned to the target policy.
Moving a rule changes its scope of operation. Before performing the operation, check the assignments of the source and target policies, as they may cover different users or devices.
Copying vs. moving
Copy
Remains in the current policy
New copy of the rule
Move
Is removed from the current policy
The same rule is assigned to the new policy
Deleting a rule
You can delete a rule that is no longer needed.
Rule deletion becomes permanent only from the Archive view. If the configuration may still be needed, it can be restored.

Permanent deletion requires confirmation of the logged-in user's credentials.
When to use which operation?
If you want to:
change the behavior of an existing rule - use Edit,
use a similar configuration in another policy - use Copy,
change the policy to which the rule belongs - use Move,
completely remove the configuration - use Delete.
Best practice
When you have a large number of rules, use names that indicate both the monitored event and the expected response.
Instead of:
USB 1
it is better to use:
USB - unauthorized media blocked
Instead of:
WWW
it is better to use:
WWW - blocked prohibited categories
This makes it possible to identify the purpose of the rule without opening its configuration.
FAQ
Last updated
Was this helpful?





