Skip to content
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Settings

Configure tenant, scan, access, agent, integration, and scope settings.

Settings contains the controls that affect scan eligibility, scan behavior, access, integrations, and scope. Review these pages before your first scan.

Usage

Open Settings -> Usage to check scan entitlement and current consumption.

Use this page to verify:

  • available credits or scan-hour allowance;

  • running and queued scan counts;

  • plan or billing state;

  • feature availability, such as network assessment, scheduled scans, API/MCP access, reports, and attack paths;

  • whether scan launch is blocked by missing domain setup, usage limits, feature access, or agent availability.

1 credit = 1 pentesting hour. Credits add up across Discovery + Assessment runs, excluding paused time. Separate runs each use credits for their own running time, even when they overlap.

See Credits and Usage for approximate web application budgets, application features that can increase usage, and shared-trial versus dedicated balances. Settings -> Billing also includes the credit guide.

Web

Open Settings -> Web to set tenant-wide defaults for web assessments. The page title is Web Assessment.

It has three sections:

  • Severity Display: show web findings as CVSS severity or Bugcrowd VRT priority;

  • Attack Vectors: the tenant's default vulnerability categories;

  • Custom Headers: headers added to web assessment requests by default.

Shared-trial workspaces may not permit tenant-wide Web settings changes. Use the per-run controls in Web Assessment -> Run Assessment; opening Settings should not be required to configure an ordinary run.

Severity display mode controls whether web assessment dashboards, finding lists, filters, and charts show the CVSS severity band or the Bugcrowd Vulnerability Rating Taxonomy priority.

  • CVSS shows standards-aligned severity data derived from CVSS scoring. Choose it for compliance reporting, general remediation tracking, and teams that already triage by Critical/High/Medium/Low.

  • VRT shows Bugcrowd-style P1-P5 priority data for web and API findings. Choose it when you want bug bounty style prioritization that maps findings to a shared web/app vulnerability taxonomy.

Learn more about Bugcrowd VRT: https://bugcrowd.com/vulnerability-rating-taxonomy

Rate limits, browser sessions, starting URLs, trajectory scope, runtime limits, and browser behavior are configured per run in Web Assessment -> Run Assessment. The wizard always sends its own attack-vector selection, so the tenant default mainly applies to API or MCP launches that do not specify one.

Common Web Settings

Network Assessment Settings

Network assessment settings are configured in the launch flow, not from a separate Settings sidebar page.

Per-subnet controls such as allowed exploits, entity exclusions, agent assignment, PCE Intercept/Inveigh, RCE safeguards, and runtime warnings are configured in Modules -> Network Assessment -> Run Assessment.

Domains

Open Settings -> Domains to manage web assessment scope.

  • Whitelist defines domains approved for web assessment.

  • Blacklist blocks domains even if they are discovered through an approved root.

Blacklist takes precedence over whitelist.

Domains

Domain Verification

Open Settings -> Domain Verification to prove DNS ownership of root domains before gated web assessment workflows.

Domain Verification

Trajectories

Open Settings -> Trajectories to create host and path rules for the single-API trajectories that Discovery finds. Rules apply to every Web Assessment run, so use them for APIs that must never be tested, such as a third-party payment provider. To narrow one run instead, use Trajectory scope in the wizard. See Web Assessment Phase.

Trajectories

Agent

Open Settings -> Agent to download agent installers, view connection details, and manage agent runtime settings.

Use it to confirm:

  • agent role, such as SANDBOX, CLOUD, or AGENT;

  • connection status;

  • public and private IPs;

  • subnets and network interfaces;

  • job-capacity settings when the agent exposes them.

Download Agent

API Keys

Open Settings -> API Keys + MCP to create, rotate, or revoke API keys for REST and MCP clients.

API keys inherit the permissions and workspace/organization scope of the creating user. They cannot bypass scan launch policy.

An AI agent connected through the platform MCP server can set up and run assessments for you. See Configure a Tenant with MCP, Agentic Testing with MCP, and the MCP Tool Reference.

API Keys & MCP Server

Integrations

Open Settings -> Integrations to connect supported external systems. Availability depends on the deployment and feature flags.

Integration surfaces are tenant-gated. Connectors shown as Coming soon are visible in the UI but not active for the tenant.

Email Identities

Open Settings -> Email Identities when browser-session recording needs controlled email addresses for OTPs, magic links, or account creation flows.

Each identity can store Account & access notes for its target accounts, credentials, roles, and connected services. The selected identity's notes are shown in Browser Session Manager.

Plan email/phone routing during onboarding if target applications only allow approved domains or phone numbers.

Email Identities

Users and Account

Use Settings -> Users and Settings -> Account to manage team access and account details. Confirm role assignments before giving users scan, report, API-key, or settings permissions.

Debug and Preflight

Users with debug access see Settings -> Debug, with Settings, Test Mode, and Pre-Flight tabs. Manual Crawler and other interactive diagnostic capabilities are available only when Debug Mode is enabled.

Use preflight checks before high-stakes scans to validate queue health, job concurrency, connectivity, and crawler behavior.

Last updated