Idea ID: 2871292

NMAP Port Fingerprinting

Status : Waiting for Votes

Thank you for sharing your idea! It’s open for comments and kudos, and we’re looking forward to input from the community. Once there is enough community traction, it will be further reviewed by the product team


See status update history
1 month ago

Unless I have missed something it looks like NMAP just checks the port is open. It would be really useful if the discovered service on the port (if possible) is also captured. this way we can find specific servcies and use them to trigger discovery with less false positives. 

Example is vCenter. At the moment the only port for trigger files for vCenter is 9443. However vcenter appliances are not using this port and just use 443. this means to auto trigger these either we need SSH or SNMP Access to discover the host fully to get enough info to trigger or you have to try to attempt all 443 ports found. 

Using NMAP you can return the port fingerprint 

This information could be used to put in the port type more accurately and allow more directed discovery. 

Labels:

Agents
CMS UI
Configure
Discovery-Content
Discovery-infra
Infrastructure
Optimization
reconciliation
Software Recognition