Skip to main content

Cloud & Workloads

The question that matters in an incident is not "do we have a vulnerable function?" It's "is it reachable from the internet, and which account is it in?" Cloud & Workloads answers that.

Connect an AWS account, a Vercel team, a Railway workspace or a Cloudflare account. The account becomes a resource, and discovery lists what runs inside it.

Prerequisites​

  • An AWS, Vercel, Railway or Cloudflare connection. See Integrations.
  • resources:read to see cloud resources.

Accounts and workloads​

KindExample
AccountAn AWS account, a Vercel team, a Railway workspace or a Cloudflare account
Function, instance, service, clusterWorkloads discovered in an AWS account
ProjectA Vercel or Railway project
ServiceA Railway service in one environment, such as api (production)
ZoneA Cloudflare zone, one domain such as example.com

Each workload carries the account it was found in, its region and its exposure. An account carries neither a region nor an exposure of its own, though it lists the regions discovery covered.

Exposure​

Exposure is the column to sort your attention by.

ExposureWhat discovery saw
Public URLA Lambda function URL with no authentication, or a Railway service domain
Public IPThe workload has a public IP address
Internet load balancerIt sits behind an internet-facing load balancer
Public endpointThe EKS API endpoint is public, or a Railway TCP proxy
Public domainA Vercel production domain, a Railway custom domain, or a Cloudflare zone
InternalNot reachable from the internet
Not assessedDiscovery couldn't say

Not assessed isn't the same as internal. Treat it as a question you still have to answer.

Read an account​

  1. Open Resources, then Cloud & Workloads.
  2. Select an account.
  3. Open Workloads to see what discovery found running in it, with each workload's kind, region, exposure and open findings.
  4. Open Findings for what the posture check reported.
  5. Open Scans to see each posture check: what it looked at, when, and what it found.

How checks run​

Cloud resources aren't scanned one at a time. A posture check runs for the whole connection, covering the account or team in the regions you chose, and findings land on the resources it looked at. That's why a workload has no Rescan button of its own.

ConnectionWhat the check covers
AWSThe security configuration of the account in the regions you chose
VercelThe security settings of the team and its projects, such as deployment protection
RailwayThe settings of the workspace, its projects, services and variable names, such as databases behind a TCP proxy and unsealed secrets. See Connect Railway
CloudflareThe settings of each zone and its DNS records, such as TLS and HTTPS enforcement, the WAF, DNSSEC, mail records and records that expose an origin. See Connect Cloudflare

Discovery plans the check, at most once a day per connection, and only while the connection's cloud posture setting and the matching category in Scanners are on. Results appear on the Scans tab and in Scan Center.

tip

Some posture checks are true but rarely worth acting on. Dwaar ignores a default set of them so your list starts with what matters, and you can turn any of them back on. See Ignore findings.

Try this next​

Filter the workloads of your busiest account by exposure and start with anything marked Public URL. Then open that workload's Lineage and see whether you can reach the code behind it. If you can't, map it. See Lineage.