· 2 min read · Security & ops · 閱讀中文版
GitHub advisory permissions: separate access from release readiness
GitHub’s granular advisory permissions create room for clearer ownership. Define investigation, drafting and publishing responsibilities, then test both allowed and denied access.
On this page
Vulnerability handling needs enough access for people to investigate while keeping unpublished information within the right scope. More granular tool permissions are a useful opportunity to revisit the workflow.
What changed on November 20?
GitHub made security advisory permissions generally available through custom repository roles on supported plans. Teams can assign viewing, management, report acceptance and publishing capabilities. Merging from a temporary private fork still requires an administrator or security manager. See the official announcement for the full limitations.
The following is 8plus’s workflow guidance, not an audit of a particular organization or a report of measured rollout results.
Map responsibilities before assigning roles
Start with four activities: assess a report, prepare a fix and draft, review the release information, and publish. These do not require four different people, but each needs an owner and a backup.
For example, an on-call engineer can document reproduction conditions, a module maintainer can prepare the fix, and a release owner can verify affected versions and external wording. This is a suggested division of work, not an approval sequence enforced by the platform.
Publishing permission is not release readiness
Permissions answer who can act. The workflow must also explain when to act. Before publication, check the affected version range, whether the fix is included in the intended release, whether the wording contains unverified assumptions, and whether other maintainers need coordination.
Keep these checks in a shared work record. Instead of writing only “fixed,” record the commit, validation approach and unresolved items. If the conclusion changes, preserve the reason so the next person does not have to reconstruct the investigation.
Test denied access as well as allowed access
Use synthetic reports without real vulnerability details to validate new roles. Can the assigned person read the intended repository’s draft? Is an unauthorized account still blocked? Has a drafting role accidentally gained publishing capability?
Then exercise a handoff. When the primary owner is unavailable, can the backup find the status, identify the next contact and recognize a step that requires approval? A complete permissions screen and a workable operational process are separate acceptance criteria.
Revisit access when responsibilities change
Project transfers, completed external engagements and departures should trigger a role review. Record the reason, scope and review date for access. Also decide whether automation or AI assistance actually needs unpublished information; the ability to summarize it is not sufficient reason to expose everything to a tool.
Start with one repository. Complete the responsibility map, negative access tests and backup exercise before expanding. Granular permissions help when the team can explain both the access and the action it enables.
Related: State checks after PR events and Copilot team plugin rollout.