Once CLAIRDEV-28 is implemented, a logical next step is to allow ingesting site-specific VEX documents.
We would need to work out:
- how/what to refactor out of the Red Hat updater
- server-side layout (e.g. Red Hat compat, single zip/tar, OCI artifact)
- how this would (not) be segmented in the indexer database
- how a matcher would consume the data
- depends on
-
CLAIRDEV-28 Move RHEL advisory source from OVALv2 to CSAF/VEX
- Closed