|
1 | | -# Open-CMSIS-Pack Security Policy |
| 1 | +# Open-CMSIS-Pack Security Policy |
2 | 2 |
|
3 | | -This document outlines the security procedures and policies for the Open-CMSIS-Pack vscode-cmsis-debugger project. |
| 3 | +This document outlines the security procedures and policies for the Open-CMSIS-Pack vscode-cmsis-debugger project. |
4 | 4 |
|
5 | | -## Table of Contents |
| 5 | +## Table of Contents |
6 | 6 |
|
7 | | -- [Reporting a Security Issue](#reporting-a-security-issue) |
8 | | -- [Vulnerability Management](#vulnerability-management) |
9 | | -- [Improving This Policy](#improving-this-policy) |
| 7 | +- [Reporting a Security Issue](#reporting-a-security-issue) |
| 8 | +- [Vulnerability Management](#vulnerability-management) |
| 9 | +- [Improving This Policy](#improving-this-policy) |
10 | 10 |
|
11 | | -## Reporting a Security Issue |
| 11 | +## Reporting a Security Issue |
12 | 12 |
|
13 | 13 | The Open-CMSIS-Pack vscode-cmsis-debugger maintainers take security issues seriously and appreciate responsible |
14 | | -disclosure. Your efforts to improve project security are highly valued. |
| 14 | +disclosure. Your efforts to improve project security are highly valued. |
15 | 15 |
|
16 | 16 | We use GitHub's [private vulnerability reporting](https://docs.github.com/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/privately-reporting-a-security-vulnerability) |
17 | 17 | guidelines. |
18 | 18 | To report a security issue, please click on |
19 | 19 | [Report a vulnerability](https://github.com/Open-CMSIS-Pack/vscode-cmsis-debugger/security/advisories/new) and |
20 | | -include: |
| 20 | +include: |
21 | 21 |
|
22 | | -- A detailed description of the issue |
23 | | -- Steps to reproduce the vulnerability |
24 | | -- Affected project versions |
25 | | -- Any known mitigations |
| 22 | +- A detailed description of the issue |
| 23 | +- Steps to reproduce the vulnerability |
| 24 | +- Affected project versions |
| 25 | +- Any known mitigations |
26 | 26 |
|
27 | 27 | A maintainer will acknowledge your report as soon as possible and guide the next steps. We will keep you informed of |
28 | | -progress toward a fix and may request additional details if needed. |
| 28 | +progress toward a fix and may request additional details if needed. |
29 | 29 |
|
30 | | -## Vulnerability Management |
| 30 | +## Vulnerability Management |
31 | 31 |
|
32 | | -Once a security issue is reported, the maintainers will: |
| 32 | +Once a security issue is reported, the maintainers will: |
33 | 33 |
|
34 | | -1. Confirm the issue |
35 | | -2. Identify/Confirm affected versions |
36 | | -3. Audit related code for similar vulnerabilities |
37 | | -4. Develop and release patches for maintained versions |
| 34 | +1. Confirm the issue |
| 35 | +2. Identify/Confirm affected versions |
| 36 | +3. Audit related code for similar vulnerabilities |
| 37 | +4. Develop and release patches for maintained versions |
38 | 38 |
|
39 | | -## Improving This Policy |
| 39 | +## Improving This Policy |
40 | 40 |
|
41 | 41 | If you have suggestions for improving this process, please open an issue or submit a pull request. |
0 commit comments