Fine Tuning DAST Results

there are a few configurations that can be used to fine tune dast results to help ensure the alerts generated are not duplicative and can help shorten the time to run a scan soos collapses instances of the same alert (even when found on different urls) which significantly reduces the number of alerts shown in the soos ui, however each instance reported can still be found under the soos web vulnerability (dast) issues docid\ l ty1xqcyiasbno p8r5a detail if needed max alerts for passive scan passive scans often find the same issue on many (or all) urls in the site (such as cookie misconfigurations or header misconfigurations) because of this you may want to limit the number of alerts that are reported using the config pscans maxalertsperrule=5 argument, where "5" is the desired number of alerts to generate for each passive rule that is triggered max alerts for active scans like passive scans, active scans also may often find the same issue on many urls in the site (such as xss) because of this you may want to limit the number of alerts that are reported using the config scanner maxresults=5 argument, where "5" is the desired number of alerts to generate for each active rule that is triggered combining multiple configurations these configurations can easily be combined to limit both active and passive scan rules docker run it soosio/dast clientid=\<soos client id> apikey="\<soos apikey>" projectname="\<project name>" otheroptions=" z ' config pscans maxalertsperrule=5 config scanner maxresults=5'" scanmode=baseline https //url to test