Skip to content

Draft: Add deployed branch is protected SOC 2 check

Huzaifa Iftikhar requested to merge 433201_deployed_branch_is_protected_soc_2_check into master

What does this MR do and why?

  1. Add deployed branch is protected SOC 2 check
  2. We are assuming that the deployed branch is the project's default branch as per this issue.

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

image

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

  1. Ensure you have GitLab ultimate license.
  2. Create a new project and visit the compliance centre dashboard. Eg: https://gdk.test:3000/groups/twitter/-/security/compliance_dashboard/standards_adherence
  3. Ensure that "Deployed branch is protected" check is visible on the dashboard.
  4. Create a new branch for that project. Go the project's repository settings and update the default branch to this new setting.
  5. Ensure that the status of the check is now set as failed.
  6. Again set the default branch to a protected branch.
  7. Refresh the compliance dashboard and ensure that the check "Deployed branch is protected" is updated to Success.

Related to #433201

Edited by Huzaifa Iftikhar

Merge request reports