Jira Insight Discovery service account requires local-admin rights on target servers

Michael Neuweiler

Our company wants to introduce Jira Insight and run Insight Discovery on a VM in the server zone of our data-centre. I have the following questions which need to be solved prior to any installation and filling of our cloud based CMDB:

• In https://confluence.atlassian.com/insightapps/discovery-system-requirements-1085180644.html it is specified that the service account the Discovery tool is running with needs local admin rights on all probed servers in order to access WMI. I'm not allowing that because in case the server or the Discovery tool is compromised, we give away full access to all our infrastructure. Is there a way to limit the rights of the service account to an acceptable level (read only) so that no malware can be installed on all servers?
• In the same document it is stated that "To transfer data between Discovery (or the Collector) and Insight in Jira, you must have a reachable network path (TCP-Port 445) or SSH-Copy (TCP-Port 22). ". Does that mean the port 445/ss has to be open for incoming traffic from the cloud/internet and thus opening a way to compromise the server/tool? Or is it an outgoing connection only to send data to Insight in the cloud?
• Is it possible to use the Discovery tool without access to WMI, Telnet, SSH? i.e. that it acts as a simple network scanner (ICMP and Port-Scanning). This doesn't give info about RAM, CPU and Disk-Space but at least servers and running services (e.g. a Tomcat, SQL server, etc.)