Help Center/ Organizations/ User Guide/ Managing SCPs/ Actions Supported by SCP-based Authorization/ Security & Compliance/ Data Security Center (DSC)
Updated on 2024-06-21 GMT+08:00
Share

Data Security Center (DSC)

The Service Control Policies (SCPs) in the Organizations service can use these authorization elements to set access control policies.

SCPs do not actually grant any permissions to a principal. They only set the permission boundary for the principal. When SCPs are attached to a member account or an organizational unit (OU), they do not directly grant permissions to that member account or OU. Instead, the SCPs just determine what permissions are available for that member account or the member accounts under that OU.

This section describes the elements used by Organizations SCPs. The elements include actions, resources, and conditions.

For details about how to use these elements to create a custom SCP, see Creating an SCP.

Actions

Actions are specific operations that are allowed or denied in an SCP.

  • 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 a 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 SCP policy statements.
    • If this column includes a resource type, you must specify a URN for the Resource element in your identity policy statements.
    • Required resources are marked with asterisks (*) in the table.

    For details about resource types defined by DSC, see Resources.

  • The Condition Key column includes keys that you can specify in the Condition element of an SCP policy statement.
    • If the Resource Type column has values for an action, the condition key only 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 condition keys defined by DSC, see Conditions.

The following table lists the actions that you can define in SCP statements for DSC.

Table 1 Actions supported by DCS

Action

Description

Access Level

Resource Type (*: Required)

Condition Key

dsc:asset:delete

Grants permission to delete data assets.

write

asset *

-

dsc:asset:list

Grants permission to query the data asset list.

list

asset *

-

dsc:asset:create

Grants permission to add data assets.

write

asset *

-

dsc:asset:update

Grants permission to update data asset information.

write

asset *

-

dsc:maskTask:operate

Grants permission to perform operations on masking tasks (such as starting, stopping, enabling, and disabling masking tasks).

write

maskTask *

-

dsc:maskTask:listSubTasks

Grants permission to query the subtask list of a masking task.

list

maskTask *

-

dsc:common:operate

Grants permission to operate DSC generic resources.

write

-

-

dsc:common:list

Grants permission to query the DSC generic resource list.

list

-

-

dsc:scanTask:create

Grants permission to create sensitive data scanning tasks.

write

scanTask *

-

dsc:scanTask:list

Grants permission to query the list of sensitive data scanning tasks or subtasks.

list

scanTask *

-

dsc:scanTask:getResults

Grants permission to query the scan result of a single scan job.

read

scanTask *

-

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:delete

Grants permission to delete scan rule groups.

write

-

-

dsc:scanRule:list

Grants permission to query the scan rule list.

list

scanRule *

-

dsc:scanRule:create

Grants permission to create scan rules.

write

scanRule *

-

dsc:scanRule:update

Grants permission to update scan rules.

write

scanRule *

-

dsc:scanRule:delete

Grants permission to delete scan rules.

write

scanRule *

-

dsc:watermark:embed

Grants permission to embed watermarks into documents, images, or databases.

write

-

-

dsc:watermark:extract

Grant permission to extract watermarks from documents, images, or databases.

write

-

-

A DSC API usually corresponds to one or more actions. Table 2 lists the supported actions and dependencies.

Table 2 Actions and dependencies supported by DSC APIs

API

Action

Dependency

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

-

Resources

A resource type indicates the resources that an SCP policy applies to. If you specify a resource type for any action in Table 3, the resource URN must be specified in the SCP policy statements using that action, and the policy applies only to resources of this type. If no resource type is specified, the Resource element is marked with an asterisk (*) and the policy applies to all resources. You can also set condition keys in a policy to define resource types.

The following table lists the resource types that you can define in SCP policy statements for DSC.

Table 3 Resource types supported by 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 SCP policies.

DSC can use global condition keys applicable to all services. For details, see Global Condition Keys.

Parent topic: Security & Compliance