SA Custom Policies

Custom policies can be created to supplement the system-defined policies of SA. For the actions that can be added to custom policies, see SA Permissions and Supported Actions.

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.

For more details, see Creating a Custom Policy. The following section contains examples of common SA custom policies.

Example Custom Policies

Example 1: Authorizing a user to obtain the alarm list and threat analysis results

{
    "Version": "1.1",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": [
                "sa:threatevent:getList",
                "sa:threatevent:getAnalyze"
            ]
        }
    ]
}

Example 2: Preventing users from modifying alarm configurations
A deny policy must be used together with other policies. If the policies assigned to a user contain both Allow and Deny actions, the Deny actions take precedence over the Allow actions.

The following method can be used to create a custom policy to disallow users who have the SA FullAccess policy assigned to modify alarm configurations. Assign both SA FullAccess and the custom policies to the group to which the user belongs. Then the user can perform all operations on SA except modifying alarm configurations. The following is an example of a deny policy:
```
{ 
         "Version": "1.1", 
         "Statement": [ 
                 { 
                         "Action": [ 
                                 "sa:subscribe:operate" 
                         ], 
                         "Effect": "Deny" 
                 } 
         ] 
 }
```

Example 3: Defining permissions for multiple services in a policy

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

{
    "Version": "1.1",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": [
                "sa:cssb:operate",
                "sa:cssb:get"
            ]
        },
        {
            "Effect": "Allow",
            "Action": [
                "obs:bucket:GetReplicationConfiguration",
                "obs:bucket:PutReplicationConfiguration",
                "obs:bucket:DeleteReplicationConfiguration"
            ],
            "Resource": [
                "obs:*:*:bucket:*"
            ]
        }
    ]
}

Parent topic: Permissions Management

Previous topic: Creating a User and Granting Permissions

Next topic: SA Permissions and Supported Actions