Skip to content

GitLab

Identity & SaaS audit logs. Group audit events: membership, tokens, and settings.

Status: available now - you connect this yourself

This source is live in the console. Create the read-only credential below, connect it on its card in Integrate -> Sources, and your dedicated instance starts collecting.

What SheerSight reads

SheerSight reads a group's audit events: a project made public, group two-factor disabled, new deploy keys / access tokens / runners, protected-branch or CI-variable tampering, and unusual actor volume.

That feed powers detections such as a project made public, 2FA requirement disabled, a persistence credential being added, branch/variable protection tampering, and an actor activity burst.

It is read-only and scoped to the one group you connect.

What you'll need

  • A GitLab group owner to issue the token.
  • The Group ID of the group you want monitored.
  • Your dedicated instance enrolled.

Create the read-only credential

Issue a group-scoped token with audit read. Do not use an instance-wide admin token.

  1. In GitLab, open the group, then Settings -> Access tokens -> Add new token.
  2. Give it a name and an expiry, set the role high enough to read audit events (Owner for full group audit visibility), and select a read-only scope: read_api (or read_audit if your GitLab edition exposes it). Do not grant write scopes.
  3. Create the token and copy it.
  4. Find the Group ID on the group's overview page (shown under the group name, or via Settings -> General).

Self-managed GitLab

If you run self-managed GitLab rather than gitlab.com, tell us your instance URL when you connect so the collector points at your own /api/v4 base.

Connect it in SheerSight

In the console, open Integrate -> Sources -> GitLab and fill in:

Field Value
Group ID The numeric group ID from step 4.
Access token The group access token from step 3.

Press Connect.

Verify

  1. The relayed credentials entry moves from pending to applied.
  2. The GitLab source badge moves from not connected to live.
  3. Group audit events begin appearing, and matching detections start firing.

Troubleshooting

  • Badge stays not connected. Confirm the Group ID is the numeric ID (not the path), and the token has a read scope and has not expired.
  • Some events missing. The token and the collector are scoped to a single group. Nested subgroups you also want monitored are connected as their own sources.

What SheerSight can and cannot do

The token is read-only and scoped to one group. SheerSight cannot change group or project settings, read code, manage members, or take any action. It only reads audit events.