GitHub Rulesets and Access as Code - New Rules, New Habits

Speakers

Most organisations cannot answer two questions about their own source code: what protects it, and who can reach it. Rulesets exist in some repositories and not in others, and they are never the same everywhere. Access granted to code only ever accumulates and is never revoked, and managing that is a manual task that falls to "someone". Fixing this changes how people work, and that is where the protection comes from. Every change to protection is reviewed before it applies, and every grant of access is approved by a second person. Nothing depends on anyone remembering how things are supposed to be. Mistakes and omissions are captured and corrected. No drift and no inappropriate access! This session walks through a working implementation of two engines, using IaC and GitHub Actions with a supporting act by Entra ID. The first declares rulesets as code, compares them against live configuration for drift, and realigns repositories automatically to adhere to the rules. It blocks. The second reports who has access to what code, with warnings when something is out of line. A team member can request access to a code base and a colleague approves it, with the grant applied automatically. Revoking access happens immediately, with no approval at all. Expect live configuration, real code, and the things that broke on the way. You leave with a model where protection survives the first time it is inconvenient, and where the answer to who can reach your code is a report rather than a screenshot.

An unhandled error has occurred. Reload 🗙