Security & trust
A security tool should be secure by design.
You are trusting us with the map of your environment. Here is how Lumen Edge is built to protect it, and how you stay in control of where it lives.
Data flow
What moves where
Sensors collect inside your network and push results out. Nothing on the platform side can reach into your network.
Your environment
EDR & XDR
Identity & directory
Cloud & MDM
SIEM, NDR & scanners

EDR & XDR
Identity & directory
Cloud & MDM
SIEM, NDR & scannersSubnets, VLANs, OT zones
Lumen Edge sensorActive & passive scans · runs integrations
Outbound HTTPS only
Lumen Edge platform · SaaS or on-prem
VerifyCleanIdentifyValidateSync
One correlated inventoryEndpoints · servers · network devices · cloud · users · licenses
DashboardsModulesReportsREST APITeams
Controls
How we protect your data
Architecture
- Dedicated instances
- Every SaaS customer gets their own deployment; there is no shared application tier between customers.
- Tenant isolation
- Within a deployment, each tenant’s assets live in a separate data store with a hard access boundary.
- Deployment choice
- Run as SaaS in your chosen region, on-prem, or air-gapped: the same product either way.
Sensors & network
- Outbound-only connectivity
- Sensors initiate every connection over HTTPS. No inbound firewall rules, proxy support included.
- Per-sensor credentials
- Sensors enroll with a short-lived token and receive their own long-lived API key, scoped to a single tenant.
- No stored integration secrets
- Credentials for your tools are kept in the console and delivered per task, not stored on the sensor host.
Access control
- Role-based access
- Global and tenant-level roles, with custom roles for least privilege.
- Multi-factor authentication
- Authenticator-app MFA that administrators can enforce per account.
- Abuse protection
- Login rate-limiting per account and per source address; accounts can be disabled without deleting history.
Data handling
- Encryption in transit
- All traffic between browsers, sensors and the platform uses TLS.
- Read-only integrations
- Connectors read from your tools; Lumen Edge does not write back to them.
- Auditability
- Scan history, approval decisions and module actions are recorded with who, what and when.
Responsible disclosure
Found a vulnerability? Email security@lumenedge.co with the details. We acknowledge reports promptly, keep you informed and do not pursue researchers acting in good faith.
FAQ
Security questions
Can we keep all asset data inside our own perimeter?
Yes. Deploy Lumen Edge on-prem or air-gapped and no inventory data leaves your environment. Pricing is the same as SaaS.
What permissions do integrations need?
Read-only API access is enough. We will share the minimum scopes for each integration you use so you can grant least privilege.
Do sensors need to be reachable from the internet?
No. Sensors only make outbound HTTPS connections to your console and never accept inbound connections from it.
Can you complete our security questionnaire?
Yes. Contact us and we will provide architecture documentation and answer your vendor-risk questionnaire.
Have security questions?
Our engineers will walk your security and network teams through the architecture in detail.
SaaS or on-prem · no endpoint agents · every module included