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.

Checks that all GitLab code repositories are classified by criticality.

​
Why This Matters

Unclassified infrastructure resources cannot be properly risk-assessed or prioritized for security controls. Classification by criticality ensures appropriate protection levels and is required by ISO 27001 (A.8.2.1) and SOC 2.

​
What DSALTA Checks

DSALTA connects to your GitLab environment using read-only API access and evaluates this configuration on every sync cycle. The test result appears in your Data Library → Tests dashboard:
  • Passing — The configuration meets requirements. No action needed.
  • Failing — The configuration does not meet requirements. Follow the remediation steps below.
  • Not configured — The integration is connected but the required service or feature has not been set up yet.
This test runs automatically every 24 hours. If you fix the underlying issue, DSALTA will detect the change on the next sync cycle and update the status to Passing. You can also trigger a manual sync from Settings → Integrations → GitLab.

​
How to Fix

If this test is failing, follow these steps to remediate:
  1. Sign in to GitLab and navigate to your group or project.
  2. For each repository, add a topic or label indicating criticality (Critical, High, Medium, Low).
  3. In DSALTA, go to Data Library → Inventory and classify each repository based on the code and data it contains.
  4. Document the classification criteria and review cadence.
  5. Once all repositories are classified in DSALTA, the test status will update to Passing.

​
Frequently Asked Questions

This test runs automatically every 24 hours when the GitLab integration is connected. You can trigger a manual sync at any time from the integration settings page.
A failing test generates an alert in your DSALTA dashboard. The assigned responsible role receives a notification. Remediate the issue before it affects your compliance posture.
Yes. If this test does not apply to your environment, you can mark it as Not Applicable with a justification. This exclusion is documented for auditors.
No. DSALTA uses read-only API access and never modifies, creates, or deletes resources in your environment. Remediation actions must be performed by your team directly in GitLab.