Create and review vulnerability exceptions
Mark a finding as accepted risk or false positive, for that asset or the whole company, with a reason and expiration, and revoke the exception when it no longer applies.
An exception silences a finding while it is active: it doesn't notify or keep a notification open. When it expires, the finding counts again. It is used in two cases:
Type | When |
|---|---|
Accepted risk | The vulnerability exists, but the company accepts the risk for a time (for example, until a maintenance window arrives) |
False positive | The vulnerability doesn't apply to that asset |
Before you start
Operate permission on Vulnerabilities.
Create an exception
Go to Security (SIEM) → Vulnerabilities → Findings and open the finding.
Click Create exception.
Choose the type: Accepted risk or False positive.
In Covers, choose the exception's reach (if the finding has no CVE, it can only cover the finding):
This finding.
The CVE on this asset.
The CVE across the whole company.
Choose the date it Expires (12 months at most).
Enter the Reason. It is recorded in the audit log.
Click Create exception.
ARGUNIS tells you how many findings the exception covers.
Review exceptions
Go to Security (SIEM) → Vulnerabilities → Exceptions.
Each row shows the Type, what it Covers, the CVE or key, the Asset, the Reason, when it Expires, who created it and how many Findings it covers. Expired or revoked ones are marked.
To end one early, click Revoke. The findings it covered count again.
Prefer This finding or The CVE on this asset. An exception for the whole company can hide the same vulnerability on a new host where it does matter.