Assets
The hosts your scans found, with their open findings, ports, technologies and scans; filters, saved views, bulk actions, and deletion that lasts and can be undone.
The Assets page lists the hosts your scans found — by infrastructure checks, domain OSINT, technology discovery, AI DAST and the AI Pentest — and the ones you added yourself. For each host it shows the open findings on it, the ports and technologies seen on it, the scans that saw it and what changed. Every host belongs to one product; hosts recorded without one are listed under No product, and a notice at the top links to them.

Counters and views
Five counters sit above the list, for the product chosen at the top: Active hosts (and how many are internet-facing), Critical / High exposure, New this week, Stale — not seen by a scan for 30 days — and No owner. Each counter is also a filter: click it to list those hosts.
Three tabs show the same hosts three ways:
| Tab | What it shows |
|---|---|
| Hosts | One row per host: its name and address, its open findings by severity, its open ports, its technologies, its product, when a scan last saw it, and its status and owner. Chips mark a host as New (first seen in the last 7 days) or Internal, and show its business criticality. |
| Technologies | Each technology once, with the versions seen and how many hosts run each, the products they belong to, how many of those hosts have open findings, and the worst risk among them. Click a row to list those hosts. |
| Services | Each open port, with the services and products that answered on it, how many hosts have it open, how many of those face the internet, and the worst risk on these hosts. Click a row to list those hosts. |

Finding hosts
- The Product selector at the top chooses All products, one product (with its host count) or No product.
- Search (Search hostname, IP, port, technology or CVE) matches host names, addresses, ports, technologies, tags, owners and notes, and the title or CVE of any finding on a host.
- The filter buttons list the values the product has, with how many hosts have each. Tick several and Apply.
- Active filters show as chips under the bar; ✕ removes one, Reset filters removes them all. Retired hosts are hidden by default — the Status chip says so — and listed again when you clear it.
- Sort by host, open findings, product or last seen. The filters and the sort are part of the page address, so a link opens the same view.
- Views holds common views — internet-facing hosts with Critical or High findings, stale hosts, hosts never scanned, hosts without an owner, retired hosts — and the ones you saved with Save current view. Saved views are your own, in each team.
| Filter | Values | Default |
|---|---|---|
| Risk | Critical, High, Medium, Low, Info, or No findings. | Any |
| Status | Active, Under Review or Retired. | Retired hidden |
| Technology, Service | The technologies and open ports seen in the product. | Any |
| Last seen | Any time, Seen in the last 7 days, New in the last 7 days, Not seen for 30+ days, Never scanned. | Any time |
| Exposure | Any, Internet-facing, Internal. | Any |
| Owner | The owners set on hosts, or No owner. | Any |
| Tag | The tags set on hosts. | Any |
A host's details
Click a host to open its details beside the list. ↑ and ↓ at the top, or the J and K keys, move to the next and previous host; Esc closes it.
| Tab | What it shows |
|---|---|
| Overview | The open findings by severity, the host's name and address, product, when it was first and last seen, and the fields you can change: status, owner, business criticality, tags and notes. |
| Vulnerabilities | The host's open findings first, by severity, then the closed ones. Each opens in Vulnerabilities; Open in Vulnerabilities lists them all there, filtered to this host. |
| Services & tech | Each open port with the service and version that answered and when it was first and last seen, and the technologies found on the host. |
| Scans | Every scan that saw the host or reported a finding on it, with its status and how many findings it added. Scan this host now opens Infrastructure Checks with the host as the target. |
| History | What each scan observed and each change made by hand, newest first. |

Risk and business criticality
A host's risk is the highest severity among its open findings — Open or In Progress. Findings are matched to a host when a scan stores them: the host named in the finding's target — a URL, host:port or a bare name or address — is looked up among the product's hosts. Risk Accepted, False Positive and Resolved findings do not count.
Business criticality — High, Medium or Low — is set by you: how much the business depends on the host. It does not change with findings, and shows as a badge on the host.
How scans fill the list
- Domain OSINT and technology discovery add the host names they find.
- AI DAST and the AI Pentest add each host they scan and link their findings to it.
- Network Discovery and vulnerability scans report what they saw at an address. That is recorded on every host of the product with that address — five host names behind one mail server all get its ports — and a host of its own is created only for an address no host has. Its reverse-DNS name, if any, becomes that host's name.
- Ports and technologies are only ever added: a scan that sees less does not remove what an earlier one found.
Adding and changing hosts
Add a host with Add asset: a host name or an IP address, the product, and optionally owner, business criticality, tags and notes. Tick Scan this host after saving to go straight to Infrastructure Checks with it as the target. Ports, services and technologies are left to the scans.
To change a host, open it and edit the fields on its Overview, then Save changes.
Acting on many hosts
Tick hosts to show the bar of actions at the bottom of the page:
| Action | What it does |
|---|---|
| Scan | Opens Infrastructure Checks with the hosts as targets — up to 50 hosts of one product. |
| Status | Active, Under Review or Retired. A retired host keeps its findings and history and is hidden by default. |
| Owner | The team or person that answers for the hosts. |
| Criticality | The business criticality of the hosts. |
| Tags | Adds a tag to the hosts, or removes it. |
| Move | Moves the hosts to another product. Their findings stay in their product. |
| Delete | Deletes the hosts — see below. |
Ticking every host on a page offers Select all N matching: the action then applies to every host the filters match, on every page. If the list changed since the page loaded, the action stops and asks you to refresh.
Deleting hosts
Delete — from the bar, or from a host's details — first shows what it affects: how many hosts and how many open findings are on them.

- Ignore these hosts in future scans is ticked by default: discovery and OSINT scans then skip them, so a host you removed does not come back with the next scan. Excluded hosts at the top of the page lists them, and Stop excluding lets scans add one again.
- Resolve their open findings closes the hosts' findings as Resolved. Without it the findings stay in Vulnerabilities, no longer linked to a host.
- Retire instead keeps a host that still runs, with its history and findings.
- Deleting more than five hosts asks you to type how many.
After deleting, Undo in the message at the bottom of the page brings the hosts back with their history, ports and links to findings, reopens findings the deletion resolved, and drops the exclusions it made.
To rebuild a product's inventory from a fresh scan, untick Ignore these hosts in future scans before you delete: otherwise the rescan skips every host you deleted.
Export
Export downloads the hosts in the current view as XLSX or JSON, with their ports, technologies, status, owner, business criticality, and open findings by severity.
Alerts
Email and Telegram alerts are sent when an infrastructure scan:
- finds a new host;
- rates a host higher or lower than the last assessment did. This is the severity an assessing scanner such as Nessus gives the host, not the risk computed from its findings.
Set them up in the Alerts card on the Integrations tab of the Teams page — see API keys for external systems for the email and Telegram fields.
The change alert is the useful one. A host you already knew about suddenly rated higher is usually the first sign of a configuration drift nobody announced.
Who can do what
| Action | Roles |
|---|---|
| See hosts, their details and findings; export; save views | Every role |
| Add asset, edit a host, bulk Status, Owner, Criticality, Tags and Move | Vulnerability manager, Operator, Team admin |
| Delete, Undo a deletion, Stop excluding | Operator, Team admin |
| Scan, Scan this host now | Operator, Team admin |
| Resolve their open findings (when deleting) | Also needs the right to change findings |
Roles are described in Teams and roles.
Last reviewed 2026-10-19