|
| 1 | +# Security |
| 2 | + |
| 3 | +NVIDIA is dedicated to the security and trust of our software products and |
| 4 | +services, including all source code repositories managed through our |
| 5 | +organization. |
| 6 | + |
| 7 | +If you need to report a security issue, please use the appropriate contact points |
| 8 | +outlined below. **Please do not report security vulnerabilities through GitHub.** |
| 9 | + |
| 10 | +## Reporting Potential Security Vulnerability in an NVIDIA Product |
| 11 | + |
| 12 | +To report a potential security vulnerability in any NVIDIA product: |
| 13 | + |
| 14 | +- Web: [Security Vulnerability Submission Form](https://www.nvidia.com/object/submit-security-vulnerability.html) |
| 15 | + |
| 16 | + - We encourage you to use the following PGP key for secure email communication: |
| 17 | + [NVIDIA public PGP Key for communication](https://www.nvidia.com/en-us/security/pgp-key) |
| 18 | + - Please include the following information: |
| 19 | + - Product/Driver name and version/branch that contains the vulnerability |
| 20 | + - Type of vulnerability (code execution, denial of service, buffer overflow, etc.) |
| 21 | + - Instructions to reproduce the vulnerability |
| 22 | + - Proof-of-concept or exploit code |
| 23 | + - Potential impact of the vulnerability, including how an attacker could |
| 24 | + exploit the vulnerability |
| 25 | + |
| 26 | +While NVIDIA currently does not have a bug bounty program, we do offer |
| 27 | +acknowledgement when an externally reported security issue is addressed under |
| 28 | +our coordinated vulnerability disclosure policy. Please visit our |
| 29 | +[Product Security Incident Response Team (PSIRT)](https://www.nvidia.com/en-us/security/psirt-policies/) |
| 30 | +policies page for more information. |
| 31 | + |
| 32 | +## NVIDIA Product Security |
| 33 | + |
| 34 | +For all security-related concerns, please visit [NVIDIA's Product Security portal](https://www.nvidia.com/en-us/security). |
0 commit comments