For the complete documentation index, see llms.txt. This page is also available as Markdown.
Cortex Cloud RuntimeCortex Cloud

Manage user roles and access management

Learn how to manage access for users, user roles, user groups, and Single Sign-On (SSO) for users on a specific Cortex Cloud tenant.

Prerequisite

Access management enables you to control who can access the different parts of your organization's resources. It ensures only authorized users can interact with sensitive data.

Cortex Cloud uses a combination of Role-Based Access Control (RBAC), Scope-Based Access Control (SBAC), and Per-object access to ensure scalability and granular control.

What is the difference between RBAC, SBAC, and Per-object access?

RBAC assigns permissions based on a user's organizational role, such as Investigator or Responder, establishing a clear hierarchy and set of capabilities for each role and simplifying management by linking access to job functions. RBAC does this by helping to manage access to Cortex Cloud components and Cortex Query Language (XQL) datasets, so that users, based on their roles, are granted minimal access required to accomplish their tasks.

SBAC refines RBAC by granting access only to the relevant data that the user requires for their designated role. Users with Access Management permission apply scopes to limit the data and content that users can be granted access to in Cortex Cloud, which are divided into different scoping areas. The scoping areas include Assets, Cases and Issues, Endpoints, and Datasets Rows, which can be applied as relevant to the enforcement area, entity, or dataset.

Per-object access allows you to manage access for individual instances of custom (user-defined) objects, such as specific dashboards, saved XQL queries, and user-managed datasets. This ensures that sensitive tools and data collections are only accessible to the owner and explicitly authorized principals, such as specific users, user groups, or API keys.

For example, an Investigator role might have access to asset information based on the RBAC permissions, but SBAC granular scoping could limit that investigator's view and control to only assets within a particular scoping area. This hybrid approach ensures scalability and granular control, significantly strengthening system security.

Understanding more about access management concepts

You can manage access for users, and create and assign user roles and user groups for a specific tenant. When Single Sign-On (SSO) is enabled, you can manage SSO for users.

Users

You can manage access permissions and activities for users allocated to a specific Customer Support Portal account and tenant. All users must belong to a user group or have an assigned role.

Note

To remove users added to your CSP account, you must do so in the CSP, not in Cortex Gateway.

User roles

User roles enable you to define the type of access and actions a user can perform. User roles are assigned to users, user groups, or API keys.

Note

For more information on assigning user roles when generating an API key, see Manage API keys.

Predefined user roles

Cortex Cloud provides predefined built-in user roles that provide specific access rights that cannot be modified. You can also create custom, editable user roles. To view the predefined permissions for each default role, go to Settings → Configurations → Access Management → Roles.

Dataset access permissions

Configuring dataset access depends on the type of dataset:

  • System-managed datasets: (Raw, System, Snapshot, and External) Access is managed by RBAC permissions on the Datasets tab. For new roles, Enable dataset access management is disabled by default, providing access to all system-managed datasets. When enabled, you can restrict access to specific dataset categories and individual datasets.

  • User-managed datasets: (User, Lookup, Dataset Views, and Correlation) Access is managed per object via the Share action in the Dataset Management page. This ensures that users only interact with datasets they own, that have been shared with them, or that are marked as Public.

For more information on how to set dataset access permissions, see Manage access to datasets.

Note

Some features are license-dependent. Accordingly, users may not see a specific feature if the feature is not supported by the license type or if they do not have access based on their assigned role or scope.

Per-object access management

In addition to role-level permissions, Cortex Cloud enforces least-privileged access for individual instances of custom (user-defined) objects. Supported objects include:

  • Dashboards and widgets

  • Report Templates

  • Playbooks and Scripts

  • Saved XQL queries (located in the Query Library)

  • User-managed datasets (User, Lookup, Dataset Views, and Correlation datasets)

For more information, see Manage access to objects.

User groups and scoping areas

You can use user groups to streamline configuration activities by grouping together users whose access permission requirements are similar. Import user groups from Active Directory, or create them from scratch in Cortex Cloud.

Users with Access Management permission can further restrict access of these user groups, specifically for the designated role and list of users configured in the user group by granting access only to the relevant data that the user requires for their designated role. This is performed by applying scopes to limit the data and content that users can be granted access to in Cortex Cloud, which are divided into different scoping areas. The scoping areas include Assets, Cases and Issues, Endpoints, and Datasets Rows, which can be applied as relevant to the enforcement area, entity, or dataset. This enables you to adhere to your company's security policies of limiting user access by specifying, for example, which groups of assets users can access and what actions they can perform.

Note

For features where scoping is not applicable, Role-Based Access Control (RBAC) is used and can be configured when managing user roles. For more information, see Manage user roles.

Single Sign-On

Manage your SSO integration with the Security Assertion Markup Language (SAML) 2.0 standard to securely authenticate system users across enterprise-wide applications and websites, with one set of credentials. This configuration allows system users to authenticate using your organization's Identity Provider (IdP), such as Okta or PingOne. You can integrate any IdP with Cortex Cloud supported by SAML 2.0.

SSO with SAML 2.0 configuration activities are dependent on your organization’s IdP. Some of the field values need to be obtained from your organization’s IdP, and some values need to be added to your organization’s IdP. It is your responsibility to understand how to access your organization’s IdP to provide these fields, and to add any fields from Cortex Cloud to your IdP.

After SSO configuration is complete, when you sign in as an SSO user, the Cortex Cloud permissions granted to you after logging in, either from the group mapping or from the default role configuration, are effective throughout the entire session for the defined maximum session length. Maximum session length is defined in your Cortex Cloud Session Security Settings. This applies even if the default role configuration is updated, or the group membership settings were changed.

Last updated

Was this helpful?