Vulnerability management quickstart
Send a first authenticated scan to Vulnesis, find its results in the Resolve Platform, triage one finding, and suppress another so later scans keep it hidden.
This page takes one repository from a first scan to a triaged backlog in the Resolve Platform. Findings reach your organisation only from an authenticated scan.
Prerequisites
- The Vulnesis CLI on your
PATH(installing the CLI). - A Vulnesis organisation. A free Community key is at
https://www.vulnes.is/resolve/register. - A console sign-in for the same organisation.
1. Sign in
vulnetix auth login
It prints a URL and a code and waits until you approve in the browser. In CI, set VULNESIS_ORG_ID and VULNESIS_API_KEY instead; see Service accounts and API keys.
2. Scan
From the repository root:
vulnetix scan
An authenticated scan publishes its results as snapshots and prints the links at the end of the report:
✔ BOM: .vulnetix/sbom.cdx.json
✔ Memory: .vulnetix/memory.yaml
✔ Snapshot: <link to this scan in the console>
An unauthenticated scan prints Snapshots are skipped for unauthenticated scans. and sends nothing.
3. Open the findings list
In the Resolve Platform, open What to fix first (https://www.vulnes.is/resolve/findings). It holds every finding your organisation owns, one row per repository, package and finding id, showing the latest scan’s copy. Sort by priority to rank them by the risk strategy.
4. Triage a finding
Open a finding and choose Triage. In Triage finding, set Analysis state, for example Not Affected, pick a Justification such as Code Not Reachable, and choose Save triage.
Not Affected and False Positive need a justification. Each triage records you as its author and writes a VEX statement for the finding. False Positive also creates a suppression, so the next scan’s copy stays hidden.
5. Suppress a finding
To hide a finding you accept rather than dispute, add an ignore rule from the repository:
vulnetix ignore add --finding CVE-2024-3094 --category sca --type risk_accepted \
--reason "Not shipped in the runtime image" --expires-in 90
Signed in, the rule is saved to your organisation as well as .vulnetix/memory.yaml, and appears on Configuration › Suppression Policies (/resolve/suppression-policies). The next scan reads it and reports the finding as suppressed. Without --expires-in the rule does not expire.
Next
- Findings and triage for every state, custom scores and bulk actions.
- Suppressions for review, expiry and pending VEX rules.
- Remediation policy for deadlines per severity.
- Campaigns for a time-boxed push.