Creates a custom sensitive data detection rule.
Debugging
Authorization information
The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action
policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:
- Operation: the value that you can use in the Action element to specify the operation on a resource.
- Access level: the access level of each operation. The levels are read, write, and list.
- Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
- The required resource types are displayed in bold characters.
- If the permissions cannot be granted at the resource level,
All Resources
is used in the Resource type column of the operation.
- Condition Key: the condition key that is defined by the cloud service.
- Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.
Operation | Access level | Resource type | Condition key | Associated operation |
---|---|---|---|---|
yundun-sddp:CreateRule | create |
|
| none |
Request parameters
Parameter | Type | Required | Description | Example |
---|---|---|---|---|
Name | string | Yes | The name of the sensitive data detection rule. | rule-tst |
Category | integer | No | The content type of the sensitive data detection rule. Valid values:
| 0 |
Content | string | Yes | The content of the sensitive data detection rule. You can specify a regular expression or keywords that are used to match sensitive fields or text. | (?:\\D|^)((?:(?:25[0-4]|2[0-4]\\d|1\\d{2}|[1-9]\\d{1})\\.)(?:(?:25[0-5]|2[0-4]\\d|[01]?\\d?\\d)\\.){2}(?:25[0-5]|2[0-4]\\d|1[0-9]\\d|[1-9]\\d|[1-9]))(?:\\D|$) |
StatExpress | string | No | The statistical expression. | 1 |
RiskLevelId | long | No | The sensitivity level of the sensitive data that hits the sensitive data detection rule. Valid values:
| 2 |
RuleType | integer | No | The type of the sensitive data detection rule. Valid values:
| 1 |
ProductCode | string | No | The name of the service to which data in the column of the table belongs. Valid values include MaxCompute, OSS, ADS, OTS, and RDS. | RDS |
ProductId | long | No | The ID of the service to which the data asset belongs. Valid values include 1, 2, 3, 4, and 5. The value 1 indicates MaxCompute. The value 2 indicates Object Storage Service (OSS). The value 3 indicates AnalyticDB for MySQL. The value 4 indicates Tablestore. The value 5 indicates ApsaraDB RDS. | 2 |
WarnLevel | integer | No | The risk level of the alert that is triggered. Valid values:
| 2 |
Description | string | No | The description of the rule. | ID card |
ContentCategory | integer | No | The type of the content in the sensitive data detection rule. Valid values include 1, 2, 3, 4, and 5. The value 1 indicates attempts to exploit SQL injections. The value 2 indicates bypass by using SQL injections. The value 3 indicates abuse of stored procedures. The value 4 indicates buffer overflow. The value 5 indicates SQL injections based on errors. | 1 |
Status | integer | No | Specifies whether to enable the sensitive data detection rule. Valid values:
| 1 |
Target | string | No | The code of the service to which the sensitive data detection rule is applied. Valid values include MaxCompute, OSS, ADS, OTS, and RDS. | MaxCompute |
MatchType | integer | No | The match type. Valid values:
| 1 |
SupportForm | integer | No | The type of the data asset. Valid values:
Note
If you set the parameter to 1 or 2, rules that support all data assets and rules that support the queried data asset type are returned.
| 1 |
SourceIp | string | No | This parameter is deprecated. | 39.170.XX.XX |
Lang | string | No | The language of the content within the request and response. Valid values:
| zh |
Response parameters
Examples
Sample success responses
JSON
format
{
"Id": 1,
"RequestId": "208B016D-4CB9-4A85-96A5-0B8ED1EBF271"
}
Error codes
For a list of error codes, visit the Service error codes.
Change history
Change time | Summary of changes | Operation |
---|---|---|
2024-03-25 | The request parameters of the API has changed | View Change Details |
2023-12-06 | The request parameters of the API has changed | View Change Details |
2023-12-06 | The request parameters of the API has changed | View Change Details |
2023-12-06 | The request parameters of the API has changed | View Change Details |
2023-12-06 | The request parameters of the API has changed | View Change Details |
2023-12-06 | The request parameters of the API has changed | View Change Details |
2023-12-06 | The request parameters of the API has changed | View Change Details |
2023-12-06 | The request parameters of the API has changed | View Change Details |
2023-12-06 | The request parameters of the API has changed | View Change Details |
2023-12-06 | The request parameters of the API has changed | View Change Details |
2023-12-06 | The request parameters of the API has changed | View Change Details |
2023-12-06 | The request parameters of the API has changed | View Change Details |
2023-12-06 | The request parameters of the API has changed | View Change Details |
2023-12-06 | The request parameters of the API has changed | View Change Details |
2023-12-06 | The request parameters of the API has changed | View Change Details |
2023-12-06 | The request parameters of the API has changed | View Change Details |
2023-12-06 | The request parameters of the API has changed | View Change Details |
2023-12-06 | The request parameters of the API has changed | View Change Details |
2023-12-06 | The request parameters of the API has changed | View Change Details |
2023-12-06 | The request parameters of the API has changed | View Change Details |