l3montree-dev / l3montree-dev/devguard
Making Vex Rules for Vulnerabilities publicy availiable in Vulnerability database
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 161
- Forks
- 43
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 37
Description
To improve the value and therefore the visibility of our public vulnerability Database (https://docs.devguard.org/vulnerability-database/), it might be a good idea to publish Vex rules (if there are any) for vulnerabilities.
They should be marked as "Beta-Feature" and also marked with a warning sign, that the vex rules should be checked by the consumer before applying them.
If there aren't any Vex rules, there should still be a content block saying, that there aren't any Vex rules currently available.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the public vulnerability database at https://docs.devguard.org/vulnerability-database/ and locate the content or entry point that presents each vulnerability. Determine how available VEX rules and the no-rules case are represented, then verify that published rules carry a Beta-Feature label and warning for consumer review.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, security
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100