Access management in Yandex Lockbox
In this section, you will learn:
- Which resources you can assign a role for.
- Which roles exist in the service.
- Which roles are required for particular actions.
About access management
In Yandex Cloud, all transactions are checked in Yandex Identity and Access Management. If a subject does not have the required permission, the service returns an error.
To grant permissions for a resource, assign roles for this resource to the subject that will perform the operations. You can assign roles to a Yandex account, service account, federated users, user group, system group, or public group. For more information, see How access management works in Yandex Cloud.
Roles for a resource can be assigned by users who have the lockbox.admin role or one of the following roles for that resource:
adminresource-manager.adminorganization-manager.adminresource-manager.clouds.ownerorganization-manager.organizations.owner
Which resources you can assign a role for
You can assign a role to an organization, cloud, or folder. The roles assigned for organizations, clouds, or folders also apply to nested resources.
You can assign a role for a secret in the management console or using the Yandex Cloud CLI, API, or Terraform.
Which roles exist in the service
You can manage access to secrets using both service and primitive roles.
The chart below shows which roles are available in the service and how they inherit each other's permissions. For example, the editor role includes all the permissions of viewer. You can find the description of each role under the chart.
Service roles
lockbox.auditor
The lockbox.auditor role enables viewing info on secrets and on access permissions assigned to them, as well as details on Yandex Lockbox quotas and folder metadata.
lockbox.viewer
The lockbox.viewer role enables viewing info on secrets and access permissions assigned to them, as well as info on the relevant folder and Yandex Lockbox quotas.
This role also includes the lockbox.auditor permissions.
lockbox.editor
The lockbox.editor role enables managing secrets and their versions, as well as viewing info on access permissions assigned to secrets.
Users with this role can:
- View info on secrets and on access permissions assigned to them, as well as create, activate, deactivate, and delete secrets.
- Modify secret version metadata, create and delete secret versions, as well as change current secret versions, schedule deleting a secret version, or cancel a scheduled deletion.
- View information on the relevant folder.
- View details on Yandex Lockbox quotas.
This role also includes the lockbox.viewer permissions.
lockbox.admin
The lockbox.admin role enables managing secrets, their versions, and access to them, as well as viewing secret contents.
Users with this role can:
- View info on access permissions assigned to secrets and modify such permissions.
- View info on secrets, including secret contents.
- Create, activate, deactivate, and delete secrets.
- Modify secret version metadata, create and delete secret versions, as well as change current secret versions, schedule deleting a secret version, or cancel a scheduled deletion.
- View information on the relevant folder.
- View details on Yandex Lockbox quotas.
This role also includes the lockbox.editor and lockbox.payloadViewer permissions.
lockbox.payloadViewer
The lockbox.payloadViewer role enables viewing secret contents.
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. This ensures more selective access control and implementation of the principle of least privilege.
For more information about primitive roles, see the Yandex Cloud role reference.
What roles do I need
The table below lists the roles required to perform a particular action. You can always assign a role offering more permissions than the one specified. For example, you can assign the editor role instead of viewer.
| Action | lockbox.admin |
lockbox.editor |
lockbox.viewer |
lockbox.payloadViewer |
kms.keys.encrypterDecrypter |
|---|---|---|---|---|---|
| Create and delete secrets | - | - | - | ||
| Change the metadata of the secret | - | - | - | ||
| Read the metadata of the secret | - | - | |||
| Change the content of the secret version | - | - | - | ||
| Read the content of the secret version | - | - | - | ||
| Control access to the secret | - | - | - | - | |
| Secret encryption and decryption operations | - | - | - | - |