Table of Contents maxLevel 2 minLevel 2
Problems Starting Your First AudIT
If you are having trouble getting your first audit started, it is best to attempt to audit a single, known machine with proper credentials before moving on to full subnets of devices. Start with this guide below on how to audit a single machine.
How to discover a single DeviceNot getting good data back from the audit? Unsure if it worked as intended? Check the discovery log to ensure the audit has ran successfully on the device.
Limited Data Returning From AudIT
Bad or Insufficient Credential Set
If you are not getting much information back from the audit then it is possible that the credential set given was not valid or received properly. To ensure that the credential set was accepted, click on the discovery log on the device summary page and scroll towards the bottom of the window.
...
As shown in the image above, this example is using SSH credential set. SSH is typically used on Linux devices, WMI is used by Windows machines, and SNMP is used in both for network devices, Linux and Windows environmentsdevices. More information on credentials and configuration can be found here: Target Client Configuration. The first underline in the image above is showing that SSH Status is true since we are using this form of authentication for the examplesuggesting the SSH port is open. Notice WMI Status is shown as false as well as SNMP, if a device was using those forms of credentials then the Status should be true.
Ensure which ever credential type you are using is displaying the Status as true, otherwise the audit will not successfully complete. The second underlined part of this image is confirming that the credential set is working for this device and then continues below to show that the SSH audit is starting. Check the discovery log for this information after auditing your device to see if the credentials are being accepted with no issues.
...
Discovery stopped working?
...