Update security policy for private vulnerability reporting - #5555
Merged
Conversation
The policy gave security@hyperledger.org as the email intake and linked to Defect Response on the retired Hyperledger wiki. It also pointed at the security advisories index rather than the form used to open a report. Rewrite it along the lines of the policy already in fabric-gateway: - Align with the LF Decentralized Trust security vulnerability disclosure policy and link to it as the governing document. - Lead with GitHub private vulnerability reporting, linking to the new advisory form for this repository, and state plainly that issues, discussions, and pull requests are not the place for a report. - Give security@lists.lfdecentralizedtrust.org as the email intake, which LF Decentralized Trust requires every project to accept. - Describe what a useful report contains, what a reporter should expect in return including the two business day acknowledgement the governing policy sets, and how vulnerabilities in dependencies are handled. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Signed-off-by: Ry Jones <ry@linux.com>
ryjones
marked this pull request as ready for review
September 6, 2026 15:50
pfi79
reviewed
Sep 6, 2026
|
|
||
| ## What to expect | ||
|
|
||
| - We will acknowledge receipt of your report within 2 business days. |
Contributor
There was a problem hiding this comment.
I'm confused about setting specific deadlines. Why specify them? And if this is not done within 2 days, then what?
pfi79
approved these changes
Sep 6, 2026
|
Tick the box to add this pull request to the merge queue (same as
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The policy gave security@hyperledger.org as the email intake and linked to Defect Response on the retired Hyperledger wiki. It also pointed at the security advisories index rather than the form used to open a report.
Rewrite it along the lines of the policy already in fabric-gateway:
Type of change
Description
Additional details
Related issues