Device42 is a cloud-based CMDB that maps relationships and dependencies for physical and virtual machines, cloud servers and containers, network components, software, services, and applications. The Balbix integration with Device42 ingests IT infrastructure assets and software information.
Balbix leverages AI to aggregate, normalize, and deduplicate ingested data, along with information integrated from your existing IT and cybersecurity tools. This creates a unified view of your entire asset inventory, including vulnerabilities and their business and operational context. Balbix’s AI models then analyze this data to provide insights such as deployment gap analysis, risk-based vulnerability prioritization (with detailed ranking and scoring), and risk quantification. This process delivers a comprehensive assessment of risk, whether for a single asset, groups of assets, or your entire enterprise, enabling more informed and effective security decisions.
Integration Summary
This table provides a summary of the Balbix integration for the Device42 connector.
Integration Type | Fetch: An inbound API integration used to fetch infrastructure assets and software information. |
Types of Assets Fetched | Host devices including servers, virtual machines, desktops, laptops. |
Types of Data Fetched | Asset names, software information, all relevant timestamps (e.g., first observed, last observed). |
Prerequisites
To configure the Balbix connector, you must first create Device42 API credentials with the appropriate permissions. These credentials are required for completing the configuration process.
To access the Device42 API, you will need either of the following API credentials:
Basic authentication: username and password. See documentation here for details.
OAuth 2.0 using an OAuth provider and profile. See documentation here for details.
Create and Configure the Connector
After you have completed the prerequisites, follow these steps to create and configure your Balbix connector for Device42.
API Reference Documentation
To learn more about the Device42 API, see the references listed below: