Fragmented inventories
One server shows up as a hostname in EDR, an IP in the scanner and an instance ID in the cloud. Three records, three owners, no single truth.
Assentra is the asset lake of the Invinsense platform. It aggregates every endpoint, identity, API and OT device into one enriched, correlated asset context, keeps that context current, and shares it with exposure management, the SOC and GRC. Every team works from the same picture of your assets.
of security leaders have experienced incidents caused by unknown or unmanaged assets.
of organizations saw a cyberattack begin through an unknown, unmanaged or poorly managed internet-facing asset.
success rate for CMDB implementations, after 40 years of the concept, per Gartner.
of organizations rate their ability to prevent attacks via non-human identities as low or moderate.
Endpoint agents see devices with sensors. Scanners see what they can reach. Cloud consoles see their own accounts. Identity providers see accounts, and the CMDB sees what someone registered. Each is accurate within its own scope, but each sees only a slice. Assentra brings those pieces together into one correlated view of every asset, so together they tell the complete picture.
One server shows up as a hostname in EDR, an IP in the scanner and an instance ID in the cloud. Three records, three owners, no single truth.
Cloud workloads, containers, APIs and service accounts change outside procurement and change tickets. A manually maintained record starts drifting the day it is written.
Exposure, detection and compliance teams each build their own asset list. Priorities diverge, tickets get misrouted and nobody trusts the totals.
An alert arrives on a host no one can place. Who owns it? Is it production? Does it hold regulated data? Analysts rebuild that context by hand while the clock runs.
An inventory tells you what exists. Assentra tells you what each asset is, who it belongs to, what it is exposed to and why it matters to the business. It does this through one continuous loop, and every pass makes the context sharper.
Assentra collects asset observations from enterprise systems and from the Invinsense modules themselves: endpoint and server agents, cloud accounts, identity directories, network and OT sensors, scanners, application inventories and your existing CMDB. No single source is treated as the complete record.
One machine often has three names. Assentra resolves which observations describe the same entity, keeps the source evidence so every merge can be explained, and links the result to its vulnerabilities, identities, network paths and business services. These persistent relationships are what make the context useful.
Each asset gets the context that turns a record into a decision: owner, business service, criticality, environment, exposures, identities with access, data classification and compliance scope.
Illustrative sample data
Trusted asset context goes to every Invinsense module that acts on it, and each module sends what it learns back. Exposure, detection, response and compliance all reason from the same asset context.
Assets appear, move, change owners and disappear. Assentra continuously absorbs those changes, tracks when each fact was last observed and proposes new memories about your environment. A human approves each one before it enters the lake.
Illustrative sample data
Invinsense Assentra covers the whole estate, including the parts that never made it into a ticket, and not only the managed parts.
Laptops and workstations with OS, agent and patch state, so blind spots surface.
Physical and virtual servers, their roles and the services they host, on-prem and in cloud.
Accounts, workloads and services across providers, with posture and ownership.
Business and internal apps mapped to owners, dependencies and the assets they run on.
Internal and exposed APIs tied to the services and data behind them.
Images and short-lived workloads, their components and where they actually run.
Human and non-human accounts, privileges and the assets they can reach.
Devices, segments and structure, so you understand reachability and blast radius.
Operational and connected devices that agent-based inventories usually miss.
Where sensitive data lives, so classification and risk map to real systems.
Context flows out of Assentra to each SecOps module, and what each module learns flows back in. Click a module to see both directions.
Every day, Assentra and the Invinsense modules learn facts about your environment that no connector reports directly. Assentra turns those facts into memories, persistent context that every module can reuse.
Which systems carry revenue, regulated data or safety risk.
Where vulnerable software is actually installed and running.
Segments, trust boundaries and what can reach what.
Ingest and query ceilings, so automation stays within your platform's limits.
Who owns an asset, who uses it and which service accounts belong to it.
Maintenance windows and known-good patterns, scoped and time-bound.
Humans stay in control. Every proposed memory shows where it came from, the evidence and a before/after diff. An analyst approves or rejects it, and both decisions are logged. The result is defense tuned in detail to your business, and nothing changes without your sign-off.
A CMDB is a system of record for configuration items and services, kept current by process. That makes it valuable for change and service management. It was not designed to answer the questions SecOps asks under pressure: what is exposed, who can reach it, how much it matters and what changed since yesterday. Gartner puts the CMDB implementation success rate at just 29%.
| Dimension | Traditional CMDB | Assentra asset lake |
|---|---|---|
| Built for | IT service, change and configuration management (ITIL workflows). | Security operations: exposure, detection, response and compliance. |
| Data freshness | Depends on discovery jobs, change records and manual updates. Accuracy drifts between reconciliations. | Continuously updated from connected sources and Invinsense modules. Each fact carries its last-observed time. |
| Discovery & scope | Strongest for known, managed configuration items. Shadow, ephemeral and unmanaged assets are often missing. | Known and unknown, managed and unmanaged assets across all domains, reconciled across sources. |
| Relationships | Service and infrastructure dependency maps. | Persistent links across asset, vulnerability, identity, environment, data and business service. |
| Security context | Usually none natively. Exposure, threat and control state live in other tools. | Exposure, detections, control coverage, criticality and compliance status attached to the asset. |
| Identity & exposure linkage | Owner fields, sometimes stale after reorganizations. No view of which identities can reach an asset. | Human and non-human identities with access, plus validated exposures from UEMP. |
| Who maintains it | IT ops and configuration managers, through process and tickets. | Machine aggregation, with SecOps feedback and human approval for new context. |
| Learning & feedback loop | Learns only what is entered or discovered. Downstream findings rarely flow back. | Bidirectional: every module shares back, and the lake adds new memories over time. |
| Governance | Change advisory and CI ownership processes. | An approval flow for every proposed memory, with provenance, diff and audit trail. |
| Consumers | ITSM, service desk, change and asset/finance teams. | UEMP, ISOC Core, ISOC Extension, GRC and the analysts behind them. |
| Primary outcome | Reliable service delivery and controlled change. | Faster, better-informed security decisions on the assets that matter. |
High-severity alert: suspicious encoded script on host 10.24.8.17.
Same alert, same host, enriched in ISOC Core from the asset lake.
Illustrative scenario with fictional data and timings. It is not a measured customer outcome.
“Tell me what this host is before I spend an hour finding out.”
Alerts arrive without owner, criticality or business context, so every triage starts from zero.
Owner, service, criticality, exposures and identities attached to the alert's asset.
Duplicate and phantom assets are resolved before they create duplicate work.
Current relationships show what else the asset and its identities can reach.
Approved verdicts and expected behaviour carry over between analysts and shifts.
“Which of these ten thousand findings actually matter to us?”
Severity scores alone can't tell you whether vulnerable software is present, reachable or on a critical service.
Exposures ranked against criticality, reachability and data sensitivity from the lake.
Newly discovered assets flow into scope, so coverage gaps become visible.
Remediation tickets go to the team that owns the asset now, not last year.
Remediation status persists on the asset, linking each exposure to its fix.
“Prove which assets are in scope, and that they're controlled.”
Audit evidence is assembled from spreadsheets that are out of date before the audit starts.
Asset classifications and compliance scope update as the estate changes.
See which in-scope assets lack a required control, and which states are unknown.
Risk registers link to real systems, exposures and owners.
Every committed memory carries provenance and an approval record.
“Can I trust the numbers my teams bring me?”
Exposure, SOC and compliance teams report different asset counts, so the board gets three versions of the truth.
A shared asset context across exposure, detection, response and compliance.
Scoping and prioritization start from business-aware asset context.
AI-assisted and automated workflows act on reconciled, approved context.
Connects the tools you already own, with no extra silo.
Assentra is your context lake for CAASM — it establishes and maintains the relationships between assets, vulnerabilities, identities, environments and business context, so your tools reason about the attack surface the way an attacker sees it.
CAASM proved that security teams need a unified, queryable view of their cyber assets. Analysts now argue that the lasting value is the context layer beneath it: reconciled, fresh, traceable asset context that exposure, detection and automation can trust.
Software Analyst Cyber Research (SACR) finds that CAASM capabilities are being absorbed into exposure, cloud, identity and operations workflows, while the need for shared, current, traceable asset context keeps growing. Its key takeaways: records that disagree are a bigger problem than missing records, and asset accuracy is perishable, so freshness and provenance must be built in.
Assentra fits this model as the context layer native to the Invinsense platform: aggregated, correlated, enriched, and shared with the modules that act on it.
Gartner predicted that by 2026, organizations prioritizing security investments based on a continuous threat exposure management program would suffer two-thirds fewer breaches. Scoping and prioritization depend on knowing which assets matter.
“CISOs must continually refine their threat assessment practices … using a CTEM approach to evaluate more than just technology vulnerabilities.”Richard Addiscott, Gartner, Apr 2023
An analyst can pause when a record looks wrong. An automated workflow may act on the wrong entity or calculate blast radius from a relationship that no longer exists. AI-driven SecOps needs approved, current context underneath it.
Stale, conflicting or unavailable context should narrow an action, delay it, or request human review.Paraphrased from SACR, 2026
79% of organizations rate their ability to prevent attacks via non-human identities as low or moderate. CISA's BOD 23-01 requires U.S. federal agencies to perform automated asset discovery every 7 days. CIS Control 1 makes knowing every enterprise asset the first control.
CAASM: “an emerging technology area focused on enabling security teams to overcome asset visibility and exposure challenges.”Gartner, Hype Cycle for Security Operations 2022
No. Your CMDB remains the system of record for IT service and change management. Assentra is the security context layer: it ingests CMDB data as one source, reconciles it with what security tools actually observe, and adds exposure, identity and business context that a CMDB doesn't model. Many teams use Assentra findings to find CMDB drift and improve it.
Assentra provides the CAASM foundation: aggregation, correlation and a unified, queryable asset view. It then goes further in two ways. It is native to the Invinsense platform, so context flows to and from UEMP, ISOC Core, ISOC Extension and GRC without extra integration work. It also keeps a persistent, human-approved memory of your environment that grows over time.
Each proposed memory, such as a new critical asset, an ownership change or a SIEM rate limit, enters an approval flow with its source, supporting evidence and a before/after diff. An authorized analyst approves or rejects it. Only approved context is committed and shared with the modules, and every decision is recorded in an audit trail.
Assentra aggregates asset information from the Invinsense modules and from enterprise sources across endpoints, servers, cloud, applications, APIs, containers, identities, network, and other data assets. That includes security tools, cloud platforms, identity systems and IT asset systems such as your CMDB. Ask us for the current connector list for your stack.
Assentra is a module of the Invinsense platform and adds the most value when it shares context across several modules. Talk to us about the right starting point for your environment.
Assentra correlates observations that describe the same asset and keeps the source evidence behind each attribute, including when it was last observed. Conflicts stay visible rather than being silently overwritten, so analysts can see why a value was chosen and correct it through the approval flow.
Discover complete cybersecurity expertise you can trust and prove you made the right choice!
.svg){kind=small}