Manage Scanning Rules¶

All created sensitive data scanning rules can be viewed in the list under Manage > Sensitive Data Scanning > Create.

Rules are executed from top to bottom in the list order, and their priority can be adjusted by dragging. When multiple rules match the same data, the first matched rule takes precedence.

Rule List¶

Upon entering the rule management page, the list displays the following information:

Rule Name: The custom rule name or official rule library name (rules are scanned in order);
Data Scope: The filter conditions defining the data scope scanned by this rule;
Data Type: The data type scanned by this rule (Log, LLM, Cloud Bill, etc.);
Options: Enable/Disable toggle, More Options (Edit, Operation Audit, Delete).

Single Rule Operations¶

For a single rule, click the ⋮ button on the right to perform the following operations:

Edit: Modify rule configuration (scan scope, matching rules, masking method, etc.);
Operation Audit: View the change history of this rule;
Delete: Delete this rule. After deletion, it will no longer perform masking on matching data;
Click the Enable/Disable toggle on the right side of the rule to quickly switch the rule status:
- Enabled (Green): The rule is active and scans/masks newly written data.
- Disabled (Gray): The rule is paused and no longer scans new data.

Batch Operations¶

Check the checkboxes on the left side of the rules to perform batch operations:

Batch Enable: Enable multiple disabled rules simultaneously;
Batch Disable: Disable multiple enabled rules simultaneously;
Batch Delete: Delete multiple rules simultaneously. Deleted rules cannot be recovered.

Search¶

In the Search Rule Name input box in the upper right corner, you can quickly locate rules based on rule name keywords.

Notes¶

Status changes take effect immediately: After enabling or disabling a rule, it takes effect immediately for newly written data. Historical data is not affected;
Deletion is irreversible: Deleted rules cannot be recovered. If needed again, they must be recreated;
Use batch operations with caution: Confirm the selected scope before batch deletion to avoid accidentally deleting important rules;
Rule priority: Rules higher in the list are executed first. It is recommended to place precise matching rules higher up.