@tduncan / Nvidia-Optimization-Stack-VLLM Mirror · read-only / commits / ce1917fcf2
Fork 0

A high-throughput and memory-efficient inference and serving engine for LLMs

Mirrored from https://github.com/tduncan-lum/Nvidia-Optimization-Stack---VLLM.git

Synced Nov 16, 03:15 UTC

[Doc] Create a vulnerability management team (#9925)

Signed-off-by: Russell Bryant <rbryant@redhat.com>

Russell Bryant committed Jan 7, 2025 at 01:57 UTC ce1917fcf211458dfbe6bb86d6a9d2d9bd346e63
3 files changed +45 -1
SECURITY.md
+1 -1
@@ -4,7 +4,7 @@
4
5 If you believe you have found a security vulnerability in vLLM, we encourage you to let us know right away. We will investigate all legitimate reports and do our best to quickly fix the problem.
6
7 -Please report security issues privately using [the vulnerability submission form](https://github.com/vllm-project/vllm/security/advisories/new).
7 +Please report security issues privately using [the vulnerability submission form](https://github.com/vllm-project/vllm/security/advisories/new). Reports will then be triaged by the [vulnerability management team](https://docs.vllm.ai/contributing/vulnerability_management/).
8
9 ---
10
docs/source/contributing/vulnerability_management.md new
+43
@@ -0,0 +1,43 @@
1 +# Vulnerability Management
2 +
3 +## Reporting Vulnerabilities
4 +
5 +As mentioned in the [security
6 +policy](https://github.com/vllm-project/vllm/tree/main/SECURITY.md), security
7 +vulnerabilities may be reported privately to the project via
8 +[GitHub](https://github.com/vllm-project/vllm/security/advisories/new).
9 +
10 +## Vulnerability Management Team
11 +
12 +Once a vulnerability has been reported to the project, the Vulnerability
13 +Management Team (VMT) is responsible for managing the vulnerability. The VMT is
14 +responsible for:
15 +
16 +- Triaging the vulnerability.
17 +- Coordinating with reporters and project maintainers on vulnerability analysis
18 + and resolution.
19 +- Drafting of security advisories for confirmed vulnerabilities, as appropriate.
20 +- Coordination with project maintainers on a coordinated release of the fix and
21 + security advisory.
22 +
23 +### Security Advisories
24 +
25 +Advisories are published via GitHub through the same system used to report
26 +vulnerabilities. More information on the process can be found in the [GitHub
27 +documentation](https://docs.github.com/en/code-security/security-advisories/working-with-repository-security-advisories/about-repository-security-advisories).
28 +
29 +### Team Members
30 +
31 +We prefer to keep all vulnerability-related communication on the security report
32 +on GitHub. However, if you need to contact the VMT directly for an urgent issue,
33 +you may contact the following individuals:
34 +
35 +- Simon Mo - simon.mo@hey.com
36 +- Russell Bryant - rbryant@redhat.com
37 +
38 +## Slack Discussion
39 +
40 +You may use the `#security` channel in the [VLLM Slack](https://slack.vllm.ai)
41 +to discuss security-related topics. However, please do not disclose any
42 +vulnerabilities in this channel. If you need to report a vulnerability, please
43 +use the GitHub security advisory system or contact a VMT member privately.
docs/source/index.md
+1
@@ -169,6 +169,7 @@ contributing/overview
169 contributing/profiling/profiling_index
170 contributing/dockerfile/dockerfile
171 contributing/model/index
172 +contributing/vulnerability_management
173 ```
174
175 # Indices and tables