Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Generating VEX statements #19

Open
another-rex opened this issue Nov 27, 2022 · 3 comments
Open

Generating VEX statements #19

another-rex opened this issue Nov 27, 2022 · 3 comments
Labels
backlog Important but currently unprioritized enhancement New feature or request

Comments

@another-rex
Copy link
Collaborator

Automatically generate VEX statements based on call graph analysis or ignored vulnerabilities set in the scanner config.

@another-rex another-rex added the enhancement New feature or request label Nov 27, 2022
@puerco
Copy link

puerco commented Dec 15, 2022

At Chainguard we are starting to run tests issuing vex for Wolfi, our linux distro. We are generating documents in a simplified VEX format which we also embed in in-toto attestations. We are proposing this format to the VEX working group and have been trying to capture the latest data model.

Here is the VEX structure and type we are using: https://github.com/chainguard-dev/vex/blob/main/pkg/vex/vex.go

We would love to collaborate and learn more about you rvex use case!

@oliverchang
Copy link
Collaborator

Hey @puerco! Thanks for reaching out!

The use case we have in mind right now is just generating VEX statements from:

  • The ignore files provided by the user.
  • Automated call graph analysis on vulnerable functions.

If possible we'd certainly like to re-use an existing VEX structure for this. Very happy to chat more here about this or other potential areas of collaboration!

CC @lumjjb

Copy link

This issue has not had any activity for 60 days and will be automatically closed in two weeks

@github-actions github-actions bot added the stale The issue or PR is stale and pending automated closure label Jul 26, 2024
@oliverchang oliverchang added backlog Important but currently unprioritized and removed stale The issue or PR is stale and pending automated closure labels Jul 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backlog Important but currently unprioritized enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants