Repository navigation
docs: add SECURITY.md with private vulnerability reporting policy - #29
Merged
Merged
Conversation
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
1 participant
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.
Summary
Adds a
SECURITY.mdso the repo's Security tab and GitHub's "Report a vulnerability" flow point reporters to a documented policy. GitHub private vulnerability reporting has been enabled on this repo, and the policy directs reports there instead of public issues.The policy covers supported versions (latest release only), how to report and what to include, what reporters can expect, and what is in and out of scope for this repo. Repos whose Helm chart is published to
quay.io/nebari/chartsalso get acosign verifycommand for the chart signature, linking to the org-wide Verifying Nebari artifacts guide for the rest.This matches the policy added to Nebari Infrastructure Core in nebari-dev/nebari-infrastructure-core#703.
How to Test
Render
SECURITY.mdon the branch and check the links. Where a "Verifying Releases" section is present, run thecosign verifycommand against the chart's latest published version; it was run against each chart's latest version on quay.io and passes.