Skip to content

Commit ad0cd2e

Browse files
Revise security issue reporting instructions (#10725)
Updated the reporting process for security issues to use the MSRC Researcher Portal and included additional guidelines for reporting.
1 parent a717e3b commit ad0cd2e

1 file changed

Lines changed: 7 additions & 19 deletions

File tree

SECURITY.md

Lines changed: 7 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -10,25 +10,13 @@ Microsoft serves as the primary maintainer of this repository. If you believe yo
1010

1111
**Please do not report security vulnerabilities through public GitHub issues.**
1212

13-
Instead, please report them to the Microsoft Security Response Center (MSRC) at [https://msrc.microsoft.com/create-report](https://aka.ms/opensource/security/create-report).
14-
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://aka.ms/opensource/security/pgpkey).
16-
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://aka.ms/opensource/security/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://aka.ms/opensource/security/bounty) page for more details about our active programs.
13+
Security issues and bugs should be reported privately to the Microsoft Security Response Center (MSRC), via the [MSRC Researcher Portal](https://msrc.microsoft.com/report/vulnerability/new).
14+
15+
You should receive a response within 24 hours. If for some reason you do not, please follow up via the [MSRC Researcher Portal](https://msrc.microsoft.com/report/vulnerability/), using the Message functionality found at the bottom of the Activity tab on your vulnerability report.
16+
17+
Further information can be found in the MSRC [Report an issue and submission guidelines](https://www.microsoft.com/en-us/msrc/faqs-report-an-issue).
18+
19+
Reports via MSRC may qualify for the Microsoft Open Source Bug Bounty. Details of the Microsoft Open Source Bug Bounty Program including terms and conditions are at [https://aka.ms/corebounty](https://aka.ms/corebounty).
3220

3321
## Preferred Languages
3422

0 commit comments

Comments
 (0)