This is “a list of URLs that set cookies on the remote host”. Most notably, this includes information on whether secure boot is enabled on the target(s).ĭropbox Software Detection (uncredentialed check). In our experience, this seems to be the case with Cisco Meraki MXes. The scan is blocked by an Intrusion Prevention System (IPS). The scan is utilising a Windows-based VPN which can cause problems with Nessus’ packet forgery. On the Windows device running Nessus, try using a different NIC (Wi-Fi instead of Ethernet or vice versa, for example). * On the Windows device running Nessus, reset networking (elevated commands netsh winsock reset and netsh int ip reset), reboot, and re-enable File and Printer Sharing. For example, you may be scanning 192.168.1.0/24 from the Wi-Fi NIC but 192.168.1.1/24 could be set statically on the Ethernet NIC which isn’t connected. On the device running Nessus, ensure that a static IP address from the target isn’t set on a host NIC that isn’t actually connected to the target network. On the Windows device running Nessus, restart the Windows service Tenable Nessus.

This is more common than you may think because cybersecurity professionals often have the habit of clicking “No” when Windows asks if you want to make your device discoverable and Tenable Nessus tends to be used physically on new networks.

* On the Windows device running Nessus, ensure that network discovery is enabled (refer to section “Windows problems” → “General failure”). The network cable may not be patched in or the VLAN configuration may be blocking the traffic, for example.

There are a number of potential causes / fixes for this problem:Įnsure that there is network connectivity.

How to use nessus enum