...
The change will be applied only on the current scan level. Changing the default proposed risks of vulnerability types can be done on a configuration file level, by editing engine JSON configuration files located in the WhiteSource Mend SAST® installation directory under ./engines/config/.
...
Once a vulnerability is suppressed, WhiteSource Mend SAST® will store its signature in the database and it will be able to recognize it in future scans over the same source code base and optionally ignore it by selecting the Ignore Stored Suppressions option in the scan configuration.
...
Issues for individual vulnerabilities can be submitted to supported issue tracking systems (currently Atlassian Jira and Azure DevOps work items). To submit an issue, click on the ticket icon in the vulnerability details header. If the credentials for the integrations have already been configured, WhiteSource Mend SAST® will automatically fetch the list of available projects, issue types and assignable users. Optional comments can be supplied to a submitted issue.
...