Lumen Edge
Lumen Edge builds and maintains a live inventory of everything on your attack surface — hosts, cloud workloads, identities and the services they expose — then keeps that inventory current from your existing security tooling and its own sensors.
It is a multi-tenant platform: one deployment serves many tenants, each with an isolated asset inventory, its own users and its own roles.
Start with the Quickstart to get a tenant collecting data, then read Core concepts to understand the model everything else in these docs assumes.
What the platform does
| Capability | What it means in practice |
|---|---|
| Discovery | Pulls assets from tools you already run — EDR, cloud providers, directory services — and from Lumen Edge sensors. |
| Correlation | Merges records describing the same real machine into one asset, so a host seen by three tools is one row, not three. |
| Enrichment | Layers ownership, custom fields and scan findings onto each asset. |
| Monitoring | Scheduled active scans and continuous passive sensing detect change and drift. |
| Reporting | Exports the inventory and findings on a schedule or on demand. |
How to read these docs
- Getting started — first tenant, first integration, first scan.
- Platform guide — one page per area of the console: assets, sensors, scanning, integrations and reports.
- Administration — tenants, users and the role model.
- API reference — wire conventions and authentication for the REST API that the console itself uses.
- Release notes — what changed in each release.
Versions
This documentation is versioned alongside the product. Use the version selector in the top-right to switch; you are currently reading the docs for the release shown there.
This site is the newly established documentation foundation. Pages marked with a TODO callout are structurally in place but still need product detail filled in.