Assets
The asset inventory is the centre of the platform. Integrations, sensors and scans all exist to keep it accurate, and every module and report reads from it.
The inventory is split into five asset types: Endpoints, Subnets, Applications, Users and Licenses. Each has its own list under Assets in the sidebar, and every list works the same way. What an asset can hold is defined by the tenant's fields, and how its page is arranged by the tenant's layouts.
Permissions
| To do this | You need |
|---|---|
| Open the asset lists and asset pages | Assets Read |
| Create, edit, import, bulk edit, merge or delete assets, or download the CSV template | Assets Write |
| Export a list | Reports Write (the export is a report job), and Reports Read to collect the file |
| See the tenant's own layout on an asset page | Layouts Read (without it the page lists every field on one tab) |
The asset lists
Each list shows the tenant's assets of one type, one row per asset. The first column is the asset's name (Names for endpoints and applications, Subnet Name, FullName for users, License Name) and is always shown. Click a row to open the asset page.
The header carries the list's actions: Show charts / Hide charts, Export, Import CSV and Create asset.
Everything you change about the view lives in the page address: the search, the filter chips, the page, the page size and the visible columns. A filtered view therefore survives a reload, the browser's Back button undoes a filter, and you can share the exact view by copying the address.
Pages hold 10, 25 or 50 rows. Search and filters run on the server, so they always cover the whole inventory, not only the page in front of you.
Columns
Open Columns above the table to show, hide and reorder columns. It offers every field in the tenant's dictionary, grouped by where the field comes from (Core, Standard, Custom, Scripted, Cached, then one group per integration), with a search box.
Each list opens with a default set of columns chosen for its asset type. Your
choice is written to the page address (?cols=); it is not saved for the
tenant or for other users. To keep a view, bookmark or share its address.
Click a column heading to see the ten most common values of that field across
everything the list currently matches, each with its share. Each value has a
+ to filter to it and a - to filter it out. Only fields where a count says
something offer this.
Hover a cell for quick actions: Filter for the value, Filter out the value, or Copy it. On an empty cell the filters become "the field has no value" and "the field has a value", so finding endpoints without an owner is one click.
Search
The search box takes a query language. As you type, it suggests field keys, then the most common values of the field you named (with counts), and, once you have typed a few characters, searches you ran before in this browser. The Search syntax button next to the box opens a panel of examples; picking an example puts it in the search box.
Fields and values
| Query | Finds |
|---|---|
os:Ubuntu | Assets whose field holds the value |
os:"Windows 11" | A value with spaces, in quotes |
names:*SRV* | * matches any characters, ? exactly one |
server | A word on its own searches every field |
Name a field by its key (shown in the suggestions and on the Fields screen), not by its display name.
Combining
| Query | Finds |
|---|---|
os:Ubuntu AND type:Server | Both must match |
type:Server OR type:Endpoint | Either may match |
NOT type:Server | Leaves matches out; -type:Server does the same |
os:(Ubuntu OR "Windows 11") | Several values of one field |
(os:Ubuntu OR os:Debian) AND type:Server | Brackets group conditions |
Ranges and presence
| Query | Finds |
|---|---|
last_seen:[now-30d TO now] | Within a range, both ends included |
last_seen:<now-90d | Compare with >, >=, < or <= |
_exists_:asset_owner | The field has any value |
NOT _exists_:asset_owner | The field is empty |
private_ip:"10.0.0.0/8" | An address within a subnet |
Exact matching
| Query | Finds |
|---|---|
os.text:windows | Ignores case and matches words within the value |
names:/[A-Z]+-[0-9]+/ | A regular expression over the whole value |
os:windows does not find Windows. Use the .text form of the field
(os.text:windows) or the exact spelling.
A few combined examples:
type:Server AND NOT _exists_:asset_owner
os_vendor:Microsoft AND last_seen:<now-30d
names:*SQL* AND private_ip:"10.20.0.0/16"
Filters
Next to the search, Add filter builds a condition from a field, an operator and a value. The operators are Is, Is not, GT, GTE, LT, LTE, Matches, Exists and Does not exist; the ones offered depend on the field's type.
Each filter becomes a chip. A chip can be edited, inverted (shown as NOT), switched off with Disable and on again with Enable, or removed. Filters, cell actions, column breakdowns and chart clicks all produce the same chips, so a filter made one way can be adjusted another.
The chart strip
Above each list is a strip of small charts, drawn over exactly what the table lists: the same search and the same filters. The defaults are:
| List | Charts |
|---|---|
| Endpoints | OS vendor, Detected by, Type, Criticality |
| Subnets | Mask, Static subnet, Detected by |
| Applications | Vendor, Product, Type, Criticality |
| Users | Organization, Department, Title, Criticality |
| Licenses | Vendor, Product, License type, Status |
Click a slice or bar for Filter to this or Filter this out; either adds a filter chip, so the table and the other charts narrow with it.
Click a chart's title to change it: pick Donut, Bars or Columns under Chart, and another field under Group by. A changed chart is marked Changed, and Reset to default puts it back. These choices, and whether the strip is shown or hidden, are remembered in your browser only.
The asset page
The asset page shows one asset. Its header has the name, an icon (a person's picture for users, the product logo for applications where one is available) and badges for Type, Criticality and Risk. An endpoint nobody has classified shows Unknown criticality.
Tabs and sections
The body is the tenant's detail layout for that asset type: tabs, each holding
sections placed on a grid, each section listing fields. The tab names, the
sections and the fields in them are all set under
Settings → Layouts, so two tenants can show the same
asset type very differently. The open tab is part of the address (?tab=), so
a link can point at a specific tab.
A field the layout names but the tenant no longer has is skipped. A section can be set to hide fields with no value. If the tenant has no detail layout, or you lack Layouts Read, the page shows a single General tab with an All fields section listing every field the asset holds a value for.
Some integrations add a tab of their own to the detail layout when they are added to a tenant; see Layouts.
Editing a value
Fields you can change show an edit button when you hover them. Only Standard and Custom fields can be edited by hand; System, Integration, Scripted and Cached fields are read-only (see Fields). In edit mode a multi-value field has one input per value and Add value; Save writes the change and Cancel discards it. Emptying every input clears the field.
A File field is not typed into: upload or remove its files directly on the asset page, within the size and extension limits the field allows.
A Standard field that an integration also writes (such as os) can be edited
by hand, but a later scan of that integration can write its own value again.
Actions
Actions in the header offers Merge asset (see Merging) and Delete asset.
Creating an asset
Create asset on a list opens a form for that asset type. The fields it asks for, and their order, come from the tenant's creation layout for the type. The asset's name field is always asked for first. Each field's type decides its control, Mandatory fields must be filled in, and multi-value fields accept several values.
Only fields a value can be typed into appear on the form: no File fields (files are uploaded once the asset exists) and no read-only fields. If the creation layout cannot be read or names no usable fields, the form falls back to the list's default columns.
A subnet's Subnet Mask must be a network in CIDR notation, for example
10.20.0.0/24; the subnet's capacity and first and last address are calculated
from it.
After Create asset, the console opens the new asset's page.
Importing from CSV
Import CSV adds new assets of the list's type from a CSV file.
- In the Upload CSV dialog, choose Download template. The template's header row holds the field keys for that asset type, followed by every Custom field of the tenant.
- Fill in one row per asset. Leave cells empty for values you do not have.
- Drop the file into the dialog and choose Import.
| Rule | Detail |
|---|---|
| File type | .csv only |
| File size | Up to 10 MB by default; a deployment can change this |
| Rows | Up to 1,000 data rows per file by default; a deployment can change this. Split larger files |
| Header | The first row names the fields by key |
| Unknown or read-only columns | Refused: every column must be a field the tenant has whose value can be set by hand |
| File fields | Must be left empty; upload files on the asset page afterwards |
| MAC and Private IP | May hold several values separated by commas |
| Integration fields | Name the integration instance by its public id |
| Asset reference fields | Checked: the referenced assets must exist |
Every row is checked before anything is written. If any row is refused, the
dialog shows the line and the reason (for example Line 14: ... Nothing was imported) and no asset is created. When every row passes, all rows are written
together.
In rare cases the storage layer can refuse some rows after the checks have
passed. The dialog then reports how many of the rows were imported
(Only N of M assets were imported), and the rows that were written stay.
The import does not report counts on success; the dialog closes with "Assets imported from" the file name, and the list refreshes.
Exporting a list
Export writes every asset the current view matches (the same search and filters as the table, across all pages) to a CSV file, with the columns the table currently shows, in the same order. The header row uses each field's display name.
The export runs as a report job. A message names the file
(<type>-export-<date and time>.csv); collect it from
Reports once it completes.
Cells that a spreadsheet would treat as a formula (values starting with =,
+, - or @, other than plain numbers) are written with a leading ', so
they open as text.
Bulk edit and bulk delete
Tick rows in the table to act on several assets at once. Ticking the header box selects the page; when there are more matches than the page, Select all N selects every asset the current search and filters match, on every page.
Bulk edit
Bulk edit sets one field to one value on every selected asset. Pick the Field, then the New value; the control matches the field's type. Only fields whose value can be set by hand are offered.
Leaving the value empty clears the field on every selected asset, after a confirmation; the old values are not kept anywhere. A Mandatory field cannot be cleared.
- Ticked rows are updated one asset at a time. If some are refused, the dialog stays open and lists which.
- Select all N is carried out by the search on the server. The result says how many assets took the value, how many already had it, and how many changed while the edit ran and were left as they were (apply the edit again to reach those).
Bulk delete
Delete assets removes the selected assets from the tenant after a confirmation. With Select all N, every asset matching the current search and filters is deleted, not only the page. Assets that an integration changed while the deletion ran are kept, and the message says how many; delete again to remove them.
Deleting an asset, alone or in bulk, removes only the asset itself. Its change history and scan findings are kept. An integration that still reports the asset may create it again on its next run, so change the integration's scope or action settings first if the asset should stay gone.
Limits
A bulk edit or delete that names assets by id (ticked rows, or the API) can name at most 1,000 assets by default; a deployment can change this. Select all N works by query and is not bound by that number.
Merging
When the same machine, person or application appears as two assets, merge them. Merging is done from the asset page that should survive: Actions → Merge asset.
- In Asset to merge into this one, pick the duplicate. Only assets of the same type in the same tenant can be merged.
- The dialog lays out every field side by side, this asset (Kept) against
the other (Deleted), grouped as:
- Needs a decision: both hold different values.
- Only one asset has a value: kept as it is unless you pick the empty side.
- Both assets agree: left untouched.
- Empty in both: hidden unless you tick Show empty fields.
- For each field, click the side to keep, or the button between them to keep both. Keeping both is only possible for multi-value fields. Resolve conflicts: with Keep this, Keep both or Keep other applies one choice to every conflict. By default a multi-value field keeps both and a single-value field keeps this asset's value.
- Choose Merge assets.
Scripted and Cached fields are not offered; the platform recalculates them on the merged asset.
What points at the deleted asset (owners, linked assets, vulnerabilities, scan changes not yet applied) is moved to the surviving asset.
The other asset is deleted when the merge runs, and there is no way to split a merged asset again. Check the pair and the field choices before you confirm.
Change history
Changes that scans make to assets are recorded as change entries on the scan run that produced them. Review them on the run's Results tab; see Reviewing a scan. Those records are kept when an asset is deleted or merged away.
The asset page has no history tab, and edits made by hand (on the asset page, by bulk edit or by import) are not recorded as change entries in the current code. Confirm whether a per-asset history view is planned before documenting one.
See also
- Asset types: what each list holds and what fills it
- Fields: field origins, types and custom fields
- Layouts: arranging the asset page and the create form
- Wizard: finding duplicates and naming problems
- Integrations: where asset records come from
- Scanning: how integrations run and produce changes