Integration · Code & DevOps

GitLab integration for continuous SOC 2, ISO 27001 & PCI DSS compliance

CATAAM connects to GitLab with read-only access and runs 6 automated checks against your real configuration. The results map to 9 controls across 11 frameworks, including SOC 2, ISO 27001, PCI DSS, GDPR, NIST CSF, SOC 1.

automated checks
6
controls mapped
9
frameworks
11

What happens when you connect GitLab

  1. Connect with read-only access

    Add a read-only role, OAuth scope or API token for GitLab. The credential is encrypted at rest.

  2. Discover assets

    CATAAM pulls the accounts, users, repositories or devices it finds into one asset inventory.

  3. Run 6 automated checks

    Every check runs against your real configuration, then keeps running on a schedule.

  4. Map results to 9 controls

    Each result lands on the controls it proves — and counts for every framework that shares them.

  5. Store evidence and raise issues

    Passing checks become audit evidence. Failures show up for the control owner and can open a Jira issue.

The 6 checks CATAAM runs on GitLab

Each check runs against your real GitLab configuration and keeps running on a schedule. Check names are shown as they appear in the CATAAM platform.

  • Application changes reviewed
  • Author is not the reviewer of pull requests
  • CI/CD system in use
  • GitLab MFA enforced for all group members
  • GitLab branch protection rules enforced
  • GitLab vulnerability scanning enabled on projects

Controls these checks support (9)

A passing check becomes evidence for each control below, and counts for every framework that shares the control.

ControlRequirementFrameworks
CFG-1Configuration management system establishedSOC 2, ISO 27001, PCI DSS, NIST CSF, COBIT 5 +1
CHG-1Change management procedures enforcedSOC 2, ISO 27001, PCI DSS, NIST CSF, SOC 1 +2
CHG-2Production deployment access restrictedSOC 2, ISO 27001, SOC 1, ITIL
CRY-1Unique production database authentication enforcedSOC 2, ISO 27001
IAC-12Remote access MFA enforcedSOC 2, ISO 27001, PCI DSS, NIST CSF, SOC 1 +1
VPM-1Service infrastructure maintainedSOC 2, COBIT 5, ITIL
VPM-2Vulnerabilities scanned and remediatedSOC 2, ISO 27001, PCI DSS, NIST CSF, Essential Eight +3
IAC-85Remote access MFA enforcedGDPR, DPDP Act
IAC-87Production deployment access restrictedGDPR

GitLab integration: frequently asked questions

What does CATAAM check in GitLab?

CATAAM runs 6 automated checks on GitLab, for example: Application changes reviewed; Author is not the reviewer of pull requests; CI/CD system in use; GitLab MFA enforced for all group members. The full list is on this page.

Which compliance frameworks does the GitLab integration support?

The GitLab checks map to 9 controls and count toward SOC 2, ISO 27001, PCI DSS, GDPR, NIST CSF, SOC 1.

Does CATAAM need write access to GitLab?

No. Connectors use read-only roles, scopes or API tokens, and credentials are encrypted at rest. The only optional write anywhere in CATAAM is opening Jira issues for failed checks.

How do I connect GitLab to CATAAM?

Add a read-only role, OAuth scope or API token for GitLab in CATAAM. CATAAM then discovers your assets, runs the checks and keeps running them on a schedule, storing each result as audit evidence.

Try the GitLab integration

Start a 14-day free trial, connect GitLab and get your first automated evidence in minutes.