Skip to content

Security: alarad27/ondemand

Security

SECURITY.md

Security Policy

This document outlines security procedures and general policies for the OnDemand project.

Reporting a Vulnerability

If you have security concerns or think you have found a vulnerability in Open OnDemand, please contact us directly via [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 (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 (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 topic or open a pull request.

Security Audits

Trusted CI, 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.

There aren’t any published security advisories