Glossary
Some words in the console mean something narrower than you would guess. "Fixed" is a good example: it does not mean someone said so. It means a run of the current version looked and did not see the finding.
The model
| Term | Meaning |
|---|---|
| Resource | Something Dwaar watches. There are seven types: Code, Artifact, Cloud and Workloads, API, AI Agent, Vendor and Build Tool. |
| Operation | What you do with a resource: Discover, Scan, Guard, Prove, Fix or Break. |
| Connection | One set of credentials to one provider account, or one installation of the Dwaar GitHub App. |
| Setup guide | The numbered steps beside every connect form that say where each value comes from on the provider's side. |
| Snapshot | One version of a resource: a commit, or an image digest. |
| Tracked ref | A branch, tag or image tag Dwaar follows on a resource. |
| Run | One scan of one snapshot. |
| Query unit | What a query reads from the database, about 100 rows a unit. See Query. |
| Custom query | One read of a query you ran on Query or with an API key, counted per page of results. See Usage and limits. |
Code-to-exploit stages
A finding climbs these stages in order. A stage stays unknown until the integration that observes it is connected. Unknown is not the same as safe.
| Stage | Meaning |
|---|---|
| Present | The problem is in the code. |
| Reachable | The code path can reach it. |
| Shipped | It is in an artifact you ship. |
| Running | It is running in your cloud. |
| Exposed | It can be reached from the internet. |
| Proven | It has been proven exploitable. |
Grades and coverage
| Term | Meaning |
|---|---|
| Grade | A to F, or ?. A and B are fine, C and D need attention, F is critical, and ? means not enough is connected to grade. A grade carries a confidence of high, medium or low. |
| Connected | Coverage is in place for that resource type. |
| Partial | Some coverage is in place. |
| Untested | The surface was found, but it has no connector. |
| Missing | Nothing covers it. |
Policies
| Term | Meaning |
|---|---|
| Assurance policy | A policy Dwaar evaluates itself on the resources in its scope, from what it holds: findings, scans, settings posture and vendor reviews. See Assurance policies. |
| Revision | One saved version of a policy. Every verdict and event names the revision that judged it. |
| Verdict | A policy's answer for one resource: compliant, non-compliant or not evaluated. Not evaluated is never counted as compliant. |
| Compliance | Compliant resources divided by compliant plus non-compliant ones, over audit and enforce policies. It does not change a grade. |
| Event | One control of an audit or enforce policy failing on one resource or connection. Open until it passes. Not a finding. The API calls it a violation. |
| Exception | An approved, time-boxed exemption of a resource or product from a policy or one of its controls. See Events and exceptions. |
Resource state
| State | Meaning |
|---|---|
| Healthy | No problem to act on. |
| Degraded | Something needs attention. |
| Vulnerable | It has findings that put it at risk. |
| Unscanned | It has not been scanned yet. |
| Scanning | A scan is running now. |
| Guarded | A guard is protecting it. |
| Blocked | A guard stopped it. |
| Archived | Set aside and no longer active. |
Findings
| Term | Meaning |
|---|---|
| Severity | Critical, high, medium, low or info. |
| New | Open, and only the run that found it has seen it. |
| Open | Open, and seen again since. |
| Reopened | Open again after a fix. |
| Fixed | A run of the current version looked and did not see it. |
| Waived | An active waiver covers it, as accepted risk or a false positive. A waiver has a reason and an optional expiry. |
| Ignored | A Finding Configurations category in Scan Center matched it, such as tests and fixtures or docs and examples. Ignored findings stay out of results unless a filter asks for them. |
| Decision | A change a person or an agent made to a finding, with its reason: a waiver, a revoked waiver, a severity change, an ignore or a comment. Findings › Decisions lists them. |
| Via | What a decision was made through: Console, AI agent (MCP), API key, or Dwaar for decisions Dwaar made itself, such as an ignore by a Finding Configurations category. |
Scans
| Term | Meaning |
|---|---|
| Full scan | Every enabled scanner on the snapshot. |
| Vulnerability re-check | Only processing, on the last full scan's SBOM. No scanner runs. |
| Posture check | Checks a connection's organization settings, AWS account, Vercel team, Railway workspace or Cloudflare account, with no single resource as the target. |
| Rescan | Queues a run per tracked ref with no live run: a re-check where the snapshot had a completed full scan, a full scan where not. |
| Force rescan | Runs every scanner again. Scanners' own caches still apply. |
| Cached | An analyzer result reused from an earlier identical scan. |
| Skipped | The analyzer does not apply to the snapshot, or it never ran. |
Scan triggers
| Trigger | Meaning |
|---|---|
| Discovery | A new or changed snapshot. |
| Schedule | A re-check of an unchanged snapshot, planned by discovery. |
| Manual | Someone pressed Rescan. |
| Push | A push to the repository. |
| Pull request | A pull request. |
| One time | A one-time scan. |
Cloud exposure
| Value | Meaning |
|---|---|
public_url | A Lambda function URL without auth, or a Railway service domain. |
public_ip | A public IP address. |
internet_lb | An internet facing load balancer. |
public_endpoint | A public EKS API endpoint, or a Railway TCP proxy. |
public_domain | A Vercel production domain, a Railway custom domain, or a Cloudflare zone. |
internal | Not reachable from the internet. |
| Empty | Not assessed. |
Outposts
| Term | Meaning |
|---|---|
| Outpost | A runner you install in your own network. It takes the discovery, connection tests and scans of the connections bound to it. See Outpost. |
| Enrollment token | A one-time token that enrolls one outpost, for one hour. Deploy outpost creates it. |
| Pending enrolment | An enrollment token that can still enroll an outpost: not spent, cancelled or expired. The Outposts tab lists them, and Cancel ends one. |
| Scan concurrency | An outpost's own limit on the scans it runs together, at most: the host's CPUs, 2 per scan, and its memory can allow fewer. Dwaar's limit for your tenant does not count outpost scans. |
| Memory overcommit | Multiplies the memory an outpost offers scans. Above 1.0 it admits scans whose limits add up to more than the host has. |
| Stopping | An outpost that was told to stop and is letting its running scans finish. It takes no new work. |
| Runs on | Where a connection's work goes, Dwaar or an outpost, and in the queue, where a run went. |
| Only reachable from the outpost | Dwaar never calls the connection's provider itself. Every call comes from its outpost. |
| Refused on | The outpost was offline, stopping or revoked when work was handed to it. Nothing ran. |
| Peak memory | The most memory a scan's containers that can run at the same time could claim by their limits. An outpost starts a scan only if its peak fits. See Plan an outpost. |
Access
| Term | Meaning |
|---|---|
| Tenant | Your whole Dwaar account. |
| Organization | A node in your tenant's tree. Access granted on it also applies to its children. |
| Role | A named set of permissions. |
| Group | One role, on chosen organizations, for chosen members. |
| Service account | A machine identity that signs in only with its own API keys. |
For how these fit together, read Administration.