Report from the left menu.Ignore vulnerabilities (and potential vulnerabilities) on a per host/IP basis. Ignoring vulnerabilities causes them to be filtered out of Auto scan reports, host information, asset search results and your dashboard. This action also closes associated remediation tickets for the vulnerability/host pair. If no ticket currently exists, one will be created and closed automatically for tracking purposes. To include ignored vulnerabilities in Auto scan reports, change filter settings in your report template. Note that ignored vulnerabilities always appear in Manual scan reports.
Note that you cannot ignore information gathered checks, or the following QIDs: 38175 (Unauthorized Service Detected), 82043 (Unauthorized Open Port Detected), 38228 (Required Service Not Detected) and 82051 (Required Port Not Detected).
Managers and Unit Managers are allowed to ignore any vulnerability on a per host/IP basis. The option to ignore vulnerabilities may be available for Scanners and Readers, depending on remediation options (see Setting Remediation Options for details).
1. Select Report from the left menu.
2. Run any scan report template set to Status or Status with Trend (auto) source selection. For example, run the Technical Report.
3. In the host details, identify the vulnerability you want to ignore, and place your cursor over 
.
4. Select Ignore vulnerability from the drop-down menu.
The Ignore Vulnerability pop-up appears with details about the vulnerability and the host.
5. Click OK.
6. Refresh the report to remove the ignored vulnerability.
To activate a previously ignored vulnerability, edit your report filter settings to include ignored checks in your Auto scan report. Ignored checks appear grayed out. Repeat the steps in the procedure above but select Activate vulnerability in step 4.
Optionally, Managers can filter vulnerabilities on a global basis, across all hosts, by disabling them. To do so, edit the vulnerability from the KnowledgeBase and select Disable this vulnerability. Note, however, that disabling vulnerabilities will not result in the automatic closing of tickets because the setting is global rather than specific to a particular host.