GitHub made custom repository role permissions for security advisories generally available on November 20. Org owners can now let people work on repository security advisories and private vulnerability reports without making them repo admins or giving them the org-wide security manager role. Four new permissions sit under Security when you create or edit a custom role: View security advisories; Create, Edit, and Manage (comment, manage collaborators, create a temporary private fork); Accept private vulnerability reports and close or reopen advisories; and Publish advisories and request CVEs. Merging from a temporary private fork still needs an admin or security manager, these roles can’t delete a private fork, and confidential comments require Create, Edit, and Manage plus write access.
My take
Least privilege for vuln handling, finally. Give your maintainers exactly the advisory powers they need on the repos they own, and stop handing out admin just so someone can triage a report.
God Bless, and Happy hacking!