Skip to content

Boot images are not inventoried for packages #104

Closed

Description

@om986

Problem

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.

Design can land in this issue before code.

Activity

  1. added
    enhancementNew feature or request
    roadmapIdeas and changes to the project roadmap
    on Oct 14, 2026
  2. om986 commented on Oct 27, 2026

    @om986
    ContributorAuthor

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestroadmapIdeas and changes to the project roadmap

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions