SECURITY.md

This document outlines security procedures and general policies for theCommerce Layer projects as found onhttps://github.com/commercelayer.

• Reporting a Vulnerability
• Disclosure Policy

Please do not report security vulnerabilities through public GitHub issues.

The Commerce Layer team and community take all security vulnerabilitiesseriously. Thank you for improving the security of our open sourcesoftware. We appreciate your efforts and responsible disclosure and willmake every effort to acknowledge your contributions.

Report security vulnerabilities by emailing the Commerce Layer security team at:

security@commercelayer.io

• Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.)
• Full paths of source file(s) related to the manifestation of the issue
• The location of the affected source code (tag/branch/commit or direct URL)
• Any special configuration required to reproduce the issue
• Step-by-step instructions to reproduce the issue
• Proof-of-concept or exploit code (if possible)
• Impact of the issue, including how an attacker might exploit the issue

This information will help us triage your report more quickly.

The lead maintainer will acknowledge your email within 24 hours, and willsend a more detailed response within 48 hours indicating the next steps inhandling your report. After the initial reply to your report, the securityteam will endeavor to keep you informed of the progress towards a fix andfull announcement, and may ask for additional information or guidance.

Report security vulnerabilities in third-party modules to the person orteam maintaining the module.

When the security team receives a security bug report, they will assign itto a primary handler. This person will coordinate the fix and releaseprocess, 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. These fixeswill be released as fast as possible.

There aren’t any published security advisories