-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #6 from uzumal/feature/2
Adding SECURITY.md
- Loading branch information
Showing
1 changed file
with
39 additions
and
0 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 |
---|---|---|
@@ -0,0 +1,39 @@ | ||
# Security Policies and Procedures | ||
|
||
This document outlines security procedures and general policies for the | ||
Cisco Api-driven Grafana Monitoring project. | ||
|
||
- [Reporting a Bug](#reporting-a-bug) | ||
- [Disclosure Policy](#disclosure-policy) | ||
- [Comments on this Policy](#comments-on-this-policy) | ||
|
||
## Reporting a Bug | ||
|
||
The Cisco Api-driven Grafana Monitoring team and community take all security bugs in | ||
Cisco Api-driven Grafana Monitoring seriously. Thank you for improving the security of | ||
Cisco Api-driven Grafana Monitoring. We appreciate your efforts and responsible disclosure and | ||
will make every effort to acknowledge your contributions. | ||
|
||
If you discover a security bug, please open an issue on our GitHub repository. | ||
|
||
The lead maintainer will acknowledge your issue within 48 hours, and will send a | ||
more detailed response within 48 hours indicating the next steps in handling | ||
your report. After the initial reply to your report, the security team will | ||
endeavor to keep you informed of the progress towards a fix and full | ||
announcement, and may ask for additional information or guidance. | ||
|
||
## Disclosure Policy | ||
|
||
When the security team receives a security bug report, they will assign it to a | ||
primary handler. This person will coordinate the fix and release process, | ||
involving the following steps: | ||
|
||
- Confirm the problem and determine the affected versions. | ||
- Audit code to find any potential similar problems. | ||
- Prepare fixes for all releases still under maintenance. These fixes will be | ||
released as quickly as possible. | ||
|
||
## Comments on this Policy | ||
|
||
If you have suggestions on how this process could be improved please submit a | ||
pull request. |