Skip to main content

Workspaces

A workspace is the unit of work in VAAST. Each workspace pins together a single target, an authentication configuration, and the scan history against that target. You typically create one workspace per application or environment — for example, one for staging and one for prod.

What's inside a workspace​

Every workspace stores:

  • Name — a human-friendly label.
  • Target URL — the HTTP endpoint VAAST will send payloads to. This is usually the chat or agent endpoint of the LLM-integrated application under test.
  • Authentication — how VAAST authenticates to the target (see below).
  • Scan history — every scan you've run against this target, plus the findings each run produced.

Workspaces are stored locally inside VAAST's per-user data directory. They never leave your machine.

Creating a workspace​

  1. Open the Workspaces screen from the sidebar.
  2. Click New workspace.
  3. Fill in:
    • Name — e.g. acme-chatbot-staging.
    • Target URL — the endpoint under test, e.g. https://staging.acme.test/api/chat.
    • Authentication type — one of:
      • None — public endpoint or unauthenticated target.
      • API key — sent via a configurable header name (e.g. X-API-Key: …).
      • Bearer — sent as Authorization: Bearer ….
      • Cookie — one or more cookies set on every request.
  4. Save. The workspace opens immediately and you can jump straight into the Scan tab.

Authenticated scanning is a Pro feature; see Plans & Billing. The Free tier supports unauthenticated targets only.

Managing workspaces​

The Workspaces screen lists every workspace you've created. For any workspace you can:

  • Open — jump into its Scan and Request Editor tabs.
  • Edit — rename, change the target URL, or rotate auth.
  • Duplicate — useful for spinning up a new environment from an existing config.
  • Delete — removes the workspace and its scan history from your machine. This cannot be undone.

Workspace hygiene​

  • Give each workspace a name that identifies the environment, not just the product (acme-chatbot-prod, not acme).
  • Before scanning, the workspace's target domain must be verified in the Targets screen. VAAST enforces this — scans are blocked until the domain is verified. See Domain Verification.
  • Do not point a workspace at a third-party system you have not been authorized to test. VAAST is a directed offensive tool and will generate traffic that some WAFs or abuse teams may treat as an attack. If you are testing under a bug bounty scope, use the Written Authorization verification method.
  • Rotate any API keys or bearer tokens you enter into a workspace the same way you'd rotate them in any other tool.