Using GitHub Protected Branches to Make SOC 2 Audits Suck Less

Written by ajy | Published 2020/03/04
Tech Story Tags: cybersecurity-compliance | github | sdlc | change-management-process | devsecops | devops | protected-branches | hackernoon-top-story

TLDR The software development process is an integral part of SOC 2 examinations. Enabling protected branches and implementing native security policies on these branches will make these audit experiences tolerable and less painful. GitHub defines protected branches in the following manner, “Protected branches ensure that collaborators on your repository cannot make irrevocable changes to branches.” Protecting a branch eliminates the risk of a planned or unplanned catastrophic event where a branch is deleted. This is the first step in enabling guardrails to secure your branch. Some additional checks or requirements can be enabled with a protected branch.via the TL;DR App

no story

Written by ajy | cloud security is fun
Published by HackerNoon on 2020/03/04