Code changes should be reviewed by peers before merging

TEST-217: Code changes should be reviewed by peers before merging
What This Test Checks
Remediation

TEST-217: Code changes should be reviewed by peers before merging

Checks that all code changes are reviewed by at least one peer before merging in GitLab. Integration: Gitlab SLA: 7 days Responsible Role: InfoSec Officer / CISO

This test runs automatically when the integration is connected. Results appear in your Tests dashboard with pass/fail evidence and timestamps.

What This Test Checks

This automated compliance test verifies that your Gitlab environment meets security best practices. When DSALTA detects a failure, you will receive an alert with remediation guidance.

Remediation

Content coming soon. This page will include step-by-step remediation instructions.

Branch protection rules should be enforced for admins GitLab access should be removed for offboarded users

Getting Connected

Identity Providers

Cloud Infrastructure

Code Repositories

Security & Monitoring

Databases

SaaS & Productivity

Code changes should be reviewed by peers before merging

TEST-217: Code changes should be reviewed by peers before merging

What This Test Checks

Remediation

Getting Connected

Identity Providers

Cloud Infrastructure

Code Repositories

Security & Monitoring

Databases

SaaS & Productivity

​TEST-217: Code changes should be reviewed by peers before merging

​What This Test Checks

​Remediation

TEST-217: Code changes should be reviewed by peers before merging

What This Test Checks

Remediation