10.3 Sensitive Information Local Control Policy
Administrators can configure a Sensitive Information Local Control Policy to manage local documents. Once the policy is set, any newly created, modified, copied, or received file that matches the sensitive information criteria will have its details recorded and trigger actions such as watermarking or encryption.
Policy Attributes Explanation
| Policy Attribute |
Description |
| Add Watermark |
Appears if the "Watermark & Traceability" module is purchased. When selected and a watermark template is specified, files triggered by the policy will be watermarked. |
| Encryption |
Appears if the "Transparent Encryption" module is purchased. When selected, unencrypted local files matching sensitive content will be encrypted. Security settings for the encrypted file, including permissions and access rights, can be configured. |
| Sensitive Information |
|
| Sensitive Content |
Select a predefined sensitive information category (configured in "Classification Management > Sensitive Information Categories") as the criteria. The client will scan files to check if the content matches the defined sensitive information. |
| Document Tags |
Files whose tag content matches the specified setting here are considered policy matches. |
| Document Security Level |
Files whose security level falls within the specified range are considered policy matches. |
| Match Any Condition |
By default, all sensitive information conditions must be met simultaneously to trigger the policy. When enabled, meeting any one condition will be considered a policy match. |
| File Type |
Specify the local file types to monitor; supports wildcards. |
| Include Scope |
Specify directories and file types to scan. Only files in these locations/types will be scanned. Multiple entries are supported. By default, all supported files on local drives are scanned. |
| Exclude Scope |
Specify directories and file types to exclude from scanning. Multiple entries are supported. |
| Application |
Specify applications that trigger local control actions. Default is <All>. |
Directory settings in the Include and Exclude scopes currently support only local drives; network drives are not supported. The directory must be a valid local path on the client machine and supports the wildcard * and the generic path {sd}. For example: {sd}users\*\Documents. Note that * can only represent a single folder level. {sd} represents the system drive root (e.g., C:\) and must be lowercase. The folder name must follow {sd} directly without a trailing backslash.
Note:
- 1. For sensitive content control, compressed files are scanned by default to detect sensitive files contained within.
- 2. If both the AnySecura Sensitive Information Local Control policy and the Document Watermark policy are triggered simultaneously, the Local Control policy takes priority, applying the watermark template specified in the Local Control policy.
Don't see what you're looking for?
