Manage access to datasets
Manage Cortex XSIAM user-managed dataset access with role permissions, object sharing, owners, editors, and viewers.
Review the following:
The Dataset Management page serves as the central repository for your user-defined data. By using object-level access, you can ensure that specific datasets, such as sensitive Lookups or Correlation results, are only accessible to authorized users and user groups. By default, newly created datasets are Restricted.
Implicit sharing and dependencies
Sharing is not inherited across dependent objects; each layer must be shared explicitly to ensure successful execution.
Dataset views: Sharing a Dataset View does not automatically share the underlying User, Lookup, or Raw datasets it queries. A user with Viewer access to a Dataset View can run the view and see its results, but a direct query against an underlying dataset will fail unless that specific dataset is also shared with them.
Correlation rules: If you create a correlation rule that uses Save to dataset to write to a dataset, you must be the Owner or Editor of that target dataset. If your Editor access is later revoked, the rule continues to evaluate, but the write action will fail.
Query Library: Sharing a saved query does not grant access to the datasets it references. A user can view and edit the saved query text, but running it will fail at runtime with a "dataset not found" or "access denied" error if the user lacks explicit access to the underlying dataset.
Correlation rules and scheduled queries
Background executions, such as active correlation rules (using Save to dataset) and scheduled queries, run with system-level privileges and therefore bypass object-level dataset permissions at runtime. This means a scheduled query or correlation rule can write to or query a Restricted dataset even if the configuring user lacks explicit Editor or Viewer access. Per-object enforcement applies strictly to real-time, ad-hoc query executions.
To reduce the risk of bypassing dataset permissions, Cortex XSIAM performs a validation check when a scheduled query or correlation rule is created or modified. If the creator does not have Editor/Owner rights to the target dataset (or the Create Datasets permission when the dataset does not yet exist), they are blocked from saving the rule or query. Administrators should treat the creation of scheduled queries and correlation rules as highly privileged actions.
Supported dataset types
Per-object access applies strictly to user-managed datasets:
Lookup datasets: Key-value pairs created through upload (CSV/JSON) to Cortex XSIAM, Cortex Query Language (XQL)
target, API, or data sources/connectors.User datasets: Custom datasets generated via XQL
targetcommand or Notebooks SDK.Dataset views: Virtual representations of data built via XQL queries in Cortex XSIAM.
Correlation datasets: Generated via Correlation Rules (Save to dataset).
Note
System-managed datasets, Raw, System, Snapshot, and External (Federated Search), continue to be managed through existing role-to-dataset mappings in Settings → Configurations → Access Management → Roles under Datasets.
How access impacts XQL Search
The permissions assigned to your role, combined with the ownership of specific datasets, directly change the tools available to you while working in XQL Search:
Visibility and autocomplete: Your XQL Search view is personalized. You will only see and receive autocomplete suggestions for datasets where you are the Owner, or those shared with you as a Viewer or Editor, or marked as Public.
Writing data: Running a query with target type = dataset or target type = lookup against an existing dataset requires Editor or Owner access. This prevents users with only Viewer access from unintentionally modifying or appending data to datasets maintained by other teams. If you only have Viewer access, the query will fail with a permission error.
Dynamic creation: If a target dataset does not exist when a query is executed, the system creates it only if your role has the Create Datasets permission. The system dynamically creates the dataset, assigns you as the Owner, and applies the initial access state defined in your tenant-level settings (Restricted by default).
How to configure access to datasets
Setting up access involves enabling role capabilities and then defining the audience for individual dataset objects.
Step 1: Define role capabilities
Role-level permissions act as the "master switch" and determine what actions a user can take in the Dataset Management page.
Select Settings → Configurations → Access Management → Roles.
Right-click the relevant user role and select Edit Role.
Under Components, expand Data Management.
Set Dataset Management to Enabled.
Assign specific capabilities:
Create Datasets: Enables the user to create new supported dataset types. The user who performs this action becomes the Owner and the dataset is assigned an initial access state based on your tenant-level settings.
Edit Public Datasets: Allows the user to modify (append or overwrite) custom datasets set to Public, even if they are not the owner.
Step 2: Manage sharing for a specific dataset
Once a dataset exists in the Dataset Management page, the Owner (or an authorized Editor) defines who can see or edit it.
Select Settings → Configurations → Data Management → Dataset Management.
Locate the dataset in the Datasets or Dataset Views table.
Right-click the dataset and select Share.
(If sharing is enabled) Search for the User or User Group.
Assign the access level: Viewer (read/query) or Editor (modify/append).
Set the General access state:
Restricted: Private to the Owner and explicitly added principals.
Public: Visible to all users with the Dataset Management component enabled.
Click Save.
Last updated
Was this helpful?
