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

Insights: perform a vulnerability scan on images #9

Open
tobybellwood opened this issue Mar 22, 2022 · 0 comments
Open

Insights: perform a vulnerability scan on images #9

tobybellwood opened this issue Mar 22, 2022 · 0 comments
Assignees
Labels

Comments

@tobybellwood
Copy link
Member

Summary

Lagoon insights collects data about deployments (SBOM, docker layer). We can use this data to generate vulnerability scans to show current vulnerabilities.

Intended Outcome

Lagoon users have access to the Insights data about their environments - package versions and vulnerabilities, and have the ability to configure "problems" if required.

Relevant Reasoning

Lagoon-remote is the best place to be controlling tasks/builds/scans etc - and core is used to store data and update the API.

How could it work?

Lagoon-remote should be able to perform the following on a build:

  1. On a build, Lagoon generates a SBOM using Syft, and stores it in a configmap (and then in S3)
  2. Using this SBOM, Lagoon can scan it using Grype to generate and store a report of this run in a configmap (and then in S3)
  3. (optional) Lagoon can report "problems" from this report back to the API
  4. Schedule a time to perform a re-scan of this data - using a Label?

Lagoon-remote should also be able to perform the following:

  1. Check for existence of previously created SBOM configmap to use as source for scan
  2. If no configmap present, scan image from Harbor to generate SBOM
  3. Using this SBOM, Lagoon can scan it using Grype to generate and store a report of this run in a configmap (and then in S3)
  4. (optional) Lagoon can report "problems" from this report back to the API
  5. Schedule a time to perform a re-scan of this data - using a Label?

The Lagoon-remote may also poll namespaces/configMaps for the existence of a Label to determine whether a re-scan is necessary

  1. Suggest weekly scans - but to conduct outside business hours - e.g 156h (168-12)
  2. Weekly scans are Grype-only - they don't update the SBOMs in ConfigMap or S3

Lagoon-CLI should be extended to retrieve Insights files for a given environment

Lagoon-UI should be able to display Insights files for a given environment

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants