Asset Inventory
Asset Inventory gives you a hardware-focused view of your fleet — manufacturer, model, CPU, warranty status, known vulnerabilities, and disk health — separate from the live performance data on the Agents page.
Assets are created automatically: the first entry appears once an agent sends its initial hardware scan, about 30 minutes after it starts.
The asset list
Section titled “The asset list”Each card shows:
- Hostname, OS/architecture, and online status
- Warranty status (active, expired, or unknown)
- Manufacturer, model, and CPU model, when detected
- Tags
- CVE counts by severity (critical / high / medium)
- A per-disk S.M.A.R.T. health summary, when available
Use the search box (hostname, OS, manufacturer, model, CPU, or IP) or the tag filter to narrow the list, and Export CSV to download the full inventory.
Click an asset to open its tag panel and add or remove free-form tags (up to 40 characters each) — useful for marking devices as production, loaner, or similar.
Risk score
Section titled “Risk score”Selecting an asset also computes a risk score on demand: a 0–100 score with a severity level (low/medium/high/critical) and the top factors driving it, blended from active alerts, compliance results, anomalies, and disk health.
Warranty and CVE checks
Section titled “Warranty and CVE checks”With Technician role or above, you can trigger:
- Check Warranty — looks up the device’s current warranty status
- Scan CVEs — rescans the device’s detected software/hardware against known vulnerabilities
Both run in the background; the list refreshes automatically a few seconds after you trigger them. When CVEs are found, selecting the asset shows a table with each CVE’s ID, severity, CVSS score, and description.
Deeper hardware detail
Section titled “Deeper hardware detail”GPU, motherboard, BIOS, and TPM identity, along with S.M.A.R.T. and thermal readings, are shown in full on the Hardware Health page for the same device. Devices assigned to a physical site and rack also appear grouped that way in Guardian Flow’s Map view. Virtual machines running on a VMware or Proxmox host are tracked separately — see Hypervisors.