|
| 1 | +## Security |
| 2 | + |
| 3 | +The Source Authors takes the security of our software products and services |
| 4 | +seriously, which includes all source code repositories managed through our |
| 5 | +GitHub organization, which include |
| 6 | +[Source-Authors](https://github.com/Source-Authors). |
| 7 | + |
| 8 | +If you believe you have found a security vulnerability in any |
| 9 | +Source-Authors-owned repository that meets |
| 10 | +[NIST Computer Security Resource Center definition of a security vulnerability](https://csrc.nist.gov/glossary/term/vulnerability), |
| 11 | +please report it to us as described below. |
| 12 | + |
| 13 | +## Reporting Security Issues |
| 14 | + |
| 15 | +**Please do not report security vulnerabilities through public GitHub issues.** |
| 16 | + |
| 17 | +Instead, please send email to |
| 18 | + |
| 19 | + |
| 20 | +You should receive a response within 24 hours. If for some reason you do not, |
| 21 | +please follow up via email to ensure we received your original message. |
| 22 | + |
| 23 | +Please include the requested information listed below (as much as you can |
| 24 | +provide) to help us better understand the nature and scope of the possible |
| 25 | +issue: |
| 26 | + |
| 27 | + * Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, |
| 28 | + etc.) |
| 29 | + * Full paths of source file(s) related to the manifestation of the issue |
| 30 | + * The location of the affected source code (tag/branch/commit or direct URL) |
| 31 | + * Any special configuration required to reproduce the issue |
| 32 | + * Step-by-step instructions to reproduce the issue |
| 33 | + * Proof-of-concept or exploit code (if possible) |
| 34 | + * Impact of the issue, including how an attacker might exploit the issue |
| 35 | + |
| 36 | +This information will help us triage your report more quickly. |
| 37 | + |
| 38 | +## Preferred Languages |
| 39 | + |
| 40 | +We prefer all communications to be in English. |
| 41 | + |
| 42 | +## Policy |
| 43 | + |
| 44 | +Source-Authors follows the principle of |
| 45 | +[ISO/IEC 29147:2018 Information technology — Security techniques — Vulnerability disclosure](https://www.iso.org/standard/72311.html). |
0 commit comments