realaravinth/debian-mirror-gitlab
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
debian-mirror-gitlab/doc/administration/audit_events.md
Mohammed Bilal 8ec612e4e8
New upstream version 15.6.4+ds1
2023-01-13 15:02:22 +05:30

19 KiB
Raw Blame History

stage group info
Govern Compliance To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments

Audit events (PREMIUM)

Use audit events to track important events, including who performed the related action and when. You can use audit events to track, for example:

  • Who changed the permission level of a particular user for a GitLab project, and when.
  • Who added a new user or removed a user, and when.

The GitLab API, database, and audit_json.log record many audit events. Some audit events are only available through streaming audit events.

You can also generate an audit report of audit events.

NOTE: You can't configure a retention policy for audit events, but epic 7917 proposes to change this.

List of events

There are two kinds of events logged:

  • Events scoped to the group or project, used by group and project managers to look up who made a change.
  • Instance events scoped to the whole GitLab instance, used by your Compliance team to perform formal audits.

NOTE: Some events are recorded and available only as streaming audit events.

Impersonation data

Introduced in GitLab 13.0.

When a user is being impersonated, their actions are logged as audit events as usual, with two additional details:

  1. Usual audit events include information about the impersonating administrator. These audit events are visible in their respective audit event pages depending on their type (group, project, or user).
  2. Extra audit events are recorded for the start and stop of the administrator's impersonation session. These audit events are visible in the:
    • Instance audit events.
    • Group audit events for all groups the user belongs to (GitLab 14.8 and later). For performance reasons, group audit events are limited to the oldest 20 groups to which you belong.

audit events

Group events

A user with:

  • Owner role (or above) can retrieve group audit events of all users.
  • Developer or Maintainer role is limited to group audit events based on their individual actions.

Group events do not include project audit events.

To view a group's audit events:

  1. Go to the group.
  2. On the left sidebar, select Security & Compliance > Audit Events.

From there, you can see the following actions:

  • Group name or path changed.
  • Group repository size limit changed.
  • Group created or deleted.
  • Group changed visibility.
  • User was added to group and with which permissions.
  • User sign-in via Group SAML.
  • Introduced in GitLab 14.5, changes to the following group SAML configuration:
    • Enabled status.
    • Enforcing SSO-only authentication for web activity.
    • Enforcing SSO-only authentication for Git and Dependency Proxy activity.
    • Enforcing users to have dedicated group-managed accounts.
    • Prohibiting outer forks.
    • Identity provider SSO URL.
    • Certificate fingerprint.
    • Default membership role.
    • SSO-SAML group sync configuration.
  • Permissions changes of a user assigned to a group.
  • Removed user from group.
  • Project repository imported into group.
  • Project shared with group and with which permissions.
  • Removal of a previously shared group with a project.
  • LFS enabled or disabled.
  • Shared runners minutes limit changed.
  • Membership lock enabled or disabled.
  • Request access enabled or disabled.
  • 2FA enforcement or grace period changed.
  • Roles allowed to create project changed.
  • Group CI/CD variable added, removed, or protected status changed. Introduced in GitLab 13.3.
  • Compliance framework created, updated, or deleted. Introduced in GitLab 14.5.
  • Event streaming destination created, updated, or deleted. Introduced in GitLab 14.6.
  • Instance administrator started or stopped impersonation of a group member. Introduced in GitLab 14.8.
  • Group deploy token was successfully created, revoked, or deleted. Introduced in GitLab 14.9.
  • Failed attempt to create a group deploy token. Introduced in GitLab 14.9.
  • IP restrictions changed. Introduced in GitLab 15.0.
  • Changes to push rules. Introduced in GitLab 15.0.
  • Introduced in GitLab 15.1, changes to the following merge request approvals settings:
    • Prevent approval by author.
    • Prevent approvals by users who add commits.
    • Prevent editing approval rules in projects and merge requests.
    • Require user password to approve.
    • Remove all approvals when commits are added to the source branch.
  • Changes to streaming audit destination custom HTTP headers. Introduced in GitLab 15.3.
  • Group had a security policy project linked, changed, or unlinked. (Introduced in GitLab 15.6)

