Discuss: Dismissing vulnerabilities should provide configuration updates for future scans
When vulnerabilities are dismissed from the dashboard, there is no relationship between the dismissal of vulnerabilities and changing the scan rules for a particular scanner. In the case of DAST, there are dozens of parameters, thresholds, and settings that can be tweaked.
The dashboard should not just 'dismiss' vulnerabilities, but it should inform the configuration of the scanner.
Example: If a false positive about a MySQL database is surfaced, and the application is not using MySQL, the user should be able to dismiss that vulnerability and check "Do Not Run MySQL vulnerability scans".