Skip to content
vScope Support Page

Proxies

Proxies extend discovery to networks the main vScope server can’t reach directly (DMZs, remote sites, customer networks).

What they are

Section titled “What they are”

Lightweight vScope instances that relay discovery traffic and are orchestrated from the main vScope server. Discovery results flow back to the main server, while each proxy keeps local runtime state such as its identity, configuration, and logs. Container deployments persist this state in /data so the proxy retains its identity when the container is replaced.

When to use

Section titled “When to use”
  • Segmented or firewalled networks with no inbound path to the main server.
  • Remote sites where latency or routing blocks direct probing.
  • Customer/tenant networks where you want strict scope control.

How it works

Section titled “How it works”
  • A proxy makes outbound connection(s) to the main vScope server (default TCP 4445).
  • You assign targets/credentials to a proxy in Discovery; only those ranges are scanned through it.
  • Results flow back to the main server; scheduling and logs remain centralized.

Security and scope

Section titled “Security and scope”
  • No discovery runs autonomously on the proxy; all commands are pushed from the main server.
  • All traffic are encrypted and proxies need to be approved before being used.
  • Keep the proxy “near the targets” to reduce latency and firewall hops.
  • Use separate proxies to isolate tenants or zones; limit each proxy to only the ranges it should see.
Section titled “Related”