Loading

Axonius Integration for Elastic

Version 0.1.0 (View all)
Subscription level
What's this?
Basic
Developed by
What's this?
Elastic
Ingestion method(s) API
Minimum Kibana version(s) 9.3.1
9.2.4
9.1.10
8.19.10
The Axonius integration v0.1.0 is in technical preview

To use pre-release integrations, go to the Integrations page in Kibana, scroll down, and toggle on the Display beta integrations option.

Axonius is a cybersecurity asset management platform that automatically collects data from hundreds of IT and security tools through adapters, merges that information, and builds a unified inventory of all assets including devices, users, SaaS apps, cloud instances, and more. By correlating data from multiple systems, Axonius helps organizations identify visibility gaps, missing security controls, risky configurations, and compliance issues. It lets you create powerful queries to answer any security or IT question and automate actions such as sending alerts, creating tickets, or enforcing policies.

This integration for Elastic allows you to collect assets and security events data using the Axonius API, then visualize the data in Kibana.

The Axonius integration is compatible with product version 7.0.

This integration periodically queries the Axonius API to retrieve logs.

This integration collects log messages of the following type:

  • Adapter: Collect details of all adapters (endpoint: /api/v2/assets/adapters).

  • User: Collect details of all user 55s (endpoint: /api/v2/assets/users).

  • Gateway: Collect details of all Gateway (endpoint: /api/v2/assets/gateway).

  • Exposure: Collect details of all exposure assets including:

    • vulnerability_instances (endpoint: /api/v2/assets/vulnerability_instances)
    • vulnerabilities (endpoint: /api/v2/assets/vulnerabilities)
    • vulnerabilities_repository (endpoint: /api/v2/assets/vulnerabilities_repository)
  • Alert Findings: Collect details of all alert findings and incident assets including:

    • alert_findings (endpoint: /api/v2/assets/alert_findings)
  • Incidents: Collect details of all incident assets including:

    • incidents (endpoint: /api/v2/assets/incidents)
  • Storage: Collect details of all storage assets including:

    • object_storages (endpoint: /api/v2/assets/object_storages)
    • file_systems (endpoint: /api/v2/assets/file_systems)
    • disks (endpoint: /api/v2/assets/disks)
  • Ticket: Collect details of all ticket assets including:

    • tickets (endpoint: /api/v2/assets/tickets)
    • cases (endpoint: /api/v2/assets/cases)
  • Network: Collect details of all identity assets including:

    • networks (endpoint: /api/v2/assets/networks)
    • load_balancers (endpoint: /api/v2/assets/load_balancers)
    • network_services (endpoint: /api/v2/assets/network_services)
    • network_devices (endpoint: /api/v2/assets/network_devices)
    • firewalls (endpoint: /api/v2/assets/firewalls)
    • nat_rules (endpoint: /api/v2/assets/nat_rules)
    • network_routes (endpoint: /api/v2/assets/network_routes)
  • Identity: Collect details of all identity assets including:

    • users (endpoint: /api/v2/assets/users)
    • groups (endpoint: /api/v2/assets/groups)
    • security_roles (endpoint: /api/v2/assets/security_roles)
    • organizational_units (endpoint: /api/v2/assets/organizational_units)
    • accounts (endpoint: /api/v2/assets/accounts)
    • certificates (endpoint: /api/v2/assets/certificates)
    • permissions (endpoint: /api/v2/assets/permissions)
    • latest_rules (endpoint: /api/v2/assets/latest_rules)
    • profiles (endpoint: /api/v2/assets/profiles)
    • job_titles (endpoint: /api/v2/assets/job_titles)
    • access_review_campaign_instances (endpoint: /api/v2/assets/access_review_campaign_instances)
    • access_review_approval_items (endpoint: /api/v2/assets/access_review_approval_items)
  • Compute: Collect details of all compute assets including:

    • devices (endpoint: /api/v2/assets/devices)
    • compute_services (endpoint: /api/v2/assets/compute_services)
    • databases (endpoint: /api/v2/assets/databases)
    • containers (endpoint: /api/v2/assets/containers)
    • serverless_functions (endpoint: /api/v2/assets/serverless_functions)
    • compute_images (endpoint: /api/v2/assets/compute_images)
    • configurations (endpoint: /api/v2/assets/configurations)
  • Application: Collect details of all application assets including:

    • software (endpoint: /api/v2/assets/software)
    • saas_applications (endpoint: /api/v2/assets/saas_applications)
    • application_settings (endpoint: /api/v2/assets/application_settings)
    • licenses (endpoint: /api/v2/assets/licenses)
    • expenses (endpoint: /api/v2/assets/expenses)
    • admin_managed_extensions (endpoint: /api/v2/assets/admin_managed_extensions)
    • user_initiated_extensions (endpoint: /api/v2/assets/user_initiated_extensions)
    • application_addons (endpoint: /api/v2/assets/application_addons)
    • admin_managed_extension_instances (endpoint: /api/v2/assets/admin_managed_extension_instances)
    • user_initiated_extension_instances (endpoint: /api/v2/assets/user_initiated_extension_instances)
    • application_addon_instances (endpoint: /api/v2/assets/application_addon_instances)
    • application_keys (endpoint: /api/v2/assets/application_keys)
    • audit_activities (endpoint: /api/v2/assets/audit_activities)
    • business_applications (endpoint: /api/v2/assets/business_applications)
    • urls (endpoint: /api/v2/assets/urls)
    • application_resources (endpoint: /api/v2/assets/application_resources)
    • secrets (endpoint: /api/v2/assets/secrets)

