-
Notifications
You must be signed in to change notification settings - Fork 4
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Signed-off-by: Nicklas Körtge <nicklas.koertge1@ibm.com>
- Loading branch information
1 parent
49dc4aa
commit b8c0ed6
Showing
1 changed file
with
7 additions
and
4 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,9 +1,12 @@ | ||
# Reporting Security Issues | ||
|
||
We and community take security bugs seriously. We appreciate your efforts to responsibly disclose your findings, and will make every effort to acknowledge your contributions. | ||
You can privately report a potential security issue via the GitHub security advisory feature. This can be done here: | ||
|
||
To report a security issue, email [nicklas.koertge1@ibm.com](mailto:nicklas.koertge1@ibm.com) and include the word "SECURITY" in the subject line. | ||
https://github.com/IBM/sonar-cryptography/security/advisories | ||
|
||
Wem will send a response indicating the next steps in handling your report. After the initial reply to your report, the security team will keep you informed of the progress towards a fix and full announcement, and may ask for additional information or guidance. | ||
Please do **not** open a public issue about a potential security vulnerability. | ||
|
||
Report security bugs in third-party modules to the person or team maintaining the module. | ||
You can find more details on the security vulnerability feature in the GitHub | ||
documentation here: | ||
|
||
https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing/privately-reporting-a-security-vulnerability |