Added initial support for vulnerability evidence #360
Closed
Conversation
This file contains 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
Signed-off-by: Steve Springett <steve@springett.us>
prabhu
reviewed
Jan 29, 2024
| "description": "The technique used in this method of analysis.", | ||
| "type": "string", | ||
| "enum": [ | ||
| "source-code-analysis", |
There was a problem hiding this comment.
For most CVEs, the exact technique used by the researcher to identify the CVE would be unknown. In case of vulnerabilities reported in custom code (say using SAST/DAST), then the key data to capture are the rules, policies, queries that helped identify the vulnerability, and some version information for scanners and their engines.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Adds vulnerability evidence support.
Closes #333