Permissions Management

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

IAM is a free service. You only pay for the resources in your account.

With IAM, you can control the access to Huawei Cloud resources through authorization. For example, some developers in your enterprise need to use HSS but you do not want them to have permissions to high-risk operations such as deleting HSS. To achieve such purpose, you can use IAM to grant them only the permissions to use HSS, but not delete HSS. With IAM, you can control their usage of HSS resources.

There are two types of IAM authorization: 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 the two types of authorization
Task name	Relationship	Permission	Authorization Method	Scenario
Policies/Roles	User-permission-authorization scope	System-defined role System-defined policy Define a policy.	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	User-Policy	System-defined policy 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

HSS supports role/policy-based authorization. By default, new IAM users do not have 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.

HSS is a project-level service deployed and accessed in specific 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 resources in the selected projects. If you set Scope to All resources, the users have permissions for resources in all region-specific projects. When accessing HSS, the users need to switch to a region where they have been authorized to use cloud services.

Table lists all system permissions of HSS. System-defined policies in role/policy-based authorization are not interoperable with those in identity policy-based authorization.

**Table 2** System-defined permissions supported by HSS
Role/Policy Name	Description	Item	Dependency
HSS Administrator	HSS administrator, who has all permissions of HSS	System-defined role	This role depends on the Tenant Guest and BSS Administrator roles.
HSS FullAccess	All HSS permissions	System-defined policy	To purchase HSS protection quotas, you must have the BSS Administrator and Tenant Guest roles.
HSS ReadOnlyAccess	Read-only permission for HSS	System-defined policy	None

Choose proper system permissions according to Common operations supported by each system policy or role.

**Table 3** Common operations supported by each system policy or role
Operation	HSS Administrator	HSSFullAccess	HSSReadOnlyAccess
Query the protected server list	√	√	√
Enable or disable protection on servers	√	√	×
Manual scan	√	√	×
Query weak password scan reports	√	√	√
Query malicious program scan results	√	√	√
Query remote login scan results	√	√	√
Query the vulnerability list	√	√	√
Query configuration scan reports	√	√	√
Query web shell scan results	√	√	√
Query risky account scan reports	√	√	√
Query password complexity policy scan reports	√	√	√
Query HSS alarms	√	√	√
Query WTP alarms	√	√	√
Perform batch operations on vulnerabilities	√	√	×
Perform batch operations on malicious programs	√	√	×
Perform operations on detected unsafe settings	√	√	×
Configure protected directories	√	√	×
Configure WTP alarms	√	√	×
Configure common login locations	√	√	×
Configure the login IP address whitelist	√	√	×
Enable or disable automatic isolation and killing of malicious programs	√	√	×
Uninstall an agent	√	√	×

Roles or Policies Required for Operations on the HSS Console

**Table 4** Roles or policies required for operations on the HSS console
Console Function	Dependency	Role/Policy Required
Select All projects and view enterprise project information	Identity and Access Management (IAM)	The IAM user has been granted the Tenant Administrator permission, or the IAM user has been granted both the HSS Administrator and Tenant Guest permissions.

Identity Policy-based Permissions Management

HSS supports identity policy-based authorization. The following table lists all identity policies in HSS. System-defined identity policies are independent from system policies in role/policy-based authorization.

**Table 5** System-defined identity policies for HSS
Policy Name	Description	Role Type
HSSAdministratorPolicy	HSS administrator, who has all permissions of HSS	System-defined identity policy
HSSReadOnlyAccessPolicy	Read-only permission for HSS	System-defined identity policy
HSSServiceLinkedAgencyPolicy	Cross-account agency association permissions of HSS.	System-defined identity policy
HSSFullAccessPolicy	Full permissions for HSS	System-defined identity policy
HSSWriteHostGroupPolicy	Server group management policy	System-defined identity policy
HSSWriteHostAllPolicy	Server management administrator policy	System-defined identity policy

Choose proper system policies by referring to the following table.

**Table 6** Common operations supported by system-defined identity policies
Operation	HSSAdministratorPolicy	HSSFullAccessPolicy	HSSReadOnlyAccessPolicy	HSSServiceLinkedAgencyPolicy	HSSWriteHostGroupPolicy	HSSWriteHostAllPolicy
Query server protection directories	√	√	√	×	×	×
Query alarm configurations	√	√	√	×	×	×
Query the status of application protection	√	√	√	×	×	×
Change protection status	√	√	×	×	×	×
Manual detection: Perform configuration detection and weak password detection on the servers specified in the policy	√	√	×	×	×	×
Uninstall an agent	√	√	×	√	×	√
Create a server group	√	√	×	√	√	√
Query the server group list	√	√	√	√	×	√
Edit server group	√	√	×	√	×	√
Delete a server group	√	√	×	√	×	√
Query server groups in the on-premises data center	√	√	√	√	×	×
Create on-premise data center server group	√	√	×	√	×	×
Copy a server policy group	√	√	×	×	×	×
Query the scan status of server vulnerabilities	√	√	√	×	×	×
Obtain asset (servers, containers, and images) statistics	√	√	√	×	×	×
Manually start a vulnerability scan	√	√	×	√	×	√
Change the status of a vulnerability	√	√	×	×	×	×
Query the vulnerability list	√	√	√	×	×	×
Query vulnerability fixing failure information	√	√	√	×	×	×