Skip to main content

Lineage

A vulnerability in an image raises two questions right away: which repository do I fix, and where is this image running? If you can't answer both, you can't size the problem or hand it to anyone.

Lineage is the chain that answers them. It links each resource to what it was built from and what it ships to.

The stages​

Every lineage graph uses the same fixed columns, reading left to right:

Build tools, Source code, Artifacts, Infra, then APIs, AI agents and Vendors in the last column.

Dwaar expects certain links, and it tells you when one is missing:

A resource of this typeShould link to
ArtifactThe code that built it
Cloud resourceThe artifact it runs
APIThe cloud resource that serves it
AI agentThe code it comes from

When the link is missing, the resource's lineage is not mapped and the graph draws a dashed gap in that column. On the resource you'll also read a line such as "No repository is linked to this artifact, so its findings cannot be followed back to their source". That sentence is worth acting on.

Read a resource's lineage​

  1. Open a resource.
  2. Open the Lineage tab.
  3. Read the graph. It shows the resource and its direct neighbours.
  4. Use the two lists under the graph, Built from and Ships to / runs on, to see those neighbours by name.
  5. Select any neighbour to open it.

If nothing is linked yet, you'll see "Nothing linked yet". Links come from what scans find, what people map, and suggestions a person approves.

A lock with a blurred label means something is connected there that you don't have access to. Dwaar shows that the link exists, so you know the chain continues, and keeps the resource's name and details hidden. To follow it, ask someone with access to that organization. It also means a resource isn't called out as missing a link when the link may be one you can't see.

On the Lineage tab of a resource or the Lineage card of a product, select Suggest with AI. Dwaar AI proposes links with its reasons and evidence, and you approve each one. See Suggest products and lineage with AI.

Scans can't always see a connection, for example an image built by a pipeline in another system. For those cases, the Map lineage button lets you add the link yourself.

  1. On the Lineage tab, select Map lineage.
  2. Choose a direction: Built from (the repository a container is built from) or Ships to (the cluster a container runs on).
  3. Choose the resource type and the resource.
  4. Select Add link.

To remove a link, select the remove control next to the neighbour's name. Both actions need resources.lineage:update.

A link joins two resources of one organization, and you can't add one if the other resource already feeds this one. You also can't remove a link a scan found: the next scan would only write it back, so Dwaar refuses and says why.

Why this beats a longer findings list​

Lineage is what turns a finding into a decision. The same vulnerability deserves different handling when it stops at a repository and when it continues through an image to a public endpoint. See Resources and operations.

Try this next​

Open your most exposed workload and walk its lineage backwards until it stops. Wherever it stops is where your visibility ends. Connect the integration that closes that gap, then look again.