From 6c2bd1922a1a99283a77aeb09f30a64225cfe99b Mon Sep 17 00:00:00 2001
From: asmallberg <69218017+asmallberg@users.noreply.github.com>
Date: Thu, 7 Aug 2025 16:35:47 -0400
Subject: [PATCH] Update CONTRIBUTING.md

---
 CONTRIBUTING.md | 51 +++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 51 insertions(+)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 0d58ed39c..6289e865c 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -104,3 +104,54 @@ To actually write an email, you'll want to modify the templates in `apps/email/l
 ## Adding a new application to the marketplace
 
 See docs on our [docs site](https://docs.plural.sh/applications/adding-new-application) for how to add applications to the marketplace.
+
+## Bug Bounty Program
+
+Plural likes to work with the security community to find vulnerabilities in order to keep our businesses and customers safe.
+
+As such, Plural has a Bug Bounty contributor program. Those interested in joining should reach out to support@plural.sh
+
+### Program Rules
+* Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue, the issue will not be eligible for a reward.
+* Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.
+* When duplicates occur, we only award the first report that was received (provided that it can be fully reproduced).
+* Multiple vulnerabilities caused by one underlying issue will be awarded one bounty.
+* Social engineering (e.g. phishing, vishing, smishing) is prohibited.
+* Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service. Only interact with accounts you own or with explicit permission of the account holder.
+
+### Out of scope vulnerabilities
+
+When reporting vulnerabilities, please consider (1) attack scenario / exploitability, and (2) security impact of the bug. The following issues are considered out of scope:
+
+* Clickjacking on pages with no sensitive actions
+* Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions
+* Attacks requiring MITM or physical access to a user's device.
+* Previously known vulnerable libraries without a working Proof of Concept.
+* Any activity that could lead to the disruption of our service (DoS).
+* Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
+* Rate limiting or bruteforce issues on non-authentication endpoints
+* Missing best practices in Content Security Policy.
+* Missing HttpOnly or Secure flags on cookies
+* Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)
+* Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version]
+* Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors).
+* Public Zero-day vulnerabilities that have had an official patch for less than 1 month will be awarded on a case by case basis.
+* Tabnabbing
+* Open redirect - unless an additional security impact can be demonstrated
+* Issues that require unlikely user interaction
+* Bugs that are already reported on any of Plural's issue trackers (https://github.com/pluralsh), or that we already know of. Note that some of our issue tracking is private.
+* Test instances
+
+### Safe Harbor
+
+Any activities conducted in a manner consistent with this policy will be considered authorized conduct and we will not initiate legal action against you. If legal action is initiated by a third party against you in connection with activities conducted under this policy, we will take steps to make it known that your actions were conducted in compliance with this policy.
+
+### Rewards
+* Low: $60
+* Medium: $125
+* High: $250
+* Critical: $750
+
+### Rewards
+Please submit to support@plural.sh to participate in bug bounty program 
+