Skip to content

Commit ff810c0

Browse files
authored
Add SECURITY.md (#1179)
1 parent accd645 commit ff810c0

File tree

3 files changed

+39
-0
lines changed

3 files changed

+39
-0
lines changed

.github/workflows/config/spellcheck_config.yml

+3
Original file line numberDiff line numberDiff line change
@@ -39,6 +39,9 @@ matrix:
3939
- open: '([A-Za-z_\\\/]+\.)+'
4040
close: '($|(?=[^a-z]))'
4141
content: '\S+?'
42+
# Ignore email addresses
43+
- open: '\b[A-Za-z0-9._%+-]+@'
44+
close: '[A-Za-z0-9.-]+\.[A-Z|a-z]{2,}\b'
4245

4346
- name: rst
4447
sources:

.github/workflows/config/spelling_allowlist.txt

+2
Original file line numberDiff line numberDiff line change
@@ -59,6 +59,7 @@ OpenQASM
5959
OpenSSL
6060
OpenSUSE
6161
POSIX
62+
PSIRT
6263
Pauli
6364
Paulis
6465
PyPI
@@ -88,6 +89,7 @@ VQE
8889
Vazirani
8990
WSL
9091
accessor
92+
acknowledgement
9193
adjoint
9294
al
9395
ansatz

SECURITY.md

+34
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,34 @@
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+
- E-Mail: <[email protected]>
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

Comments
 (0)