currently, only the nmap parser for TLS includes the info about the transport protocol in the asset ID (e.g. identifier = f"{host}:{port} ({transport_protocol})").
all the other tools/parsers (sslscan, sslyze and testssl) don't provide that info in their scan results.
some services (e.g. HTTP, DNS, LDAPS, ...) could be provided over TCP or UDP, so there is no way of guessing based on the application protocol.
this makes combining results from multiple scanners/tools (e.g. Nmap and testssl) a tedious process: the assets will always be different with those tools.
currently, only the
nmapparser for TLS includes the info about the transport protocol in the asset ID (e.g.identifier = f"{host}:{port} ({transport_protocol})"). all the other tools/parsers (sslscan,sslyzeandtestssl) don't provide that info in their scan results.some services (e.g. HTTP, DNS, LDAPS, ...) could be provided over TCP or UDP, so there is no way of guessing based on the application protocol.
this makes combining results from multiple scanners/tools (e.g. Nmap and testssl) a tedious process: the assets will always be different with those tools.
how should we handle this?