Assigning roles for a trail

If you do not have the Yandex Cloud CLI yet, install and initialize it.

The folder used by default is the one specified when creating the CLI profile. To change the default folder, use the yc config set folder-id <folder_ID> command. You can also specify a different folder for any command using --folder-name or --folder-id.

If you access a resource by its name, the search will be limited to the default folder. If you access a resource by its ID, the search will be global, i.e., through all folders based on access permissions.

1. See the description of the CLI command for assigning roles for a trail:

   yc audit-trails trail set-access-bindings --help
   

2. Get a list of trails:

   yc audit-trails trail list
   

   Result:

   +----------------------+--------------+--------+-------------------+
   |          ID          |     NAME     | STATUS |      FILTERS      |
   +----------------------+--------------+--------+-------------------+
   | cnp82sb0phnm******** | trailfromapi | ACTIVE | storage compute   |
   |                      |              |        | management.events |
   | cnp8v52idttr******** | tf-trail     | ACTIVE | storage compute   |
   |                      |              |        | mdb.postgresql    |
   | cnpnkcubr529******** | test-2       | ACTIVE | compute           |
   +----------------------+--------------+--------+-------------------+
   

3. Run the following command to assign a role for a trail:

   yc audit-trails trail set-access-bindings \
     --id <trail_ID> \
     --access-binding role=<role>,subject=<subject_type>:<subject_ID>
   

   Where:

   • --id: ID of the digital signature key pair.

   • Where --access-binding is the role and the subject the role is assigned to.

     Subject designations

     To indicate a subject, use the --subject parameter in <subject_type>:<ID> format. For some subject types, the Yandex Cloud CLI provides separate parameters instead of --subject, where you only need to specify the subject name or ID without the type. Possible subject designations and matching CLI parameters:

     Subject type	Subject designation	Yandex Cloud CLI parameter
     userAccount	userAccount:<user_ID>	--user-account-id or --user-yandex-login
     serviceAccount	serviceAccount:<service_account_ID>	--service-account-id or --service-account-name
     federatedUser	federatedUser:<user_ID>	--user-account-id
     group	group:<group_ID>	--group-members
     system	system:allAuthenticatedUsers (All authenticated users group)	--all-authenticated-users
     	system:allUsers (All users group)	—
     	system:group:organization:<organization_ID>:users (All users in organization X group)	--organization-users
     	system:group:federation:<federation_ID>:users (All users in federation N group)	--federation-users
     	system:group:userpool:<pool_ID>:users (All users in userpool P group)	—

   Provide a separate --access-binding parameter for each role. Here is an example:

   yc audit-trails trail set-access-bindings \
     --id <trail_ID> \
     --access-binding role=<role1>,subject=<subject_type>:<subject_ID> \
     --access-binding role=<role2>,subject=<subject_type>:<subject_ID> \
     --access-binding role=<role3>,subject=<subject_type>:<subject_ID>