|
1 |
| -<!-- BEGIN MICROSOFT SECURITY.MD V0.0.9 BLOCK --> |
| 1 | +# Reporting Security Issues |
2 | 2 |
|
3 |
| -## Security |
| 3 | +Munson’s Pickles and Preserves take security bugs in Team Messaging System seriously. We appreciate your efforts to responsibly disclose your findings, and will make every effort to acknowledge your contributions. |
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) and [Xamarin](https://github.com/xamarin). |
| 5 | +To report a security issue, please use the GitHub Security Advisory ["Report a Vulnerability"](https://github.com/electron/electron/security/advisories/new) tab. |
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://aka.ms/security.md/definition), please report it to us as described below. |
| 7 | +Munson’s Pickles and Preserves will send a response indicating the next steps in handling your report. After the initial reply to your report, the security team will keep you informed of the progress towards a fix and full announcement, and may ask for additional information or guidance. |
8 | 8 |
|
9 |
| -## Reporting Security Issues |
| 9 | +Report security bugs in third-party modules to the person or team maintaining the module. You can also report a vulnerability through the [npm contact form](https://www.npmjs.com/support) by selecting "I'm reporting a security vulnerability". |
10 | 10 |
|
11 |
| -**Please do not report security vulnerabilities through public GitHub issues.** |
| 11 | +## The Electron Security Notification Process |
12 | 12 |
|
13 |
| -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). |
| 13 | +For context on Electron's security notification process, please see the [Notifications](https://github.com/electron/governance/blob/main/wg-security/membership-and-notifications.md#notifications) section of the Security WG's [Membership and Notifications](https://github.com/electron/governance/blob/main/wg-security/membership-and-notifications.md) Governance document. |
14 | 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/security.md/msrc/pgp). |
| 15 | +## Learning More About Security |
16 | 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://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://aka.ms/security.md/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://aka.ms/security.md/cvd). |
40 |
| - |
41 |
| -<!-- END MICROSOFT SECURITY.MD BLOCK --> |
| 17 | +To learn more about securing an Electron application, please see the [security tutorial](docs/tutorial/security.md). |
0 commit comments