|
1 | 1 | # Security Policy |
2 | 2 |
|
3 | | -## Supported Versions |
| 3 | +Python [provides a security policy and threat model](https://devguide.python.org/security/policy/) |
| 4 | +in the Python Development Guide documenting what bugs are vulnerabilities, |
| 5 | +how to structure reports, and what versions of Python accept reports. |
4 | 6 |
|
5 | | -The Python team applies security fixes according to the table |
6 | | -in [the devguide]( |
7 | | -https://devguide.python.org/versions/#supported-versions |
8 | | -). |
| 7 | +Python Security Response Team (PSRT) members |
| 8 | +balance security work against many other responsibilities. Please be thoughtful |
| 9 | +about the time and attention your report requires. Repeated failure to respect |
| 10 | +the security policy will result in future reports being rejected, or the |
| 11 | +reporter being banned from the ``python`` GitHub organization, regardless of |
| 12 | +technical merit. |
9 | 13 |
|
10 | 14 | ## Reporting a Vulnerability |
11 | 15 |
|
12 | | -Please read the guidelines on reporting security issues [on the |
13 | | -official website](https://www.python.org/dev/security/) for |
14 | | -instructions on how to report a security-related problem to |
15 | | -the Python team responsibly. |
| 16 | +The [Python security policy](https://devguide.python.org/security/policy/) |
| 17 | +documents [how to submit a vulnerability report](https://devguide.python.org/security/policy/#how-to-submit-a-vulnerability-report) |
| 18 | +using GitHub Security Advisories. Please read the security policy |
| 19 | +prior to filing a vulnerability report, especially the section on [what information to |
| 20 | +include and exclude](https://devguide.python.org/security/policy/#what-to-include-and-how-to-structure-a-vulnerability-report) |
| 21 | +in vulnerability reports. Following the security policy means the PSRT can |
| 22 | +quickly and efficiently triage your report, not following the security policy |
| 23 | +will only delay triaging your report. |
16 | 24 |
|
17 | | -To reach the response team, email `security at python dot org`. |
|
0 commit comments