Help Center/ Web Application Firewall/ Service Overview/ WAF Permissions Management
Updated on 2024-11-18 GMT+08:00
View PDF
Share

WAF Permissions Management

To assign different permissions to employees in your enterprise to access your WAF resources, IAM is a good choice for fine-grained permissions management. IAM provides identity authentication, permissions management, and access control, helping you secure access to your cloud resources.

With IAM, you can use your Huawei ID to create IAM users for your employees, and assign permissions to the users to control their access to specific resource types. For example, some software developers in your enterprise need to use WAF resources but must not delete them or perform any high-risk operations. To achieve this result, you can create IAM users for the software developers and grant them only the permissions required for using WAF resources.

If your Huawei ID does not need individual IAM users for permissions management, then you may skip over this chapter.

IAM can be used free of charge. You pay only for the resources in your account. For more details, see IAM Service Overview.

WAF Permissions

By default, new IAM users do not have any permissions assigned. You need to add a user to one or more groups, and attach permissions policies or roles to these groups. Users inherit permissions from the groups to which they are added and can perform specified operations on cloud services based on the permissions.

WAF is a project-level service deployed and accessed in specific physical regions. To assign WAF permissions to a user group, specify the scope as region-specific projects and select projects for the permissions to take effect. If All projects is selected, the permissions will take effect for the user group in all region-specific projects. When accessing WAF, the users need to switch to a region where they have been authorized to use the WAF service.

You can grant users permissions by using roles and policies.
  • Roles: A type of coarse-grained authorization mechanism that defines permissions related to users responsibilities. Only a limited number of service-level roles for authorization are available. You need to also assign other dependent roles for the permission control to take effect. Roles are not ideal for fine-grained authorization and secure access control.
  • Policies: A fine-grained authorization mechanism that defines permissions required to perform operations on specific cloud resources under certain conditions. This mechanism allows for more flexible policy-based authorization and meets secure access control requirements. For example, you can grant WAF users only the permissions for managing a certain type of resources. Most policies define permissions based on APIs. For the API actions supported by WAF, see Permissions Policies and Supported Actions.

Table 1 lists all the system roles supported by WAF.

Table 1 System policies supported by WAF

Role/Policy Name

Description

Category

Dependencies

WAF Administrator

Administrator permissions for WAF

System-defined role

Dependent on the Tenant Guest and Server Administrator roles.

  • Tenant Guest: A global role, which must be assigned in the global project.
  • Server Administrator: A project-level role, which must be assigned in the same project.

WAF FullAccess

All permissions for WAF

System-defined policy

None.

WAF ReadOnlyAccess

Read-only permissions for WAF.

System-defined policy

Helpful Links

WAF FullAccess Policy Content

{    "Version": "1.1",    
      "Statement": [        
           {            
              "Action": [                
                "waf:*:*",                
                "lts:groups:get",                
                "lts:groups:list",                
                "lts:topics:get",                
                "lts:topics:list",                
                "smn:*:list*",                
                "vpc:*:get*",                
                "vpc:*:list*",                
                "ecs:*:get*",                
                "ecs:*:list*",                
                "elb:*:get*",                
                "elb:*:list*"            
             ],            
                "Effect": "Allow"       
          }    
                 ]
}

WAF ReadOnlyAccess Policy Content

{
    "Version": "1.1",
    "Statement": [
        {
           "Action": [
             "waf:*:get*",                
             "waf:*:list*",                
             "lts:groups:get",                
             "lts:groups:list",                
             "lts:topics:get",                
             "lts:topics:list",                
             "smn:*:list*",                
             "vpc:*:get*",                
             "vpc:*:list*",                
             "ecs:*:get*",                
             "ecs:*:list*",                
             "elb:*:get*",                
             "elb:*:list*"            
         ],            
             "Effect": "Allow"
        }
    ]
}