I've tested this with Nessus and Qualys. Import scanner output into Dradis.
Expected behavior
Both of the above scanners include an issue that describes the results of the port scan. In a perfect world, Dradis would treat all port-scan related issues as the same and parse this data into a node service entry.
Actual behavior
Qualys port scans are removed from All Issues and imported as expected.
Nessus port scans are treated as an issue.
The output of both scanners is combined at the node level, but is duplicated.
Steps to reproduce
I've tested this with Nessus and Qualys. Import scanner output into Dradis.
Expected behavior
Both of the above scanners include an issue that describes the results of the port scan. In a perfect world, Dradis would treat all port-scan related issues as the same and parse this data into a node service entry.
Actual behavior
Qualys port scans are removed from All Issues and imported as expected.
Nessus port scans are treated as an issue.
The output of both scanners is combined at the node level, but is duplicated.
System configuration
Dradis version: Dradis Pro 2.6
Ruby version:
OS version: