Authorizes Data Security Center (DSC) to scan data assets. The data assets can be a database, a project, or a bucket.
Operation description
You can call this operation to authorize DSC to scan data assets to ensure the security of the data assets.
Limits
You can call this operation up to 10 times per second per account. If the number of the calls per second exceeds the limit, throttling is triggered. As a result, your business may be affected. We recommend that you take note of the limit when you call this operation.
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 Resourcesis 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:CreateDataLimit | create |
|
| none |
Request parameters
| Parameter | Type | Required | Description | Example |
|---|---|---|---|---|
| ResourceType | integer | Yes | The type of service to which the data asset belongs. Valid values:
| 1 |
| ServiceRegionId | string | No | The region in which the data asset resides. Valid values:
| cn-hangzhou |
| ParentId | string | No | The name of the data asset. | test-11** |
| UserName | string | No | The username that is used to access the database. | yhm |
| Password | string | No | The password that is used to access the database. | passwd |
| AuditStatus | integer | No | Specifies whether to enable the security audit feature. Valid values:
| 1 |
| AutoScan | integer | No | Specifies whether to automatically trigger a re-scan after a rule is modified. Valid values:
Note
When a re-scan is triggered, DSC scans all data in your data asset.
| 1 |
| LogStoreDay | integer | No | The retention period of raw logs after you enable the security audit feature. Unit: days. Valid values:
| 30 |
| EngineType | string | No | The database engine that is run by the instance. Valid values:
| MySQL |
| Port | integer | No | The port that is used to connect to the database. | 3306 |
| OcrStatus | integer | No | Specifies whether to enable optical character recognition (OCR). Valid values:
| 0 |
| EventStatus | integer | No | Specifies whether to enable anomalous event detection. Valid values:
| 1 |
| Enable | integer | No | Specifies whether to enable sensitive data detection. Valid values:
Note
If this is your first time to authorize DSC to access the data asset, the default value is 1. If this is not your first time to authorize DSC to access the data asset, the default value is the same as that used in the last authorization operation. Both 1 and 0 are possible.
| 1 |
| SamplingSize | integer | No | The number of sensitive data samples that are collected after sensitive data detection is enabled. Valid values:
| 0 |
| CertificatePermission | string | No | The permissions. Valid values:
| ReadOnly |
| FeatureType | integer | No | This parameter is deprecated. | 2 |
| SourceIp | string | No | This parameter is deprecated. | 39.170.XX.XX |
| Lang | string | No | The language of the content within the request and response. Default value: zh_cn. Valid values:
| zh_cn |
Response parameters
Examples
Sample success responses
JSONformat
{
"Id": 1,
"RequestId": "7C3AC882-E5A8-4855-BE77-B6837B695EF1"
}Error codes
For a list of error codes, visit the Service error codes.
Change history
| Change time | Summary of changes | Operation |
|---|---|---|
| 2024-07-02 | The request parameters of the API has changed | View Change Details |
| 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 |