Discovery

Discovery is the agentless process that keeps the asset repository in sync with your environment. It updates assets, tags, relations, and history after each run.

Agentless discovery runing

You control

Credentials, access, permissions, targets, schedules, proxies.

vScope controls

Collect data, normalize assets, stitch assets and data, prune, and version history.

Discovery is always initiated from the vScope server. This is also the server where all results are encrypted and stored. Depending on the size of your infrastructure, your may need to adjust the server specs (RAM, CPU, Disk) to ensure best discovery performance.

Feature	Purpose / notes
Probes	Pair credentials with targets; each run updates existing assets and adds new ones.
Targets	IPs, ranges, hostnames, URLs. Smart Targets expand coverage automatically from data sources.
Credentials	Used to authorize access; stored and encrypted in your environment.
Stitching	Removes duplicates and builds relations across data sources based on built-in identity rules.
Schedules	Control when discovery runs; Main Schedule catches anything not on a custom schedule.
Pruning	Defines how long an asset stays “in use” when no longer found.
Proxies	Reach remote or segmented networks via discovery proxies.
History	Every change is versioned; you can view when an asset, tag, or relation changed.

A typical Discovery flow

1. A schedule triggers a Discovery.
2. Targets are pinged to initialize contact.
3. Probe runs: Assigned credentials are used to collecting data.
4. Results are stitched with existing data.
5. Asset repository is updated, including history versioning.

Common Errors

• Invalid credentials or insufficient permissions.
• Blocked ports/targets unreachable.
• Disabled or wrong schedule, too-narrow target scope.

Learn more

• Discovery UI reference
• Ports used by vScope.