|
| 1 | +# Security |
| 2 | + |
| 3 | +NVIDIA is dedicated to the security and trust of our software products and services, |
| 4 | +including all source code repositories managed through our organization. |
| 5 | + |
| 6 | +If you need to report a security issue, please use the appropriate contact points outlined |
| 7 | +below. **Please do not report security vulnerabilities through GitHub/GitLab.** |
| 8 | + |
| 9 | +## Reporting Potential Security Vulnerability in nvmath-python |
| 10 | + |
| 11 | +To report a potential security vulnerability in nvmath-python: |
| 12 | + |
| 13 | +- Web: [Security Vulnerability Submission |
| 14 | + 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: [NVIDIA |
| 17 | + 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 exploit the |
| 24 | + vulnerability |
| 25 | + |
| 26 | +While NVIDIA currently does not have a bug bounty program, we do offer acknowledgement when |
| 27 | +an externally reported security issue is addressed under our coordinated vulnerability |
| 28 | +disclosure policy. Please visit our [Product Security Incident Response Team |
| 29 | +(PSIRT)](https://www.nvidia.com/en-us/security/psirt-policies/) policies page for more |
| 30 | +information. |
| 31 | + |
| 32 | +## NVIDIA Product Security |
| 33 | + |
| 34 | +For all security-related concerns, please visit NVIDIA's Product Security portal at |
| 35 | +<https://www.nvidia.com/en-us/security>. |
| 36 | + |
0 commit comments