Axonius
Asset Management- Overview
- Setup
- Data & mappings
- Operations & API
- Changelog
Data retrieved from Axonius
| Connector Object | Required | Maps to Data Model |
|---|---|---|
| Device | Yes | Host |
| User | Yes | Person |
Model relationships
For detailed steps on how to view the data retrieved from Axonius in the Brinqa Platform, see How to view your data.
Connection settings
When setting up a data integration, select Axonius from the Connector dropdown and provide the following:
| Setting | Required | Default | Description |
|---|---|---|---|
| Axonius URL | Yes | — | Axonius instance URL |
| API key | Yes | — | Axonius API key |
| API secret | Yes | — | Axonius API secret |
| User custom properties | No | — | Comma delimited list of case-insensitive custom property names to promote as attributes on the User. |
| Device custom properties | No | — | Comma delimited list of case-insensitive custom property names to promote as attributes on the Device. |
| Page size | No | 100 | Maximum number of records to get per API request |
| Parallel requests | No | min(4, availableProcessors) | Maximum number of parallel API requests |
| Maximum retries | No | 10 | The maximum number of retry attempts before giving up a request |
| SSL / TLS | No | false | Skip certificate verification |
How to obtain Axonius credentials
Generate Axonius API keys
For the Axonius connector to use the Axonius API, you must provide API keys. To generate API keys, follow these steps:
Info: Before you begin, ensure that the the Axonius account is assigned at least the Viewer role and has the API access enabled permission. This role and permission are necessary to retrieve device data from the Axonius API, as it grants read-only access. For additional information, see the Axonius documentation on managing roles and enabling API access.
-
Log in to your organization's Axonius platform.
-
On the bottom left-hand side of the page, click the profile photo, and then click User Settings.
-
Click the API Key tab.
Your existing API key and API secret display. Click Reset Key if you want to replace your existing keys. Copy the API key and API secret values into the respective integration configuration fields.
Note: If you do not have permissions to create an Axonius API key, contact your Axonius administrator. For additional information, see Axonius documentation.
Attribute mappings
Expand the sections below to view the mappings between the source and the Brinqa data model attributes:
Device
| Source Field Name | SDM Attribute |
|---|---|
adapters | adapters |
| adapters + labels | TAGS |
| Derived | CATEGORIES |
| Derived from FQDN | PRIVATE_DNS_NAMES |
| Derived from FQDN | PUBLIC_DNS_NAMES |
| Derived from IPs | PRIVATE_IP_ADDRESSES |
| Derived from IPs | PUBLIC_IP_ADDRESSES |
| Generated | STATUS |
| Generated | LAST_CAPTURED |
| internal_axon_id | UID |
| internal_axon_id | internal_axon_id |
labels | labels |
specific_data.data.boot_time_preferred | BOOT_TIME |
specific_data.data.cloud_id | INSTANCE_ID |
specific_data.data.cloud_id | CLOUD_ID |
specific_data.data.device_manufacturer_preferred | MANUFACTURER |
specific_data.data.domain_preferred | DOMAIN |
specific_data.data.first_seen | FIRST_SEEN |
specific_data.data.hostname_fqdn_preferred | DNS_NAMES |
specific_data.data.hostname_fqdn_preferred | FQDN |
specific_data.data.hostname_preferred | HOSTNAMES |
specific_data.data.hostname_preferred | HOSTNAME |
specific_data.data.is_virtual_preferred | IS_VIRTUAL |
specific_data.data.is_windows_server_preferred | IS_WINDOWS_SERVER |
specific_data.data.last_seen | LAST_SEEN |
specific_data.data.name_preferred | DEVICE_NAME |
specific_data.data.name_preferred / hostname_preferred / hostname_fqdn_preferred | NAME |
specific_data.data.network_interfaces.ips_preferred | IP_ADDRESSES |
specific_data.data.network_interfaces.ips_v4_preferred | IPV4_ADDRESSES |
specific_data.data.network_interfaces.ips_v6_preferred | IPV6_ADDRESSES |
specific_data.data.network_interfaces.mac_preferred | MAC_ADDRESSES |
specific_data.data.os.build_preferred | OS_BUILD |
specific_data.data.os.distribution_preferred | OS_DISTRIBUTION |
specific_data.data.os.os_str_preferred | DESCRIPTION |
specific_data.data.os.os_str_preferred | OPERATING_SYSTEM |
specific_data.data.os.type_preferred | OS_TYPE |
specific_data.data.serial_number_preferred | SERIAL_NUMBER |
specific_data.data.uptime_preferred | UPTIME |
specific_data.data.user_preferred | LAST_LOGIN_USER |
User
| Source Field Name | SDM Attribute |
|---|---|
adapters | adapters |
| adapters + labels | TAGS |
| Derived | CATEGORIES |
| Generated | STATUS |
| Generated | LAST_CAPTURED |
| internal_axon_id | UID |
| internal_axon_id | internal_axon_id |
labels | labels |
specific_data.data.account_disabled | ACCOUNT_DISABLED |
specific_data.data.account_expired | ACCOUNT_EXPIRED |
specific_data.data.account_expires | ACCOUNT_EXPIRES |
specific_data.data.account_state | ACCOUNT_STATE |
specific_data.data.cloud_provider | CLOUD_PROVIDER |
specific_data.data.days_until_password_expiration | DAYS_UNTIL_PASSWORD_EXPIRATION |
specific_data.data.description | DESCRIPTION |
specific_data.data.description | USER_DESCRIPTION |
specific_data.data.display_name | NAME |
specific_data.data.display_name | DISPLAY_NAME |
specific_data.data.domain | DOMAIN |
specific_data.data.employee_id | EMPLOYEE_ID |
specific_data.data.employee_type | EMPLOYEE_TYPE |
specific_data.data.first_name | FIRST_NAME |
specific_data.data.first_name | USER_FIRST_NAME |
specific_data.data.first_seen | FIRST_SEEN |
specific_data.data.id | USER_ID |
specific_data.data.is_admin | IS_ADMIN |
specific_data.data.is_delegated_admin | IS_DELEGATED_ADMIN |
specific_data.data.is_local | IS_LOCAL |
specific_data.data.is_locked | IS_LOCKED |
specific_data.data.is_managed_by_application | IS_MANAGED_BY_APPLICATION |
specific_data.data.is_managed_by_sso | IS_MANAGED_BY_SSO |
specific_data.data.is_mfa_enforced | IS_MFA_ENFORCED |
specific_data.data.is_mfa_enrolled | IS_MFA_ENROLLED |
specific_data.data.is_orphaned | IS_ORPHANED |
specific_data.data.is_saas_user | IS_SAAS_USER |
specific_data.data.last_logon | LAST_LOGIN |
specific_data.data.last_name | LAST_NAME |
specific_data.data.last_name | USER_LAST_NAME |
specific_data.data.last_password_change | LAST_PASSWORD_CHANGE |
specific_data.data.last_seen | LAST_SEEN |
specific_data.data.logon_count | LOGON_COUNT |
specific_data.data.mail | EMAILS |
specific_data.data.organizational_unit | ORGANIZATIONAL_UNIT |
specific_data.data.password_expiration_date | PASSWORD_EXPIRATION_DATE |
specific_data.data.password_never_expires | PASSWORD_NEVER_EXPIRES |
specific_data.data.password_not_required | PASSWORD_NOT_REQUIRED |
specific_data.data.user_city | USER_CITY |
specific_data.data.user_created | USER_CREATED |
specific_data.data.user_sid | USER_SID |
specific_data.data.user_status | USER_STATUS |
specific_data.data.user_telephone_number | PHONE_NUMBERS |
specific_data.data.user_type | USER_TYPE |
specific_data.data.username | USERNAME |
Operations & API
Expand each connector object to see its operation options, delta-sync behavior, and the API it uses. See connector operation options for how to apply operation options (keys and values are case-sensitive).
Device
Operation options
This object does not support any operation options.
Delta sync
The connector README does not document sync behavior for this object.
API
- Type: REST · Endpoint:
POST /api/devices
User
Operation options
This object does not support any operation options.
Delta sync
The connector README does not document sync behavior for this object.
API
- Type: REST · Endpoint:
POST /api/users
Changelog
The Axonius connector has undergone the following changes:
| Version | Description | Migration Steps |
|---|---|---|
| 3.0.6 | Improvements - Device manufacturer, last login user, and operating system attributes now map to standard Brinqa UDM attributes - User cloud provider and last login attributes now map to standard Brinqa UDM attributes Bug Fixes - Removed duplicate attribute mapping where employee_id was emitted as both EMPLOYEE_NUMBER (Integer) and EMPLOYEE_ID (String) | • Device: LAST_USED_USER renamed to LAST_LOGIN_USER, MANUFACTURER remapped to standard attribute — Action: purge and re-sync • Device: Timestamp fields ( BOOT_TIME) changed from Long to Instant — Action: purge and re-sync • User: LAST_LOGON renamed to LAST_LOGIN, CLOUD_PROVIDER remapped to standard attribute, EMPLOYEE_NUMBER removed (data now captured by EMPLOYEE_ID) — Action: purge and re-sync • User: Timestamp fields ( LAST_LOGIN, LAST_PASSWORD_CHANGE, PASSWORD_EXPIRATION_DATE, USER_CREATED) changed from Long to Instant — Action: purge and re-sync |
| 3.0.5 | New Features - Added User custom properties and Device custom properties settings, letting you promote any Axonius custom property to a first-class attribute on synchronized Users and Devices by listing the property names (comma-delimited, case-insensitive). | N/A |
| 3.0.4 | New Features - Added the User asset model, so user accounts discovered by Axonius are now synchronized alongside Devices. Improvements - Consolidated overlapping device and user attributes onto Brinqa's standard attributes, eliminating duplicate values that were previously emitted under both the raw Axonius field name and the standard attribute name. | N/A |
| 3.0.3 | Improvements Dependency Upgrades - Upgraded internal framework and model libraries to the latest stable versions for improved reliability, security patches, and alignment with the rest of the connector platform. | N/A |
| 3.0.2 | Improvements Dependency Upgrades - Upgraded internal framework and model libraries to the latest stable versions for improved reliability, security patches, and alignment with the rest of the connector platform. | N/A |
| 3.0.1 | Improvements - Hostnames, MAC addresses, and serial numbers on Devices are now normalized during synchronization, improving consistency and matching of device records across data sources. | N/A |
| 3.0.0 | Overview The Axonius connector integrates with Axonius to synchronize asset inventory data into Brinqa. Category: Asset Management Models | N/A |