Skip to main content

Resources and operations

Most security tools are organized by scanner category: SAST here, secrets there, container checks somewhere else. That is how the tools are built, and nobody thinks about their software that way.

The console is organized by what you own and what you do to it. Finer categories only appear once you drill into one resource.

The 7 resources​

Resource typeWhat it covers
Code SecurityRepositories, what Dwaar scans in them and what it found.
Artifact SecurityContainer images, packages, models and mobile apps you ship, linked back to the code that built them.
Cloud & WorkloadsAccounts and the functions, instances, services, clusters and projects running in them.
API SecurityAPIs and web apps you expose, how they were found, and which were tested.
AI Agent SecurityAgents and MCP servers your products use, and what each can do.
Vendor Risk AssessmentThird parties your products depend on.
Build Tool SecurityPipelines, runners and developer devices.

The 6 operations​

OperationThe question it answers
DiscoverWhat do we have?
ScanWhat is wrong with it?
GuardWhat should be stopped, before or while it runs?
ProveCan we show evidence to an auditor or a customer?
FixWhat is the least work that removes the most risk?
BreakWhich of these could an attacker really exploit?

Every product and resource page uses these as its tabs, so once you have learned the row you can find your way around any screen. Not every type gets every tab, because some make no sense. A cloud account has no Prove or Break tab, for example, and only APIs and AI agents have a Connector tab.

Products sit on top​

A product groups the resources behind one thing you ship, because that is the level at which people ask "are we safe to release?".

Try this next​

Open a repository in Resources and click through its tabs with this table beside you.