Skip to content

Commit 6f122cf

Browse files
Revise security reporting guidelines in SECURITY.md
Updated the SECURITY.md file to enhance clarity on reporting vulnerabilities and included specific contact information.
1 parent 480e09b commit 6f122cf

1 file changed

Lines changed: 20 additions & 9 deletions

File tree

SECURITY.md

Lines changed: 20 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,25 @@
1-
# Reporting vulnerabilities
1+
# Security
22

3-
Please email reports about any security related issues you find to `<TODO -- contact email here>`.
3+
NVIDIA is dedicated to the security and trust of our software products and services, including all source code repositories managed through our organization.
44

5-
Please use a descriptive subject line for your report email. After the initial reply to your report, the team will endeavor to keep you informed of the progress being made towards a fix and announcement.
5+
If you need to report a security issue, please use the appropriate contact points outlined below. **Please do not report security vulnerabilities through GitHub.** If a potential security issue is inadvertently reported via a public issue or pull request, NVIDIA maintainers may limit public discussion and redirect the reporter to the appropriate private disclosure channels.
66

7-
In addition, please include the following information along with your report:
7+
## Reporting Potential Security Vulnerability in an NVIDIA Product
88

9-
- Your name and affiliation (if any).
10-
- A description of the technical details of the vulnerabilities. It is very important to let us know how we can reproduce your findings.
11-
- An explanation who can exploit this vulnerability, and what they gain when doing so -- write an attack scenario. This will help us evaluate your report quickly, especially if the issue is complex.
12-
- Whether this vulnerability public or known to third parties. If it is, please provide details.
9+
To report a potential security vulnerability in any NVIDIA product:
1310

14-
If you believe that an existing (public) issue is security-related, please send an email to `<TODO - contact email here>`. The email should include the issue ID and a short description of why it should be handled according as a security issue.
11+
- Web: [Security Vulnerability Submission Form](https://www.nvidia.com/object/submit-security-vulnerability.html)
12+
- E-Mail: psirt@nvidia.com
13+
- We encourage you to use the following PGP key for secure email communication: [NVIDIA public PGP Key for communication](https://www.nvidia.com/en-us/security/pgp-key)
14+
- Please include the following information:
15+
- Product/Driver name and version/branch that contains the vulnerability
16+
- Type of vulnerability (code execution, denial of service, buffer overflow, etc.)
17+
- Instructions to reproduce the vulnerability
18+
- Proof-of-concept or exploit code
19+
- Potential impact of the vulnerability, including how an attacker could exploit the vulnerability
20+
21+
While NVIDIA currently does not have a bug bounty program, we do offer acknowledgement when an externally reported security issue is addressed under our coordinated vulnerability disclosure policy. Please visit our [Product Security Incident Response Team (PSIRT)](https://www.nvidia.com/en-us/security/psirt-policies/) policies page for more information.
22+
23+
## NVIDIA Product Security
24+
25+
For all security-related concerns, please visit NVIDIA's Product Security portal at https://www.nvidia.com/en-us/security

0 commit comments

Comments
 (0)