The News, Explained

On November 20, GitHub made security advisory permissions generally available in custom repository roles. A repository stores a project’s files and history. Organizations can delegate work on selected repositories rather than appointing the person as a repository administrator or an organization-wide security manager. Source

A security advisory supports private discussion and repair of a vulnerability in a public project before informing its users. A temporary private fork is a separate working copy used for that collaboration. A CVE is an identifier for a known vulnerability; requesting one does not publish the advisory. Receiving a report, collaborating on a fix and disclosing it are separate stages. Source

The four permissions separate viewing drafts, status and comments; creating, editing and managing advisories; accepting private reports and closing or reopening advisories; and publishing advisories and requesting CVEs. Create, Edit, and Manage includes viewing, collaborator management and temporary private fork creation. Accepting reports or publishing requires either View or Create, Edit, and Manage first. Source Source

Some boundaries remain. Merging, or integrating changes from a temporary private fork into the original project, still requires a repository administrator or security manager. People holding only the new permissions cannot delete that fork. Confidential comments require both Create, Edit, and Manage and repository write access. Publication decisions and merging code changes each have their own permission boundary. Source

The Enterprise Cloud documentation limits creation of these roles to Enterprise Cloud organizations and identifies organization owners as the creators. The Repository roles area in organization settings combines an inherited role with added permissions. Deleting a role reassigns its users, teams and pending invitations to the organization’s base permissions. Access after deletion therefore depends on that baseline. Source

The inherited role is Read, Triage, Write or Maintain: starting points for reading, organizing issues and requests, writing, or maintaining a project. A custom role keeps those permissions and adds selected capabilities. Permissions from other routes, including organization defaults and team membership, also accumulate. GitHub’s example is a member with a Read-based custom role who still has write access because the organization grants Write as its base permission. Source

OYOPICK’s Take

We see value in separating responsibility for handling a vulnerability from authority to disclose it. A team maintaining a public project can first decide who receives reports, who prepares the advisory and who publishes it, then map those responsibilities to permissions. Defining the actions to delegate is a more useful starting point than choosing a new role name.

Creating a narrow role alone is insufficient grounds to consider an access review complete. Organization and team permissions accumulate, and deleting a role leaves base permissions in place. Reviewing advisory visibility, publication authority and code-merging authority together should make this finer division of responsibilities more useful.