Role-based Permission Levels

Configure role-based permission levels in Cortex XSOAR 6.13.

When editing rule-based control (RBAC) permission levels or creating new 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.
Data	Sets the permission level generally for data related to investigations, dashboards, and reports. If you select none, the user role cannot view and edit incidents, indicators, dashboards, and reports. When Read/Write is selected, you can define the following: Granular data permissions Execute potential harmful actions - allows executing integration commands that are marked as Potentially Harmful in the integration code/settings. You would be able to run this from the XSOAR CLI. Playbook tasks that use these commands would not be affected, as they are run by the DBot user as part of playbook execution. Edit incident properties - allows editing an Incident's fields from the layout or via the Actions menu. Change incident status - allows closing or reopening an incident. Delete incident - allows deleting incidents. We recommend only granting this permission to the default Admin or select Administrators. Note Users with Delete incident permission but without Administration Read/Write permissions can delete incidents from the main Incidents table but not from the Actions menu inside the incident. Manage the Work Plan - allows interacting with the Playbook on the Incident. Edit indicators - allows editing indicators either from the Threat Intel pane, or when viewing the Indicator via it’s full layout or quick view tab. Edit layouts (incidents, indicators, and Threat Intel Reports) Note If you want to limit dashboards and reports but allow other permissions, you need to remove access to those pages in the Page Access section. Incident table actions. Limit table actions in the Incidents page, such as delete, edit, and close. Tip If you want to enable chat in the War Room, but exclude permissions for everything else, you should give the role read/write permissions under Data but remove all other granular data permissions. Also remove permissions in Integrations (under Settings). This leaves the role with access to chat only. If you want to limit specific page access such as dashboards and reports, you can limit permission in the Page Access section.
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 role has read/write permissions, you can enable user roles 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 and Roles: Includes invitations and editing permissions. Note If selecting none, it does not affect the ability to see a list of users when assigning users to an incident and other workflows. Integrations: Whether a role can add, edit or delete instances, pre-process rules, classify and map incidents and indicators. Roles that have read permissions for 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. Integration Permissions: Sets the permissions in the Integration Permissions page. Integration permissions enable you to assign different permission levels for the same command in each instance. None: The user role cannot view the page. Read: The user role can view the page. Read/Write: The user role can view and edit permissions. API Keys: Whether a role can create/delete API keys, or has read permission. Note API Key Read + Admin Read: Users can only view their own API keys (a key is attached to the generating user). Users can delete them even if they have read access, but cannot create new ones. API Key Read/Write + Admin Read: Users can only view their own API keys and can create and delete their own keys. API Key Read + Admin Read/Write: Users can see all the keys in the system but delete only their keys. They are not be able to create new ones. Credentials: Whether a role can add, edit, or delete credentials.
Administration	Limits permissions for administration tasks, such as server configurations, audit trails, password policy, machine learning, certain Docker permissions, backups, changing logos, license upload, log bundles, and disaster recovery.
Propagation labels (Multi-tenant)	Enables you to do the following: Read: Enables you to select from existing propagation labels. 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. Note If you select none in the Data section, even though you allow page access, the user role cannot access those pages. For example, if you allow page access to Dashboards, but Data is set to none, the user role cannot access the Dashboards page.
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.

Role Permission Example

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 cannot create indicators.

role-perm-6_11.png