On This Page

Overview

A tracking group is a label (or category) that will be assigned to content when a policy runs. A policy can contain multiple tracking groups, and each tracking group includes multiple pieces of information that determine everything from the criteria content needs to meet to be a part of the tracking group to the actions that should be taken against the content in the tracking group. The tracking groups are the heart of the policy.

Understanding Tracking Groups

Tracking groups contain multiple pieces of information: name, risk level, priority, cost, assignment rules, and actions.

Name

The A name - The group name would typically line up with an existing labeling scheme such as AIP/MIP. This is displayed in any roll-ups that are performed at the group level

Risk Level

The risk level is defined at the tracking group level, so any content within the tracking group is classified as having that defined risk. For example, if you create a tracking group "Sensitive" and set the risk level to "High," any content that meets the criteria of the assignment rules for the tracking group is considered high-risk content and will be flagged accordingly.

Priority

SkySync evaluates the tracking groups in priority order. Although a file may match the rules for multiple groups, it can only exist in one tracking group. Therefore, it will be assigned to the first group that is matched.

Cost

Each tracking group can be assigned a cost. This is the amount that a file in the tracking group could cost the company in legal fees or penalties if it remains in its current state. For example, if a file contains sensitive data and is located on a share, it could cost the company a set amount of money in fines if the company’s data were to be audited.

Assignment Rules

Assignment rules are simply a list of rules that dictate whether a file should be assigned to the group or not. Assignment rules also include a "justification" for each rule, which would be included in the audit log for traceability purposes.

The assignment rules can also contain a list of entity types that should be run against a file. Entity type assignments exist at both the policy level as well as the tracking group level. This is because there may be entity types that are more costly to run against content and should only be done when all previous tracking groups have been evaluated and ruled out. An example would be a custom classification entity type that only runs on videos to detect sensitive information.

Actions

The actions for a tracking group tell SkySync what to do with the content in each tracking group.