You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are various situations where the user will want to filter out reported vulnerabilities, for example in the case of a false-positive, or if a particular vulnerability does not affect the user's product due to bug/implementation specifics.
It should therefore be possible to filter these bugs from the view. This could perhaps be done in the following way:
User spots a vulnerability in the Error List that is to be filtered
Right click the vulnerability to get the context menu
Select "Hide vulnerability"
Presto, the vulnerability will be filtered from the view for this, and all subsequent user sessions
It should also be possible to undo filtering. Perhaps in the following way:
Click the "Tools->Options..." menu item, the options dialog will appear
Expand the "Audit.NET" element on the left
Click the "Filter List" sub-item, which will display a list of filtered vulnerabilities
Select the listed vulnerability
Click the "remove" button
Click "OK" to close the options dialog and save the changes
Initially the filter will work on a Visual-studio wide basis. If there is desire at a future time we might be able to add a project-specific filter.
The filter file should be stored in a user-friendly file format that makes it possible to not only edit by hand, but copy to a different installation of Visual Studio to share filters with different users. The importer should be robust enough to handle corrupt files. XML or JSON would be likely candidates for the file format. The file should store enough information to work as a filter and provide user friendly information for the list, which means at least the following:
vulnerability id (used for the filter)
package name
vulnerability title
The text was updated successfully, but these errors were encountered:
There are various situations where the user will want to filter out reported vulnerabilities, for example in the case of a false-positive, or if a particular vulnerability does not affect the user's product due to bug/implementation specifics.
It should therefore be possible to filter these bugs from the view. This could perhaps be done in the following way:
It should also be possible to undo filtering. Perhaps in the following way:
Initially the filter will work on a Visual-studio wide basis. If there is desire at a future time we might be able to add a project-specific filter.
The filter file should be stored in a user-friendly file format that makes it possible to not only edit by hand, but copy to a different installation of Visual Studio to share filters with different users. The importer should be robust enough to handle corrupt files. XML or JSON would be likely candidates for the file format. The file should store enough information to work as a filter and provide user friendly information for the list, which means at least the following:
The text was updated successfully, but these errors were encountered: