Skip to content

Integrating SailPoint with GitGuardian

GitGuardian is a cloud-based secrets detection platform designed for engineering and security teams. It helps organizations detect, investigate, and remediate secrets in source code. It lets organizations track user identity and account-related attributes and connects to other tools via its REST API using an API Token. This document provides the instructions required to configure a new direct connection between SailPoint and GitGuardian. For a reference to the terminology specific to SailPoint products, refer to Source and Connector Definitions.

Note

To view the latest features, enhancements, and fixes for all SaaS connectors, refer to the SaaS Release Notes page.

Supported Features

The GitGuardian connector supports the following:

Account Management

  • Aggregate Members

Note

User role is captured as part of account aggregation (embedded within the user record via the role attribute), so a separate entitlement aggregation is not required.

Note

This connector is read-only. It supports test connection and account aggregation for Quick Compliance. Provisioning, de-provisioning, and write operations are not supported.

Important

Quick Compliance connectors have the following manual aggregation limits within a 24-hour period:

  • Organization Admins: Limited to 3 manual account or entitlement aggregations per day per source. This limit is cumulative across all admins in the organization.
  • Regular Users: Limited to 1 manual account or entitlement aggregation per day per source.

These limits ensure that individual compliance statuses are kept up to date while maintaining continuous compliance monitoring. If you need to run additional aggregations beyond these limits, contact SailPoint Support.

Prerequisites

Before you configure the GitGuardian connector, ensure the following requirements are met:

  1. Sign in to GitGuardian.
  2. On the GitGuardian Dashboard, go to Settings > API > Personal Access Token and select Create Token.
  3. Select members:read as the minimum scope for reading members.
  4. Copy and securely store the following details, which are required during connector configuration:
    • Base URL
    • API Token

Note

  • The GitGuardian API uses an API Token for authentication. The token is passed on each API request: Authorization: Token {{ your_api_token }}.
  • All API requests must be made over HTTPS; unencrypted HTTP calls are not supported and will fail.
  • Tokens should be stored securely and treated like a password.

Required Permissions

GitGuardian uses role-based access at the account level. Available roles include the following:

  • Owner - Full access to all workspace settings, members, and administration.
  • Manager - Broad access to manage members, incidents, and workspace settings.
  • Member - Standard access to the GitGuardian workspace.
  • Restricted - Limited access to incidents they are given access to only.

For more detailed information on GitGuardian API authentication, refer to the GitGuardian API documentation.

Note

The linked document is not maintained by SailPoint and is subject to change without notice.