System requirements

This page outlines the system requirements for running Assets Discovery and the network connection requirements for the hosts you'd like to scan.

Supported platforms

Discovery runs under the following environments:

Operating systemDistribution
Windows

Requirements:

Linux
  • Ubuntu Desktop 18.04, 20.04, 22.04
  • Debian 11 - 12 (GNOME & KDE)
  • CentOS Stream 9 (GNOME)

Requirements:

Learn how to use Discovery on Linux

Minimum system requirements

Virtual machines and 64-bit systems are supported. The minimum suggested configuration is:

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


The system requirements for Assets Discovery depends on how many hosts are scanned and how many parallel threads are in use. Read our recommendations

Network connection requirements

Assets Discovery uses various methods to collect data on your network. To determine whether a host should be explored, Discovery sends 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 by using the IP-Modifier.

To transfer data between Discovery (or the Collector) and Assets in Jira Service Management:

  • Data Center: 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.
  • Cloud:Data is uploaded via HTTPS requests to https://api.atlassian.com and https://api.media.atlassian.com. Make sure that you configure the allowlist.

Note that you cannot set up a proxy between Discovery (or the Collector) and Jira Service Management Cloud.

The following table describes the network connection requirements:

Device typeProtocol usedDescription
Linux machinesSSH

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 machinesWMI

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 hosts you wish to scan:

  • Windows Management Instrumentation (WMI-In) (TCP-Port: 135) 
  • Windows Management Instrumentation (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.

Network devicesSNMP

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-ServerWeb APIDiscovery uses the WEB-API to get information from the server. For communication, it uses the SSL-Port 443. Make sure to enable it.

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

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

You can configure these ports in Discovery settings.

Dependencies

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 May 21, 2024

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.