Skip to content

Security: ossf-cve-benchmark/ossf-cve-benchmark

.github/security.md

Security Policies and Procedures

This document outlines security procedures and general policies for the ossf-cve-benchmark project.

Reporting a Bug

The ossf-cve-benchmark team and community take all security bugs in ossf-cve-benchmark seriously. Thank you for improving the security of ossf-cve-benchmark. We appreciate your efforts and coordinated disclosure and will make every effort to acknowledge your contributions.

Report security bugs by creating an issue, requesting an invite to a collaboration on a Security Advisory.

The lead maintainer will acknowledge your issue within 48 hours, and will send an invite for further collaboration. 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.

Report security bugs in third-party modules to the person or team maintaining the module.

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.

Comments on this Policy

If you have suggestions on how this process could be improved please submit a pull request.

There aren’t any published security advisories