Skip to content

Commit bf0e531

Browse files
authored
Added vulnerability reporting process SECURITY.md (#279)
## Checklist <!-- Put an `x` in the boxes. All tasks must be completed and boxes checked before merging. --> - [x] 🤖 This change is covered by unit tests as required. - [x] 🤹 All required manual testing has been performed. - [x] 🛡️ Security impacts have been considered. - [x] 📖 All documentation updates are complete. - [x] 🧠 This change does not change third-party dependencies
1 parent cb3d2fc commit bf0e531

File tree

1 file changed

+34
-0
lines changed

1 file changed

+34
-0
lines changed

SECURITY.md

Lines changed: 34 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,34 @@
1+
# Open-CMSIS-Pack Security Policy
2+
3+
This document outlines the security procedures and policies for the Open-CMSIS-Pack cmsis-toolbox project.
4+
5+
## Table of Contents
6+
- [Reporting a Security Issue](#reporting-a-security-issue)
7+
- [Vulnerability Management](#vulnerability-management)
8+
- [Improving This Policy](#improving-this-policy)
9+
10+
## Reporting a Security Issue
11+
12+
The Open-CMSIS-Pack cmsis-toolbox maintainers take security issues seriously and appreciate responsible disclosure. Your efforts to improve project security are highly valued.
13+
14+
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). To submit a report, please include:
15+
16+
- A detailed description of the issue
17+
- Steps to reproduce the vulnerability
18+
- Affected project versions
19+
- Any known mitigations
20+
21+
A maintainer will acknowledge your report as soon as possible and guide the next steps. We will keep you informed of progress toward a fix and may request additional details if needed.
22+
23+
## Vulnerability Management
24+
25+
Once a security issue is reported, the maintainers will:
26+
27+
1. Confirm the issue
28+
2. Identify/Confirm affected versions
29+
3. Audit related code for similar vulnerabilities
30+
4. Develop and release patches for maintained versions
31+
32+
## Improving This Policy
33+
34+
If you have suggestions for improving this process, please open an issue or submit a pull request.

0 commit comments

Comments
 (0)