SecMaster Custom Policies

Example Custom Policies

• Example 1: Authorization for alert list search permission and permission execution analysis

  {
      "Version": "1.1",
      "Statement": [
          {
              "Effect": "Allow",
              "Action": [
                  "secmaster:alert:list",
                  "secmaster:search:createAnalysis"
              ]
          }
      ]
  }

• Example 2: Preventing users from modifying alert 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 SecMaster FullAccess policy assigned to modify alert configurations. Assign both SecMaster FullAccess and the custom policies to the group to which the user belongs. Then the user can perform all operations except modifying alert configurations on SecMaster. The following is an example of a deny policy:

  { 
           "Version": "1.1", 
      "Statement": [
          {
              "Effect": "Deny",
              "Action": [
                  "secmaster:alert:updateType"
              ]
          }
      ]
  }

• 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": [
                  "secmaster:alert:get",
                  "secmaster:alert:update"
              ]
          },
          {
              "Effect": "Allow",
              "Action": [
                  "hss:vuls:set",
                  "hss:vuls:list"
              ]
          }
      ]
  }