Skip to content
This repository has been archived by the owner on Jul 24, 2024. It is now read-only.

Latest commit

 

History

History
118 lines (91 loc) · 5.05 KB

jupiterone.md

File metadata and controls

118 lines (91 loc) · 5.05 KB

GitLab

GitLab + JupiterOne Integration Benefits

  • Visualize GitLab users, groups, code repositories, and merge requests in the JupiterOne graph.
  • Map GitLab users to employees in your JupiterOne account.
  • Map GitLab users to development/security trainings.
  • Monitor GitLab software development activities within repositories including changes and approvals.
  • Monitor changes to GitLab user groups, users, code repositories, and merge requests using JupiterOne alerts.

How it Works

  • JupiterOne periodically fetches GitLab users, code repositories, and pull requests in those repositories to update the graph.
  • Write JupiterOne queries to review and monitor updates to the graph.
  • Configure alerts to take action when the JupiterOne graph changes.

Requirements

  • JupiterOne requires a personal access token configured with read access and the API base URL, such as https://gitlab.com.
  • You must have permission in JupiterOne to install new integrations.

## Support

If you need help with this integration, contact JupiterOne Support.

Integration Walkthrough

In GitLab

See GitLab's documentation for Creating a personal access token.

In JupiterOne

  1. From the top navigation of the J1 Search homepage, select Integrations.
  2. Scroll to the GitLab integration tile and click it.
  3. Click the Add Configuration button and configure the following settings:
  • Enter the Account Name by which you'd like to identify this GitLab account in JupiterOne. Ingested entities will have this value stored in tag.AccountName when Tag with Account Name is checked.
  • Enter a Description that will further assist your team when identifying the integration instance.
  • Select a Polling Interval that you feel is sufficient for your monitoring needs. You may leave this as DISABLED and manually execute the integration.
  • Enter the Personal Access Token configured for read access in GitLab.
  • Enter the API Base URL (such as https://gitlab.com) of your self-managed GitLab instance.
  1. Click Create Configuration once all values are provided.

How to Uninstall

  1. From the top navigation of the J1 Search homepage, select Integrations.
  2. Scroll to the GitLab integration tile and click it.
  3. Identify and click the integration to delete.
  4. Click the trash can icon.
  5. Click the Remove button to delete the integration.

Data Model

Entities

The following entities are created:

Resources Entity _type Entity _class
Account gitlab_account Account
Commit gitlab_commit CodeCommit
Finding gitlab_finding Finding
Group gitlab_group Group
Label gitlab_label Record
Merge Request gitlab_merge_request CodeReview, PR
Project gitlab_project CodeRepo, Project
User gitlab_user User

Relationships

The following relationships are created:

Source Entity _type Relationship _class Target Entity _type
gitlab_account HAS gitlab_group
gitlab_account HAS gitlab_project
gitlab_group HAS gitlab_group
gitlab_group HAS gitlab_project
gitlab_group HAS gitlab_user
gitlab_merge_request HAS gitlab_commit
gitlab_project HAS gitlab_finding
gitlab_project HAS gitlab_label
gitlab_project HAS gitlab_merge_request
gitlab_project HAS gitlab_user
gitlab_user APPROVED gitlab_merge_request
gitlab_user OPENED gitlab_merge_request