-
Notifications
You must be signed in to change notification settings - Fork 94
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
43 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,43 @@ | ||
# Security Policies and Procedures | ||
|
||
This document outlines security procedures and general policies for the Cylc | ||
project. | ||
|
||
* [Reporting a Bug](#reporting-a-bug) | ||
* [Disclosure Policy](#disclosure-policy) | ||
* [Comments on this Policy](#comments-on-this-policy) | ||
* [Current Alerts](#current-alerts) | ||
|
||
## Reporting a Bug | ||
|
||
The Cylc team take security bugs seriously. Thank you for improving the | ||
security of Cylc. We appreciate your efforts and responsible disclosure and | ||
will make every effort to acknowledge your contributions. | ||
|
||
Report security bugs by sending an email to the [Cylc | ||
Forum](mailto:cylc@googlegroups.com) or by posting a [Cylc repository | ||
Issue](https://github.com/cylc/cylc-flow/issues). Project maintainers will | ||
endeavor to respond within 48 hours. Progress toward a fix will be recorded on | ||
the Issue page, and resulting new releases will be announced on the mail forum. | ||
|
||
Report security bugs in third-party modules to the person or team maintaining | ||
the module. | ||
|
||
## Disclosure Policy | ||
|
||
When the team receives a security bug report, they will assign it to a primary | ||
handler. This person will coordinate the fix and release process as follows: | ||
|
||
* 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 fast as possible. | ||
|
||
## Comments on this Policy | ||
|
||
If you have suggestions on how this process could be improved please submit a | ||
pull request. | ||
|
||
## Current Alerts | ||
|
||
(None) |