-
Notifications
You must be signed in to change notification settings - Fork 108
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
update our security policy with the new email distro
- Loading branch information
Showing
1 changed file
with
16 additions
and
14 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 |
---|---|---|
|
@@ -3,33 +3,35 @@ | |
This document outlines security procedures and general policies for the `OnDemand` | ||
project. | ||
|
||
## Security Audits | ||
|
||
[Trusted CI](https://trustedci.org/), the NSF Cybersecurity Center of | ||
Excellence, conducted an in-depth vulnerability assessment of Open OnDemand, completing | ||
it in December 2018. This assessment included a careful review of the code, increasing | ||
our confidence in its security. The Ohio Supercomputing Center addressed the implementation | ||
issues (bugs) that were found during this review, producing a more robust revision of Open OnDemand. | ||
|
||
## Reporting a Vulnerability | ||
|
||
If you have security concerns or think you have found a vulnerability in Open OnDemand, | ||
please contact us directly via [email](mailto:[email protected]) on the news list found | ||
[here](https://lists.osu.edu/mailman/listinfo/ood-users). Emails sent to it are only seen by | ||
the core project team. | ||
please contact us directly via [[email protected]](mailto:[email protected]). | ||
Emails sent to it are only seen by the core project team. | ||
|
||
## Disclosure Policy | ||
|
||
Reporters should get a response from the core team within hours of reporting that | ||
acknowledging the disclosure. | ||
|
||
When the team receives a security vulnerability, they will generally 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. | ||
* Confirm the problem and determine the affected versions (1-2 days). | ||
* Audit code to find any potential similar problems (1-2 days). | ||
* Prepare fixes for all releases still under maintenance. These fixes will be | ||
released as fast as possible. | ||
released as fast as possible (2-7 days). | ||
|
||
## Comments on this Policy | ||
|
||
If you have suggestions on how this process could be improved please submit | ||
a ticket, open a [Discorse](https://discourse.osc.edu/) topic or open a pull request. | ||
|
||
## Security Audits | ||
|
||
[Trusted CI](https://trustedci.org/), the NSF Cybersecurity Center of | ||
Excellence, conducted an in-depth vulnerability assessment of Open OnDemand, completing | ||
it in December 2018. This assessment included a careful review of the code, increasing | ||
our confidence in its security. The Ohio Supercomputing Center addressed the implementation | ||
issues (bugs) that were found during this review, producing a more robust revision of Open OnDemand. |