|
1 |
| -<!-- BEGIN MICROSOFT SECURITY.MD V0.0.5 BLOCK --> |
| 1 | +# Security Policy |
2 | 2 |
|
3 |
| -## Security |
| 3 | +## Supported Versions |
4 | 4 |
|
5 |
| -Microsoft takes the security of our software products and services seriously, which includes all source code repositories managed through our GitHub organizations, which include [Microsoft](https://github.com/Microsoft), [Azure](https://github.com/Azure), [DotNet](https://github.com/dotnet), [AspNet](https://github.com/aspnet), [Xamarin](https://github.com/xamarin), and [our GitHub organizations](https://opensource.microsoft.com/). |
| 5 | +We provide security updates for `main` and for the most recent minor (`X.Y`) release series of TorchGeo. Security updates will be made available as patch (`X.Y.1`, `X.Y.2`, etc.) releases. |
6 | 6 |
|
7 |
| -If you believe you have found a security vulnerability in any Microsoft-owned repository that meets [Microsoft's definition of a security vulnerability](https://docs.microsoft.com/en-us/previous-versions/tn-archive/cc751383%28v=technet.10%29), please report it to us as described below. |
| 7 | +For more on Spack's release structure, see our |
| 8 | +[Wiki](https://github.com/microsoft/torchgeo/wiki/Releasing-Instructions). |
8 | 9 |
|
9 |
| -## Reporting Security Issues |
| 10 | +## Reporting a Vulnerability |
10 | 11 |
|
11 |
| -**Please do not report security vulnerabilities through public GitHub issues.** |
| 12 | +You can report a vulnerability using GitHub's private reporting feature: |
12 | 13 |
|
13 |
| -Instead, please report them to the Microsoft Security Response Center (MSRC) at [https://msrc.microsoft.com/create-report](https://msrc.microsoft.com/create-report). |
| 14 | +1. Go to [https://github.com/microsoft/torchgeo/security](https://github.com/microsoft/torchgeo/security). |
| 15 | +2. Click "Report a vulnerability" in the upper right corner of that page. |
| 16 | +3. Fill out the form and submit your draft security advisory. |
14 | 17 |
|
15 |
| -If you prefer to submit without logging in, send email to [[email protected]](mailto:[email protected]). If possible, encrypt your message with our PGP key; please download it from the [Microsoft Security Response Center PGP Key page](https://www.microsoft.com/en-us/msrc/pgp-key-msrc). |
| 18 | +More details are available in [GitHub's docs](https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing/privately-reporting-a-security-vulnerability). |
16 | 19 |
|
17 |
| -You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Additional information can be found at [microsoft.com/msrc](https://www.microsoft.com/msrc). |
18 |
| - |
19 |
| -Please include the requested information listed below (as much as you can provide) to help us better understand the nature and scope of the possible issue: |
20 |
| - |
21 |
| -- Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.) |
22 |
| -- Full paths of source file(s) related to the manifestation of the issue |
23 |
| -- The location of the affected source code (tag/branch/commit or direct URL) |
24 |
| -- Any special configuration required to reproduce the issue |
25 |
| -- Step-by-step instructions to reproduce the issue |
26 |
| -- Proof-of-concept or exploit code (if possible) |
27 |
| -- Impact of the issue, including how an attacker might exploit the issue |
28 |
| - |
29 |
| -This information will help us triage your report more quickly. |
30 |
| - |
31 |
| -If you are reporting for a bug bounty, more complete reports can contribute to a higher bounty award. Please visit our [Microsoft Bug Bounty Program](https://microsoft.com/msrc/bounty) page for more details about our active programs. |
32 |
| - |
33 |
| -## Preferred Languages |
34 |
| - |
35 |
| -We prefer all communications to be in English. |
36 |
| - |
37 |
| -## Policy |
38 |
| - |
39 |
| -Microsoft follows the principle of [Coordinated Vulnerability Disclosure](https://www.microsoft.com/en-us/msrc/cvd). |
40 |
| - |
41 |
| -<!-- END MICROSOFT SECURITY.MD BLOCK --> |
| 20 | +You can expect to hear back about security issues within two days. If your security issue is accepted, we will do our best to release a fix within a week. If fixing the issue will take longer than this, we will discuss timeline options with you. |
0 commit comments