-
-
Notifications
You must be signed in to change notification settings - Fork 5.1k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[Doc] Propose a vulnerability management team
The project has a policy for how vulnerabilties are reported, but there is no specific indivudual(s) who has the responsibility for ensuring that these reports are acted on in a timely manner. To address this, I propose naming a "vulnerability management team" who would have this responsibility. The list of individuals that would seed this team is TBD. Signed-off-by: Russell Bryant <[email protected]>
- Loading branch information
Showing
2 changed files
with
36 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,35 @@ | ||
# Vulnerability Management | ||
|
||
## Reporting Vulnerabilities | ||
|
||
As mentioned in the [security | ||
policy](https://github.com/vllm-project/vllm/tree/main/SECURITY.md), security | ||
vulnerabilities may be reported privately to the project via | ||
[GitHub](https://github.com/vllm-project/vllm/security/advisories/new). | ||
|
||
## Vulnerability Management Team | ||
|
||
Once a vulnerability has been reported to the project, the Vulnerability | ||
Management Team (VMT) is responsible for managing the vulnerability. The VMT is | ||
responsible for: | ||
|
||
- Triaging the vulnerability. | ||
- Coordinating with reporters and project maintainers on vulnerability analysis | ||
and resolution. | ||
- Drafting of security advisories for confirmed vulnerabilities, as appropriate. | ||
- Coordination with project maintainers on a coordinated release of the fix and | ||
security advisory. | ||
|
||
### Security Advisories | ||
|
||
Advisories are published via GitHub through the same system used to report | ||
vulnerabilities. More information on the process can be found in the [GitHub | ||
documentation](https://docs.github.com/en/code-security/security-advisories/working-with-repository-security-advisories/about-repository-security-advisories). | ||
|
||
### Team Members | ||
|
||
We prefer to keep all vulnerability-related communication on the security report | ||
on GitHub. However, if you need to contact the VMT directly for an urgent issue, | ||
you may contact the following individuals: | ||
|
||
- ... TODO ... |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters