This repository has been archived by the owner on Nov 16, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 38
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #486 from gratipay/security-program
start versioning security program text from H1
- Loading branch information
Showing
1 changed file
with
77 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,77 @@ | ||
#################################################################################### | ||
# # | ||
# This gets copied and pasted into a textarea on hackerone.com/gratipay whenever # | ||
# it changes. # | ||
# # | ||
#################################################################################### | ||
|
||
|
||
## Guidelines | ||
|
||
We ask that all researchers: | ||
|
||
* Make every effort to avoid privacy violations, degradation of user experience, disruption to production systems, and destruction of data during security testing; | ||
* Perform research only within the scope set out below; | ||
* Use the identified communication channels to report vulnerability information to us; | ||
* Report vulnerabilities as soon as you discover them; and | ||
* Keep information about any vulnerabilities you’ve discovered confidential between yourself and Gratipay until we’ve had 90 days to resolve the issue. | ||
|
||
If you follow these guidelines when reporting an issue to us, we commit to: | ||
|
||
* Not pursue or support any legal action related to your research; | ||
* Work with you to understand and resolve the issue quickly (including an initial confirmation of your report within 72 hours of submission). | ||
|
||
Additionally, if you are the first to report the issue, and we make a code or configuration change based on the issue, we commit to: | ||
|
||
* Recognize your contribution on HackerOne; | ||
* Reward you with a bounty, ranging from $1 to $100 based on the severity of the vulnerability and the quality of your report (reports received prior to 2016-01-31 are not eligible for monetary rewards). | ||
|
||
Please note that our policy is to fully disclose all resolved issues, in the interest of openness and transparency for our customers. | ||
|
||
## Scope | ||
|
||
* [https://gratipay.com](https://gratipay.com) | ||
* [https://grtp.co](https://grtp.co) | ||
* the [Aspen](http://aspen.io/) web framework | ||
* any other [software we publish](https://github.com/gratipay) | ||
|
||
## Out of scope | ||
|
||
Any services hosted by 3rd party providers and services are excluded from scope. | ||
|
||
In the interest of the safety of our users, staff, the Internet at large and you as a security researcher, the following test types are excluded from scope: | ||
|
||
* Findings from physical testing such as office access (e.g. open doors, tailgating) | ||
* Findings derived primarily from social engineering (e.g. phishing, vishing) | ||
* Findings from applications or systems not listed in the ‘Scope’ section | ||
* UI and UX bugs and spelling mistakes | ||
* Network level Denial of Service (DoS/DDoS) vulnerabilities | ||
|
||
Things we do not want to receive: | ||
|
||
* Personally identifiable information (PII) | ||
* Credit card holder data | ||
|
||
## How to Report a Security Vulnerability | ||
|
||
If you believe you’ve found a security vulnerability in one of our products or platforms, please [send it to us on HackerOne](https://hackerone.com/gratipay/reports/new). | ||
|
||
|
||
We prefer that you file reports on HackerOne, but we also accept reports via email to [email protected]. Please include the following details with your report: | ||
|
||
* Description of the location and potential impact of the vulnerability; | ||
* A detailed description of the steps required to reproduce the vulnerability (POC scripts, screenshots, and compressed screen captures are all helpful to us); and | ||
* Your name/handle and a link for recognition in our legacy [Hall of Fame](https://gratipay.com/about/security/hall-of-fame) (if reporting via email and not willing to join HackerOne). | ||
|
||
To encrypt your message, you may use [our PGP key](https://gratipay.com/about/security/pgp.asc): | ||
|
||
```sh | ||
$ curl https://gratipay.com/about/security/pgp.asc | gpg --import | ||
gpg: key 7A5F6B30: "Gratipay Security <[email protected]>" imported | ||
gpg: Total number processed: 1 | ||
gpg: imported: 1 | ||
$ | ||
``` | ||
|
||
We only use PGP to decrypt messages, never to encrypt messages or authenticate our identity. Instead, we'll create a ticket on HackerOne to track your report, which we'll invite you to join (see our [internal policy document](http://inside.gratipay.com/howto/handle-security-issues) for more details). If you do not wish to join HackerOne, we can acknowledge you instead on our legacy [Hall of Fame](https://gratipay.com/about/security/hall-of-fame). |