How does Kenna determine if an asset already exists?

Kenna makes every attempt to de-duplicate asset data in the platform. For example, in a DHCP environment, Kenna would not create a new asset every time a new IP was assigned to a host. 

Below is the order of preference (High to Low) given to asset locator data in order to assess if an asset already exists in the environment:

  1. EC2 identifier
  2. MAC address
  3. NetBIOS
  4. external IP address
  5. hostname
  6. URL
  7. file name
  8. fully qualified domain name (FQDN)
  9. application name
  10. internal IP address (RFC 1918)
  11. scanner-specific asset ID (eg Qualys host ID, Nexpose device-id)
Powered by Zendesk