Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

outline a vulnerability disclosure program (for discussion first) #47

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

ioweb-gr
Copy link

I've read a bit of Google's guide for running a Vulnerability Disclosure Program so I added a couple parts that I think should be added to the security policy so we can discuss them over a pull request.

This is my first time touching a ruby application and I'm not sure I did it correctly so don't merge or anything yet. We also need to fill in some gaps here and decide issue severity, remediation procedure and disclosure.

@colinmollenhour
Copy link
Member

Thanks for the contribution, @ioweb-gr!

There is also the SECURITY.md file in the main repo but it doesn't hurt to have it on the website as well.

We have submitted a program via HackerOne and are awaiting approval there so I think some of this info may change, but I have no objection to merging it for now and then updating it when the time comes.

@ioweb-gr
Copy link
Author

ioweb-gr commented Jun 25, 2020

No problem. We still have to discuss on the severity levels which need to be listed exactly on the table, as well as what they mean for users before merging.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants