Products
"Is the checkout service safe to release?" is a question about four repositories, two images and a cloud account. No single resource page can answer it, which is why products exist.
A product groups the resources that make up one thing you ship. Grades and findings roll up to it.
What the page shows
The Products list grades everything you ship by what the scanners can prove. Its Not tracked tab holds what discovery found that belongs to no product yet, and that is worth reviewing regularly. Unowned systems are where risk hides.
Each product has the operation tabs (Overview, Discover, Scan, Guard, Prove, Fix, Break) plus Versions.
How resources join a product
Discovery finds resources but never puts them in a product on its own. They wait on the Not tracked tab until someone decides. You have two ways to do that:
- By hand. On Not tracked, pick a product in a row's Add to product column and select Add. Select Create product when the product doesn't exist yet.
- With Dwaar AI. Select Suggest products and it proposes where each resource belongs and which new products should exist, for you to approve one by one. See Suggest products and lineage with AI.
A product holds resources of its organization and those below it. Another organization that needs the same repository connects its own copy.
See how a product fits together
A product's Overview has a Lineage card: its resources as one chain, from source code through artifacts and infrastructure to vendors. A dashed node is something Dwaar expected and can't see yet. See Lineage.
Try this next
Create one product for the service you worry about most, before you try to model your whole company. Add its main repository, then select Suggest with AI on its Lineage card and see what else belongs. Then read Grades and coverage.