REST Resource: projects.locations.instances.socRoles

Resource: SocRole

This service is available for customers who migrated SOAR to a customer managed project and have the Chronicle API enabled. Conventionally, different access rights are assigned to different SOC roles, but within your organization, you can experiment with the permission levels and environments to determine the full scope of responsibility for each user group in the Google Security Operations platform. The Google Security Operations platform comes with predefined SOC roles but customized roles can be added.

JSON representation 
{
  "name": string,
  "displayName": string,
  "defaultRole": boolean,
  "additionalRolesAccess": [
    string
  ]
}
Fields
name

string

Identifier. The unique name(ID) of the SocRole. Format: projects/{project}/locations/{location}/instances/{instance}/socRoles/{socRole}
displayName

string

Required. Name of the soc-role. MAX_NAME_LENGTH = 256.
defaultRole

boolean

Optional. One of the roles can be set as default. The default role will have all new cases automatically assigned to it. Note, there may not be any default role, but the default role cannot be deleted once set. Once a role is set as default the previous one will become non-default.
additionalRolesAccess[]

string (int64 format)

Optional. Additional roles users associated with this role will have access to. This will affect which cases they can see in the Google Security Operations platform.

Methods

create

 Creates a SocRole.

delete

 Deletes a SocRole.

get

 Gets a SocRole.

list

 Lists SocRoles.

patch

 Updates a SocRole.