StateWarden's Vigil subsystem ingests global threat intelligence feeds (OSV, NVD, MalwareBazaar) and matches them against the software inventory of your devices. Security feeds are occasionally noisy: a technically correct match may not be exploitable or relevant in your specific environment.
A vulnerability scanner is only useful if its output is actionable. Alert fatigue caused by hundreds of "False Positives" will cause your SecOps team to ignore the Dashboard entirely.
StateWarden handles this through the Vulnerability Triage view - a decision workflow with mandatory accountability, suppression rules, and a full audit trail.
1. What Constitutes a False Positive?
A finding reported by Vigil is technically accurate - the hash matches MalwareBazaar, or the package version matches a known CVE in the NVD database. A "False Positive" in this context means the threat is not exploitable or relevant within your specific operational environment.
Common Scenarios:
- Isolated Environments: An outdated version of
curlis flagged with a High CVSS score, but the server is completely air-gapped and does not have outbound internet access, rendering the vulnerability unexploitable. - Upstream Backports (Linux): Enterprise Linux distributions (like Ubuntu LTS or Red Hat) frequently patch critical vulnerabilities by "backporting" the fix into an older version of the software without updating the main version number. Standard CVE feeds look at the version number and incorrectly flag it as vulnerable.
- Internal Security Tools: Custom penetration testing tools or aggressive administrative scripts (e.g., PSExec) might match behavioral heuristics or specific hashes flagged by MalwareBazaar.
2. The Vulnerability Triage View
All triage work happens in Vulnerability Triage (/triage), which is organized into three tabs:
- ACTIVE - all findings currently requiring attention, with severity, affected device, and detection date. Findings can be filtered by device and searched by CVE ID, package, or device name.
- RESOLVED / IGNORED - the history of closed findings: findings auto-resolved after the underlying software was patched, and findings suppressed by a triage decision.
- SUPPRESSION RULES - standing rules that automatically suppress matching findings (see Section 4).
3. Triaging a Finding (The DECIDE Dialog)
When your security team investigates a finding, they record the outcome as a formal decision:
- In the ACTIVE tab, locate the finding and click DECIDE.
- In the dialog, select one of four decisions:
- Confirm - the finding is real and stays active/acknowledged.
- False Positive - the finding does not apply; it is moved to the history tab.
- Accept Risk - the finding is real but consciously accepted; it is moved to the history tab.
- Snooze - the finding is hidden until a date you specify.
- Enter a justification note (e.g., "Verified patched via Ubuntu backports. Unexploitable."). The note is stored with the decision and included in the audit record.
- Submit the decision.
Decisions of False Positive, Accept Risk, and Snooze remove the finding from the ACTIVE list; Confirm keeps it active with the decision recorded.
4. Suppression Rules
For recurring noise, a one-off decision is not enough. From the DECIDE dialog, click Create Rule to define a standing suppression rule:
- Scope: a single device or the entire realm.
- Target: a specific package or a specific vulnerability ID.
- Reason: False Positive, Accepted Risk, or Not Applicable, plus a free-text comment.
Rules are listed in the SUPPRESSION RULES tab and can be deleted there. Matching future findings are suppressed automatically.
5. Bulk Triage and CSV Export
- Bulk triage: On the ACTIVE tab, select multiple findings with the checkboxes (or select all filtered results), then click DECIDE in the bulk action bar. One decision - with one justification - is applied to every selected finding.
- CSV export: The Export CSV button on the ACTIVE tab downloads the currently filtered findings (severity, CVE ID, package, device, detection date, triage status, and note) for reporting or further analysis.
6. Permissions and Auditability
In a HighSec environment, hiding a vulnerability is a sensitive action and is strictly controlled:
- Realm permission: Recording a triage decision or managing suppression rules requires the realm permission
vigil.triage_risks. Users without it can view findings but cannot decide or suppress. - Platform support roles are read-only: The platform roles
SUPPORT_L1andSUPPORT_L2have read-only access (dashboards and audit logs). They cannot suppress findings or manage rules. - Audit trail: Every decision - including the deciding user, the chosen status, and the justification note - is recorded in the realm's audit trail, visible on the Events & Logs page (
/events). - Nothing is deleted: Suppressed findings are retained in the RESOLVED / IGNORED tab, where compliance officers or external auditors can review the team's security decisions at any time.
7. Revisiting a Decision
If the environmental context changes (e.g., an air-gapped server is connected to the public internet), a previously suppressed finding becomes relevant again.
- Open the RESOLVED / IGNORED tab.
- Locate the finding and click DECIDE.
- Set the decision to Confirm and submit.
The finding returns to the ACTIVE list. Snoozed findings likewise become visible again once their snooze date passes, and findings whose underlying software was patched are marked as resolved automatically by subsequent scans.
StateWarden: Resilience Engineered.