Configure testing scope

Enterprise deployments rely on the customer’s authorisation to test targets under their agreement. DNS verification and individual public-host approvals are not required. Register a target, then choose its testing level when starting a battletest.

Restrict targets (optional)

With no scope entries, all registered targets in the organisation are allowed. Add entries to restrict testing to specific domains or network ranges.

1. Open Settings → Policy → Testing scope and select the organisation.
2. Select Add entry.
3. Choose Domain or Network range.
4. Enter a domain or CIDR range, add an optional note, and save.

A domain entry covers that domain and its subdomains. A CIDR entry covers IP address targets inside that range. For a hostname or local alias, add its domain name.

The target picker checks these restrictions before you continue. Launches and scheduled runs check them again. DNS verification does not override a configured restriction.

Change restrictions

Remove an entry to exclude its targets, unless another entry covers them. Removing the last entry removes the organisation’s scope restrictions.

Scope management requires the organisation’s testing scope permission. Member permissions, licensing, testing levels, and human approval requirements still apply.

Managed deployments

Managed deployments retain their domain ownership checks. Follow Add a target to publish the DNS verification record.