Update security policies with bug bounty info #139
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cygnusv
previously approved these changes
May 4, 2023
mswilkison
reviewed
May 4, 2023
SECURITY.md
Outdated
|
|
||
| ## Reporting a Vulnerability Not Covered by the Bug Bounty Program | ||
|
|
||
| For those assets that are not covered in the Immunefi Bug Bounty program, (please see the updated program [here](https://immunefi.com/bounty/thresholdnetwork/)), if you identify any vulnerabilities within the Threshold Network code and outside our bounty program, please let us know. You can send an email to `security@threshold.network` with relevant information about your findings. We will work with researchers to coordinate vulnerability disclosure between our stakers, partners, and users to ensure the successful mitigation of vulnerabilities. |
Contributor
There was a problem hiding this comment.
do we prefer people to report out-of-scope issues to security@threshold.network or to just use immunefi anyway since we can escalate/scope in anything that's sufficiently important
Contributor
Author
There was a problem hiding this comment.
I would like to get more inputs on this issue, that’s a very good question
Member
There was a problem hiding this comment.
Good point, let's funnel everything through immunefi
derekpierre
reviewed
May 5, 2023
cygnusv
previously approved these changes
Jun 7, 2023
derekpierre
reviewed
Jun 7, 2023
This is a first draft to update the security policies across repositories with the immunefi bug bounty information after its launch (and first amendment) Requesting review and feedback on language
Co-authored-by: MacLane S Wilkison <maclane@nucypher.com>
Co-authored-by: Derek Pierre <derek.pierre@gmail.com>
This is a review of language on the security policy taking into account the given feedback to funnel all bugs through the Immunefi program. Please check if everything is correct.
removing assets out-of-scope to avoid duplicated maintenance of the list, and also making modifications regarding the severity classification of impacts (v2.2 -> v2.3)
remove spaces
Co-authored-by: Derek Pierre <derek.pierre@gmail.com>
pdyraga
approved these changes
Jun 15, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a first draft to update the security policies across repositories with the immunefi bug bounty information after its launch (and first amendment) Requesting review and feedback on language @mhluongo @mswilkison @cygnusv @pdyraga @derekpierre