Using GitHub Protected Branches to Make SOC 2 Audits Suck Lessby@ajy
2,525 reads

Using GitHub Protected Branches to Make SOC 2 Audits Suck Less

March 4th 2020
3 min
by @ajy 2,525 reads
tldt arrow
Read on Terminal Reader🖨️

Too Long; Didn't Read

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.

Company Mentioned

Mention Thumbnail
featured image - Using GitHub Protected Branches to Make SOC 2 Audits Suck Less
AJ HackerNoon profile picture

@ajy

AJ

About @ajy
LEARN MORE ABOUT @AJY'S EXPERTISE AND PLACE ON THE INTERNET.
react to story with heart

RELATED STORIES

L O A D I N G
. . . comments & more!
Hackernoon hq - po box 2206, edwards, colorado 81632, usa