Discovery Proxies

Objective: Deploy a vScope Discovery Proxy and connect it to the main vScope to scan remote/segmented networks.

When to use

• DMZs, remote sites, customer/tenant networks, or any segment the main vScope cannot reach directly.
• You can run multiple proxies; assign each to its own target ranges.

Prerequisites

• Port open from proxy → main vScope (default TCP 4445; configurable).
• Host near the target network:
  • OS: Windows (full features). Linux supported, but no WMI (use WinRM/PowerShell for Windows targets).
  • CPU: 2 cores; RAM: 6 GB (4 GB to vScope); Disk: ~10 GB.
• Main vScope address/hostname and chosen port.

Secure design

All communication between the proxy and master is secured by TLSv1.3 and that every proxy needs to be approved in the master before it is allowed to take part in discoveries.

Install the proxy

Windows

1. Download the installer: latest-Setup.exe
2. Run installer; set Host Address to the main vScope (IP/DNS).
3. Set Port (default 4445) if different.
4. Finish and start the service.

Linux

Caution

Linux proxy cannot do WMI; use WinRM/PowerShell for Windows targets.

1. Download: latest-amd64.deb
2. Edit /etc/vscopeproxy/config.ini:

   proxy.master.host=<vscope-master-host>
   proxy.master.port=4445   # if changed, set your port

3. Restart the proxy service.

Changing port settings

You can change the port setting by rerunning the proxy installer, or editing config.ini, on both the proxy and the master, and adding: proxy.master.port=<port>. Ensure that all proxies use the same port configuration.

Register in vScope

1. In vScope, go to Discovery → Proxies → Available; click Refresh if needed.
2. Approve the proxy; it moves to Approved. If it shows Pending, wait for first data to be sent and validated.
3. (Optional) Rename and assign targets/ranges to the proxy; click Save.

Tip

You may also assign targets to proxy from Discovery > Targets.

Verify

1. Assign a target, an IP or a range to the proxy.
2. Run discovery; open Log History or build a quick IP table to confirm assets are found via the proxy.

Frequently asked questions Review the FAQ for Discovery proxies.

Troubleshooting

• Proxy disconnected/pending: see detailed guide → Proxy not appearing or disconnected
• Pending status persists: ensure proxy reaches main vScope on the chosen port; check proxy log C:\vScopeProxyData\log\debug.log (Windows) or /var/log/vscopeproxy/debug.log (Linux, path may vary).
• Failed discovery results: assign correct credentials to targets; ensure target ports are open from the proxy.

Related

• Concept: Proxies
• Ports: Ports used by vScope
• FAQ: Discovery Proxy FAQ
• Troubleshooting: Proxy not appearing or disconnected