Group events can also be accessed via the Group Audit Events API

Project events

A user with a Maintainer role (or above) can retrieve project audit events of all users. A user with a Developer role is limited to project audit events based on their individual actions.

To view a project's audit events:

  1. Go to the project.
  2. On the left sidebar, select Security & Compliance > Audit Events.

From there, you can see the following actions:

  • Added or removed deploy keys

  • Project created, deleted, renamed, moved (transferred), changed path

  • Project changed visibility level

  • User was added to project and with which permissions

  • Permission changes of a user assigned to a project

  • User was removed from project

  • Project export was downloaded

  • Project repository was downloaded

  • Project was archived

  • Project was unarchived

  • Added, removed, or updated protected branches

  • Release was added to a project

  • Release was updated

  • Release was deleted (introduced in GitLab 15.3)

  • Release milestone associations changed

  • Permission to approve merge requests by committers was updated (introduced in GitLab 12.9)

  • Permission to approve merge requests by committers was updated.

  • Permission to approve merge requests by authors was updated (introduced in GitLab 12.9)

  • Number of required approvals was updated (introduced in GitLab 12.9)

  • Added or removed users and groups from project approval groups (introduced in GitLab 13.2)

  • Project CI/CD variable added, removed, or protected status changed (Introduced in GitLab 13.4)

  • Project access token was successfully created or revoked (Introduced in GitLab 13.9)

  • Failed attempt to create or revoke a project access token (Introduced in GitLab 13.9)

  • When default branch changes for a project (Introduced in GitLab 13.9)

  • Created, updated, or deleted DAST profiles, DAST scanner profiles, and DAST site profiles (Introduced in GitLab 14.1)

  • Changed a project's compliance framework (Introduced in GitLab 14.1)

  • User password required for approvals was updated (introduced in GitLab 14.2)

  • Permission to modify merge requests approval rules in merge requests was updated (introduced in GitLab 14.2)

  • New approvals requirement when new commits are added to an MR was updated (introduced in GitLab 14.2)

  • When strategies for feature flags are changed (introduced in GitLab 14.3)

  • Allowing force push to protected branch changed (introduced in GitLab 14.3)

  • Code owner approval requirement on merge requests targeting protected branch changed (introduced in GitLab 14.3)

  • Users and groups allowed to merge and push to protected branch added or removed (introduced in GitLab 14.3)

  • Project deploy token was successfully created, revoked or deleted (introduced in GitLab 14.9)

  • Failed attempt to create a project deploy token (introduced in GitLab 14.9)

  • When merge method is updated (introduced in GitLab 14.9)

  • Merged results pipelines enabled or disabled (introduced in GitLab 14.9)

  • Merge trains enabled or disabled (introduced in GitLab 14.9)

  • Automatically resolve merge request diff discussions enabled or disabled (introduced in GitLab 14.9)

  • Show link to create or view a merge request when pushing from the command line enabled or disabled (introduced in GitLab 14.9)

  • Delete source branch option by default enabled or disabled (introduced in GitLab 14.9)

  • Squash commits when merging is updated (introduced in GitLab 14.9)

  • Pipelines must succeed enabled or disabled (introduced in GitLab 14.9)

  • Skipped pipelines are considered successful enabled or disabled (introduced in GitLab 14.9)

  • All discussions must be resolved enabled or disabled (introduced in GitLab 14.9)

  • Commit message suggestion is updated (introduced in GitLab 14.9)

  • Status check is added, edited, or deleted (introduced in GitLab 15.0)

  • Merge commit message template is updated (introduced in GitLab 15.0)

  • Squash commit message template is updated (introduced in GitLab 15.0)

  • Default description template for merge requests is updated (introduced in GitLab 15.0)

  • Project was scheduled for deletion due to inactivity (introduced in GitLab 15.0)

  • Project had a security policy project linked, changed, or unlinked (introduced in GitLab 15.6)

Project events can also be accessed via the Project Audit Events API.

Project event queries are limited to a maximum of 30 days.

Instance events (PREMIUM SELF)

