Assets
The asset inventory is the centre of the platform. Every integration, sensor and scan exists to keep it accurate.
The asset list
Assets shows one row per correlated asset. The list supports:
- Free-text search across hostnames, addresses and identifiers.
- Filters on any indexed attribute, combined with AND semantics.
- Column layouts — saved per tenant, so a team can standardise on the columns it cares about.
A layout saved in a tenant is visible to everyone in that tenant. Name them for the job they do ("Patch review", "Cloud only") rather than after yourself.
Asset detail
Opening an asset shows everything known about it, grouped into:
| Section | Contents |
|---|---|
| Overview | Core attributes and current state |
| Sources | Every integration or sensor contributing to this asset, with last-seen timestamps |
| Ownership | Resolved owner and the source that resolved it |
| Custom fields | Tenant-defined values |
| Findings | Results from scans that touched this asset |
| History | Attribute changes over time |
The Sources section is the one to check first when an attribute looks wrong — it tells you which system asserted the value.
Correlation, merging and splitting
Lumen Edge correlates incoming records into existing assets automatically. When it is wrong, correct it by hand.
Merging
If the same machine appears as two assets, merge them. From the asset list, select both and choose Merge, or open one asset and use Merge with….
You choose which asset survives as the primary; the other's sources and history are folded into it.
The merged asset ceases to exist as a separate record. Its identifiers move to the surviving asset. Verify you have the right pair before confirming.
Splitting
If correlation collapsed two genuinely different machines into one asset, split it. The sources are separated back out and re-correlated independently.
Custom fields
Custom fields attach tenant-specific data the platform cannot discover — cost centre, criticality, compliance scope, ticket references.
Define them under Fields. Each field has a type, and typed fields are filterable and reportable like built-in attributes.
Document the available field types and whether fields can be populated by rule as well as by hand.
Bulk actions
Confirm which operations are available in bulk from the asset list (tagging, custom-field assignment, delete, export) and document the selection limits.
See also
- Sensors — discovering assets nothing else reports
- Integrations — where asset records come from
- Scanning — generating findings against these assets