Role-based Permission Levels - Administrator Guide - 6.5 - Cortex XSOAR - Cortex - Security Operations

Cortex XSOAR Administrator Guide

Product
Cortex XSOAR
Version
6.5
Creation date
2022-09-28
Last date published
2024-03-21
End_of_Life
EoL
Category
Administrator Guide
Abstract

RBAC permission levels for Cortex XSOAR components, including investigations, jobs, scripts, playbooks, and settings. Category permission levels for user roles.

When editing rule based control (RBAC) permission levels or creating new user roles you can set permission levels to the following Cortex XSOAR components:

Component

Description

Account Management ( Multi-tenant)

Enables you to configure and manage the multi-tenant deployment, such as add/delete a host, change hosts, move to HA group, etc.

If you have Read or read/write permissions, you can select whether the role can sync content to tenant accounts.Sync Content to Tenant Accounts

Investigations

Sets the permission level generally for investigations or sets different permission levels for data and chats. You can also limit the role to exclude executing potential harmful actions when building your own integrations.

Incident table actions

Limits table actions in the Incidents page, such as delete, edit, close, and so on.

Exclusion List

Limits permissions when editing, creating, or deleting an indicator in an exclusion list.

Jobs

Limits permissions for managing jobs. Roles that have read permissions to content items, retain partial read access. If you do not want to retain partial read access, set the permission to none.

Scripts

Limits permissions for managing scripts. If the user has read/write permissions, you can enable users to create scripts that run as a Super User.

Note

When creating a script, permissions for scripts are determined by the Run as and Role fields in the automation settings. Run as determines the permissions with which the automation runs. Role determines who the automation can be seen and executed by. For more information, see Automation Permissions.

In the Script page, you can define which roles are permitted to run an automation, and according to which role the automation executes.

Caution

User roles with scripts permissions (write) can create/edit/delete scripts and access credentials data. Users with such roles should have a higher level of trust in the organization.

Playbooks

Limits permissions for creating, editing and deleting Playbooks.

You can also add, change, and remove roles from a playbook when clicking Settings in the Playbooks page.

Settings

You can set the permission level generally for all settings or split them according to the following:

Users: includes invitations and editing permissions.

Integrations: whether a user can add, edit or delete instances. Roles that have read permissions to content items, retain partial read access. If you do not want to retain partial read access, set the permission to none.

Caution

User roles with integration permissions (write) can create/edit/delete integrations and access credentials data. Users with such roles should have a higher level of trust in the organization.

Credentials: whether a user can add, edit, or delete credentials.

Administration

Limits permissions for server configurations, editing layouts for indicators and incidents, integration permissions, audit trails and the password policy.

Propagation labels ( Multi-tenant)

Enables you to do the following:

Read: Enables you to select from existing propagation labels.Manage Content Overview

Read/Write: Enables you to create new and select from existing propagation labels

Marketplace

View Marketplace: Enables you to view the Marketplace.

Install Content Pack: install, upgrade, downgrade, and delete Content Pack content.

Contribute to Marketplace: Enables you to contribute a Content Pack in the Contributions tab or generally.

Page Access

Select the pages you want the user to have access to.

Default Dashboards

Select the default dashboards for each role. If a user has not modified their dashboard, these dashboards are added automatically, otherwise users can add these dashboards to their existing dashboards.

Pre-set Role Queries

Select the Pre-set Query per Role for each of the available components.

Example Role

In the following example, the user can chat in the War Room, create widgets, create incidents, and set context entries with the !Set command. In addition, the user can view incidents, scripts, and playbooks. The user can not create indicators.

permissions-role-example.png