]> wirehaze git hosting - MS-DOS.git/blob - SECURITY.md

wirehaze git hosting

Moving localized READMEs
[MS-DOS.git] / SECURITY.md
1 <!-- BEGIN MICROSOFT SECURITY.MD V0.0.9 BLOCK -->
2
3 ## Security
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) and [Xamarin](https://github.com/xamarin).
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://aka.ms/security.md/definition), please report it to us as described below.
8
9 **Since MS-DOS is historical reference software, this file is in place as a template only.**
10
11 ## Reporting Security Issues
12
13 **Please do not report security vulnerabilities through public GitHub issues.**
14
15 Instead, please report them to the Microsoft Security Response Center (MSRC) at [https://msrc.microsoft.com/create-report](https://aka.ms/security.md/msrc/create-report).
16
17 If you prefer to submit without logging in, send email to [secure@microsoft.com](mailto:secure@microsoft.com). If possible, encrypt your message with our PGP key; please download it from the [Microsoft Security Response Center PGP Key page](https://aka.ms/security.md/msrc/pgp).
18
19 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).
20
21 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:
22
23 * Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.)
24 * Full paths of source file(s) related to the manifestation of the issue
25 * The location of the affected source code (tag/branch/commit or direct URL)
26 * Any special configuration required to reproduce the issue
27 * Step-by-step instructions to reproduce the issue
28 * Proof-of-concept or exploit code (if possible)
29 * Impact of the issue, including how an attacker might exploit the issue
30
31 This information will help us triage your report more quickly.
32
33 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://aka.ms/security.md/msrc/bounty) page for more details about our active programs.
34
35 ## Preferred Languages
36
37 We prefer all communications to be in English.
38
39 ## Policy
40
41 Microsoft follows the principle of [Coordinated Vulnerability Disclosure](https://aka.ms/security.md/cvd).
42
43 <!-- END MICROSOFT SECURITY.MD BLOCK -->