> For the complete documentation index, see [llms.txt](https://docs.dispel.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dispel.com/integrate-and-administer/integrations/asset-discovery/armis.md).

# Armis

Connect your Armis tenant to pull discovered managed and unmanaged assets into Dispel, map Armis sites to Wickets, and keep device data and vulnerability findings in sync.

## Overview

The Armis integration lets Dispel pull the assets Armis has discovered across your environment — managed and unmanaged alike — and bring them in as Dispel devices. You connect to your Armis tenant once, map each Armis site to a Dispel facility and Wicket, and Dispel imports the matching devices and keeps them current on a recurring sync.

Armis is a cloud-native **asset-discovery** integration. There is no on-premise appliance — Dispel connects to your Armis tenant in the cloud and only ever reads from it.

#### What Dispel imports

* Discovered assets (name, IP address, MAC address, make/model, operating system, device type) as Dispel devices.
* Observed network protocols and ports for each asset.
* A link back to the asset in Armis, stored on the device.
* **Vulnerability findings** for each imported device, refreshed on every sync.

{% hint style="info" %}
**Where to find it.** Sign in as an organization administrator and open **Settings → Integrations**. Armis appears in the **Asset Discovery / Network Visibility** section. Click **Connect** on the Armis card to begin.
{% endhint %}

## Before you begin

You'll need the following from your Armis tenant:

* An **API key** (secret key), created in your Armis console under your API settings.
* Your **Armis Tenant URL** — for example `https://acme.armis.com`.

{% hint style="warning" %}
**Allowlist Dispel's IP.** When you open the connection form, Dispel shows a **Whitelist IP** value. If your Armis tenant restricts API access by source IP, add this address to the allowlist so Dispel can connect.
{% endhint %}

## Connecting Armis

1. Go to **Settings → Integrations** and click **Connect** on the Armis card.
2. Optionally set a **Display Name** to tell this integration apart from others (you can connect more than one Armis tenant).
3. Fill in the connection fields:

| Field                | Type       | Notes                                                                |
| -------------------- | ---------- | -------------------------------------------------------------------- |
| **Armis Tenant URL** | Config     | The base URL of your Armis tenant (e.g. `https://acme.armis.com`).   |
| **API Key**          | Credential | Your Armis API (secret) key. Stored encrypted and never shown again. |

4. Click **Test Connection** to confirm Dispel can authenticate against Armis. Fix any reported error before saving.
5. Click **Save**. Dispel saves the integration and immediately runs the initial sync to discover your Armis sites.

{% hint style="info" %}
**Your credentials are encrypted.** The API key is encrypted at rest and is never displayed again after you save. When editing later, leave the credential field blank to keep the stored value.
{% endhint %}

## Mapping sites to Wickets

Once the initial sync finishes, open the integration to find the **Site Mapping** section. Armis exposes the sites configured in your tenant, and this is where you decide which ones become Dispel devices and where they land.

> Map each vendor site to a Dispel facility and wicket. Devices from mapped sites will be synced into Dispel.

For each site you want to import:

1. Pick a **Facility**.
2. Pick a **Wicket**. If the facility has only one Wicket, Dispel selects it for you.
3. Click **Save Mappings & Import**.

Dispel works through each mapped site — you'll see per-site progress move from waiting, to fetching, to syncing, to complete — and then reports how many devices were imported (for example, **"12 devices imported"** or a breakdown of new versus already-imported devices). Imported devices appear in the mapped Wicket alongside any devices you've added manually.

## Keeping your inventory current

* Dispel **re-syncs automatically** on a recurring schedule, so newly discovered assets and changed details are picked up without any action from you.
* To pull the latest inventory immediately, open the integration and choose **Refresh**.
* To change connection details or rotate credentials, edit the integration and use **Save & Sync**. Leave the credential field blank to keep the current key.

## Vulnerability findings

Armis reports known vulnerabilities for the assets it monitors. After each successful sync, Dispel pulls the vulnerability findings for your imported devices and attaches them to those devices, so you can see a device's known issues without leaving Dispel. Findings are refreshed every sync, and resolved findings drop off automatically.

## Connection status

Each integration shows a status so you always know where it stands:

| Status              | Meaning                                                 |
| ------------------- | ------------------------------------------------------- |
| **Not Initialized** | Saved, but the first sync hasn't run yet.               |
| **Initializing**    | Running the first sync and discovering sites.           |
| **Ready**           | Connected and synced; mappings are applied.             |
| **Needs Refresh**   | New vendor data is available; run a refresh to pull it. |
| **Refreshing**      | A sync is in progress.                                  |
| **Pending Changes** | Mapping changes are saved but not yet applied.          |
| **Applying**        | Importing devices for your saved mappings.              |
| **Failed**          | The last operation failed — see the error guidance.     |

A separate **health badge** (Connected, Degraded, Unreachable) reflects whether Dispel can currently reach the Armis API.

## Troubleshooting

If a sync or test connection fails, Dispel classifies the error and suggests a fix:

| Error                     | What it usually means and how to fix it                                                                                       |
| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------- |
| **Authentication Failed** | The API key was rejected. The key may have been rotated, expired, or revoked — generate a new one and update the integration. |
| **Endpoint Unreachable**  | Dispel couldn't reach the API. Verify the tenant URL and that Dispel's IP is allowlisted if your tenant restricts API access. |
| **Connection Timed Out**  | Armis took too long to respond — usually transient network latency.                                                           |
| **Rate Limited**          | Armis throttled requests. The next scheduled sync should succeed.                                                             |
| **Configuration Error**   | The tenant URL looks wrong. Re-check that it points at your Armis tenant.                                                     |

## Frequently asked questions

<details>

<summary>Can I connect more than one Armis tenant?</summary>

Yes. Armis supports multiple integrations, so you can connect several tenants side by side. Give each a distinct **Display Name** to tell them apart.

</details>

<details>

<summary>Is there an on-premise option for Armis?</summary>

No. Armis is a cloud platform, so Dispel always connects to your Armis tenant over the internet. There is no appliance to point at.

</details>

<details>

<summary>Does connecting Armis change anything in my Armis tenant?</summary>

No. Dispel only reads from Armis. It never creates, modifies, or deletes data on the Armis side.

</details>

<details>

<summary>How quickly do new assets appear?</summary>

New assets show up on the next sync — automatically on the recurring schedule, or immediately if you choose **Refresh**.

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.dispel.com/integrate-and-administer/integrations/asset-discovery/armis.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.