Enabling Service Discovery
This module provides autodiscovery and documentation of services running on Windows and Linux machines.
To get started with services discovery, head to Discovery menu –> Hypervisors/*nix/Windows. Create a new or edit an existing discovery:
The Windows Discovery Service (WDS) needs to be installed on a single Windows machine on your network capable of reaching your scan targets. If the Discover Services box is checked, then when autodiscovery is run, the services running on that machines will be retrieved.
The autodiscovery job will find each service. In the above example, the postgres service was found running on the device named “stackstorm-001.device42.pvt”. If the service is found on multiple machines, the ‘Service Instances’ section will display those multiple machines in a list.
If you do not wish to track a particular service, in the Edit view simply set the Service Type to “Ignored”.
You can also link a service to an Application Component. In the example above, the nginx service is linked to an application component named “Web Server”. In the edit mode, you can choose the Application Component from a pulldown list.
Note on Autodiscovery of Services
Device42 intelligently compares the output of several commands to provide an accurate reflection of services running on your servers; note that there are minor limitations in special circumstances: For example, many Java applications are currently discovered as running Java processes – but the actual application name, e.g., JIRA is only visible in service details by viewing the executed Java command. Device42 pulls in any service that is listed in `chkconfig` or service –status-all, and/or listed in the Services Console, depending on the distribution/OS in question. Device42 attempts to match all listening ports to respective services, but sometimes differences in reported process names cause connections not be made. It is however possible to map two services so that their relationship is shown in Device42.
To map services and relate them to each other in Device42, go to Apps>Services>Service Ports. You can filter by device name/port to drill down to the service you would like to map.
Click on the port number to view services on that service port, and then in the next window click “Edit” in the upper right. In the Listeners section, click the magnifying glass for “Mapped Service Instance” and choose the service you would like to map.
Now when you click on the mapped service, you will be able to see the discovered service, as well as port and remote IP information.