Skip to content

Add private vulnerability reporting to org security policy - #2

Open
jmiranda wants to merge 2 commits into
mainfrom
docs/security-policy-private-reporting
Open

jmiranda wants to merge 2 commits into
mainfrom
docs/security-policy-private-reporting

Conversation

@jmiranda

@jmiranda jmiranda commented Oct 13, 2026 •

Copy link
Copy Markdown
Member

Keeps the org-wide default SECURITY.md short, but adds GitHub private vulnerability reporting: reporters are directed to the Report a vulnerability button on the affected repository's Security tab, with support@openboxes.com kept as an alternative.

The wording is repo-agnostic because this file is the default for every repo without its own policy (e.g. openboxes-mobile). Private vulnerability reporting must be enabled per repo (or org-wide) for the button to appear.

Companion PR: openboxes/openboxes#6244

🤖 Generated with Claude Code

https://claude.ai/code/session_01XFBkWxcdHFNkD8xFdNi9Ko

jmiranda and others added 2 commits October 13, 2026 17:18
…lnerability reporting

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XFBkWxcdHFNkD8xFdNi9Ko
@jmiranda jmiranda changed the title Align org security policy with openboxes/openboxes and add private vulnerability reporting Add private vulnerability reporting to org security policy Oct 13, 2026
@jmiranda
jmiranda requested a review from ewaterman October 13, 2026 21:25
@jmiranda

Copy link
Copy Markdown
Member Author

@ewaterman Sorry I'm dealing with a lot of security stuff recently so I wanted to update our default and openboxes/openboxes SECURITY.md so people go through the right channel. Since we can't assume the repositories using the default messaging have Private vulnerability reporting enabled, it seems best to leave the wording vague. But perhaps we want to enable reporting on all repositories.

Comment thread .github/SECURITY.md
## Reporting a Vulnerability

If you've uncovered a security vulnerability in the application, instead of creating a public GitHub Issue for it (which would inform potential attackers of the vulnerability), we ask that you please email us at support@openboxes.com with details about the vulnerability.
If you've uncovered a security vulnerability in the application, instead of creating a public GitHub Issue for it (which would inform potential attackers of the vulnerability), please report it privately using the **Report a vulnerability** button on the affected repository's **Security** tab, or email us at support@openboxes.com with details about the vulnerability.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
If you've uncovered a security vulnerability in the application, instead of creating a public GitHub Issue for it (which would inform potential attackers of the vulnerability), please report it privately using the **Report a vulnerability** button on the affected repository's **Security** tab, or email us at support@openboxes.com with details about the vulnerability.
If you've uncovered a security vulnerability in the application, instead of creating a public GitHub Issue for it (which would inform potential attackers of the vulnerability), please report it privately using the **Report a vulnerability** button on the **Security and quality** tab, or email us at support@openboxes.com with details about the vulnerability.

they'll already be within the repository when they see this message so no need to hilight the fact

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants