Skip to main content

Integrations

Dwaar can only judge what it can see. An empty console is not a clean bill of health: it means nothing is connected yet.

A connection fixes that. It is one set of credentials to one place your software lives, such as a GitHub organization or an AWS account. Every connection adds resources Dwaar can discover and scan, so connect source control first and add the rest as you need them.

Connect one provider, or the same one five times​

Each provider can hold many connections. Two GitHub organizations are two connections, each with its own credentials, discovery settings and schedule. Name each one after the org or account it covers, because that is the name you will read in every list later.

What each category adds​

CategoryWhat you connectWhat you getGuide
Source controlGitHub (GitHub App, token or one public repository), GitLab, Bitbucket, Azure DevOps, GitHub Enterprise ServerRepositories to scanSource control
Container and package registriesECR, Artifact Registry, ACR, Docker Hub, Artifactory, Harbor, Nexus, GitHub Packages, any OCI registryImages and packages to scanContainer and package registries
Cloud and workloadsAWS, Vercel, Railway, CloudflareAccounts, workloads and posture checksCloud accounts
Identity and SaaSOkta, Microsoft Entra ID, Microsoft 365, Google Workspace, Expense data (CSV)SaaS apps and vendors to assessIdentity and SaaS
Secrets managersHashiCorp Vault, AWS Secrets ManagerA place to keep other connections' credentialsSecrets managers

The catalog also lists providers you cannot connect yet. Planned integrations names them, and the Integration catalog shows everything in one table.

How connecting works​

Connecting takes two steps. Secrets managers only need the first, because they have nothing to discover.

  1. Connection. You enter the credentials and press Test connection. Dwaar signs in with those values and saves nothing. The test tells you who the credentials belong to and what discovery would find. You cannot go on until it passes, and changing a value means testing again.
  2. Discovery. You choose what to read and how often, then save.

The GitHub App is the exception. You tick what Dwaar may do and press Continue to GitHub, then choose the repositories on GitHub. Dwaar tests the installation itself when GitHub sends you back.

Every form tells you where its values come from​

Beside each connect form is a guide: numbered steps on the provider's own pages that end with the exact values the form asks for. It names the permissions or scopes Dwaar actually uses and nothing more, gives you policies and commands to copy, and links to the provider's documentation for each step. For AWS it already contains your tenant's external id and Dwaar's principal, so the trust policy you copy is ready to paste.

On a narrow window the guide folds above the form under How to get these values. Replace credential shows the same guide, so rotating a token later does not mean finding this page again.

tip

Use a read-only credential. Dwaar's connect forms ask for read scopes, and a read-only token is enough for discovery and scanning.

When Dwaar cannot reach the provider​

A Git server or registry on a private network, or a token that only works from your IP addresses, cannot be reached from Dwaar. Install an outpost in your network and bind the connection to it under Where it runs: its tests, discovery and scans then run there. The same goes for an AWS account that should not trust an outside account. See Bind connections.

Secrets you type are stored encrypted and never shown again. If you would rather not hand them over at all, keep them in a secrets manager and let Dwaar read them each time it needs them.

Discovery is the schedule​

This is the one thing to get right. There is no separate scan schedule. The connection's discovery frequency, hourly, daily or weekly, is the only clock. Every discovery run lists what the connection can see and queues the scans you turned on.

Press Sync now when you do not want to wait for the next run. Only one discovery of a connection can be queued or running at a time.

Read Discovery and scans for how a discovery turns into findings.

The settings tabs​

Open a connection and you get tabs. Which ones appear depends on the provider.

TabWhat it does
ConnectionShows the method, status, last sync and non-secret values. Replace the credential here. The test must pass before Dwaar saves the new one. A GitHub App connection shows what Dwaar may do and Manage on GitHub instead, because it has no credential of yours.
DiscoveryWhat to read and how often: all or selected items, include and exclude globs, skip archived, skip forks, regions, tag rules.
ScanningWhat each discovery scans: new and changed code, re-checks of unchanged code, and which branches besides the default.
ScannersRead-only view of the scanners that apply. You change them in Scan Center, and they are shared by every connection of those resource types.
AccessSecrets managers only. Every read Dwaar made, with its request id.
ActivitySyncs, scans and settings changes for this connection.
In preview

You may also see Fixing, SBOMs and Routing tabs, and a Guard section under Scanning. These depend on features that are still in preview, so do not rely on them yet.

Turn off both scan triggers and nothing gets scanned​

The Scanning tab has two triggers:

  • Scan new and changed code runs every scanner on each new commit, tag or image digest discovery finds.
  • Re-check unchanged code for new vulnerabilities on every discovery runs no scanner. It matches the last scan's SBOM against today's vulnerability data.

With both off, discovery still lists your resources, but none is scanned until someone runs a rescan or a one-time scan. Dwaar warns you, and it is a valid setup for a connection you only want to inventory. Just do it on purpose.

Disconnecting​

Disconnect stops syncing and scanning that connection's resources. Findings already recorded are kept, and you can connect again later.

Renaming a connection changes the name in Dwaar only. Nothing changes at the provider.

Try this next​

Connect one source control organization, with the GitHub App or a read-only token, and look at what discovery finds. If that list surprises you, that is your first useful result, before a single scan has run. Start with Source control.