Skip to content

Commit dcc9a1f

Browse files
committed
security: add SECURITY.md vulnerability disclosure policy
1 parent fb2c168 commit dcc9a1f

1 file changed

Lines changed: 27 additions & 0 deletions

File tree

SECURITY.md

Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
# Security Policy
2+
3+
## Reporting a Vulnerability
4+
5+
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.
6+
7+
**Please do not report security vulnerabilities through public GitHub issues or public forums.**
8+
9+
### How to Report
10+
Please choose the path that best fits your intent:
11+
12+
* **Responsible Disclosure:** If you have identified a security vulnerability, please email **[security@mixpanel.com](mailto:security@mixpanel.com)**.
13+
* *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.
14+
15+
* **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.
16+
* *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.
17+
18+
### What to Include in Your Report
19+
To help us triage the issue effectively, please include:
20+
* **Summary:** A clear description of the vulnerability.
21+
* **Environment:** The affected service, SDK, or repository.
22+
* **Reproduction Steps:** Step-by-step instructions to reproduce the issue.
23+
* **Impact:** A description of the potential risk.
24+
* **Remediation Suggestions:** Any specific recommendations you have for mitigating or fixing the vulnerability.
25+
26+
### Supported Versions
27+
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.

0 commit comments

Comments
 (0)