Data Security Center (DSC)
IAM provides system-defined identity policies to define common actions supported by cloud services. You can also create custom identity policies using the actions supported by cloud services for more refined access control.
In addition to IAM, the Organizations service also provides Service Control Policies (SCPs) to set access control policies.
SCPs do not actually grant any permissions to an entity. They only set the permissions boundary for the entity. When SCPs are attached to an organizational unit (OU) or a member account, the SCPs do not directly grant permissions to that OU or member account. Instead, the SCPs only determine what permissions are available for that member account or those member accounts under that OU. The granted permissions can be applied only if they are allowed by the SCPs.
To learn more about how IAM is different from Organizations for access control, see How IAM Is Different from Organizations for Access Control?.
This section describes the elements used by IAM custom identity policies and Organizations SCPs. The elements include actions, resources, and conditions.
- For details about how to use these elements to edit an IAM custom identity policy, see Creating a Custom Identity Policy.
- For details about how to use these elements to edit a custom SCP, see Creating an SCP.
Actions
Actions are specific operations that are allowed or denied in an identity policy.
- The Access Level column describes how the action is classified (List, Read, or Write). This classification helps you understand the level of access that an action grants when you use it in an identity policy.
- The Resource Type column indicates whether the action supports resource-level permissions.
- You can use a wildcard (*) to indicate all resource types. If this column is empty (-), the action does not support resource-level permissions and you must specify all resources ("*") in your identity policy statements.
- If this column includes a resource type, you must specify the URN in the Resource element of your identity policy statements.
- Required resources are marked with asterisks (*) in the table. If you specify a resource in a statement using this action, then it must be of this type.
For details about the resource types defined by DSC, see Resources.
- The Condition Key column contains keys that you can specify in the Condition element of an identity policy statement.
- If the Resource Type column has values for an action, the condition key takes effect only for the listed resource types.
- If the Resource Type column is empty (-) for an action, the condition key takes effect for all resources that action supports.
- If the Condition Key column is empty (-) for an action, the action does not support any condition keys.
For details about the condition keys defined by DSC, see Conditions.
- The Alias column lists the policy actions that are configured in identity policies. With these actions, you can use APIs for policy-based authorization. For details, see Policies and Identity Policies.
The following table lists the actions that you can define in identity policy statements for DSC.
|
Action |
Description |
Access Level |
Resource Type (*: required) |
Condition Key |
Alias |
|---|---|---|---|---|---|
|
dsc:authorization:get |
Grants permission to query authorization status of cloud data assets. |
permission_management |
- |
- |
- |
|
dsc:authorization:grant |
Grants permission to authorize or deauthorize cloud data assets. |
permission_management |
- |
- |
- |
|
dsc:asset:delete |
Grants permission to delete data assets. |
write |
asset * |
- |
- |
|
dsc:asset:list |
Grants permission to query data asset list. |
list |
asset * |
- |
- |
|
dsc:asset:create |
Grants permission to create data assets. |
write |
asset * |
- |
- |
|
dsc:asset:update |
Grants permission to update data asset info. |
write |
asset * |
- |
- |
|
dsc:overview:list |
Grants permission to view data security overview. |
list |
- |
- |
- |
|
dsc:maskTask:create |
Grants permission to create data masking tasks. |
write |
maskTask * |
- |
- |
|
dsc:maskTask:update |
Grants permission to update data masking tasks. |
write |
maskTask * |
- |
- |
|
dsc:maskTask:list |
Grants permission to query data masking tasks list. |
list |
maskTask * |
- |
- |
|
dsc:maskTask:get |
Grants permission to query the detail of a data masking task. |
read |
maskTask * |
- |
- |
|
dsc:maskTask:delete |
Grants permission to delete data masking tasks. |
write |
maskTask * |
- |
- |
|
dsc:maskTask:operate |
Grants permission to operate (such as start, stop, enable or disable) data masking tasks. |
write |
maskTask * |
- |
- |
|
dsc:maskTask:listSubTasks |
Grants permission to query the subtask list of a data masking task. |
list |
maskTask * |
- |
- |
|
dsc:common:operate |
Grants permission to operate DSC general resources. |
write |
- |
- |
- |
|
dsc:scanTask:create |
Grants permission to create data scan tasks. |
write |
scanTask * |
- |
- |
|
dsc:scanTask:update |
Grants permission to update data scan tasks. |
write |
scanTask * |
- |
- |
|
dsc:scanTask:delete |
Grants permission to delete data scan tasks or subtasks. |
write |
scanTask * |
- |
- |
|
dsc:scanTask:operate |
Grants permission to operate data scan tasks or subtasks. |
write |
scanTask * |
- |
- |
|
dsc:scanTask:list |
Grants permission to query the list of data scan tasks or subtasks. |
list |
scanTask * |
- |
- |
|
dsc:scanRuleGroup:update |
Grants permission to update info of scan rule groups. |
write |
- |
- |
- |
|
dsc:scanRuleGroup:list |
Grants permission to query the list of scan rule groups. |
list |
- |
- |
- |
|
dsc:scanRuleGroup:create |
Grants permission to create scan rule groups. |
write |
- |
- |
- |
|
dsc:scanRuleGroup:get |
Grants permission to query the detail of a scan rule group. |
read |
- |
- |
- |
|
dsc:scanRuleGroup:delete |
Grants permission to delete scan rule groups. |
write |
- |
- |
- |
|
dsc:scanRule:list |
Grants permission to query the list of scan rules. |
list |
scanRule * |
- |
- |
|
dsc:scanRule:create |
Grants permission to create scan rules. |
write |
scanRule * |
- |
- |
|
dsc:scanRule:update |
Grants permission to update info of scan rules. |
write |
scanRule * |
- |
- |
|
dsc:scanRule:get |
Grants permission to query the detail of a scan rule. |
read |
scanRule * |
- |
- |
|
dsc:scanRule:delete |
Grants permission to delete scan rules. |
write |
scanRule * |
- |
- |
|
dsc:scanTask:getResults |
Grants permission to query the scan results of a scan task. |
read |
scanTask * |
- |
- |
|
dsc:common:list |
Grants permission to query DSC general resource list. |
list |
- |
- |
- |
|
dsc:sensitiveData:mask |
Grants permission to perform dynamic masking for sensitive data. |
write |
- |
- |
- |
|
dsc:watermark:embed |
Grants permission to embed watermark into documents, images or databases. |
write |
- |
- |
- |
|
dsc:watermark:extract |
Grants permission to extract watermark from documents, images or databases. |
write |
- |
- |
- |
|
dsc:scanTemplate:list |
Grants permission to query scan template list. |
list |
scanTemplate * |
- |
- |
|
dsc:scanTemplate:create |
Grants permission to create scan templates. |
write |
scanTemplate * |
- |
- |
|
dsc:scanTemplate:update |
Grants permission to update scan templates. |
write |
scanTemplate * |
- |
- |
|
dsc:scanTemplate:delete |
Grants permission to delete scan templates. |
write |
scanTemplate * |
- |
- |
|
dsc:scanTemplate:get |
Grants permission to query the detail of scan templates. |
read |
scanTemplate * |
- |
- |
Each API of DSC usually supports one or more actions. Table 2 lists the supported actions and dependencies.
|
API |
Action |
Dependencies |
|---|---|---|
|
DELETE/v1/{project_id}/sdg/asset/obs/bucket/{bucket_id} |
dsc:asset:delete |
obs:bucket:GetBucketLogging |
|
obs:bucket:PutBucketLogging |
||
|
GET/v1/{project_id}/sdg/asset/obs/buckets |
dsc:asset:list |
obs:bucket:listAllMyBuckets |
|
POST/v1/{project_id}/sdg/asset/obs/buckets |
dsc:asset:create |
obs:bucket:GetBucketStorage |
|
obs:bucket:listAllMyBuckets |
||
|
PUT/v1/{project_id}/sdg/asset/{asset_id}/name |
dsc:asset:update |
- |
|
POST/v1/{project_id}/period/order |
dsc:common:operate |
bss:renewal:update |
|
bss:order:update |
||
|
GET/v1/{project_id}/period/product/specification |
dsc:common:list |
- |
|
POST/v1/{project_id}/sdg/server/mask/dbs/templates/{template_id}/operation |
dsc:maskTask:operate |
- |
|
GET/v1/{project_id}/sdg/server/mask/dbs/templates/{template_id}/tasks |
dsc:maskTask:listSubTasks |
- |
|
PUT/v1/{project_id}/sdg/smn/topic |
dsc:common:operate |
- |
|
GET/v1/{project_id}/sdg/smn/topics |
dsc:common:list |
smn:topic:list |
|
GET/v1/{project_id}/openapi/called-records |
dsc:common:list |
- |
|
POST/v1/{project_id}/sdg/scan/job |
dsc:scanTask:create |
- |
|
GET/v1/{project_id}/sdg/scan/jobs |
dsc:scanTask:list |
- |
|
GET/v1/{project_id}/sdg/server/scan/groups |
dsc:scanRuleGroup:list |
- |
|
POST/v1/{project_id}/sdg/server/scan/groups |
dsc:scanRuleGroup:create |
- |
|
DELETE/v1/{project_id}/sdg/server/scan/groups/{group_id} |
dsc:scanRuleGroup:delete |
- |
|
GET/v1/{project_id}/sdg/server/scan/rules |
dsc:scanRule:list |
- |
|
POST/v1/{project_id}/sdg/server/scan/rules |
dsc:scanRule:create |
- |
|
PUT/v1/{project_id}/sdg/server/scan/rules |
dsc:scanRule:update |
- |
|
DELETE/v1/{project_id}/sdg/server/scan/rules/{rule_id} |
dsc:scanRule:delete |
- |
|
GET/v1/{project_id}/sdg/scan/job/{job_id}/results |
dsc:scanTask:getResults |
- |
|
GET/v1/{project_id}/sdg/server/relation/jobs/{job_id}/dbs |
dsc:common:list |
- |
|
GET/v1/{project_id}/sdg/server/relation/jobs/{job_id}/dbs/{db_id}/tables |
dsc:common:list |
- |
|
GET/v1/{project_id}/sdg/server/relation/jobs/{job_id}/dbs/{table_id}/columns |
dsc:common:list |
- |
|
GET/v1/{project_id}/sdg/server/relation/jobs/{job_id}/obs/buckets |
dsc:common:list |
- |
|
GET/v1/{project_id}/sdg/server/relation/jobs/{job_id}/obs/{bucket_id}/files |
dsc:common:list |
- |
|
POST/v1/{project_id}/data/mask |
dsc:sensitiveData:mask |
- |
|
POST/v1/{project_id}/doc-address/watermark/embed |
dsc:watermark:embed |
- |
|
POST/v1/{project_id}/doc-address/watermark/extract |
dsc:watermark:extract |
- |
|
POST/v1/{project_id}/image-address/watermark/embed |
dsc:watermark:embed |
- |
|
POST/v1/{project_id}/image-address/watermark/extract |
dsc:watermark:extract |
- |
|
POST/v1/{project_id}/image-address/watermark/extract-image |
dsc:watermark:extract |
- |
|
POST/v1/{project_id}/image/watermark/embed |
dsc:watermark:embed |
- |
|
POST/v1/{project_id}/image/watermark/extract |
dsc:watermark:extract |
- |
|
POST/v1/{project_id}/image/watermark/extract-image |
dsc:watermark:extract |
- |
|
POST/v1/{project_id}/sdg/database/watermark/embed |
dsc:watermark:embed |
- |
|
POST/v1/{project_id}/sdg/database/watermark/extract |
dsc:watermark:extract |
- |
|
POST/v1/{project_id}/sdg/doc/watermark/embed |
dsc:watermark:embed |
- |
|
POST/v1/{project_id}/sdg/doc/watermark/extract |
dsc:watermark:extract |
- |
|
GET/v1/{project_id}/sdg/asset/{asset_type}/{asset_id}/detail |
dsc:common:list |
- |
|
GET /v1/{project_id}/sdg/asset/authorization |
dsc:authorization:get |
- |
Resources
A resource type indicates the resources that an identity policy applies to. If you specify a resource type for any action in Table 3, the resource URN must be specified in the identity policy statements using that action, and the identity policy applies only to resources of this type. If no resource type is specified, the Resource element is marked with an asterisk (*) and the identity policy applies to all resources. You can also set condition keys in an identity policy to define resource types.
The following table lists the resource types that you can define in identity policy statements for DSC.
|
Resource Type |
URN |
|---|---|
|
scanTask |
dsc:<region>:<account-id>:scanTask:<task-id> |
|
scanRule |
dsc:<region>:<account-id>:scanRule:<rule-id> |
|
scanTemplate |
dsc:<region>:<account-id>:scanTemplate:<template-id> |
|
maskTask |
dsc:<region>:<account-id>:maskTask:<task-id> |
|
asset |
dsc:<region>:<account-id>:asset:<asset-id> |
Conditions
DSC does not support service-specific condition keys in identity policies.It can only use global condition keys applicable to all services. For details, see Global Condition Keys.
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