Skip to content

GitHub lets you delegate security advisories without admin access

Custom repository roles now carry four new security advisory permissions, so a maintainer can triage vulnerability reports without being made a repo admin or org-wide security manager.

GitHub made security advisory permissions for custom repository roles generally available on 20 November. Until now, working on a repository security advisory or private vulnerability report meant being a repository administrator or holding the organisation-wide security manager role, both of which hand over far more than advisory access.

The change adds four separate permissions an organisation owner can mix into a custom role: viewing draft advisories, creating and managing them, accepting private vulnerability reports and closing or reopening advisories, and publishing advisories or requesting a CVE. They apply per repository, so a maintainer can be given advisory access to the one repo they look after without seeing anything else in the organisation. Merging a fix from a temporary private fork still needs administrator or security manager access, and confidential comments are limited to those with the manage permission plus write access to the repo.

Why it matters: the old choice, full admin or nothing, pushed a lot of teams toward over-granting access just so one contributor could triage a report. Custom roles make it possible to hand off vulnerability handling to the people who actually fix the code, without widening who can change repository settings or billing.

The caveat: it needs a plan that supports custom repository roles, which means GitHub Enterprise Cloud, not every GitHub plan.

Share

Related reading

More from The Wire

All briefs