This page describes how data role-based access control (data RBAC)
administrators and users can assign scopes to reference lists.
A reference list is a list of values (for example, IP addresses) that are used
for matching and filtering data in UDM Search and detection rules. By assigning
scopes to a reference list, you can control which users and resources (for example,
rules and UDM search instances) can access and utilize it.
To add scopes to a reference list, you must have access to all the scopes that
you intend to add. You cannot add scopes that you don't have access to.
Data RBAC impacts reference lists in the following ways:
Data RBAC is enabled before assigning scopes to reference lists: all existing
reference lists are automatically assigned global scope. Assign
scopes to each reference list according to your data access control requirement.
Data RBAC is enabled after assigning scopes to reference lists: scoped
reference lists operate on ingested data according to their defined scopes, even
before data RBAC is enabled.
A scoped user and a global user have different access permissions, with the
following variation:
A scoped user can create a scoped reference list with all or a subset of
scopes that are assigned to them.
A global user can create either an unscoped reference list (a reference list
that all the users can use) or a scoped reference list.
To add scopes to a reference list, do the following:
In the List manager window, select the list that you want to add scopes
to.
In the Details tab, in the Scope assignment menu, select all the
scopes that the reference list must have access to.
Click Save edits.
The scopes are added to the reference list.
Update scopes in a reference list
To update the scopes in a reference list, you must have access to all the data
scopes that you intend to add to the reference list. You cannot add scopes that
you don't have access to.
The following considerations apply when updating a reference list:
Removing scopes from a reference list is allowed only if all the existing
rules that use the reference list stay functional with the change.
For example, an update for a reference list from scopes A and B to scope A
is not allowed if a rule with scope B uses the reference list. Similarly,
an update for a reference list from being unscoped to scope A is not allowed
if a rule with scope B uses the reference list.
A scoped user can remove a scope from a reference list which can cause
another scoped user to lose access to the reference list.
For example, a user with scopes A and B can remove scope B from a reference
list with scopes A and B. After this change, the user can still use the
reference list, but another user with only scope B can no longer view or
access the reference list.
Updating scopes to add more scopes can cause some users to lose their edit
access to the reference list.
For example, a user with scopes A and B can add scope B to a reference list
that has scope A. After this change, the user can still edit the reference
list, but another user with only scope A is no longer able to edit the
reference list.
To update the scopes in a reference list, do the following:
In the List manager window, select the list that you want to add scopes to.
In the Details tab, in the Scope assignment menu, select all the
scopes that the reference list should have access to. Deselect the scopes that
the reference list shouldn't have access to.
Click Save edits.
The scope assignment of the reference list is updated.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-29 UTC."],[[["\u003cp\u003eData RBAC allows administrators to assign scopes to reference lists, controlling which users and resources can access and use them for matching and filtering data in UDM Search and detection rules.\u003c/p\u003e\n"],["\u003cp\u003eScoped users can create reference lists with their assigned scopes, while global users can create either unscoped or scoped lists.\u003c/p\u003e\n"],["\u003cp\u003eWhen adding or updating scopes to a reference list, users must have access to all scopes they intend to add, and removing scopes is restricted to ensure existing rules using the list remain functional.\u003c/p\u003e\n"],["\u003cp\u003eUpdating scopes can cause some users to lose edit or view access to the reference lists, depending on their scopes and the changes made to the reference list.\u003c/p\u003e\n"]]],[],null,["Configure data RBAC for reference lists \nSupported in: \nGoogle secops [SIEM](/chronicle/docs/secops/google-secops-siem-toc)\n\nThis page describes how *data role-based access control* (*data RBAC*)\nadministrators and users can assign scopes to reference lists.\nA reference list is a list of values (for example, IP addresses) that are used\nfor matching and filtering data in UDM Search and detection rules. By assigning\nscopes to a reference list, you can control which users and resources (for example,\nrules and UDM search instances) can access and utilize it.\n\nTo understand how data RBAC works, see [Overview of Data RBAC](/chronicle/docs/administration/datarbac-overview).\n\nAdd scopes to reference list\n\nTo add scopes to a reference list, you must have access to all the scopes that\nyou intend to add. You cannot add scopes that you don't have access to.\n\nData RBAC impacts reference lists in the following ways:\n\n- **Data RBAC is enabled *before* assigning scopes to reference lists:** all existing\n reference lists are automatically assigned global scope. Assign\n scopes to each reference list according to your data access control requirement.\n\n- **Data RBAC is enabled *after* assigning scopes to reference lists**: scoped\n reference lists operate on ingested data according to their defined scopes, even\n before data RBAC is enabled.\n\nA scoped user and a global user have different access permissions, with the\nfollowing variation:\n\n- A scoped user can create a scoped reference list with all or a subset of\n scopes that are assigned to them.\n\n- A global user can create either an unscoped reference list (a reference list\n that all the users can use) or a scoped reference list.\n\nTo add scopes to a reference list, do the following:\n\n1. [Log in to Google Security Operations](/chronicle/docs/log-in-to-ui).\n\n2. Click **Detection** \\\u003e **Lists**.\n\n3. In the **List manager** window, select the list that you want to add scopes\n to.\n\n4. In the **Details** tab, in the **Scope assignment** menu, select all the\n scopes that the reference list must have access to.\n\n5. Click **Save edits**.\n\nThe scopes are added to the reference list.\n\nUpdate scopes in a reference list\n\nTo update the scopes in a reference list, you must have access to all the data\nscopes that you intend to add to the reference list. You cannot add scopes that\nyou don't have access to.\n\nThe following considerations apply when updating a reference list:\n\n- Removing scopes from a reference list is allowed only if all the existing\n rules that use the reference list stay functional with the change.\n\n For example, an update for a reference list from scopes A and B to scope A\n is not allowed if a rule with scope B uses the reference list. Similarly,\n an update for a reference list from being unscoped to scope A is not allowed\n if a rule with scope B uses the reference list.\n- A scoped user can remove a scope from a reference list which can cause\n another scoped user to lose access to the reference list.\n\n For example, a user with scopes A and B can remove scope B from a reference\n list with scopes A and B. After this change, the user can still use the\n reference list, but another user with only scope B can no longer view or\n access the reference list.\n- Updating scopes to add more scopes can cause some users to lose their edit\n access to the reference list.\n\n For example, a user with scopes A and B can add scope B to a reference list\n that has scope A. After this change, the user can still edit the reference\n list, but another user with only scope A is no longer able to edit the\n reference list.\n\nTo update the scopes in a reference list, do the following:\n\n1. [Log in to Google Security Operations](/chronicle/docs/log-in-to-ui).\n\n2. Click **Detection** \\\u003e **Lists**.\n\n3. In the **List manager** window, select the list that you want to add scopes to.\n\n4. In the **Details** tab, in the **Scope assignment** menu, select all the\n scopes that the reference list should have access to. Deselect the scopes that\n the reference list shouldn't have access to.\n\n5. Click **Save edits**.\n\nThe scope assignment of the reference list is updated.\n\n**Need more help?** [Get answers from Community members and Google SecOps professionals.](https://security.googlecloudcommunity.com/google-security-operations-2)"]]
