CNAD Advanced

If you need to assign different permissions to personnel in your enterprise to access your CNAD Advanced resources, Identity and Access Management (IAM) is a good choice for fine-grained permissions management. IAM provides functions such as identity authentication, permissions management, and access control. If your Huawei account works good for you and you do not need an IAM account to manage user permissions, then you may skip over this chapter.

IAM can be used free of charge. You pay only for the resources in your account.

With IAM, you can control the access to Huawei Cloud resources through authorization. For example, you can allow some software developers in your enterprise to access CNAD Advanced resources without giving them the ability to delete CNAD Advanced instances or perform other risky actions. To do this, you can create IAM users and assign them the appropriate permissions.

IAM supports role/policy-based authorization and identity policy-based authorization.

The differences and relationships between the two authorization models are as follows:

**Table 1** Differences between role/policy-based authorization and identity policy-based authorization
Authorization Model	Core Relationship	Permission	Authorization Method	Scenario
Role/Policy-based Authorization	User-permission-authorization scope	System-defined roles System-defined policies Custom policies	Granting a role or policy to a subject	To authorize a user, you need to add it to a user group first and then specify the scope of authorization. It is hard to provide fine-grained permissions control using authorization by user groups and a limited number of condition keys. This method is suitable for small- and medium-sized enterprises.
Identity Policy-based Authorization	User-policy	System-defined identity policies Custom identity policies	Granting an identity policy to a subject Attaching identity policies to principals	You can authorize a user by attaching an identity policy to it. User-specific authorization and a variety of key conditions allow for more fine-grained permissions control. However, this model can be hard to set up. It requires a certain amount of expertise and is suitable for medium- and large-sized enterprises.

Assume that you want to grant IAM users the permissions needed to create ECSs in CN North-Beijing4 and OBS buckets in CN South-Guangzhou. With role/policy-based authorization, the administrator needs to create two custom policies and assign both to the IAM users. With identity policy-based authorization, the administrator only needs to create one custom identity policy and configure the condition key g:RequestedRegion for the policy, and then attach the policy to the principals or grant the principals the access permissions to the specified regions. Identity policy-based authorization is more flexible than role/policy-based authorization.

Policies/identity policies and actions in the two authorization scenarios are not interoperable. You are advised to use the identity policy-based authorization model. Role/Policy-based Permissions Management and Identity Policy-based Permissions Management describe the system permissions of the two models.

For details about IAM, see IAM Service Overview.

Role/Policy-based Permissions Management

CNAD Advanced supports role/policy-based authorization. By default, new IAM users do not have any permissions. You need to add a user to one or more groups, and attach permission policies or roles to these groups. Users inherit permissions from their groups and can perform specified operations on cloud services based on the permissions.

CNAD Advanced is a project-level service and is deployed in different physical regions. When you set Scope to Region-specific projects and select the specified projects (for example, ap-southeast-2) in the specified regions (for example, AP-Bangkok), the users only have permissions for ECSs in the selected projects. If you set Scope to All resources, the users have permissions for ECSs in all region-specific projects. When accessing CNAD Advanced, users need to switch to a region where they have been authorized.

Table 2 lists all system permissions of CNAD Advanced. System-defined policies in role/policy-based authorization and identity policy-based authorization are not interoperable.

**Table 2** System-defined permissions for CNAD
Role/Policy Name	Description	Type
CNAD FullAccess	All permissions for CNAD Advanced.	System-defined policy
CNAD ReadOnlyAccess	Read-only permissions for CNAD Advanced.	System-defined policy

Table 3 describes the common operations supported by each system-defined permission of CNAD. Select the permissions as needed.

**Table 3** Common operations supported by system policy of CNAD Advanced
Operation	CNAD ReadOnlyAccess	CNAD FullAccess
Querying quotas	√	√
Querying details about a protection policy	√	√
Querying statistics	√	√
Querying asset security status	√	√
Querying weekly security statistics	√	√
Creating an alarm notification	×	√
Deleting an alarm notification	×	√
Querying an alarm notification	√	√
Upgrading an instance	×	√
Binding a protected IP address to an instance	×	√
Creating a protection policy	×	√
Updating a protection policy	×	√
Deleting a protection policy.	×	√
Binding a protection policy to a protected IP address	×	√
Removing a protection policy from a protected IP address	×	√
Adding a blacklist or whitelist rule	×	√
Deleting a blacklist or whitelist rule	×	√
Updating the tag of a protected IP address	×	√
Querying the scrubbing scope	√	√
Querying the instance list	√	√
Querying the protection policy list	√	√
Querying the list of protected IP addresses	√	√
Querying details of an instance	√	√
Querying details of a protection policy	√	√
Querying the list of protected IP addresses	√	√
Querying total traffic	√	√
Querying attack traffic	√	√
Querying the total number of data packets	√	√
Querying the number of attack packets	√	√
Querying DDoS mitigation trend	√	√
Querying the peak traffic scrubbed	√	√
Querying attack types	√	√
Querying attack events	√	√
Querying top 10 attacked IP addresses	√	√
Creating an instance	×	√

