guides
Assets
An asset is one thing under protection — a web app, a repository, or a cloud account. Muster meters and scans per asset. This page covers the asset types and exactly how to connect each one.
what you'll learn
- The three asset types and what each one scans
- How to add each type, field by field
- How to reach behind a login with authenticated scanning
- How context docs make the agents smarter
Asset types
Add assets from an organization's assets tab (/orgs/<your-org>/assets), shown as your tracked assets. Three types are available:
| parameter | type | description |
|---|---|---|
Web app | web-app scanning | A live website, app, or API. Muster attacks it like a real user — auth bypass, IDOR, injection, business-logic flaws. |
GitHub repository | code scanning | Source code, discovered from a GitHub org or username. Finds code-level vulnerabilities, and (with Deps) known-vulnerable dependencies. |
Cloud account | cloud posture | AWS, Azure, or GCP. Read-only posture scanning for misconfiguration and exposure. |
Adding an asset
- 1
Open the Assets page
From the org, click the assets tab. New here? ✦ Set up with agent runs the guided wizard instead — see Getting started.
- 2
Click + Add asset
The + Add asset button opens a modal — “What kind of asset do you want to scan?” Pick a type.
- 3
Provide the details (varies by type)
See the per-type fields just below.
- 4
Scan
Cloud connects and scans immediately (Connect & scan). For web apps and repos, launch from the asset row with Scan, or run Scan all assets. See Scanning.
Web app
Add a URL directly in add a web app by url (e.g. https://app.example.com) and click Add web app, or discover apps from a domain. To authorize active scanning of a domain you verify ownership with a DNS TXT record on the root domain (the verify domain panel gives you the exact record).
Every web app also gets hourly DNS monitoring: Muster snapshots the host's records and raises a finding when they drift (nameserver or mail changes, CNAME removal, CAA and SPF/DMARC edits, address changes). If a host sits on rotating infrastructure — hourly IP recycling, a load balancer, a CDN — open its Configure panel and set DNS monitoring to Hijack signals only, which skips A / AAAA / CNAME churn while still watching the records that matter for a takeover. The setting covers the root domain too, unless another web app on the same domain still watches all records. Off removes the host from the monitor entirely; the root domain stays watched as long as another web app shares it.
GitHub repository
Enter a GitHub org or username in discover repositories from github and click Discover. Muster lists the public repositories (forks and archived repos filtered out); tick the ones to protect and add them. This is discovery by org/username — no GitHub App install required.
Cloud account
Choose a provider — AWS, Azure, or GCP — give the account a label, and paste read-only credentials (the form shows the least-privilege policy per provider, e.g. AWS SecurityAudit + ViewOnlyAccess). Click Connect & scan and posture scanning starts.
Authenticated scanning
Much of an app lives behind a login. On any web-app asset, click 🔒 Auth and open the Authentication tab to give Muster a way in — it then tests the authenticated surface too:
- Header — a header name and value, e.g. an
Authorization: Bearer …token, for API-style apps. - Cookie — a session cookie string like
session=…; csrf=…. - Form login — a login URL, test-account username and password, the field names, and a logged-in indicator. This drives the crawl and active scan as a logged-in user.
Save with Save authentication. Use a dedicated test account with the least privilege that still exercises the flows you care about.
Context documents
The Context docs tab (next to Authentication) lets you paste in knowledge that helps the agents reach flows a blind scanner never would:
- OpenAPI — paste an OpenAPI/Swagger spec so every endpoint is probed.
- Business logic — describe how the app is meant to work, so the agents can test for authorization and logic flaws.
- Notes — anything else useful about the target.
Give each document a name and content, then Add document. The agents fold it into their probing plan.
Safety
You authorize every target and confirm you control it. Web-app scanning is gated behind an ownership attestation and DNS verification; cloud access is read-only. Scans are scoped and rate-limited — and you can point Muster at staging first if you prefer.
continue