Skip to main content

​
Overview

DSALTA connects to GitLab using read-only API access to collect compliance evidence automatically. Data syncs every 24 hours and feeds into your Data Library modules.
Read-only access. DSALTA never modifies, creates, or deletes resources in your GitLab environment.

​
How to Connect

  1. Go to Integrations in the DSALTA sidebar.
  2. Find GitLab and click Connect.
  3. Authenticate with admin-level access.
  4. Select the scope (accounts, projects, or resources to monitor).
  5. DSALTA performs an initial sync (5-15 minutes). Checks activate after sync completes.

​
Automated Compliance Checks

Each check below runs automatically every 24 hours. Click any check for step-by-step remediation guidance.
CheckDescription
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.

​
Troubleshooting

Re-authenticate from Integrations → GitLab → Reconnect. This usually happens when API tokens expire.
Verify the connected account has admin permissions. Try a manual sync from the integration settings.