# 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](/cli/get-started/install.md)).
- 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

```bash
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](/organization/people/service-accounts-and-api-keys.md).

## 2. Scan

From the repository root:

```bash
vulnetix scan
```

An authenticated scan publishes its results as snapshots and prints the links at the end of the report:

```text
  ✔ 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](/vulnerability-management/prioritisation/risk-strategies.md).

## 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:

```bash
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.

> [!CAREFUL] Any member can triage and suppress
> Triage and suppressions have no owner-only check. Every member and every service account can write them, and every write names who made it.

## Next

- [Findings and triage](/vulnerability-management/findings/triage.md) for every state, custom scores and bulk actions.
- [Suppressions](/vulnerability-management/findings/suppressions.md) for review, expiry and pending VEX rules.
- [Remediation policy](/vulnerability-management/prioritisation/remediation-policy.md) for deadlines per severity.
- [Campaigns](/vulnerability-management/campaigns/campaigns.md) for a time-boxed push.
