To prevent business losses caused by employees sending out sensitive files, use the outbound file detection feature of SASE (Secure Access Service Edge) to detect and control these transfers in real time. By configuring data classification detection rules, you can identify and manage data leakage risks. This document describes how to configure these detection rules for outbound files.
Prerequisites
-
You have purchased the Office Data Protection Edition of SASE for internet access security. For more information, see Billing and Get started.
-
The SASE client installed on your corporate endpoints is version 4.3.1 or later.
Configuration methods
When you configure data classification detection rules for outbound files, you can choose one of the following three methods based on your business needs. These methods improve the accuracy and efficiency of rule configuration while ensuring the security and compliance of outbound file transfers.
-
Built-in rules: SASE provides built-in data classification detection rules for common enterprise file types. You can select these rules when creating an outbound policy to efficiently manage and protect sensitive data.
-
Custom rules: You can create custom rules based on multiple dimensions, including file content, file names, file name extensions, and data sources.
-
AI recommendation library: You can add detection rules from the AI recommendation library directly to your configured data categories, which greatly simplifies the configuration process.
WarningTo use detection rules from the AI recommendation library, you must first complete asset mapping. A large model then analyzes these files and generates detection rules. For more information, see Create an asset mapping task.
Configure a custom rule
Step 1: Create data elements
You can configure data elements using multiple dimensions, such as sensitive word libraries for file content (like dictionaries and regular expressions), file name extensions, and data sources.
Log on to the Secure Access Service Edge console.
-
In the left-side navigation pane, choose .
-
On the Data Classification page, click the Data Elements tab. Configure data elements as described in the following table.
Tab
Description
Actions
Dictionaries and Regular Expressions
Configure a sensitive word library. You can use a dictionary or regular expression to detect file content.
Create a sensitive word library:
-
Click Create Sensitive Word Library.
-
In the Create Sensitive Word Library panel, configure the following parameters and click OK.
-
Name: Enter a name for the sensitive word library.
-
Type: Configure a dictionary or regular expression to validate file content.
-
Dictionary: Customize the dictionary content. You can add multiple entries, separated by commas (,), and press Enter to confirm each entry.
-
Regular Expression: Enter a custom regular expression. For example,
([A-Za-z0-9]+)matches one or more uppercase letters, lowercase letters, or digits. After you configure the regular expression, click Test Regular Expression and enter sample text to validate the expression.
-
-
Other actions:
-
Filter data by criteria such as type and data source.
-
In the Actions column, click Delete to remove a library that is not associated with any rules.
ImportantIf a library is associated with a detection rule, you must first disassociate it from the rule before you can delete the library.
Data Types
SASE provides several built-in intelligent algorithm classifications. When you configure a detection rule, you can assign an algorithm classification. SASE then uses the selected classification and file type for efficient and accurate detection of file content.
In the Associated Rules column, you can view the detection rules that are configured with the algorithm classification.
Data Levels
SASE provides several built-in intelligent algorithm levels. When you configure a detection rule, you can assign an algorithm level. SASE then uses the selected algorithm level, general definitions of data sensitivity, and the amount of sensitive data for efficient and accurate detection of file content.
In the Associated Rules column, you can view the detection rules that are configured with the algorithm level.
File Name Extensions
SASE provides built-in file name extensions. You can also define custom file name extensions to detect files.
Add a file name extension:
-
Click Add File Extension.
-
In the Add File Extension panel, enter a file name extension and click OK.
Other actions:
-
Filter data by data source.
-
In the Actions column, click Delete to remove a custom file name extension.
Data Source
Add Web Applications and Code Repository. When users send files downloaded from these sources, the system automatically triggers the detection process. This helps you monitor the flow of sensitive data and ensure compliance with security policies.
Add an application:
-
Click Create Application.
-
In the Add Data Source panel, configure the following parameters:
-
Web Applications
-
Application Name: Enter a name for the application.
-
Application Address: Enter the URL and file path. Click Add to enter multiple application addresses. For example:
-
URL: www.aliyun.com/api/file
-
Path: /api/file
-
-
-
Code Repository
-
Repository Name: Enter a name for the repository.
-
Git Repository URL: Enter the Git repository URL.
-
-
-
-
After you complete the configuration, click OK.
Step 2: Create a custom detection rule
SASE provides default data classification detection rules for common file types that you can use when you configure file exfiltration policies. You can also create custom detection rules based on your business requirements and validate them against files reported by the asset mapping feature to ensure accuracy and applicability.
Create a detection rule
Log on to the Secure Access Service Edge console.
-
In the left-side navigation pane, choose .
-
On the Data Classification page, click the Identification Rules tab.
-
In the Data Category area on the left, click Create, and then click Create Category.
-
In the Create Category dialog box, enter a category name and click OK.
-
To the right of the data category you created, click Create Rule Group to create a detection rule for this data category.
-
In the Create Group panel, configure the following parameters. Then, click OK.
Parameter
Description
Rule Name
The name of the detection rule. The name must be 2 to 32 characters long and can contain Chinese characters, letters, digits, hyphens (-), and underscores (_).
Data Category
Select the data category for the group.
Sensitivity Level
The sensitivity level of the file. Valid values:
Rule Configuration
Configure the conditions for the sensitive data detection rule.
In the rule configuration section, click + Add Condition to add a rule condition, or click + Add Group to add a condition group. For each condition, select a field (such as Data source), an operator (such as Include Any), and a match value (such as RDS database).
For example, a rule configured as "File name includes salary" triggers detection if a file name contains the word "salary".
We recommend configuring multiple conditions to ensure your policy accurately matches file content based on your business needs. You can set the logical relationship between multiple conditions or groups to AND or OR.
-
Detection rule parameters
Other operations
For custom detection rules or rules generated by the AI recommendation library, you can perform operations such as editing, enabling, or disabling them. You can also create sub-rules under existing detection rules for more fine-grained management and flexible configuration.
-
Edit: Click Edit Group Information to view and modify a configured detection rule.
-
Enable/Disable: Click the Rule Status switch to enable or disable the detection rule.
Click the More icon (⋮) to the right of a category node and select New Rule, Edit, or Copy.
Related documents
-
For more information about intelligent rule generation, see Intelligent rule generation.
-
For more information about how to use data classification detection rules in an outbound file detection policy, see Configure an outbound file detection policy.
-
For more information about asset mapping, see Create an asset mapping task.