Enhance Your Security and IT Stacks Without Replacing Them

Elisity integrations are API connections that enrich the Elisity IdentityGraph with context from systems you already run. You enter the partner platform’s API credentials in the Elisity Cloud Control Center, and that platform’s device, user, and risk data begins flowing into IdentityGraph, where it is resolved against every other attribute Elisity holds for the same identity. Policy groups then reference those attributes (device type, manufacturer, firmware version, endpoint posture, business owner) instead of IP addresses or VLANs. Elisity enforces the resulting least-privilege policy through the network infrastructure you already own, with no new hardware and no endpoint agents required.

Each integration needs three things: network reachability between the Elisity Cloud Control Center and the partner platform’s API endpoint, a service account or API key with read permissions, and the partner tenant or appliance address. Elisity reads from these platforms and does not write configuration back into them, so the credentials you provision can be scoped read-only. Step-by-step connection guides for every supported platform are published at support.elisity.com. Most teams complete the credential exchange and watch partner data appear in IdentityGraph inside a single working session.

No. Elisity is a policy and enforcement layer, not a replacement for asset intelligence, endpoint detection, OT security, or IT service management platforms. Claroty, Armis, Nozomi Networks, ORDR, and Dragos remain your discovery and threat detection systems. CrowdStrike and SentinelOne remain your endpoint detection and response systems. ServiceNow and NetBox Labs remain your systems of record. Elisity consumes what those platforms already know and converts it into least-privilege policy enforced across your existing network infrastructure, which raises the return on the tools you have already bought.

Yes. IdentityGraph merges attributes from multiple sources onto a single resolved identity for each device and user. If Claroty classifies an infusion pump, CrowdStrike reports the posture of the workstation that programs it, and ServiceNow supplies the owning department and criticality rating, all three attribute sets attach to the same identities. Policy can then reference any combination of them. Adding a second or third source does not create duplicate records or competing policy, it increases the confidence and the granularity of the classifications Elisity already holds.

The API connection itself takes minutes. You add the partner platform in the Elisity Cloud Control Center, enter the credentials, and confirm the connection. Partner data begins enriching IdentityGraph immediately, and the first full inventory synchronization typically completes within the hour, depending on how many devices the partner platform tracks. From there, most teams move from connected integration to enforced microsegmentation policy in weeks, because policy groups are built from attributes that already exist rather than from a manual inventory or a VLAN redesign.

Elisity supports five categories. Asset intelligence and device visibility (Claroty, Armis, Nozomi Networks, ORDR) supplies device classification across IT, OT, IoT, and IoMT. Endpoint detection and response (CrowdStrike, SentinelOne) supplies posture and risk signals for managed endpoints. OT and industrial security (Dragos) supplies vulnerability and threat context for control system assets. IT service management and source of truth (ServiceNow CMDB, NetBox Labs) supplies ownership, criticality, and infrastructure records. Network enforcement (Palo Alto Networks) extends Elisity policy to firewall enforcement points.

No. Elisity is agentless. It learns about devices through the integrations listed on this page, through network telemetry, and through directory sources including Active Directory, and it enforces policy across the network infrastructure you already own rather than on the device itself. That matters for equipment that cannot accept software: legacy programmable logic controllers, imaging systems, building management controllers, and medical devices under vendor or safety certification restrictions. Where an endpoint agent such as CrowdStrike Falcon or SentinelOne Singularity is already deployed, Elisity reads its posture through the API instead of adding a second agent.

An integration is not required to deploy Elisity. IdentityGraph builds device and user identities from network telemetry, directory sources including Active Directory, and its own classification engine, so microsegmentation can be deployed with no third-party feed connected. Integrations make classification faster and more specific, which matters most in environments with large populations of unmanaged OT, IoT, or IoMT devices. Most teams start with the platforms they already own and add sources over time as coverage expands.