Skip to content

Commit 2392094

Browse files
authored
Merge pull request #54 from eclipse-biscuit/push-romwsuuuunnn
update SECURITY.md
2 parents c0fa698 + 8cc4a32 commit 2392094

1 file changed

Lines changed: 35 additions & 2 deletions

File tree

SECURITY.md

Lines changed: 35 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,37 @@
1-
# Security issues reporting
1+
# Security Policy
22

3-
Security issues can be reported via [github](https://github.com/eclipse-biscuit/biscuit-python/security).
3+
This Eclipse Foundation Project adheres to the [Eclipse Foundation Vulnerability Reporting Policy](https://www.eclipse.org/security/policy/).
44

5+
## How To Report a Vulnerability
6+
7+
If you think you have found a vulnerability in this repository, please report it to us through coordinated disclosure.
8+
9+
**Please do not report security vulnerabilities through public issues, discussions, or change requests.**
10+
11+
Instead, report it using one of the following ways:
12+
13+
* Contact the [Eclipse Foundation Security Team](mailto:security@eclipse-foundation.org) via email
14+
* Create a [confidential issue](https://gitlab.eclipse.org/security/vulnerability-reports/-/issues/new?issuable_template=new_vulnerability) in the Eclipse Foundation Vulnerability Reporting Tracker
15+
* Report a [vulnerability](https://github.com/eclipse-biscuit/biscuit-python/security/advisories/new) directly via private vulnerability reporting on GitHub
16+
17+
You can find more information about reporting and disclosure at the [Eclipse Foundation Security page](https://www.eclipse.org/security/).
18+
19+
Please include as much of the information listed below as you can to help us better understand and resolve the issue:
20+
21+
* The type of issue (e.g., possible misuse, missing checks, etc)
22+
* Affected version(s)
23+
* Impact of the issue, including how an attacker might exploit the issue
24+
* Step-by-step instructions to reproduce the issue
25+
* The location of the affected source code (tag/branch/commit or direct URL)
26+
* Full paths of source file(s) related to the manifestation of the issue
27+
* Configuration required to reproduce the issue
28+
* Log files that are related to this issue (if possible)
29+
* Proof-of-concept or exploit code (if possible)
30+
31+
This information will help us triage your report more quickly.
32+
33+
## Supported Versions
34+
35+
Supported versions are:
36+
37+
* 0.4.0

0 commit comments

Comments
 (0)