- What's New
- Function Overview
- Service Overview
- Billing
- Getting Started
-
User Guide
- Service Provisioning
- Allowing or Disallowing Access to Cloud Assets
- Asset Map
- Asset Management
- Sensitive Data Identification
- Policy Center
- Data Asset Protection
- Data Security Operations
- Alarm Notifications
- Multi-Account Management
- Permissions Management
- Key DSC Operations
- Best Practices
-
API Reference
- Before You Start
- Calling APIs
-
API Description
- Data Watermarking
- Resource Management
- Dynamic Data Masking
- Alarm Notifications
-
Image Watermarking
- Injecting Invisible Watermarks into Images
- Extracting Invisible Text Watermarks
- Extracting Invisible Watermarks from Images
- Injecting Invisible Watermarks into Images (Image Addresses)
- Extracting Dark Watermarks from Images (Image Addresses)
- Extracting Invisible Image Watermarks from Images (Image Addresses)
- Asset Management
- Document Watermarking
-
Sensitive Data Discovery
- Querying the Identification Task List
- Querying the Result of an Identification Task
- Viewing the Rule List
- Creating a Sensitive Data Scanning Rule
- Modifying a Sensitive Data Scanning Rule
- Deleting a Sensitive Data Scanning Rule
- Querying Sensitive Data Scanning Rule Groups
- Creating a Sensitive Data Scanning Rule Group
- Deleting a Sensitive Data Scanning Rule Group
- Creating a Sensitive Data Scanning Task
- Deleting a Sensitive Data Scanning Task
- Static Data Masking
- API Call Records
- Appendixes
- SDK Reference
-
FAQs
- Product Consulting
- Regions and AZs
- Asset Authorization
-
Sensitive Data Identification and Masking
- What Services Can Use DSC to Scan for Sensitive Data?
- How Long Does It Take for DSC to Identify and Mask Sensitive Data?
- What Are the Built-in Identification Rules of DSC?
- What Are the Identification Rules in the Built-in Identification Template of DSC?
- Does Data Masking Affect My Raw Data?
- Does DSC Have Specific Requirements on the Character Set for Which Sensitive Data Is to Be Identified and Masked?
- Why Cannot I Find a Table in an Existing Database When Creating a Database Data Masking Task?
- Data Watermarking
- Data Usage Audit
- Videos
-
More Documents
-
User Guide (ME-Abu Dhabi Region)
- Service Overview
- Service Provisioning
- Assets
- Overview
- Sensitive Data Identification
- Data Masking
- Data Watermarking
- Alarm Notifications
- Permissions Management
-
FAQs
- Product Consulting
- Adding Data Assets
-
Sensitive Data Identification and Masking
- What Services Can Use DSC to Scan for Sensitive Data?
- How Long Does It Take for DSC to Identify and Mask Sensitive Data?
- Which Types of Sensitive Data Can Be Identified by DSC?
- Does Data Masking Affect My Raw Data?
- Does DSC Have Specific Requirements on the Character Set for Which Sensitive Data Is to Be Identified and Masked?
- How Do I Add Multiple Identification Rule Groups?
- Data Watermarking
- Change History
-
API Reference (ME-Abu Dhabi Region)
- Before You Start
- Calling APIs
-
API Description
- Data Watermarking
- Resource Management
- Dynamic Data Masking
- Alarm Notifications
-
Image Watermarking
- Injecting Invisible Watermarks into Images
- Extracting Invisible Text Watermarks
- Extracting Invisible Watermarks from Images
- Injecting Invisible Watermarks into Images (Image Addresses)
- Extracting Dark Watermarks from Images (Image Addresses)
- Extracting Invisible Image Watermarks from Images (Image Addresses)
- Asset Management
- Document Watermarking
-
Sensitive Data Discovery
- Querying the Identification Task List
- Querying the Result of an Identification Task
- Viewing the Rule List
- Creating a Sensitive Data Scanning Rule
- Modifying a Sensitive Data Scanning Rule
- Deleting a Sensitive Data Scanning Rule
- Querying Sensitive Data Scanning Rule Groups
- Creating a Sensitive Data Scanning Rule Group
- Deleting a Sensitive Data Scanning Rule Group
- Creating a Sensitive Data Scanning Task
- Querying the Database Lineage Graph
- Querying the Table Lineage Graph in Pages
- Querying Data Linage Graph at the Column Level
- Querying the OBS Bucket Lineage Graph
- Querying the OBS File Linage Graph in Pages
- Static Data Masking
- API Call Records
- Appendixes
- Change History
-
User Guide (ME-Abu Dhabi Region)
- General Reference
Show all
Copied.
Adding a Rule
An identification rule group, as a service logic group, includes scattered rules. A rule group is the prerequisite for operating a sensitive data identification task.
Constraints
You can add a built-in rule or customized rule. Built-in rules cannot be added, edited, and deleted.
Procedure
- Log in to the management console.
- Click
in the upper left corner of the management console and select a region or project.
- In the navigation pane on the left, click
and choose Security > Data Security Center.
- In the navigation pane, choose Sensitive Data Identification > Identification Rule.
Figure 1 Rules
- In the upper left corner of the rule list, click Add Rule.
- In the displayed dialog box, configure basic parameters. For parameter details, see Table 1.
Figure 2 Adding an identification rule
Table 1 Parameters for adding an identification rule Name
Description
Example Value
Rule
You can customize a rule name.
The rule name must meet the following requirements:
- Contain 1 to 255 characters.
- Consist of letters, digits, underscores (_), and hyphens (-).
- Be unique.
N/A
Type
Set it to Keyword or Regular expression.
- Keyword: Indicates that the rule can be executed using keywords.
- Regular expression: A regex follows concise, flexible principles to match (specify and identify) characters, words, and patterns.
Keyword
Keyword
This parameter is displayed when Type is set to Keyword.
- Logic: Select a logical relationship for keywords.
- AND: All keywords are included.
- OR: Only one keyword is included.
- Content: Enter a keyword. You can click
to add a maximum of 10 keywords.
and, Zhang San
Regular Expression
This parameter is displayed when Type is set to Regular expression.
N/A
Risk Level
Select the risk level for the rule.
The risk level ranges from 1 to 10. Levels 1 to 3 indicate low risks, 4 to 7 indicate medium risks, and 8 to 10 indicate high risks.
5 (Medium)
Minimum Matching Times
Number of rule hits. If the number of rule hits reaches the set value, the information will be marked as sensitive information.
2
Description
(Optional) This parameter is used to differentiate this rule from others.
N/A
- Click OK.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot