-
Notifications
You must be signed in to change notification settings - Fork 2k
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
feat: add a security policy for Haystack #3130
Conversation
02a0170
to
ba85be1
Compare
SECURITY.md
Outdated
|
||
We will keep the reporter updated as the security issue moves through our process. | ||
|
||
Our goal is to disclose bugs as soon as possible once a user mitigation is available. We |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here we're saying that we want to disclose bugs but only after we have a user mitigation. And if we don't have a user mitigation, we won't disclose bugs. Is this what we want to say?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The idea is if we fix the bug, we disclose it right ahead. If we don't, the researcher has the right to eventually disclose it anyways but we would appreciate coordination.
Co-authored-by: Agnieszka Marzec <[email protected]>
Related Issues
Proposed Changes:
After setting up an incident response process internally, we're ready to publish a Security Policy for Haystack
Checklist