Elisity supports simple API connectivity to Armis as a method to enrich IT, IoT, OT and IoMT device discovery and identity. This enables asset data from Armis to be imported into IdentityGraph for all assets that appear on your Elisity-secured network. This enhances the precision and effectiveness of asset classification.
Prerequisites
- Armis API URL (Unique to your instance)
-
Armis API Secret Key
Steps to Connect Armis
Step 1. Create a Armis API Secret Key by following the directions below or by reading the Armis API Guide. The access the API guide, log into the Armis console and navigate to Settings and selecting API Management under the Data Sources category.
a) Log into the Armis console and navigate to Settings > API Management.
b) Under the Secret API Key section select the Create button
c) Copy the Secret API Key and then select OK. Please keep it private, as it grants full access to the API.
Step 2. Log into Elisity Cloud Control Center and navigate to Settings > Connectors and select + Add Connector button.
Step 3. A list of tiles will slide out from the right side of the screen. Select configure on the Armis connector.
Step 4. Input the API URL (unique to your instance) and the API Secret Key you generated in the first step and select Submit.
Step 5 (optional). Configure advanced settings for the Armis connector.
The following chart provides details about each advanced setting
| Global Timer | The frequency at which Cloud Control Center queries Armis for updates. From 1 to 168 hours. Default is 24 hours. |
| Initial Delay | The delay in seconds before Cloud Control Center initiates the first query to Armis after initially discovering a new device. Default is 0 seconds |
| Connector Data Purging | When the Connector Data Purging feature is enabled, Cloud Control Center will purge all data learned about the device from this connector if the device is no longer found when querying the connected application. The time period between purge events is configurable and can be set between 1 and 90 days. The connector status will change from "Up to Date" to "Stale" if the device is no longer known by the connector but prior to the purge event. |
| IP Only Based Lookup | This option enables fallback behavior to query by IP address when a query by MAC address does not return a result. |
| Query Exclusion Rules | Limit the scope of Cloud Control Center queries by specifying Subnets and Virtual Edge Nodes, and by enabling or disabling the querying of devices with Random MAC addresses. |
Step 6. If all of the required connector values are correct, all checks will pass and the connector will be created.
After successful configuration, you should begin to see devices enriched by Armis in IdentityGraph.
Connector Status
The Connector status reflects its health and availability based on recent query performance. To ensure accuracy and reduce false positives, the status is determined using a rolling 15-minute evaluation window.
Connector Status Levels:
- Active: Normal operation with minimal query failures.
- Degraded: Increased query failures detected, but the connector is still operational.
- Inactive: The connector is unresponsive due to persistent failures.
Failures are defined as unsuccessful query responses, and the platform continuously monitors performance to update the status accordingly. These status changes are visible in the UI, event logs, and notifications pane for better troubleshooting. Email alerts can also be configured for connector status changes.
If the connector has not been queried within the evaluation window, the last known status is retained. This approach ensures reliable status reporting and helps identify potential issues before they impact operations.
Leveraging Armis with Elisity
When Elisity discovers a new asset on the network and the Armis connector is active, Cloud Control Center queries the Armis platform via API for additional device attributes in order to enrich IdentityGraph. This enriched data is displayed in the IdentityGraph tab of the device and can be leveraged in Policy Group definition.
If a device discovered by Elisity is also known in Armis, the Trust Attribute flag for "Known in Armis" will be set to Yes. You can then leverage this trust attribute as match criteria in Policy Group definition.
To learn more about how to leverage IdentityGraph Trust Attributes review the Leveraging Trust Attributes for Policy Group Definition article.
Sharing Asset Enforcement Status with Armis
Step 1. Ensure that the "Share Asset Enforcement Status" is selected under the connector configuration.
Step 2. Ensure that at least one asset in the Cloud Control Center has an Enforcement Status of "Enforced." For an asset to display "Enforced" status, it must be associated with a Policy Group that belongs to an active policy set containing at least one active policy for that Policy Group. Note that simulated policies do not contribute to the "Enforced" status.
Step 3. Log into Armis and navigate to Settings > Custom Properties.
Step 4. On the Custom Properties page select + Add Property.
Step 5. On the column selection window, choose + Custom Attribute.
Step 6. Fill out Property Name and Data Type exactly as shown below and select Add.
Step 7. Navigate to Assets > Devices (All Assets). Select column picker, search "elisity" and checkmark the ElisityEnforcement box to add it as a new column.
Step 8. Here, you'll see a checkmark in the Elisity Enforcement column for each device currently enforced by an Elisity policy. You can also view this information within the Device Inventory table located in the Custom Properties section.