This article summarizes which device attributes can be enriched from our connector with Asimily, and the benefits of using that enriched data in policy.
Our integration with Asimily is intended to allow customers to use the most accurate device classifications in policy decisions. Asimily collects and analyzes device traffic in order to identify device details and attributes over time. Elisity leverages our own rapid device discovery mechanisms along with Asimily's analysis so that our customer’s devices get the most appropriate policies applied in a timely manner.
Device Matching
When a new device is discovered by any of Elisity's methods, Cloud Control Center queries Asimily using the following parameters, in order, until a match is found:
- IP + MAC Address
- MAC Address
Engage Elisity support to modify the behavior of the above query order.
Cloud Control Center does not query Asimily by IP address alone.
By default, Cloud Control Center syncs Asimily data every few minutes and re-enriches a device as soon as its Asimily record changes. Refresh a device on demand by clicking the refresh button next to the IdentityGraph tile for Asimily.
Devices that Elisity learned before the connector was configured are eligible for enrichment when their last seen timestamp falls within the connector's Enrichment Lookback Window (3 days by default).
The IdentityGraph tile for Asimily also shows Matched on (MAC+IP or MAC), Last Update and Status (Up to date or Stale). Elisity records these fields for each lookup; Asimily does not supply them.
Core Effective Attributes
Asimily maps the following attributes to Elisity Core Effective Attributes. IdentityGraph resolves each Core Effective Attribute separately by enrichment priority, so Asimily populates an attribute when no higher-priority source has a value for it:
| Asimily Attribute | Elisity Core Effective Attribute | Example Value |
|---|---|---|
| Hostname | Hostname | RADIOLOGY |
| Device Model | Model | 990001ESP |
| Device Type | Type | X-Ray |
| Manufacturer | Vendor | GE Healthcare |
| OS | Operating System | ThreadX |
Enrichment Attributes
The following table describes the attributes that Asimily provides to IdentityGraph for each discovered device:
| Attribute | Description | Example Value |
|---|---|---|
| Device ID | The unique device identifier in the Asimily platform | 1151381 |
| Risk Score | A numeric risk assessment score assigned by Asimily based on known vulnerabilities, configuration, and network exposure | 4 |
| Department | The hospital department, clinical area, or organizational unit where the device is deployed | P/T VERMILION |
| Facility | The facility or site name associated with the device in Asimily | Asimily Demo |
| Location | The physical location of the device | Victoria |
| OS Version | The operating system version reported by Asimily | 5.4.0 |
| Is Wireless | Indicates whether the device connects to the network wirelessly | false |
| Stores ePHI | Indicates whether the device stores electronic Protected Health Information | true |
| Transmit ePHI | Indicates whether the device transmits electronic Protected Health Information | true |
| Tags | Tags applied to the device in Asimily (supports multiple values) | critical-care |
| Managed By | The management entity or team responsible for the device | Biomed |
| Anomaly Present | Indicates whether Asimily has detected anomalous behavior from the device | true |
The specific attributes available depend on the data Asimily collects for each device. Not all attributes are populated for every device.
Next Steps
- Configure Dynamic Policy Groups using Asimily attributes to automate medical device segmentation. See Policy Groups.
- Adjust the enrichment priority order to define how Asimily attributes interact with other connectors. See IdentityGraph.