-
Notifications
You must be signed in to change notification settings - Fork 208
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'main' into cleanup_v15
- Loading branch information
Showing
1 changed file
with
24 additions
and
0 deletions.
There are no files selected for viewing
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,24 @@ | ||
## How to Report a Security Bug | ||
|
||
If you believe you have found a security vulnerability in Stride, | ||
you can report it to our primary vulnerability disclosure email **[email protected]**. | ||
|
||
Please include the issue details, reproduction, impact, and other | ||
information. Please submit only one unique email thread per vulnerability. | ||
|
||
Artifacts from an email report are saved at the time the email is triaged. | ||
Please note: our team is not able to monitor dynamic content (e.g. a Google | ||
Docs link that is edited after receipt) throughout the lifecycle of a report. | ||
If you would like to share additional information or modify previous | ||
information, please include it in an additional reply as an additional attachment. | ||
|
||
***Please DO NOT file a public issue in this repository to report a security vulnerability.*** | ||
|
||
### Guidelines | ||
We require that all researchers: | ||
- Abide by this policy to disclose vulnerabilities, and avoid posting vulnerability information in public places, including GitHub, Discord, Telegram, and Twitter. Make every effort to avoid privacy violations, degradation of user experience, disruption to production systems (including but not limited to the Cosmos Hub), and destruction of data. | ||
- Keep any information about vulnerabilities that you’ve discovered confidential between yourself and the Stride engineering team until the issue has been resolved and disclosed. | ||
- Avoid posting personally identifiable information, privately or publicly. | ||
|
||
If you follow these guidelines when reporting an issue to us, we commit to: | ||
- Work with you to understand, resolve and ultimately disclose the issue in a timely fashion |