Updated on: November 17, 2026

9 min read

Guide to fulfilling SOC 2 security requirements with GitLab

Learn how GitLab maps to the SOC 2 Trust Services Criteria, which scanners and policies produce audit evidence, where GitLab Duo helps, and what stays outside GitLab.

SOC 2 (System and Organization Controls 2) is an auditor's opinion that your stated controls were designed correctly and operated consistently across a review window, typically three to 12 months. The controls are measured against the 2017 AICPA Trust Services Criteria, and for a software company most of the evidence an auditor samples is engineering evidence:

  • Who reviewed each change
  • Who authorized each deployment
  • Which vulnerabilities were found, and how fast they were fixed
  • Who had access to what

Most organizations assemble that evidence from a source control tool, a CI system, several scanners, a ticketing system, and a compliance vendor that screen-scrapes all of them. Every seam between those tools is a place where evidence can go missing during fieldwork.

This guide explains how GitLab closes those seams. It covers where each SOC 2 criterion lands in GitLab, which scanners back which criteria, where GitLab Duo speeds up the work, and which obligations GitLab does not cover.

How GitLab assists SOC 2 adherence

GitLab supports SOC 2 adherence in three ways.

Controls are enforced above the project

A custom compliance framework marks which projects are in scope, injects a compliance pipeline they cannot remove, and carries the requirements each project is measured against.

Security policies live in a separately permissioned policy project, so a developer with the Maintainer role cannot disable the control that governs them. GitLab offers four policy types: scan execution, merge request approval, pipeline execution, and vulnerability management.

A SOC 2 framework template ships with its requirements and controls already mapped, so you configure the framework instead of building it from scratch.

Merge request approval policy in action

Evidence is a by-product, not a project

Normal engineering activity generates merge request approvals, pipeline results, scan reports, vulnerability state changes, and audit events. Each of these is attributable, timestamped, and tamper-evident by default, so audit preparation means exporting evidence that already exists instead of reconstructing it.

Drift is visible while you can still fix it

GitLab re-evaluates adherence whenever a framework changes, and again every 12 hours. The security inventory shows where scanner coverage is actually missing.

The most common cause of a Type II exception is a project created mid-window without the framework applied. With these checks, that gap surfaces within hours instead of at the next audit.

As a result, the criteria with the heaviest sampling burden are answered from one system, with one link per sampled change. Those criteria are CC6 (access control), CC7 (vulnerability management), and CC8 (change management).

Where the criteria land

The table below maps each SOC 2 Common Criterion to the GitLab capability that satisfies it and to the evidence artifact you hand to the auditor.

SOC 2 criterionGitLab capabilityEvidence artifact
CC3.2 Risk identificationSecurity inventory, dependency listInventory export, group vulnerability report
CC5.2, CC5.3 Control deploymentCompliance pipelines, scan execution policies in a separate policy projectPolicy YAML under version control
CC6.1–6.3 Access controlSAML/SCIM, enforced 2FA, custom roles, expiring membership, Security Manager roleMembers export with roles and expiry, access audit events
CC6.6–6.8 Credentials and integritySecret Detection with push protection, signed commits, protected branchesFindings, branch protection settings, signature status
CC7.1 Vulnerability detectionThe full scanner suite (see Scanner coverage)Vulnerability report with severity and detection date
CC7.2 Anomaly monitoringAudit event streaming to a SIEMSIEM ingestion records
CC7.3–7.5 Response and remediationIncident management, vulnerability workflow states with SLAIncident timelines, state changes with actor and timestamp
CC8.1 Change managementMerge request approval policies, no self-approval, protected branchesOne merge request link showing author, approvers, pipeline, and merge time
CC9.2 Supply chainDependency Scanning, license approval policy, CycloneDX SBOMSBOM per project, license violations

Criteria are defined in the 2017 AICPA Trust Services Criteria.

What this means: GitLab already produces the artifacts for CC6, CC7, and CC8, the criteria that dominate an engineering SOC 2 sample. Your work is to enforce them above the project level, so the artifacts appear by default instead of by convention.

Access control (CC6.1–6.3)

Custom roles let you grant fine-grained permissions beyond the default roles and follow the principle of least privilege. Pair them with SAML/SCIM provisioning, enforced two-factor authentication, and membership expiry dates so that access is revoked on schedule. The members export and access audit events become your CC6 evidence.

GitLab custom roles

Credentials and integrity (CC6.6–6.8)

Protected branches and Code Owners control who can change which code. Signed commits prove each change came from the person it claims to come from. Secret Detection with push protection blocks a credential before it ever reaches the repository.

Protected branches

Commit signed with verified signature

Anomaly monitoring (CC7.2)

Audit events record changes across groups and projects, with the actor and timestamp of each one. Streaming them to your SIEM puts GitLab activity alongside the rest of your monitoring, and the ingestion records serve as CC7.2 evidence.

Project-level audit events

Change management (CC8.1)

For a sampled change, the auditor wants to see who wrote it, who approved it, that the pipeline passed, and when it merged. In GitLab, that is a single merge request link. Merge request approval policies, a ban on self-approval, and protected branches ensure that every change follows the same path.

