Access management Audit Trails

In this section, you will learn:

• Which resources you can assign a role for.
• Which roles exist in the service.

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 audit-trails.admin or one of the following roles for that resource:

• admin
• resource-manager.admin
• organization-manager.admin
• resource-manager.clouds.owner
• organization-manager.organizations.owner

Which resources you can assign a role forWhich 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 trail via the YC CLI or the Yandex Cloud API.

Which roles exist in the serviceWhich roles exist in the service

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 rolesService roles

audit-trails.auditoraudit-trails.auditor

The audit-trails.auditor role enables viewing the list of trails and info on them, as well as the info on the relevant cloud, folder, and Audit Trails quotas.

audit-trails.vieweraudit-trails.viewer

The audit-trails.viewer role enables reading audit logs and viewing the list of trails and info on them, as well as the info on the relevant cloud, folder, and Audit Trails quotas.

This role also includes the audit-trails.auditor permissions.

audit-trails.editoraudit-trails.editor

The audit-trails.editor role enables managing trails and reading audit logs.

Users with this role can:

• View the list of trails and info on them, as well as create, modify, and delete them.
• Read audit logs.
• View info on the relevant cloud and folder.
• View info on the Audit Trails quotas.

This role also includes the audit-trails.viewer permissions.

audit-trails.adminaudit-trails.admin

The audit-trails.admin role enables managing trails and user access to them, as well as reading audit logs.

Users with this role can:

• View info on access permissions assigned to trails and modify such permissions.
• View the list of trails and info on them, as well as create, modify, and delete them.
• Read audit logs.
• View info on the relevant cloud and folder.
• View info on the Audit Trails quotas.

This role also includes the audit-trails.editor permissions.

audit-trails.configVieweraudit-trails.configViewer

The audit-trails.configViewer role enables viewing the list of trails and info on them, as well as the info on the relevant cloud, folder, and Audit Trails quotas.

This role is no longer available. Please use audit-trails.auditor instead.

Primitive rolesPrimitive roles

Primitive roles allow users to perform actions in all Yandex Cloud services.

auditorauditor

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.

viewerviewer

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.

editoreditor

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.

adminadmin

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 needWhat roles do I need

The table shows actions and minimum roles required to perform them. You can always assign a role offering more permissions than the one specified in the table. For example, instead of audit-trails.configViewer, you can assign the audit-trails.editor role.

Action	Role
Viewing information about a trail	audit-trails.auditor
Collecting and viewing audit events in a trail	audit-trails.viewer
Creating a trail	audit-trails.editor
Editing a trail	audit-trails.editor
Deleting a trail	audit-trails.editor
Managing roles of other users for a trail	audit-trails.admin

What's nextWhat's next

• Review the audit log structure.
• See an example of uploading audit logs to Cloud Logging.