Server-wide audit events introduce the ability to observe user actions across the entire instance of your GitLab server, making it easy to understand who changed what and when for audit purposes.

Instance events do not include group or project audit events.

To view the server-wide audit events:

  1. On the top bar, select Main menu > Admin.
  2. On the left sidebar, select Monitoring > Audit Events.

The following user actions are recorded:

  • Sign-in events and the authentication type (such as standard, LDAP, or OmniAuth)
  • Failed sign-ins
  • Added SSH key
  • Added or removed email
  • Changed password
  • Ask for password reset
  • Grant OAuth access
  • Started or stopped user impersonation
  • Changed username (introduced in GitLab 12.8)
  • User was deleted (introduced in GitLab 12.8)
  • User was added (introduced in GitLab 12.8)
  • User requests access to an instance (introduced in GitLab 13.9)
  • User was approved via Admin Area (introduced in GitLab 13.6)
  • User was rejected via Admin Area (introduced in GitLab 13.9)
  • User was blocked via Admin Area (introduced in GitLab 12.8)
  • User was blocked via API (introduced in GitLab 12.9)
  • Failed second-factor authentication attempt (introduced in GitLab 13.5)
  • A user's personal access token was successfully created or revoked (introduced in GitLab 13.6)
  • A failed attempt to create or revoke a user's personal access token (introduced in GitLab 13.6)
  • Administrator added or removed (introduced in GitLab 14.1)
  • Removed SSH key (introduced in GitLab 14.1)
  • Added or removed GPG key (introduced in GitLab 14.1)
  • A user's two-factor authentication was disabled (introduced in GitLab 15.1)

Instance events can also be accessed via the Instance Audit Events API.

Sign-in events (FREE)

Successful sign-in events are the only Audit Events available at all tiers. To see successful sign-in events:

  1. Select your avatar.
  2. Select Edit profile > Authentication log.

After upgrading from GitLab Free to a paid tier, successful sign-in events are the only Audit Events visible in Audit Events views until more events are logged.

"Deleted User" events

Audit events can be created for a user after the user is deleted. The user name associated with the event is set to "Deleted User" because the actual user name is unknowable. For example, if a deleted user's access to a project is removed automatically due to expiration, the audit event is created for "Deleted User". We are investigating whether this is avoidable.

Missing events

Some events are not tracked in audit events. See the following epics for more detail on which events are not being tracked, and our progress on adding these events into GitLab:

Don't see the event you want in any of the epics linked above? You can either:

Removed events

  • Repositories push events was deprecated in GitLab 14.3.
  • Repositories push events was removed in GitLab 15.0.

The repositories push events feature was:

Search

The search filters you can see depends on which audit level you are at.

Filter Available options
Scope (Project level) A specific user who performed the action.
Scope (Group level) A specific user (in a group) who performed the action.
Scope (Instance level) A specific group, project, or user that the action was scoped to.
Date range Either via the date range buttons or pickers (maximum range of 31 days). Default is from the first day of the month to today's date.

audit events

Export to CSV (PREMIUM SELF)

Export to CSV allows customers to export the current filter view of your audit events as a CSV file, which stores tabular data in plain text. The data provides a comprehensive view with respect to audit events.

To export the audit events to CSV:

  1. On the top bar, select Main menu > Admin.
  2. On the left sidebar, select Monitoring > Audit Events.
  3. Select the available search filters.
  4. Select Export as CSV.

Sort

Exported events are always sorted by created_at in ascending order.

Format

Data is encoded with a comma as the column delimiter, with " used to quote fields if needed, and newlines to separate rows. The first row contains the headers, which are listed in the following table along with a description of the values:

Column Description
ID Audit event id
Author ID ID of the author
Author Name Full name of the author
Entity ID ID of the scope
Entity Type Type of the scope (Project/Group/User)
Entity Path Path of the scope
Target ID ID of the target
Target Type Type of the target
Target Details Details of the target
Action Description of the action
IP Address IP address of the author who performed the action
Created At (UTC) Formatted as YYYY-MM-DD HH:MM:SS

Limitation

The audit events CSV file is limited to a maximum of 100,000 events. The remaining records are truncated when this limit is reached.