Discovery system requirements

Here you can find system requirements for running Discovery, and network connection requirements for the hosts you'd like to scan.

Supported platforms

We've tested Discovery on the following platforms, though other distributions should also work.

Operating systemDistribution
  • Windows 10
  • Windows 11
  • Windows Server 2016
  • Windows Server 2019 (requires FOD)


  • Microsoft .Net Framework 4.7.2 or later
  • Ubuntu Desktop 18.04, 20.04, 22.04
  • Debian 11 - 12 (GNOME & KDE)
  • CentOS Stream 9 (GNOME)


See: Using Discovery on Linux

Virtual machines and 64-bit systems are supported.

Minimum system requirements

System requirements depend on how many hosts you are planning to scan and how many threads you would like to use. Here are the minimum ones:

  • 4GB of available RAM
  • 2+GHZ CPU
  • 500MB of disk space

System requirements depend on the number of hosts scanned and parallel threads used. For details, see Recommended information.

Network connection requirements

Assets Discovery uses various methods to collect data on your network.

To determine whether a host should be explored, Discovery send an ICMP-Echo Request to the hosts and tries to connect to every host that answers.

You can also connect to hosts where ICMP is forbidden. For more info, see IP-Modifier.

To transfer data between Discovery (or the Collector) and Assets in Jira, you must have a reachable network path (TCP-Port 445) or SSH-Copy (TCP-Port 22). Make sure the network path is also available for the user that runs the service.

Note that it's not possible to set up a proxy between Discovery (or the Collector) and cloud.

Linux: SSH

Discovery uses SSH to access Linux machines.

By default, the SSH TCP-Port 22 is used. Discovery can connect to a changed SSH-Port on the target machine. For more info, see IP-Modifier.

Windows: WMI

To query devices, Discovery uses the Windows Management Instrumentation (WMI) interface. Because of Microsoft security restrictions for WMI, the credentials used must have local admin privileges on the target machine.

Make sure the following firewall rules are enabled for the host that should be scanned:

  • Windows Management Instrumentaion (WMI-In) (TCP-Port: 135) 
  • Windows Management Instrumentaion (DCOM-In) (TCP-Port: Dynamic)
    (By default, WMI (DCOM) uses a randomly selected TCP port between 1024 and 65535)
  • PowerShell (TCP-Port: 5985)

The WMI or PowerShell can only be used when Discovery is running on the Windows operating system. They won't work on Linux.

SNMP Devices

For network devices, Discovery uses the Simple Network Management Protocol (SNMP) to query the devices. SNMP version 1,2, and 3 is supported.

For SNMP, the default UPD-Port 161 is used. Make sure to enable it.

vSphere ESXi-Server

Discovery uses the WEB-API to get information from the server. For communication, it uses the SSL-Port 443. Make sure to enable it.

(Optional) Windows: Discovery agent

If you're using the optional Discovery agent on Windows systems, here are the ports used:

  • Discovery: TCP-Port 51337 (outgoing)
  • Discovery agent: TCP-Port 51337 (inbound)


All Discovery app dependencies can be found in the sbom.json (software bill of materials) file, which is located in the installation directory.

Last modified on Feb 16, 2024

Was this helpful?

Provide feedback about this article

In this section

Powered by Confluence and Scroll Viewport.