Roles or Policies Required for Operations on the CNAD Advanced Console

**Table 4** Roles or policies that are required for performing operations on the CNAD Advanced console
Console Function	Dependent Services	Policy/Role Required
Enabling LTS	Log Tank Service (LTS)	The LTS ReadOnlyAccess system policy is required to select log group and log stream names created in LTS.
Enabling alarm notifications	Simple Message Notification (SMN)	The SMN ReadOnlyAccess system policy is required to obtain SMN topic groups.
Configuring instance tags	Tag Management Service (TMS)	Tag keys can be created only after the TMS FullAccess system policy is added.
Purchasing a CNAD Instance	Enterprise Project Management Service (EPS)	You can select an enterprise project when purchasing an instance only after adding the EPS ReadOnlyAccess system policy.

Identity Policy-based Permissions Management

CNAD Advanced supports identity policy-based authorization. Table 1 lists all the system-defined identity policies for CNAD Advanced. System-defined identity policies and system-defined policies in the two authorization models are not interoperable.

**Table 5** System-defined identity policies for CNAD Advanced
Policy Name	Description	Policy Type
CNADReadOnlyPolicy	Read-only permissions for CNAD Advanced. Users granted these permissions can only view CNAD Advanced information.	System-defined identity policies
CNADFullAccessPolicy	All permissions for CNAD Advanced.	System-defined identity policies

Table 6 lists the common operations supported by system-defined identity policies of CNAD Advanced.

**Table 6** Common operations supported by system-defined identity policies of CNAD Advanced
Operation	CNADReadOnlyPolicy	CNADFullAccessPolicy
Querying quotas	√	√
Querying details about a protection policy	√	√
Querying statistics	√	√
Querying asset security status	√	√
Querying weekly security statistics	√	√
Creating an alarm notification	×	√
Deleting an alarm notification	×	√
Querying an alarm notification	√	√
Upgrading an instance	×	√
Binding a protected IP address to an instance	×	√
Creating a protection policy	×	√
Updating a protection policy	×	√
Deleting a protection policy.	×	√
Binding a protection policy to a protected IP address	×	√
Removing a protection policy from a protected IP address	×	√
Adding a blacklist or whitelist rule	×	√
Deleting a blacklist or whitelist rule	×	√
Updating the tag of a protected IP address	×	√
Querying the scrubbing scope	√	√
Querying the instance list	√	√
Querying the protection policy list	√	√
Querying the list of protected IP addresses	√	√
Querying details of an instance	√	√
Querying details of a protection policy	√	√
Querying the list of protected IP addresses	√	√
Querying total traffic	√	√
Querying attack traffic	√	√
Querying the total number of data packets	√	√
Querying the number of attack packets	√	√
Querying DDoS mitigation trend	√	√
Querying the peak traffic scrubbed	√	√
Querying attack types	√	√
Querying attack events	√	√
Querying top 10 attacked IP addresses	√	√
Creating an instance	×	√

Identity Policies on Which Console Functions Depend

**Table 7** Identity policies of services on which Cloud Native Anti-DDoS Basic console functions depend
Console Function	Dependent Services	Policy/Role Required
Enabling LTS	Log Tank Service (LTS)	The log groups and log streams created in LTS can be selected only after the LTSReadOnlyAccessPolicy system identity policy is added.
Enabling alarm notifications	Simple Message Notification (SMN)	SMN topic groups can be obtained only after the SMNReadOnlyPolicy system identity policy is added.
Configuring instance tags	Tag Management Service (TMS)	Tag keys can be created only after the TMSReadOnlyPolicy system identity policy is added.
Purchasing a CNAD Advanced instance	Enterprise Project Management Service (EPS)	Enterprise projects can be selected only after the EPSReadOnlyPolicy system identity policy is added.