Skip to content

Commit 0445f3f

Browse files
authored
Add SECURITY.md file (eiffel-community#15)
* Add SECURITY.md file Adding the SECURITY.md file from the community repository to this one.
1 parent 1592e5b commit 0445f3f

File tree

1 file changed

+20
-0
lines changed

1 file changed

+20
-0
lines changed

SECURITY.md

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
# Eiffel-community Vulnerability and Security Reporting and Response
2+
3+
## Report a Vulnerability or Security Issue
4+
We as a community encourage researchers, users and contributors to report vulnerabilities and security related issues to the Eiffel community. All issues are thoroughly investigated by a community security officer and/or other community security volunteers. All reported and fixed security and vulnerability issues can be found on the [Eiffel community security page](https://eiffel-community.github.io/security.html) .
5+
6+
## How to Report a Security Vulnerability
7+
To file a vulnerability report please send and e-mail to the private [email protected] list. The e-mail should list the security specific details as well as the [standard bug report information](https://github.com/eiffel-community/.github/blob/master/.github/ISSUE_TEMPLATE/general.md). Only the community security officers will have access to e-mails sent on the security and vulnerability list. This process is the same whether the report stems from a project within the Eiffel community or from an external contributor.
8+
9+
Triage and handling of the vulnerability report will be conducted within one week. If the vulnerability severity and impact is high a patch will be published with urgency.
10+
11+
## When Should I Report a Vulnerability?
12+
* You think you discovered a potential security vulnerability in an eiffel-community service, application or repository
13+
* You are unsure how a vulnerability affects the eiffel-community service or application.
14+
* You think you discovered a vulnerability in another project that a eiffel-community service or application depends on.
15+
16+
## Security Vulnerability Response
17+
As mentioned, each report is acknowledged and analyzed by a eiffel-community security officer within one week. If the vulnerability is reproduced and verified a response will be sent to the reporter. As the issue progresses from triage, to fix, test and release the reporter will be updated.
18+
19+
## Public Disclosure
20+
The eiffel-community humbly asks all vulnerability reporters to hold off on public disclosure and instead negotiate a time frame within which the vulnerability report will be processed, fixed and released by the eiffel-community. Once released it will be listed on the [Eiffel community security page](https://eiffel-community.github.io/security.html) .

0 commit comments

Comments
 (0)