Scanner coverage

No single scanner satisfies CC7.1, because it requires coverage of code, dependencies, containers, infrastructure, and runtime together. The table below shows which criteria each scanner supports and how its results are enforced.

ScannerPrimary criteriaEnforcement mechanism
SAST / Advanced SASTCC7.1Scan execution policy; merge request approval policy on new critical and high findings
Business logic scanning (beta)CC6.1, CC7.1Scan profile runs on every merge request; full-repository scans feed the vulnerability report
Secret DetectionCC6.1, CC6.6, CC6.7Pre-receive push protection blocks the commit
Dependency ScanningCC7.1, CC9.2Scan execution policy; merge request approval gated on severity
License approval policyCC9.2Blocks merge on a disallowed license
Container ScanningCC7.1, CC6.8, CC9.2Scan execution policy; scheduled registry rescans
IaC ScanningCC6.6, CC6.8, CC7.1Scan execution policy on infrastructure repositories
DAST / API security testingCC7.1, CC6.1Scheduled policy against staging
Coverage-guided fuzzingCC7.1Pipeline job in the compliance pipeline
SBOM / dependency listCC9.2, CC3.2Generated by every compliant pipeline
Operational container scanningCC7.1, CC7.2Agent-based scheduled scan

What this means: The enforcement column is the part auditors actually test. A scan that runs but blocks nothing is telemetry, not a control.

That is why scanners should be enforced through a scan execution policy in the policy project instead of through an include: that each project can edit or remove. For example:

      scan_execution_policy:
  - name: SOC 2 baseline scans
    description: Run SAST, Secret Detection, and Dependency Scanning on every pipeline
    enabled: true
    rules:
      - type: pipeline
        branches:
          - "*"
    actions:
      - scan: sast
      - scan: secret_detection
      - scan: dependency_scanning

    

Once a pipeline runs, findings appear directly in the merge request, and a merge request approval policy can require security sign-off before vulnerable code merges.

Merge request view of introduced vulnerability

Every compliant pipeline also generates a software bill of materials (SBOM), which you can review at the group level. This gives you CC9.2 and CC3.2 evidence without a separate tool.

Group-level dependency list (SBOM)

The security dashboard aggregates results from every scanner across projects, so you can track vulnerability trends over the full audit window.

Group-level Security Dashboard


Security Dashboard

Where AI helps

GitLab Duo shortens the slowest steps in the controls above: triage, remediation, and evidence summaries.

Duo capabilityWhat it shortensCriterion
Vulnerability ExplanationDocuments each triage decision with reasoning, not just a severity labelCC7.1, CC7.4
Vulnerability ResolutionTime to remediate against your stated SLACC7.5
Secret false positive detectionSeparates real credential exposure from noiseCC6.6, CC7.1
Business logic scanningFinds broken authorization, missing access checks, and mass assignment that pattern-based scanners missCC6.1, CC7.1
Duo Code ReviewAdds review feedback beneath human approval, never in place of itCC8.1
Duo Security Analyst agentRisk-based triage and audit-ready evidence summariesCC3.2, CC7.1
Session-based AI audit trailProves what agents did, streamed to the same SIEMCC7.2

What this means: Duo accelerates controls; it does not replace them. Auditors will ask how AI is governed, and that answer matters as much as the speed gains:

  • Agents act within the permissions of the user who requested them.
  • Agent-authored code clears the same gates as human-authored code.
  • Every agent session is logged.

A human remains accountable for every merge.

What GitLab does not cover

SOC 2 spans the whole organization, not just engineering. These obligations stay outside GitLab:

ObligationWhere it gets done
HR controls, security training, background checksHRIS and training platform
Device management, endpoint protectionMDM vendor
Physical and environmental securityYour cloud provider's own SOC 2 report
Production cloud IAM and infrastructure access reviewCloud IAM (GitLab covers code, CI, and registry access only)
Vendor and subservice organization monitoringGRC tooling (GitLab covers the open source slice through the SBOM)
Business continuity and disaster recovery testingDR runbooks and test records
Access review sign-off, policy attestationYour attestation workflow (GitLab supplies the data)
The audit itselfA licensed CPA firm

What this means: GitLab covers the engineering half of the control set, which is the more expensive half to evidence manually. A GRC vendor is still useful, but you can scope it to corporate and HR controls instead of having it screen-scrape your pipelines.

Get started

Framework requirements and controls, the compliance status report, security policies, the security inventory, and most scanners require GitLab Ultimate. Compliance frameworks are available as labels in GitLab Premium, but adherence reporting is not.

To start, apply the SOC 2 framework template to your in-scope projects, then move your scanners into scan execution policies. After that, check the security inventory for gaps before your review window opens.

Try these features with a free trial of GitLab Ultimate.

Read more

We want to hear from you

Enjoyed reading this blog post or have questions or feedback? Share your thoughts by creating a new topic in the GitLab community forum.

Share your feedback

Start building faster today

See what your team can do with the intelligent orchestration platform for DevSecOps.