Skip to content

Commit 1db31c9

Browse files
committed
[IN-68] Add default GitHub SECURITY policy
this file must exist on the default branch Signed-off-by: Ry Jones <[email protected]> Change-Id: I8a172ea9a8f0e4ffbdd7b789fe879cac489a76b6 (cherry picked from commit af3dec0)
1 parent 8cca4bb commit 1db31c9

File tree

1 file changed

+12
-0
lines changed

1 file changed

+12
-0
lines changed

SECURITY.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
# Hyperledger Security Policy
2+
3+
## Reporting a Security Bug
4+
5+
If you think you have discovered a security issue in any of the Hyperledger projects, we'd love to hear from you. We will take all security bugs seriously and if confirmed upon investigation we will patch it within a reasonable amount of time and release a public security bulletin discussing the impact and credit the discoverer.
6+
7+
There are two ways to report a security bug. The easiest is to email a description of the flaw and any related information (e.g. reproduction steps, version) to [security at hyperledger dot org](mailto:[email protected]).
8+
9+
The other way is to file a confidential security bug in our [JIRA bug tracking system](https://jira.hyperledger.org). Be sure to set the “Security Level” to “Security issue”.
10+
11+
The process by which the Hyperledger Security Team handles security bugs is documented further in our [Defect Response page](https://wiki.hyperledger.org/display/HYP/Defect+Response) on our [wiki](https://wiki.hyperledger.org).
12+

0 commit comments

Comments
 (0)