This integration brings Axonius asset and security data into Elastic so teams can search, correlate, and investigate in one place instead of moving between separate tools. Use it to maintain a current view of what Axonius is collecting, how adapters and ingestion are performing, and how that inventory connects to alerts, tickets, identity, and infrastructure context in Elastic Security and Kibana.

Adapter and User data streams support integration health and user-oriented reporting from Axonius. Adapter data helps confirm which sources are connected and ingesting as expected. User data supports population and account-oriented views that complement identity and access analysis elsewhere in the package.

Compute, Network, Gateway, and Storage data streams cover core infrastructure and connectivity. Compute includes devices, cloud services, databases, containers, and related configuration. Network covers networks, load balancers, services, devices, firewalls, routes, and NAT rules. Gateway adds gateway-level visibility. Storage covers object storage, file systems, and disks. Together they support asset inventory, segmentation review, and investigations that need host, cloud, or data-store context.

Exposure, Alert Finding, and Incident data streams support vulnerability and security-operations workflows. Exposure brings vulnerability instances, vulnerability records, and repository context into Elastic. Alert Finding and Incident data help track detections, severity, status, and progression from alert to case so analysts can prioritize and respond with less context switching.

Ticket data streams support IT and security operations processes with tickets and cases, including status, priority, and queue-oriented views for backlog and workload tracking.

Identity data streams enrich access and governance use cases with users, groups, roles, organizational units, accounts, permissions, certificates, profiles, job titles, and access-review artifacts. Teams can review account states, role and permission patterns, and access-review activity alongside other security data.

Application data streams focus on software and SaaS posture: business applications, installed software, licenses, expenses, extensions, audit activity, and related application assets. Use them to understand application usage and distribution, validate SaaS and business-application activity, spot unusual or dormant applications, and add application context to investigations.

Bundled dashboards summarize these data streams for day-to-day monitoring, risk and backlog sizing, access hygiene checks, and incident investigation with correlated operational, identity, asset, and event context.

This integration installs Elastic latest transforms. For more details, check the Transform setup and requirements.

To collect data through the Axonius APIs, you need to provide the URL, API Key and API Secret. Authentication is handled using the API Key and API Secret, which serves as the required credential.

  1. Log in to the Axonius instance.
  2. Your instance URL is your Base URL.
  3. Navigate to User Settings > API Key.
  4. Generate an API Key.
  5. If you do not see the API Key tab in your user settings, follow these steps:
    1. Go to System Settings > User and Role Management > Service Accounts.
    2. Create a Service Account, and then generate an API Key.
  6. Copy both values including API Key and Secret Key and store them securely for use in the Integration configuration.

Note: To generate or reset an API key, your role must be Admin, and you must have API Access permissions, which include API Access Enabled and Reset API Key.

This integration supports both Elastic Agentless-based and Agent-based installations.

Elastic Agent must be installed. For more details, check the Elastic Agent installation instructions. You can install only one Elastic Agent per host.

Elastic Agent is required to stream data from the syslog or log file receiver and ship the data to Elastic, where the events will then be processed via the integration's ingest pipelines.

Agentless deployments are only supported in Elastic Serverless and Elastic Cloud environments. Agentless deployments provide a means to ingest data while avoiding the orchestration, management, and maintenance needs associated with standard ingest infrastructure. Using an agentless deployment makes manual agent deployment unnecessary, allowing you to focus on your data instead of the agent that collects it.

