Skip to content

Initial thoughts and ideas #1

@ckotzbauer

Description

@ckotzbauer

Sources

  • Load SBOMs from Git-Repository (previously created from sbom-operator)
  • Cron-Trigger (like sbom-operator)
  • Webhook-Trigger (e.g. called from sbom-operator)

Targets

  • Prometheus-Metrics (⚠️ needs more specification)
  • Messaging (How to avoid sending the same messages for found CVEs on each scan?)
  • Report generation
    • READMEs
    • Web-Report served from vulnerability-operator itself or uploaded to a destination
    • JSON-Report served from vulnerability-operator itself
  • PolicyReport-CRDs (maybe there's a way to include this in Kyverno's Policy-Reporter)

Scanning

CVE-Filtering-Options

  • Only fixed
  • Severity-Threshold
  • Ignorelist

Build / Security

Deployment

  • Plain Kubernetes-YAMLs
  • Helm-Chart
  • Built-in (but optional) ServiceMonitor for Prometheus-Operator CRD

Metadata

Metadata

Assignees

No one assigned

    Labels

    lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions