Connect cloud accounts
A vulnerability in a repository is a to-do item. The same vulnerability in a Lambda function with a public URL is an incident waiting for a date. Connecting your cloud accounts is how Dwaar learns what is really running and how it is exposed.
An AWS account, a Vercel team, a Railway workspace or a Cloudflare account becomes a Cloud resource. Its workloads appear under it, each with a kind, a region and an exposure.
Connect AWS
Dwaar never asks for AWS keys. You create a role in your account, and Dwaar assumes it using an external id unique to your tenant.
If the role must not trust an account outside yours, set Role assumed by to An outpost: an outpost in your account assumes the role with its own identity instead. See AWS connections the outpost assumes.
Prerequisites
- A Dwaar role that holds
integrations:create. - Permission to create an IAM role and a CloudFormation stack in the AWS account.
Steps
- Open Integrations, choose Amazon Web Services, then Add connection, and name the connection after the account.
- In the guide beside the form, Create the DwaarSecurityAudit role, choose Open CloudFormation quick-create if it offers it. The stack arrives with your external id and Dwaar's principal filled in.
- Create the stack, then copy its RoleArn output.
- Paste it into Role ARN in Dwaar. It looks like
arn:aws:iam::<account-id>:role/DwaarSecurityAudit. - Enter Regions as a comma-separated list, or leave it empty for every enabled region.
- Press Test connection, then finish the discovery step.
No quick-create link, or your team creates roles by hand? The guide's next steps give you the trust policy and the DwaarRead policy to copy, already filled with your values, and the two managed policies to attach. They are the same as the stack's. Your external id and Dwaar's principal are there with copy buttons too.
What the role can do
The stack creates one role, DwaarSecurityAudit, with a session of up to an hour. Read this before you approve it, because your security team will ask.
- Trust: only the Dwaar principal, and only when it presents your external id.
- Managed policies:
SecurityAuditandViewOnlyAccess. - Discovery reads: listing regions, ECS, EKS, Lambda and pulling ECR images.
- Posture reads: the additional read actions the posture checks need beyond those two policies.
The template describes itself as unable to change the account, and almost everything in it is a read. Review three things closely with your security team before you deploy it. securityhub:BatchImportFindings is on the list the posture checks require, and it is a write action. logs:FilterLogEvents can read log contents. lambda:GetFunction can reach function code packages.
The stack has an Enable workload scanning option. It is reserved for a later release and does nothing today, so leave it at false.
What you should see
The account appears under Resources as a Cloud resource, with a Workloads tab listing Lambda functions, EC2 instances, ECS services and EKS clusters. Each workload shows its exposure, such as a function URL without auth, a public IP, an internet facing load balancer or a public EKS endpoint.
Posture checks of the account run once a day, using Prowler, and appear on the resource's Scans tab.
Connect Vercel
Method: Access token.
Prerequisites
- A Dwaar role that holds
integrations:create. - A Vercel token scoped to the team you want to connect.
Steps
- Open Integrations, choose Vercel, and name the connection after the team.
- Enter the values below.
- Press Test connection, then finish the discovery step.
| Field | Required | Value |
|---|---|---|
| Team id | Yes | From the team's Settings › General › Team ID. It starts with team_. Hobby teams have one too. |
| Token | Yes | A token scoped to this team with All Projects, created on your account's Tokens page. |
A Vercel token acts with the team role of the person who creates it. Dwaar only reads, so create it as a member with the Pro Viewer or Enterprise Viewer role. There is no reason to hand over more. Test connection tells you which role the token acts with.
What you should see
The team appears as a Cloud resource, with its projects listed as workloads and production domains shown as public exposure. Dwaar tracks each project's production deployment, which is what your users reach. Tracking preview deployments is not available yet. Posture checks cover the team as well, and they appear on the resource's Scans tab. Dwaar also reads the names, types and targets of environment variables, which is enough to find plain-text and misplaced secrets, without reading their values.
Connect Railway
Method: Workspace token.
Prerequisites
- A Dwaar role that holds
integrations:create. - A Railway workspace token for the workspace you want to connect.
Steps
- In Railway, open the workspace, then Workspace Settings › Tokens, and create a token named
dwaar. Copy it now: Railway shows it only once. - In Dwaar, open Integrations, choose Railway, and name the connection after the workspace.
- Paste the token into Token.
- Press Test connection, then finish the discovery step.
Use a workspace token. An account token reaches every workspace you belong to, and a project token can't read the workspace. One connection is one workspace.
Railway has no read-only token, so this token could change anything in the workspace. Dwaar only reads with it. Keep it in Dwaar or your vault, and delete it in Railway when you disconnect.
What you should see
The workspace appears as a Cloud resource. Its projects and their services are listed as workloads, one per service in each environment, with the service's region and exposure. A service reachable through a TCP proxy is a public endpoint, one with a custom domain a public domain, and one with only a Railway domain a public URL.
Posture checks of the workspace run once a day, after discovery, and appear on the resource's Scans tab. Railway has no Prowler provider, so Dwaar runs its own checks. They cover:
- Workspace: two-factor authentication, single sign-on, the number of admins, the guardrail policy and tokens that never expire.
- Projects: public projects, pull request environments that copy variables, members without two-factor authentication and old project tokens.
- Services: databases or other services reachable through a TCP proxy, public database URLs used between services, unpinned images, deploys that don't wait for CI, preview environments without Railway authentication, unverified custom domains and volumes without a backup schedule.
- Variables: secret-looking variables that aren't sealed, haven't changed in a year, or are exposed to browser bundles with a prefix such as
NEXT_PUBLIC_.
Dwaar reads variable names, never their values.
Some settings only exist on Railway's Pro or Enterprise plans, such as single sign-on and guardrails. On a Hobby workspace those findings say which plan the setting needs.
A check Dwaar couldn't decide is skipped, never passed, so a finding it raised before stays open until a later check can read the setting again. That happens when the token can't read something, such as member two-factor status without a workspace admin, or when an environment has more variables than one page of Railway's API returns. Railway services aren't scanned as images or repositories yet. Connect the registry or repository behind them to scan the code.
Connect Cloudflare
Method: API token.
Prerequisites
- A Dwaar role that holds
integrations:create. - A Cloudflare user who can create API tokens for the account you want to connect.
Steps
- In Cloudflare, open My Profile › API Tokens (or Manage Account › Account API Tokens) and choose Create Token › Create Custom Token. Name it
dwaar. - Give it these read permissions, and nothing that edits:
- Account: Account Settings Read.
- Zone: Zone Read, Zone Settings Read, DNS Read, SSL and Certificates Read, Zone WAF Read, Firewall Services Read, Bot Management Read.
- Under Account Resources, include only the account to connect. Under Zone Resources, include all zones of that account. Create the token and copy it: Cloudflare shows it only once.
- In Dwaar, open Integrations, choose Cloudflare, and name the connection after the account.
- Paste the token into API token. If the token reaches more than one account, or you created it under Account API Tokens, also copy the Account ID from the account's home page into Account id.
- Press Test connection, then finish the discovery step.
One connection is one Cloudflare account. Don't use the Global API Key: it can change everything your user can, and Dwaar refuses it.
What you should see
The account appears as a Cloud resource, with each zone listed as a workload. A zone is a domain served through Cloudflare, so its exposure is public domain. DNS records aren't listed one by one.
Posture checks of the account run once a day, after discovery, and appear on the resource's Scans tab. They cover:
- TLS and HTTPS: Full (Strict) SSL, the minimum TLS version, TLS 1.3, HSTS, Always Use HTTPS, automatic HTTPS rewrites and universal SSL.
- Protection: the WAF and its OWASP managed rules, firewall rules that block, rate limiting, Bot Fight Mode, Browser Integrity Check, and Under Attack or Development Mode left on.
- DNS and mail: DNSSEC, and SPF, DKIM, DMARC and CAA records.
- DNS records: records not proxied through Cloudflare, records that point at an internal address, wildcard records, and CNAMEs whose target no longer resolves.
A finding about a DNS record shows on its zone and names the record.
The checks cover only the zones discovery keeps. If the account has no zone, or the discovery settings exclude every zone, the checks don't run. They also don't run for more than 1,000 zones: narrow the discovery settings.
The managed WAF isn't available on Cloudflare's Free plan. On a Free zone that finding is informational and says which plan the setting needs.
Try this next
After the first discovery, sort the workloads by exposure. Pick one public workload and walk its lineage back to the code that built it. If the chain breaks, connect the missing registry or repository so Dwaar can tell you what is really exposed.