Design VEX changes for Advisories

Open
#452 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Domain
security

Research direction

Start with the Evaluation DejaCode vulnerabilities view linked in the issue and review how current VEX functionality is keyed by Vulnerability. Define the intended grouping for related Advisories and the behavior for importer-based exclusions, including how users are alerted; the work is done when these design decisions are documented clearly enough to guide implementation.

Written by the indexing model from the issue text.

Description

design needed

The planned Vulnerablecode change for the migration to Advisories instead of Vulnerabilities will have a significant impact on the current VEX functionality in DejaCode which is currently "keyed" by Vulnerability.

Looking at the example of: https://public.dejacode.com/products/Evaluation/DejaCode/5.1/#vulnerabilities in DjC Evaluation, it seems that we will be missing the VCID to group related advisories and this will make the display much more complex.

  • Have we ruled out having something like VCID to group advisories - perhaps the aliases from the advisory record? It is difficult to suggest how to display without some way to group obviously related advisories.
  • It looks like the change will make the VEX reporting more complex if we cannot logically group them so that a user can apply one VEX statement to many advisories.
  • We may also need to consider a DejaCode configuration option to filter the Advisories that are imported into DejaCode based on the origin (importer). For example a user might want to ignore RedHat advisories if they do not use RedHat products. Red Hat is an interesting example because there are multiple datasets to exclude - e.g. Red Hat, Fedora and ? If some Advisories are excluded we would want some way to alert the user about the intentional exclusion and the availability of additional data.
Dominant language
Python
Stars
53
Forks
32
Avg merge
16h 44m
Merged PRs (30d)
10

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aboutcode-org/dejacode

All issues in aboutcode-org/dejacode

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.