/
SECURITY.md
63 lines (46 loc) · 2.74 KB
/
SECURITY.md
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
# Responsible Disclosure Policy
Open Synthesis Responsible Disclosure Policy
We take the security of our systems seriously, and we value the security community. The responsible disclosure of
security vulnerabilities helps us ensure the security and privacy of our users.
**Guidelines**
We require 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; and
* Keep information about any vulnerabilities you’ve discovered confidential between yourself and Open Synthesis until
we’ve had [60] 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);
* Recognize your contribution on our Security Researcher Hall of Fame, if you are the first to report the issue and we
make a code or configuration change based on the issue.
**Scope**
* https://www.opensynthesis.org
* https://open-synthesis-sandbox.herokuapp.com/
**Out of scope**
Any services hosted by 3rd party providers and services are excluded from scope. These services include, but are not
limited to:
* GitHub
* Gitter
* Rollbar
* SendGrid
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 by
emailing security@opensynthesis.org. 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 Hall of Fame.
If you’d like to encrypt the information, please use the following PGP key: https://keybase.io/tschiller.