Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Important
Lakewatch is in Beta. Workspace admins can control access to this feature from the Previews page. See Manage workspace-level previews.
Lakewatch governs each resource type with Unity Catalog privileges. This reference lists the privileges for datasources, detection rules, signals, alerts, and queries, and the capability each one grants.
How privileges are organized
Datasources and detection rules have resource privileges and security-data privileges:
- Resource privileges: Govern the resource itself: reading its configuration, managing it, and managing its access.
- Security-data privileges: Govern the resource's outputs: the signals and alerts a detection rule produces, and the system-error alerts a datasource raises.
You grant these privileges on a folder (schema) or the environment (catalog), and they inherit down to every resource beneath.
Permission groups
In the Lakewatch UI, you grant access with permission groups instead of individual privileges. A folder permission group grants its privileges on the folder's schema, so they apply to every datasource and detection rule in the folder. Lakewatch admin is granted on the environment's catalog, so it applies to every folder. Combine permission groups for one principal, or select individual permissions to make a Custom grant.
| Permission group | Granted on | Privileges |
|---|---|---|
| Lakewatch admin | Catalog | CREATE_RULE, CREATE_DATASOURCE, READ_METADATA, MANAGE, READ_SECURITY_DATA, UPDATE_SECURITY_DATA, SELECT, MODIFY, CREATE TABLE, CREATE SCHEMA, CREATE_SECRET |
| Folder admin | Folder | CREATE_RULE, CREATE_DATASOURCE, READ_METADATA, MANAGE, READ_SECURITY_DATA, UPDATE_SECURITY_DATA, SELECT, MODIFY, CREATE TABLE |
| Datasource manager | Folder | CREATE_DATASOURCE, READ_METADATA, MANAGE, SELECT, MODIFY, CREATE TABLE |
| Detection rule manager | Folder | CREATE_RULE, READ_METADATA, MANAGE, SELECT, MODIFY, CREATE TABLE, READ_SECURITY_DATA |
| Alert triage | Folder | READ_METADATA, SELECT, READ_SECURITY_DATA, UPDATE_SECURITY_DATA |
You don't grant USE CATALOG and USE SCHEMA separately. Lakewatch grants all account users USE CATALOG on the environment's catalog and USE SCHEMA on every folder, regardless of the folder's other permissions. These traversal privileges allow users to reach a folder but not to view or change anything in it. The UI hides Detection rule manager and Alert triage on the default datasource folder, and Datasource manager on the default detection rule folder, because those permissions don't apply to the resources the folder holds.
When you select individual permissions for a Custom grant, the UI shows each privilege under the following label:
| Label | Privilege |
|---|---|
| Create datasources | CREATE_DATASOURCE |
| Create detection rules | CREATE_RULE |
| Read detection rules/datasources | READ_METADATA |
| Manage resources and permissions | MANAGE |
| Read alerts | READ_SECURITY_DATA |
| Update alerts | UPDATE_SECURITY_DATA |
| Read Lakewatch tables | SELECT |
| Modify Lakewatch tables | MODIFY |
| Create Lakewatch tables | CREATE TABLE |
| Create folders | CREATE SCHEMA |
| Create secrets | CREATE_SECRET |
CREATE_SECRET only enables you to create the Unity Catalog secrets that alert destinations and Settings export destinations use, stored in the __lakewatch schema. API connectors don't use it. They authenticate through Unity Catalog connections.
Share resources with your team
Folder permissions apply to every resource in the folder, including resources that other users created. This access comes from the folder or catalog grant, not from an administrator override. The access control model has no override, so a group reaches exactly what its grants cover, and nothing in a folder where it holds no grant.
You share Lakewatch resources through folders. A permission group on a folder applies to every datasource and detection rule in the folder, including resources created later. To share resources with your team, do one of the following:
- Use a folder the team can access: Create the resource in a folder where the team already has the permission group it needs.
- Grant the team access to the folder: A user with
MANAGEon the folder, such as a Folder admin or Lakewatch admin, grants the team a permission group on the folder. For example, grant Alert triage so the team can work the folder's alerts.
With the example setup in Set up access control, each team already has the permission group it needs on its folder, so resources you create there are shared with the team automatically. To limit who can access a resource, create it in a folder that only the intended team can access.
Datasources and detection rules
Datasources and detection rules share the same resource privileges and security-data privileges. They differ in the create privilege (CREATE_DATASOURCE for a datasource, CREATE_RULE for a detection rule). Detection rules produce signals and alerts, and datasources raise system errors, which Lakewatch records as alerts:
| Privilege | Grants |
|---|---|
READ_METADATA |
Read the resource and its configuration. |
MANAGE |
Update and delete the resource, manage its access, and read its configuration. Doesn't grant the security data (signals and alerts) the resource produces. |
MANAGE_ACCESS_CONTROL |
Grant and revoke privileges on the resource. |
READ_SECURITY_DATA |
Read the signals and alerts the resource produces. Detection rules and datasources. |
UPDATE_SECURITY_DATA |
Update the alerts the resource produces. Detection rules and datasources. |
To create a datasource, you must have CREATE_DATASOURCE on its folder, which Datasource manager, Folder admin, and Lakewatch admin include. To create a detection rule, you must have CREATE_RULE on its folder, which Detection rule manager, Folder admin, and Lakewatch admin include. Creating a resource also requires USE CATALOG and USE SCHEMA, which Lakewatch grants to all account users.
Access to a resource another user owns follows these same privileges, whether it is a datasource or a detection rule:
- To view it, you must have
READ_METADATAorMANAGEon its folder or environment. - To edit or delete it, you must have
MANAGEor be its owner. - To change who can access it, you must have
MANAGE_ACCESS_CONTROL(included inMANAGE) or be its owner.
In every case, the principal must also have USE CATALOG on the catalog and USE SCHEMA on the schema that contain the resource, because a datasource or detection rule is a Unity Catalog securable that a principal must be able to reach before any privilege on it takes effect. Lakewatch grants both to all account users. See Privileges.
Signals and alerts (derived artifacts)
Signals and alerts are derived artifacts. They aren't separate securables, so the security-data privileges on the parent detection rule or datasource control access to them:
| Action | Privilege on the parent resource |
|---|---|
| View or list signals and alerts | READ_SECURITY_DATA |
| Update an alert | UPDATE_SECURITY_DATA |
Signals are immutable, so only alerts can be updated.
Queries
You manage query access through the Lakewatch app, using these permission levels:
| Permission level | Grants |
|---|---|
CAN_VIEW |
View the query and its results. |
CAN_RUN |
Run the query. |
CAN_EDIT |
Edit and save the query. |
CAN_MANAGE |
Manage the query, including its access. The query's creator gets this. |