|
a |
|
b/SECURITY.md |
|
|
1 |
## Security |
|
|
2 |
|
|
|
3 |
NVIDIA is dedicated to the security and trust of our software products and services, including all source code repositories managed through our organization. |
|
|
4 |
|
|
|
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/GitLab.** |
|
|
6 |
|
|
|
7 |
## Reporting Potential Security Vulnerability in an NVIDIA Product |
|
|
8 |
|
|
|
9 |
To report a potential security vulnerability in any NVIDIA product: |
|
|
10 |
- Web: [Security Vulnerability Submission Form](https://www.nvidia.com/object/submit-security-vulnerability.html) |
|
|
11 |
- E-Mail: psirt@nvidia.com |
|
|
12 |
- 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) |
|
|
13 |
- Please include the following information: |
|
|
14 |
- Product/Driver name and version/branch that contains the vulnerability |
|
|
15 |
- Type of vulnerability (code execution, denial of service, buffer overflow, etc.) |
|
|
16 |
- Instructions to reproduce the vulnerability |
|
|
17 |
- Proof-of-concept or exploit code |
|
|
18 |
- Potential impact of the vulnerability, including how an attacker could exploit the vulnerability |
|
|
19 |
|
|
|
20 |
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. |
|
|
21 |
|
|
|
22 |
## NVIDIA Product Security |
|
|
23 |
|
|
|
24 |
For all security-related concerns, please visit NVIDIA's Product Security portal at https://www.nvidia.com/en-us/security |