Skip to main content

Documentation Index

Fetch the complete documentation index at: https://help.dsalta.com/llms.txt

Use this file to discover all available pages before exploring further.

​
Overview

GitLab is a complete DevOps platform providing source code management, CI/CD, security scanning, and project management. DSALTA monitors repository security configuration, MFA enforcement, code review policies, and access management.
Read-only access. DSALTA never modifies, creates, or deletes resources in your GitLab environment. All API access is strictly read-only.

​
Integration Details

PropertyValue
CategoryCode Repository
Data Library ModulesAccess, Code Changes
AuthenticationPersonal Access Token with read_api scope
Sync FrequencyEvery 24 hours (manual sync available)
PermissionsRead-only

​
What Data DSALTA Collects

When you connect GitLab, DSALTA automatically collects the following data on every sync cycle:
  • Repository configurations
  • Branch protection rules
  • Merge request review requirements
  • Group-level MFA enforcement
  • User access and roles
Every record includes the integration name as its source, a sync timestamp, and is treated identically to manually entered records by auditors.

​
Key Use Cases

  • Enforce group-level MFA
  • Require peer review before merges
  • Validate branch protection for admins
  • Track offboarded user access revocation
  • Classify repositories by criticality

​
How to Connect

1

Navigate to Integrations

Go to Settings → Integrations in your DSALTA dashboard and find GitLab in the catalog.
2

Review Permissions

Review the permissions DSALTA requires. All access is read-only. Click Connect.
3

Authenticate

Follow the on-screen instructions to authenticate with your GitLab account. Admin-level access is required for the initial setup.
4

Configure Scope

Select which accounts, projects, or resources DSALTA should monitor. You can adjust this later from the integration settings.
5

Initial Sync

DSALTA performs an initial data pull (typically 5–15 minutes). Automated compliance tests are generated immediately after sync completes.
After connecting, allow 15–20 minutes for the initial data sync. DSALTA may take up to 24 hours to fully evaluate all synced data and activate all relevant compliance tests.

​
Automated Compliance Tests

When you connect GitLab, DSALTA automatically generates the following compliance tests. Each test runs every 24 hours and produces pass/fail evidence for your auditor.
TestDescription
Code repositories should be classifiedChecks that all GitLab code repositories are classified by criticality.
GitLab group-level MFA should be enforcedChecks that group-level MFA enforcement is enabled in GitLab.
Peer review should be enforced for code changesChecks that peer review is required before code changes can be merged in GitLab.
Merging code changes should require passing status checksChecks that passing status checks are required before merging in GitLab.
Branch protection rules should be enforced for adminsChecks that branch protection rules apply to admin users in GitLab.
Code changes should be reviewed by peers before mergingChecks that all code changes are reviewed by at least one peer before merging in GitLab.
GitLab access should be removed for offboarded usersChecks that GitLab access is revoked for offboarded users.
Tests run automatically every 24 hours. Failed tests generate alerts and appear in your compliance dashboard with remediation guidance. All test results are stored as audit evidence with timestamps.

​
Compliance Frameworks

This integration provides evidence for the following compliance frameworks:

SOC 2

Access controls, monitoring, and change management evidence.

ISO 27001

Asset management, access control, and operations security evidence.

GDPR

Access records and data processing evidence.

​
Troubleshooting

Re-authenticate by going to Settings → Integrations → GitLab and clicking Reconnect. This usually happens when API tokens expire or permissions change.
Verify that the connected account still has the required admin permissions. Try a manual sync from the integration settings page. If the issue persists, check your GitLab API rate limits.
Tests generate after the first successful data sync. If sync completed but tests are missing, ensure the relevant features are configured in GitLab (e.g., GuardDuty must be enabled in AWS for GuardDuty tests to appear).
DSALTA syncs all users visible to the connected admin account. If users are missing, verify they are within the scope you configured during setup. Suspended or deleted accounts may not appear.