Help Center/ Managed Threat Detection/ Service Overview/ Permission Management
Updated on 2024-06-11 GMT+08:00
View PDF
Share

Permission Management

If you need to assign different permissions to employees in your enterprise to access your MTD resources, IAM is a good choice for fine-grained permissions management. IAM provides identity authentication, permissions management, and access control, helping you efficiently manage access to your MTD resources.

With IAM, you can use your account 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 MTD but must not delete MTD resources 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 MTD resources.

If your account does not need individual IAM users for permissions management, then you may skip over this section.

IAM is free. You pay only for the resources in your account. For more information about IAM, see the IAM Service Overview.

MTD Permissions

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

MTD is a project-level service deployed and accessed in specific physical regions. To assign 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. Users need to switch to the authorized region when accessing MTD.

You can grant users permissions by using roles and policies.
  • Roles: A coarse-grained authorization mechanism provided by IAM to define permissions based on users' job responsibilities. This mechanism provides a limited number of service-level roles for authorization. If one role has a dependency role required for accessing MTD, assign both roles to the users. Roles are not an ideal choice 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 MTD users the permissions to manage only a certain type of resources.