For more information, refer to Agentless integrations and Agentless integrations FAQ

  1. In the top search bar in Kibana, search for Integrations.

  2. In the search bar, type Axonius.

  3. Select the Axonius integration from the search results.

  4. Select Add Axonius to add the integration.

  5. Enable and configure only the collection methods which you will use.

    • To Collect logs from Axonius API, you'll need to:

      • Configure URL, API Key and API Secret.
      • Adjust the integration configuration parameters if required, including the Interval, HTTP Client Timeout etc. to enable data collection.
  6. Select Save and continue to save the integration.

  1. In the top search bar in Kibana, search for Dashboards.
  2. In the search bar, type Axonius, and verify the dashboard information is populated.
  1. In the top search bar in Kibana, search for Transforms.
  2. Select the Data / Transforms from the search results.
  3. In the search bar, type Axonius.
  4. All transforms from the search results should indicate Healthy under the Health column.

An Elastic Transform is created for each data stream, to provide a view of the most recent, active Axonius data. Use the relevant destination alias from the table below to access the latest data, whether for use in dashboards, rules, or elsewhere. Destinations indices are aliased to logs-axonius_latest.<data_stream_name>.

Source Data stream Destination Index Pattern Destination Alias
logs-axonius.adapter-* logs-axonius_latest.dest_adapter-* logs-axonius_latest.adapter
logs-axonius.alert_finding-* logs-axonius_latest.dest_alert_finding-* logs-axonius_latest.alert_finding
logs-axonius.exposure-* logs-axonius_latest.dest_exposure-* logs-axonius_latest.exposure
logs-axonius.gateway-* logs-axonius_latest.dest_gateway-* logs-axonius_latest.gateway
logs-axonius.incident-* logs-axonius_latest.dest_incident-* logs-axonius_latest.incident
logs-axonius.user-* logs-axonius_latest.dest_user-* logs-axonius_latest.user
logs-axonius.storage-* logs-axonius_latest.dest_storage-* logs-axonius_latest.storage
logs-axonius.ticket-* logs-axonius_latest.dest_ticket-* logs-axonius_latest.ticket
logs-axonius.network-* logs-axonius_latest.dest_network-* logs-axonius_latest.network
logs-axonius.identity-* logs-axonius_latest.dest_identity-* logs-axonius_latest.identity
logs-axonius.compute-* logs-axonius_latest.dest_compute-* logs-axonius_latest.compute
logs-axonius.application-* logs-axonius_latest.dest_application-* logs-axonius_latest.application
Note

Assets deleted from Axonius may reappear in a future discovery cycle if they are still present in connected data sources and get re-detected. Because the exact duration for which a deleted asset may remain dormant before being rediscovered is unknown, the transform retention period is set to 90 days to reduce the risk of data loss for such assets. This means deleted assets will continue to appear in dashboards for up to 90 days after deletion. The assets destination indices are a content-based deduplicated view, not an entity-level latest-state view like the other data streams (for example user and gateway), which rely on a unique entity identifier and reflect the latest state of each entity.

For help with Elastic ingest tools, check Common problems.

For more information on architectures that can be used for scaling this integration, check the Ingest Architectures documentation.

The adapter data stream provides adapter logs from axonius.

The user data stream provides user events from axonius.

The gateway data stream provides gateway events from axonius.

The exposure data stream provides exposure logs from axonius.

The alert_finding data stream provides alert findings asset logs from axonius.

The incident data stream provides incident asset logs from axonius.

The storage data stream provides storage asset logs from axonius.

The ticket data stream provides ticket asset logs from axonius.

The network data stream provides network events from axonius.

The identity data stream provides identity asset logs from axonius.

The compute data stream provides compute asset logs from axonius.

The application data stream provides application asset logs from axonius.

These inputs can be used with this integration:

To collect logs via API endpoint, configure the following parameters:

  • API Endpoint URL
  • API credentials (tokens, keys, or username/password)
  • Request interval (how often to fetch data)

