User guide
This guide is for people who use the web interface to see what is vulnerable and what to do about it. It describes what each page shows and how to filter it. It does not cover installing agents or managing users; see the Administrator guide for that.
Pages
| Page | Question it answers |
|---|---|
| Dashboard | How bad is it, where is it, and is the data current? |
| Findings | Which vulnerabilities are present, and which of them can be fixed? |
| Dependencies | Which packages are installed, and where? |
| Assets | Which hosts and containers have reported an inventory? |
| Reports | How do I hand the current picture to someone else? |
| Alerts | Which alerts were sent, and why? |
| Account | How do I change my password or create a token for scripts and AI assistants? |
The side bar lists the pages you can open. Scans and tasks, Alerts and CPE mappings appear only if your roles include them, and Agents and Reports need their own permission. Settings is always listed; the sections inside it depend on your permissions.
Working with the data
The interface reads from the same inventory everywhere, so the numbers match from page to page. Four habits make the work easier:
- Start from the dashboard, then open the findings. The dashboard links its panels to the findings page with the same filters.
- Filter first, then export. The CSV, JSON and PDF exports keep the filters of the page you export from.
- Read the fix column before you ticket. A finding with a fixed version tells you what to upgrade to. A finding with No fix yet needs a mitigation or a decision to accept the risk.
- Check the scope. If a cluster you expect is missing, you may not be allowed to see it. Your administrator can widen your scope.
Filters are part of the address of the page. Copy the address to share the same view with a colleague who can see the same data.
Continue with key concepts for the terms used throughout the interface.