|
| 1 | +# Security Policy |
| 2 | + |
| 3 | +## Reporting a Vulnerability |
| 4 | + |
| 5 | +We at [Mozilla AI](https://www.mozilla.ai/) take the security of our projects seriously. We appreciate your efforts to responsibly disclose security vulnerabilities. |
| 6 | + |
| 7 | +This document outlines the process for reporting vulnerabilities in `mcpd-plugins-sdk-dotnet`. |
| 8 | + |
| 9 | +### Supported Versions |
| 10 | + |
| 11 | +The following versions are currently supported for security updates: |
| 12 | + |
| 13 | +| Version | Supported | |
| 14 | +|---------|--------------------| |
| 15 | +| 0.0.x | :white_check_mark: | |
| 16 | + |
| 17 | +**Please ensure you are using a supported version when reporting a vulnerability.** |
| 18 | + |
| 19 | +## Reporting a Vulnerability |
| 20 | + |
| 21 | +**Please DO NOT open a public GitHub issue.** |
| 22 | + |
| 23 | +To report a security vulnerability, please send a detailed email to: [security@mozilla.ai](mailto:security@mozilla.ai) |
| 24 | + |
| 25 | +Please include the following information in your report: |
| 26 | + |
| 27 | +1. **Project Name and Version:** Specify which project (`mozilla-ai/mcpd-plugins-sdk-dotnet`) and which version(s) are affected. |
| 28 | +2. **Vulnerability Description:** A clear and concise description of the vulnerability. |
| 29 | +3. **Steps to Reproduce:** Detailed steps to reproduce the vulnerability, including any necessary code, configuration, or environment details. |
| 30 | +4. **Impact:** Describe the potential impact of the vulnerability (e.g., data breach, denial of service, privilege escalation). |
| 31 | +5. **Proof of Concept (Optional but Recommended):** Any proof-of-concept code or demonstration that helps us understand and verify the vulnerability. If you have this in a repository please ensure it is private, we can privately discuss granting access to specific Mozilla AI employees for review. |
| 32 | +6. **Your Contact Information (Optional):** If you wish to be credited for your discovery, please provide your name/handle and preferred contact method. |
| 33 | + |
| 34 | +### Our Commitment |
| 35 | + |
| 36 | +* We will acknowledge receipt of your report within 2 business days. |
| 37 | +* We will investigate the report promptly and provide an initial assessment within 5 business days. |
| 38 | +* We will keep you informed of our progress throughout the vulnerability resolution process. |
| 39 | +* Once the vulnerability is patched, we will notify you and, with your permission, include your name in our release notes or security advisory as a thank you for your responsible disclosure. |
| 40 | +* We follow a 'coordinated disclosure' approach, meaning we aim to have a fix available before public disclosure. |
| 41 | + |
| 42 | +### Public Disclosure |
| 43 | + |
| 44 | +Please allow us a reasonable amount of time to address the vulnerability before public disclosure. We request that you do not disclose the vulnerability publicly until we have confirmed a fix is available and have agreed on a disclosure timeline. |
| 45 | + |
| 46 | +Our typical disclosure timeline for critical issues is up to 30 days from the initial report, but this may vary depending on complexity. |
| 47 | + |
| 48 | +### Scope |
| 49 | + |
| 50 | +This security policy applies to all components of [mcpd](https://github.com/mozilla-ai/mcpd) (for example, this repository: [mcpd-plugins-sdk-dotnet](https://github.com/mozilla-ai/mcpd-plugins-sdk-dotnet)). |
| 51 | + |
| 52 | +Thank you for helping us keep our projects secure for everyone. |
0 commit comments