Feature Request: Role (Security Manager?) granting automatic access to Security Advisories #203354
Unanswered
epuertat
asked this question in
Code Security
Replies: 1 comment
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Product Feedback
💬 Feature/Topic Area
Other
Discussion Details
Current: Right now only Org Owners and Repo Admins are granted access to Sec. Advisories. However, in big projects, like https://github.com/ceph/, there's a specific @ceph/security team (with Security Manager role), which might include non-Org Owners nor Repo Admins. Since the Security Manager role doesn't give them access to vulnerability reports so far, that forces Org Owners or Repo Admins to manually review and add @ceph/security team to each advisory.
Proposed: either extend Security Manager role, or add a new super-charged Security Whatever role granting access to Security Advisories.
Benefit: it separates day to day management role (Org Owner, Repo Admin) from security duties. It gives security experts full access to all security related workflows.
All reactions