Access management in Yandex Security Deck
Yandex Cloud users can only perform the operations on resources that are allowed by the roles assigned to them. If a user has no roles yet, they cannot perform any operations.
To allow a user or group, e.g., Yandex account, service account, federated user, user group, or system group, access to Security Deck resources, assign them the roles from the list below. Currently, a role can only be assigned for a parent resource (folder or cloud). Roles are inherited by nested resources.
Note
For more information about role inheritance, see Inheritance of access permissions in the Resource Manager documentation.
Which roles exist in the service
In Security Deck, you can manage access using both service and primitive roles.
Service roles
Yandex Cloud supports a separate list of roles for each Security Deck module. For more information, see:
- Roles for Access Transparency data analysis.
- Roles for Data Security Posture Management.
- Roles for Cloud Infrastructure Entitlement Management.
Primitive roles
Primitive roles allow users to perform actions in all Yandex Cloud services.
auditor
The auditor
role grants a permission to read configuration and metadata of any Yandex Cloud resources without any access to data.
For instance, users with this role can:
- View info on a resource.
- View the resource metadata.
- View the list of operations with a resource.
auditor
is the most secure role that does not grant any access to the service data. This role suits the users who need minimum access to the Yandex Cloud resources.
viewer
The viewer
role grants the permissions to read the info on any Yandex Cloud resources.
This role also includes the auditor
permissions.
Unlike auditor
, the viewer
role provides access to service data in read mode.
editor
The editor
role provides permissions to manage any Yandex Cloud resources, except for assigning roles to other users, transferring organization ownership, removing an organization, and deleting Key Management Service encryption keys.
For instance, users with this role can create, modify, and delete resources.
This role also includes the viewer
permissions.
admin
The admin
role enables assigning any roles, except for resource-manager.clouds.owner
and organization-manager.organizations.owner
, and provides permissions to manage any Yandex Cloud resources (except for transferring organization ownership and removing an organization).
Prior to assigning the admin
role for an organization, cloud, or billing account, make sure to check out the information on protecting privileged accounts.
This role also includes the editor
permissions.
Instead of primitive roles, we recommend using service roles with more granular access control, allowing you to implement the least privilege principle.
For more information about primitive roles, see the Yandex Cloud role reference.
See also
Hierarchy of Yandex Cloud resources