These APIs are used with this integration:

  • Adapter (endpoint: /api/v2/assets/adapters)
  • User (endpoint: /api/v2/assets/users)
  • Gateway (endpoint: /api/v2/assets/gateway)
  • Exposure:
    • vulnerability_instances (endpoint: /api/v2/assets/vulnerability_instances)
    • vulnerabilities (endpoint: /api/v2/assets/vulnerabilities)
    • vulnerabilities_repository (endpoint: /api/v2/assets/vulnerabilities_repository)
  • Alert Findings:
    • alert_findings (endpoint: /api/v2/assets/alert_findings)
  • Incidents:
    • incidents (endpoint: /api/v2/assets/incidents)
  • Storage:
    • object_storages (endpoint: /api/v2/assets/object_storages)
    • file_systems (endpoint: /api/v2/assets/file_systems)
    • disks (endpoint: /api/v2/assets/disks)
  • Ticket:
    • tickets (endpoint: /api/v2/assets/tickets)
    • cases (endpoint: /api/v2/assets/cases)
  • Network
    • networks (endpoint: /api/v2/assets/networks)
    • load_balancers (endpoint: /api/v2/assets/load_balancers)
    • network_services (endpoint: /api/v2/assets/network_services)
    • network_devices (endpoint: /api/v2/assets/network_devices)
    • firewalls (endpoint: /api/v2/assets/firewalls)
    • nat_rules (endpoint: /api/v2/assets/nat_rules)
    • network_routes (endpoint: /api/v2/assets/network_routes)
  • Identity:
    • users (endpoint: /api/v2/assets/users)
    • groups (endpoint: /api/v2/assets/groups)
    • security_roles (endpoint: /api/v2/assets/security_roles)
    • organizational_units (endpoint: /api/v2/assets/organizational_units)
    • accounts (endpoint: /api/v2/assets/accounts)
    • certificates (endpoint: /api/v2/assets/certificates)
    • permissions (endpoint: /api/v2/assets/permissions)
    • latest_rules (endpoint: /api/v2/assets/latest_rules)
    • profiles (endpoint: /api/v2/assets/profiles)
    • job_titles (endpoint: /api/v2/assets/job_titles)
    • access_review_campaign_instances (endpoint: /api/v2/assets/access_review_campaign_instances)
    • access_review_approval_items (endpoint: /api/v2/assets/access_review_approval_items)
  • Compute:
    • devices (endpoint: /api/v2/assets/devices)
    • compute_services (endpoint: /api/v2/assets/compute_services)
    • databases (endpoint: /api/v2/assets/databases)
    • containers (endpoint: /api/v2/assets/containers)
    • serverless_functions (endpoint: /api/v2/assets/serverless_functions)
    • compute_images (endpoint: /api/v2/assets/compute_images)
    • configurations (endpoint: /api/v2/assets/configurations)
  • Application:
    • software (endpoint: /api/v2/assets/software)
    • saas_applications (endpoint: /api/v2/assets/saas_applications)
    • application_settings (endpoint: /api/v2/assets/application_settings)
    • licenses (endpoint: /api/v2/assets/licenses)
    • expenses (endpoint: /api/v2/assets/expenses)
    • admin_managed_extensions (endpoint: /api/v2/assets/admin_managed_extensions)
    • user_initiated_extensions (endpoint: /api/v2/assets/user_initiated_extensions)
    • application_addons (endpoint: /api/v2/assets/application_addons)
    • admin_managed_extension_instances (endpoint: /api/v2/assets/admin_managed_extension_instances)
    • user_initiated_extension_instances (endpoint: /api/v2/assets/user_initiated_extension_instances)
    • application_addon_instances (endpoint: /api/v2/assets/application_addon_instances)
    • application_keys (endpoint: /api/v2/assets/application_keys)
    • audit_activities (endpoint: /api/v2/assets/audit_activities)
    • business_applications (endpoint: /api/v2/assets/business_applications)
    • urls (endpoint: /api/v2/assets/urls)
    • application_resources (endpoint: /api/v2/assets/application_resources)
    • secrets (endpoint: /api/v2/assets/secrets)

To facilitate adapter, user, gateway and assets data including exposures, alert findings, incidents, storage and ticket, network and identity source data stream-backed indices .ds-logs-axonius.adapter-*, .ds-logs-axonius.user-*, .ds-logs-axonius.gateway-*, .ds-logs-axonius.exposure-*, .ds-logs-axonius.alert_finding-*, .ds-logs-axonius.incident-*, .ds-logs-axonius.storage-*, .ds-logs-axonius.ticket-*, .ds-logs-axonius.network-*, .ds-logs-axonius.identity-*, .ds-logs-axonius.compute-* and .ds-logs-axonius.application-* respectively are allowed to contain duplicates from each polling interval. ILM policies logs-axonius.adapter-default_policy, logs-axonius.user-default_policy, logs-axonius.gateway-default_policy, logs-axonius.exposure-default_policy, logs-axonius.alert_finding-default_policy, logs-axonius.incident-default_policy, logs-axonius.storage-default_policy, logs-axonius.ticket-default_policy, logs-axonius.network-default_policy, logs-axonius.identity-default_policy, logs-axonius.compute-default_policyand logs-axonius.application-default_policy are added to these source indices, so it doesn't lead to unbounded growth. This means that in these source indices data will be deleted after 30 days from ingested date.

This integration includes one or more Kibana dashboards that visualizes the data collected by the integration. The screenshots below illustrate how the ingested data is displayed.