GitLab
Protected-branch and merge-approval settings across your GitLab groups, on GitLab.com or a self-managed instance, evidencing that changes are authorised before they merge.
What CMDash reads
- Branch protection & merge approvals
Syncs only read from GitLab. Some integrations also support write-back actions on Command and Enterprise plans, such as opening a ticket or deactivating a user.
How you connect
An API key or token you create in the vendor console and enter in CMDash.
Once connected, CMDash syncs it every 4 hours by default. What it finds maps to your controls through rules you install or write.
Where this fits in your frameworks
- SOC 2 Type II — Branch protection & merge approvals feeds Change Management
- SOX ITGC — Branch protection & merge approvals feeds Change Management
This is where GitLab’s data is documented as relevant on our framework pages — not a pre-built, automatic control mapping. You configure which controls it maps to inside CMDash.
Also in Code Security
Ready to see your posture?
Start a 30-day free trial of any paid plan — a card is required, and it converts unless you cancel — or sign up for Free with no card at all.