Skip to content

Commit 2eefa47

Browse files
Update SECURITY.md to reflect bug bounty program (#169)
## Summary Updates `SECURITY.md` to direct security reporters to LaunchDarkly's Bug Bounty program. ## Changes - Security issues should be reported through the [Bug Bounty program](https://bugcrowd.com/engagements/launchdarkly-mbb-og) rather than via GitHub Issues or PRs - Clarifies that valid security issues may be eligible for a bounty This is a cross-repository update to standardize security reporting instructions across LaunchDarkly repositories. <!-- CURSOR_SUMMARY --> --- > [!NOTE] > **Low Risk** > Documentation-only change to security reporting instructions; no application or infrastructure code is modified. > > **Overview** > **`SECURITY.md`** is updated so security reporting matches LaunchDarkly’s current process across repos. > > The doc now **boldly warns** not to file GitHub Issues or PRs for vulnerabilities, with clearer rationale about public exposure. Reporting is directed to the **Bugcrowd** [Bug Bounty program](https://bugcrowd.com/engagements/launchdarkly-mbb-og) instead of the previous **HackerOne** link, and a line is added asking reporters **not to contact LaunchDarkly staff directly**. > > <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit ee5537f. Bugbot is set up for automated code reviews on this repo. Configure [here](https://www.cursor.com/dashboard/bugbot).</sup> <!-- /CURSOR_SUMMARY -->
1 parent 5f605d4 commit 2eefa47

1 file changed

Lines changed: 5 additions & 2 deletions

File tree

SECURITY.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,8 @@
11
# Reporting and Fixing Security Issues
22

3-
Please report all security issues to the LaunchDarkly security team by submitting a bug bounty report to our [HackerOne program](https://hackerone.com/launchdarkly?type=team). LaunchDarkly will triage and address all valid security issues following the response targets defined in our program policy. Valid security issues may be eligible for a bounty.
3+
**Do not open Issues or Pull Requests for security issues.**
4+
This will make potential issues publicly visible before LaunchDarkly's Security Team can address them, which could lead to a compromise of the platform and negatively impact our customers.
45

5-
Please do not open issues or pull requests for security issues. This makes the problem immediately visible to everyone, including potentially malicious actors.
6+
Security issues must be reported through our [Bug Bounty program](https://bugcrowd.com/engagements/launchdarkly-mbb-og), following the program policy, for triage and remediation by the LaunchDarkly Security Team. Valid security issues may be eligible for a bounty.
7+
8+
Please do not attempt to directly contact members of LaunchDarkly staff.

0 commit comments

Comments
 (0)