Target

A Target is a place you want looked at: a fleet of laptops, a network, a Kubernetes cluster, a cloud account. A Target is a scope. It names the place, and the Collectors do the looking inside it. Many Collectors can report into one Target.

The command line and the API call a Target a deployment, which is why Target commands use the deployment-* names and the API path reads /v1/discover/deployments. The New scan modal in the Console calls them scan surfaces. All three names mean the same object.

What a Target Holds

Holds	Meaning
Collectors	Every scanner reporting into this scope, and whether each is connected
Scans	Every scan run against the Target, and what each returned
Resources	Everything found in this scope
Credentials	The scanner tokens and enrollment codes that let Collectors join
Policies	Rules that say what this scope allows, and violations against them

Until a Collector connects, a Target shows zeroes and the Console reads No agent connected. Here the word “Agent” means Collector. The Agent Registry uses the same word for an AI Agent, which is a different thing.

Target Types

Type	Use it for
`scanner`	Anything that goes looking for services. This covers all four Collector kinds.
`dlp`	A scope that receives runtime events from a Vijil Dome proxy. It runs no scans.

Most Targets are scanner. Choose dlp only when Dome telemetry feeds the scope.

How Many Targets You Need

One Target per source. One for endpoints, one per network, one per cluster, one per cloud account.

Create a Target

Create your first Target and find it in the Console.

Last modified on October 2, 2026

⌘I

Overview

Trust Score

Discovery

Evaluation

Red Team

Runtime Defense

Reference

What a Target Holds

Target Types

How Many Targets You Need

Next

Create a Target

​What a Target Holds

​Target Types

​How Many Targets You Need

​Next

Create a Target

What a Target Holds

Target Types

How Many Targets You Need

Next