Uploaded image for project: 'Red Hat Advanced Cluster Security'
  1. Red Hat Advanced Cluster Security
  2. ROX-27663

[VM]: Design and Implement the VM Vulnerability Data Model

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • 4.10.0
    • None
    • None
    • VM VulnMgmt - Persistence
    • Product / Portfolio Work
    • M
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Selected
    • To Do
    • ROX-30216 - Vulnerability Management in ACS for Virtual Machines running on OpenShift Virtualization platform (Tech Preview)
    • 100% To Do, 0% In Progress, 0% Done
    • Rox Sprint 4.8G - Global, Rox Sprint 4.8H - Global, Rox Sprint 4.9A - Global, Rox Sprint 4.9B - Global, Rox Sprint 4.9C - Global, Rox Sprint 4.9D - Global, Rox Sprint 4.9E - Global, Rox Sprint 4.9F - Global, Rox Sprint 4.9G - Global, Rox Sprint 4.9H - Global, Rox Sprint 4.10A - Global, Rox Sprint 4.9I - Global, Rox Sprint 4.10B, Rox Sprint 4.10C, Rox Sprint 4.10D, Rox Sprint 4.10E, Rox Sprint 4.10F, Rox Sprint 4.10G

      The data model should likely include information about the VMs themselves, similar to platform nodes. There should be a separate table (or tables) to represent components, i.e. packages installed in the VM. And there should be a table (or tables) to represent vulnerabilities identified on the host.

      This assumes that we can't reuse existing tables for this data.

              Unassigned Unassigned
              rh-ee-klape Kyle Lape
              Shubha Badve Shubha Badve
              ACS Core Workflows
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: