Skip to content
Connection Guide

Connect Armis Centrix Without Breaking the Audit Trail

Use this guide to connect Armis Centrix or confirm the export-based path that fits your environment. Aurora keeps source, timestamps, ownership, and collection history attached so the first run becomes reusable proof instead of one-off setup work.

Connector Summary
Connection typeDirect connection
CategoryCloud Security
Checklist5 steps
Want help with rollout?
We'll confirm what can be automated, what stays export-based, and how to keep the first evidence record clean.

First-Run Checklist

Use this sequence to connect Armis Centrix and make sure the first collection lands cleanly.

  1. 1
    Register the integration in the Armis developer portal and capture vendor_id.
  2. 2
    Create a dedicated read-only Armis service account and generate its Secret Key.
  3. 3
    Configure tenant_url, vendor_id, client_id, requested_scopes, and optionally api_base_url, then store client_secret securely.
  4. 4
    Keep requested_scopes limited to the documented read scopes needed for sites and device custom-property configuration.
  5. 5
    Validate sites and device custom-property retrieval before enabling scheduled sync.

Credentials and Secrets

The keys, secrets, or tokens Aurora uses to authenticate and collect proof.

client_secret

Recommended Access

Aurora only asks for the minimum read access needed for collection and checks.

Access requirements depend on the collection mode and scope you choose.