Asset types
Every asset belongs to one of five types. Each type has its own list under Assets in the sidebar, its own default columns and charts, its own CSV template, and its own detail and creation layouts. The lists themselves work the same way for every type; see Assets.
| Type | Holds | Named by | Filled by |
|---|---|---|---|
| Endpoints | Servers, workstations, laptops, network and other devices | Names | Most integrations, by hand, CSV import |
| Subnets | Network ranges | Subnet Name | By hand, CSV import |
| Applications | Software and services, and the application register | Names | Application integrations, by hand, CSV import |
| Users | People (directory and identity accounts), not console accounts | FullName | Identity integrations, by hand, CSV import |
| Licenses | Software licences and entitlements | License Name | By hand, CSV import |
The type is fixed when an asset is created. Assets of different types cannot be merged.
Fields belong to the tenant, not to an asset type: every type can carry every field. The type decides which fields are on its default columns, CSV template and layouts, and which ones integrations fill. See Fields.
Endpoints
Endpoints are the machines and devices on your network. The list opens on Names, Type, OS, Private IP, Private Ip Subnet, Last Public IP, Criticality, Risk, Detected By and Last Seen.
The icon beside each endpoint follows its Type value (a server, an IP phone, a printer and so on), falling back to the generic endpoint icon.
Private Ip Subnet is calculated: it names the subnet asset whose range contains the endpoint's first private IP. It stays empty until a matching subnet exists.
The default detail layout has one General tab with Host fields, Time fields, Security fields and Ownership fields sections. Hosted Applications (calculated from applications that list the endpoint as a host) can be added to a layout from the field palette.
Integrations that create endpoints: Active scanner, Passive scanner, CrowdStrike, Windows Defender, Carbon Black, Elastic agent, Nessus agents, Tenable Security Center, Active Directory, Azure managed devices, Azure VMs, LinkShadow assets, LinkShadow DHCP, QRadar log sources and Vectra NDR.
Integrations that only add to existing endpoints: CrowdStrike asset owner, Elastic asset owner, CrowdStrike process events and Elastic aggregation query.
Subnets
Subnets describe your network ranges. No integration creates subnets; add them with Create asset or a CSV import. The CSV template has subnet_name, subnet_mask and static_subnet.
| Field | Origin | Meaning |
|---|---|---|
| Subnet Name | Standard | The subnet's name |
| Subnet Mask | Standard | The network in CIDR notation, for example 10.20.0.0/24. Required to be valid: a value that is not a network is refused |
| Static Subnet | Standard | Yes or no |
| Subnet Capacity | Cached | How many addresses the range holds, calculated from the mask |
| Subnet Min IP, Subnet Max Ip | Cached | The first and last address of the range |
| Subnet Assets Count | Scripted | How many assets have a private IP inside the range |
Subnets are what fill an endpoint's Private Ip Subnet. The Vectra NDR integration also reads them.
Applications
The Applications list is the tenant's application register: what software and services run in the estate, who answers for them, and what their loss would cost. Entries come from the application integrations, or are registered by hand or by CSV import.
The list opens on Names, Type, HW Vendor, HW Product, HW Version, the CrowdStrike applications host count and evidence (when that integration is present), Criticality, Risk, Detected By, First Seen and Last Seen. Each row shows the product's logo where the console has one.
The application register
The register fields are Standard fields every tenant has. No integration fills them; they are set by hand. The default detail layout groups them like this:
| Section | Fields |
|---|---|
| Overview | Names, Type, HW Vendor, HW Product, HW Version, Description, Business Function, Application URL, Hosting Model (On-premises, Private cloud, Public cloud, SaaS, Hybrid), Environment (Production, Staging, Test, Development, Disaster recovery), Lifecycle (Planned, In development, Active, Deprecated, Retired), Vendor Support End |
| Ownership | Asset Owner, Asset custodian, Department |
| Continuity | RTO (hours) (how long the application may be down), RPO (hours) (how much data, in hours, may be lost), Backup Policy |
| Classification & risk | Criticality, Risk, C, I, A, Data Classification (Public, Internal, Confidential, Restricted), Internet Facing, Processes Personal Data |
| Hosts | Application Hosts: the endpoints the application runs on |
| Dependencies | Depends On Applications, Depends On Hosts (hosts it needs beyond the ones it runs on, such as a database or file server), Used By |
| Discovery | Detected By, Tags, First Seen, Last Seen |
The default creation form asks for Names, Type, HW Vendor, HW Product, HW Version, Description, Business Function, Environment, Asset Owner, Asset custodian, Criticality and Data Classification.
Relationships are recorded once and read back from the other side, so the two sides always agree:
- Application Hosts is set on the application (by an inventory integration or by hand). The endpoint's Hosted Applications is calculated from it.
- Depends On Applications is set on the application that depends. The needed application's Used By is calculated from it.
Asset Owner and Asset custodian are Team fields: they point at people in the Users list.
Integrations that create applications: CrowdStrike applications and LinkShadow applications.
Users
Users are the people in your estate, as directory and identity systems know them. They are not the accounts that sign in to the Velum Edge console; those are managed under Tenants and users.
The list opens on FullName, Email, Title, Organization, User Department, Criticality, Risk, Detected By and Last Seen, with each person's picture (or a generic portrait) beside the name. The CSV template has user_full_name, user_email, user_organization, user_department and user_title.
Owned Assets on a user is calculated: it lists the endpoints whose Asset Owner names that user.
The default detail layout has one General tab. The CrowdStrike identities and LinkShadow users integrations each add a tab of their own when they are added to the tenant.
Integrations that create users: Active Directory users, LDAP users, Azure users, Atlassian users, CrowdStrike identities and LinkShadow users.
Licenses
Licenses record the software licences and entitlements you hold. No integration creates them; add them with Create asset or a CSV import.
| Field | Meaning |
|---|---|
| License Name | Name the licence is tracked under |
| License Vendor | Vendor it was bought from |
| License Product | Product it entitles |
| License Version | Product version it covers |
| License Key | Serial or activation key |
| License Type | How it is held, for example Perpetual, Subscription, OEM |
| License Status | Lifecycle state, for example Active, Expired, Suspended |
| Total Seats, Used Seats | Seats entitled and seats assigned |
| Start Date, Expiration Date | When the licence became valid and when it stops |
| Cost, Currency | What it cost, and in which currency |
License Key is left off the default columns so that a shared list address does not show keys; add it from Columns when you need it.
The License Optimization module does not read licence assets; it is documented on its own page.
See also
- Assets: the lists, search, import, export and merging
- Fields: the fields each type carries
- Layouts: arranging each type's asset page and create form
- Integrations: connecting the sources that fill these lists