From the course: GitHub Advanced Security Cert Prep by Microsoft Press

Unlock this course with a free trial

Join today to access over 24,700 courses taught by industry experts.

Describe how permissions are interpreted throughout a security workflow

Describe how permissions are interpreted throughout a security workflow - GitHub Tutorial

From the course: GitHub Advanced Security Cert Prep by Microsoft Press

Start my 1-month free trial Buy for my team

Describe how permissions are interpreted throughout a security workflow

“

- [Instructor] While permissions in not only GitHub Advanced Security Workflows, but throughout all of GitHub is layered, isn't it? Now when we're looking at least privileged permissions, not just, I would argue in GitHub Workflows, GitHub Actions Workflows, but throughout all of our GitHub ecosystem that we're responsible for, we're looking at layers, layers of controls that are coming down from a centralized higher level. We're talking about granular ownership, where we're giving, again, least privilege. Some folks at the repo level may be authorized to override or disable policies that are coming through org or enterprise-level GitHub settings. But above all else, our goal is to support least privilege authorization so that those who are collaborating with you on your repos have only those permissions as relevant for their job role. This is often called Role-Based Access Control or RBAC. Let's take a look at a case study example here. Let's say at the org level, we create a team…

Contents