Data Security Center:CreateRule

The natural language of the request and response. Valid values:

• zh: Chinese
• en: English

The name of the sensitive data detection rule.

The content type of the sensitive data detection rule. Valid values:

• 0: keyword
• 2: regular expression

The content of the sensitive data detection rule. The content can be a regular expression or keywords used to match sensitive fields or text.

The statistical expression.

The risk level ID f data that hits the sensitive data detection rule. Valid values:

• 1: N/A, which indicates that no sensitive data is detected.
• 2: S1, which indicates sensitive data at level 1.
• 3: S2, which indicates sensitive data at level 2.
• 4: S3, which indicates sensitive data at level 3.
• 5: S4, which indicates sensitive data at level 4.

The feature type of the rule. Valid values:

• 1: data detection rule
• 2: audit rule
• 3: anomalous activity detection rule
• 99: custom rule

The name of the service to which the columns belong. Valid values include MaxCompute, OSS, ADS, OTS, and RDS.

The ID of the service to which the data asset belongs. Valid values include 1, 2, 3, 4, and 5. A value of 1 indicates MaxCompute. A value of 2 indicates Object Storage Service (OSS). A value of 3 indicates AnalyticDB for MySQL. A value of 4 indicates Tablestore. A value of 5 indicates ApsaraDB RDS.

The severity level. Valid values:

• 1: low severity level
• 2: medium severity level
• 3: high severity level

The description of the rule.

The type of the audit rule. Valid values include 1, 2, 3, 4, and 5. A value of 1 indicates Attempt to Exploit SQL Injections. A value of 2 indicates Bypass Attempt by Using SQL Injections. A value of 3 indicates Stored Procedure Abuse. A value of 4 indicates Buffer Overflow. A value of 5 indicates Error-based SQL Injection.

The status of the rule. Valid values:

• 1: The rule is enabled.
• 0: The rule is disabled.

The service for which the rule is enabled. Valid values include MaxCompute, OSS, ADS, OTS, and RDS.