-
Epic
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
VM VulnMgmt - Persistence
-
Product / Portfolio Work
-
M
-
False
-
-
False
-
Not Selected
-
To Do
-
ROX-30216 - TP OpenShift Virtualization Vulnerability Reporting
-
-
-
-
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
-
0
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.