What is the Dwaar Console?
Your scanner just reported four thousand vulnerabilities. Which ten matter?
A list cannot answer that. The answer depends on things no single scanner knows: is the vulnerable code in an image you ship, is that image running, and can anyone on the internet reach it? The Dwaar Console is built to connect those facts. It starts from your real source control, registries and cloud accounts, so scanning covers what you actually have and the results land in one place.
What the console does
You connect the tools where your software lives. Dwaar then does the same loop for everything it finds:
- Discover. Each connection is read on a schedule you choose, and what it holds becomes resources.
- Scan. Discovery queues scans of each new version, and the results land in one findings list.
- Act. You waive what you accept, ignore noise from tests and fixtures, and work through the rest, using severity along with public exploit signals such as EPSS and CISA KEV.
The real trick is the first step. Dwaar does not ask you to list what you own, because that list is always wrong. It reads your systems and tells you.
The words you will see everywhere
The console talks in 7 resources and 6 operations. Learn these and every screen makes sense.
| Term | What it means |
|---|---|
| Resource | One thing Dwaar watches, such as a repository, an image or a cloud account. There are seven types. |
| Product | The group of resources that make up one thing you ship. |
| Operation | What Dwaar does to a resource: Discover, Scan, Guard, Prove, Fix or Break. |
| Finding | One problem on one resource, with a severity and a status. |
| Connection | One set of credentials for one provider. You can have several per provider. |
Resources and operations covers this properly.
What is available today
Be clear about this before you plan around it. Connections, discovery, scans, findings, components and account administration are the working core of the console. Pages marked Preview in this guide describe areas still being built, including products, guards, reports, tests and the code-to-exploit stages that will rank findings by how close they are to an attacker. Their behavior can change.
Try this next
Connect one GitHub organization and look at what comes back. Ten minutes with your own repositories teaches more than any overview page, so head to the Quickstart.