docs(security): add Draft GHSA option #12747
Merged
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.
Fixes #12745
Motivation
Modifications
SECURITY.md
(we already have email), which is using draft GHSAs.Verification
See the rendered markdown in this PR
Notes to Reviewers
Do not merge until Draft GHSAs are enabled by an admin, i.e. until this link works: https://github.com/argoproj/argo-workflows/security/advisories/new
For clarity and explicitness, draft GHSAs are not equivalent to CVEs. If a draft GHSA is determined to be an active vuln (as opposed to false positive etc), then a CVE can be assigned. It is just another method of private disclosure, one that keeps things consistent and in the same place as public disclosures.