You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Many instances boot from one image: an AMI, an Azure image, or a GCE image. The image is a snapshot of a root volume, and it is where the golden software lives. Scanning only running instances repeats that work per instance and misses an image that is not currently booted.
Done when
The opt-in workload scan reads a boot image once, through the same package walker as a root volume, and deletes any snapshot or disk it created.
Instances launched from that image carry the image's package identifiers on their workload nodes.
A package that exists only on an instance's own disk, added after boot, is attributed to that instance and not to the image.
The graph stores CPE 2.3 names and versioned package URLs. om enrich cve matches them as it does any other packages list.
Depends on the root-volume scan. Marketplace images the account is not allowed to snapshot stay unscanned, and the scan says so.
Closed by #127. om scan workload image aws, om scan workload image azure, and om scan workload image gcp read each boot image once and add those package identifiers to instances launched from it. This shipped in v0.5.0. The pull request mentioned this issue without a closing keyword, so it stayed open after merge.
Activity
om986 commentedon Oct 27, 2026
Closed by #127.
om scan workload image aws,om scan workload image azure, andom scan workload image gcpread each boot image once and add those package identifiers to instances launched from it. This shipped in v0.5.0. The pull request mentioned this issue without a closing keyword, so it stayed open after merge.