Skip to content

Commit 0da9fe0

Browse files
authored
🔒 Create SECURITY.md
1 parent a50c06b commit 0da9fe0

File tree

1 file changed

+36
-0
lines changed

1 file changed

+36
-0
lines changed

‎SECURITY.md

+36
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
# Security Policy
2+
3+
## Supported Versions
4+
5+
We provide security updates and fixes actively for the latest major version of the project. Previous major versions are supported until 1 year after the release of the next major version.
6+
7+
| Version | Supported |
8+
|---------|--------------------|
9+
| 2.3.x | :white_check_mark: |
10+
| 2.2.x | :white_check_mark: |
11+
| 2.1.x | :x: |
12+
| < 2.0 | :x: |
13+
14+
## Reporting a Vulnerability
15+
16+
We take security very seriously. If you have found any issues that might have security implications, please send a report to our dedicated email at [[email protected]](mailto:[email protected]?subject=grpc-in-python%20-%20Security%20Issue) instead of posting a public issue on GitHub.
17+
18+
When reporting, please include as much information as possible to help us understand the scope and severity of the issue. This may include:
19+
20+
- A description of the vulnerability
21+
- Steps to reproduce the issue
22+
- Potential impacts of the vulnerability
23+
- Suggestions for mitigating the vulnerability, if any
24+
25+
Please avoid including sensitive information in the initial report. We will provide a secure, encrypted channel for further communication after the initial report.
26+
27+
### What to expect
28+
29+
After you have reported a vulnerability:
30+
31+
1. **Acknowledgement**: We will acknowledge your email within 3 business days.
32+
2. **Verification & Analysis**: Our security team will work to verify the vulnerability and determine its potential impacts.
33+
3. **Response & Mitigation**: We will aim to provide a first response, including our plans for mitigating the vulnerability, within 10 business days.
34+
4. **Communication**: If the vulnerability is confirmed, we will release a security advisory on our GitHub repository and might also communicate it via other channels.
35+
36+
We appreciate your effort in improving the security of our project and will acknowledge your contribution when we disclose the issue, unless you prefer to remain anonymous.

0 commit comments

Comments
 (0)