Help Center/ Data Security Center/ User Guide (ME-Abu Dhabi Region)/ Permissions Management/ DSC Custom Policies
Updated on 2022-12-29 GMT+08:00
View PDF
Share

DSC Custom Policies

Custom policies can be created to supplement the system-defined policies of DSC.

You can create custom policies in either of the following ways:

  • Visual editor: Select cloud services, actions, resources, and request conditions. This does not require knowledge of policy syntax.
  • JSON: Edit JSON policies from scratch or based on an existing policy.

Example Custom Policies

  • Example 1: Allowing a user to query the big data assets 
    {
        "Version": "1.1",
        "Statement": [
                {
                        "Effect": "Allow",
                        "Action": [
                                "dsc:bigdataAsset:list"
                                                       ]
                }
        ]
}
  • Example 2: Disallowing a user to query the OBS assets

    A deny policy must be used together with other policies. If the permissions assigned to a user contain both "Allow" and "Deny", the "Deny" permissions take precedence over the "Allow" permissions.

    The following method can be used if you need to assign permissions of the DSC FullAccess policy to a user but also forbid the user from querying the OBS asset list (dsc:obsAsset:list). Create a custom policy with the same action for denying querying the OBS asset list, and assign both policies to the group the user belongs to. Then, the user can perform all operations on DSC except querying the OBS asset list. The following is an example policy for denying querying OBS asset list.

    {
        "Version": "1.1",
        "Statement": [
                {
                        "Effect": "Deny",
                        "Action": [
                                "dsc:obsAsset:list"                                
                        ]
                },
        ]
}
  • Multi-action policy

    A custom policy can contain the actions of multiple services that are of the project-level type. The following is an example policy containing actions of multiple services:

    {
        "Version": "1.1",
        "Statement": [
                {
                        "Effect": "Allow",
                        "Action": [
                                "dsc:obsAsset:list",
                                "dsc:scanRule:list"
                        ]
                },
               {
                        "Effect": "Allow",
                        "Action": [
                                "hss:hosts:switchVersion",
                                "hss:hosts:manualDetect",
                                "hss:manualDetectStatus:get"
                        ]
                }
        ]
}
Parent topic: Permissions Management