Skip to content

security: add SECURITY.md #82

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
scotmatson wants to merge 1 commit into from
Closed

security: add SECURITY.md #82

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
27 changes: 27 additions & 0 deletions .github/SECURITY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,27 @@
# Security Policy

## Reporting a Vulnerability

We take the security of our services and the privacy of our users' data very seriously. If you have discovered a security vulnerability, we appreciate your help in disclosing it to us responsibly.

**Please do not report security vulnerabilities through public GitHub issues or public forums.**

### How to Report
Please choose the path that best fits your intent:

* **Responsible Disclosure:** If you have identified a security vulnerability, please email **[security@mixpanel.com](mailto:security@mixpanel.com)**.
* *Note:* Your report will be routed to our internal ticketing system. We will acknowledge receipt of your findings. Please be advised that we do not maintain ongoing communication regarding the status of reports unless we have specific follow-up questions.

* **Bug Bounty Program:** If you are a security researcher interested in participating in our private bug bounty program, please email **[bugbounty@mixpanel.com](mailto:bugbounty@mixpanel.com)** to request onboarding instructions.
* *Note:* Participation in our private program is subject to eligibility requirements, including a verification process to ensure researchers are in good standing on the [HackerOne](https://www.hackerone.com/) platform.

### What to Include in Your Report
To help us triage the issue effectively, please include:
* **Summary:** A clear description of the vulnerability.
* **Environment:** The affected service, SDK, or repository.
* **Reproduction Steps:** Step-by-step instructions to reproduce the issue.
* **Impact:** A description of the potential risk.
* **Remediation Suggestions:** Any specific recommendations you have for mitigating or fixing the vulnerability.

### Supported Versions
We are committed to securing our latest stable releases. We recommend all users keep their implementations updated to the most current version to ensure they have the latest security patches.
Loading