• POLICY:

Our security policy is to avoid leaving the ecosystem worse than we found it. Meaning we are not planning to introduce vulnerabilities into the ecosystem.

The "RocketCyberAPI" team and community take all security bugs in "RocketCyberAPI" seriously. Thank you for improving the security of "RocketCyberAPI". We appreciate your efforts and responsible disclosure and will make every effort to acknowledge your contributions.

Report security bugs by emailing the lead maintainer at [celerium@celerium.org] and include the word "SECURITY" in the subject line..

The lead maintainer will acknowledge your email within a week, and will send a more detailed response 48 hours after that 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.

• "RocketCyberAPI" will confirm the problem and determine the affected versions.
• "RocketCyberAPI" will audit code to find any potential similar problems.
• "RocketCyberAPI" will prepare fixes for all releases still under maintenance. These fixes will be released as fast as possible.

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

• SECURITY DISCLOSURE:

Your responsibility is to report vulnerabilities to us using the guidelines outlined below.

Discuss how someone should disclose a vulnerability to "RocketCyberAPI", in tl;dr ( or ELI5 ) language. Then expand on this with "How To Disclose a vulnerability in detail". Please give detailed steps on how to disclose the vulnerability. Keep these OWASP guidelines in mind ( https://www.owasp.org/index.php/Vulnerability_Disclosure_Cheat_Sheet ) when creating your disclosure policy. Below are some recommendations for security disclosures:

• "RocketCyberAPI" security contact { contact: mailto:[celerium@celerium.org] }
• Disclosure format: When disclosing vulnerabilities please
  1. Your name and affiliation (if any).
  2. include scope of vulnerability. Let us know who could use this exploit.
  3. document steps to identify the vulnerability. It is important that we can reproduce your findings.
  4. how to exploit vulnerability, give us an attack scenario.