nano SIEM
Settings

Source Visibility

Supported in:Self-hosted

Hide events from specific log sources with a restricted-source registry and group grants.

Use Source Visibility to control which log sources' events your analysts can read. Access control permissions determine the actions they can take on that data.

Use it to keep sensitive sources — HR systems, executive endpoints, an insider-threat investigation — away from analysts who shouldn't read them.

The unit of control is the log source an event arrived on: the metadata.log_source value you filter on in Search (for example windows_sysmon, aws_cloudtrail, otlp_log).

Open Settings → Source Visibility (/settings/source-scopes).

PermissionGrants
source_scopes:viewSee the visibility configuration
source_scopes:manageChange restrictions, grants and exceptions
source_scopes:view_allBypass: see every source regardless of restrictions. Held by the built-in Admin role.

source_scopes:manage doesn't include source_scopes:view_all: someone can administer restrictions without being able to read the restricted data. Give it to a custom role only if that role should see everything.

How it works

nano uses a restricted-source registry with group grants:

  • Empty registry = everything visible. Nothing changes until you add a source.
  • Adding a source to the registry hides it from everyone (except holders of source_scopes:view_all) until you grant groups.
  • Grants re-open it per group. A source can be granted to any number of groups.
  • Granting the built-in Everyone group makes the source visible to all users again while keeping the registry entry.

Registry values match metadata.log_source (stored on each event as the lowercased source_type column). Values are stored lowercased and trimmed, so you can restrict a source before it has sent any events.

Restrict a source

  1. On Settings → Source Visibility, click Restrict a source.
  2. Pick a source or type its name, and optionally add a reason.
  3. Save. The source is hidden immediately from everyone without source_scopes:view_all.
  4. Select the source and Grant group for each group that should see it.

To undo: revoke a group's grant, or remove the restriction (deletes the registry entry and all its grants).

API

Method and pathPermissionPurpose
GET /api/source-scopes/restrictedsource_scopes:viewList restricted sources
POST /api/source-scopes/restrictedsource_scopes:manageRestrict a source (the source name plus an optional description)
DELETE /api/source-scopes/restricted/{slug}source_scopes:manageRemove a restriction and its grants
GET /api/source-scopes/restricted/{slug}/grantssource_scopes:viewList a source's grants
POST /api/source-scopes/grantssource_scopes:manageGrant a group (the source name plus group_id)
DELETE /api/source-scopes/grants/{slug}/{group_id}source_scopes:manageRevoke a grant

Auditing

Every change is recorded in the platform audit trail under api.service.name=source_scope: source_scope_restricted, source_scope_unrestricted, source_scope_granted, and source_scope_revoked.

metadata.log_source=audit api.service.name=source_scope
| table time, actor.user.name, api.operation, message

Good practice

  • Restrict sensitive sources when you onboard them, then grant (or leave visible to) the owning team.
  • Check that the people who must monitor a source can still see it: make sure a group you belong to is granted.
  • Pair with least-privilege permissions: visibility limits which data is seen, permissions limit what can be done with it.

Troubleshoot

Need help with these checks? Contact support with the request ID and time with timezone.

A user still sees a restricted source

Check for source_scopes:view_all, then check the user’s group grants, including Everyone.

What's next

On this page