The Balbix Subnet connector ingests subnets, associated sites, and site geolocation information from IP Address Management (IPAM) data sources. IPAM tools are used for network management and IP address allocations (as IP ranges and subnets) in the private and public IP spaces. These are generally treated as the blueprint for network resource allocation and distribution for organizations' networking infrastructure across geographical locations.
Information ingested from the Balbix Subnet connector populates the site-subnet mapping structure needed to enable dynamic identification of infrastructure asset locations (geolocation or company site) based on IP addresses. Asset location is critical to enable comprehensive visibility about asset inventory, and for effective risk prioritization, remediation, and reporting.
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 Subnet connector integration.
Integration Type | Fetch: An inbound CSV ingestion used to fetch subnet information |
Types of Data Fetched | Subnet details, associated site, geolocation information for each site, 'should scan' flag for scanning by the Network Analyzer sensor |
Subnet Inventory Field Descriptions
Field Definitions
CSV Field (Example) | Balbix Field Mapping | Required? | Description | Example |
Subnet IP | Subnet - IP | Yes | The network address of the subnet. Represented in CIDR notation or standard dotted decimal format | 192.168.1.0 |
Subnet Mask | Subnet – Net Mask | Yes | The subnet mask defining the network's range. For example, “24” represents a “/24” CIDR suffix | 24 |
Site Name | Subnet – Site Name | Yes | The name of the physical or logical site associated with the subnet, aiding in location-based grouping | Austin Data Center |
Site Description | Subnet – Site Description | No | Provides a descriptive context of the subnet’s use or purpose | Austin data center for production system delivery |
Site Location: City | Location: City | No | City of the physical site location | Austin |
Site Location: State | Location: State | No | State of the physical site location | TX |
Site Location: Country | Location: Country | No | Country of the physical site location | United States |
Site Location: Continent | Location: Continent | No | Continent of the physical site location | North America |
Should Scan | Subnet – Should Scan | No | A boolean (e.g., Yes / No ) indicating whether the Network Analyzer (NA) should scan this subnet. Relevant only if NA is deployed. | No |
Note: If the City, State, Country, and Continent columns in the CSV file are all empty (i.e., values are "" or "Unknown"), the Balbix Subnet Connector will attempt to derive the Site location from the Site Name. If any of these columns contain values, the connector will use the provided City, State, Country, and Continent data to set the Site location.
Notes & Best Practices
Ensure Subnet-IP and Subnet-Mask are validated for correctness and consistency.
Subnet-Should Scan should be updated in coordination with NA configuration owners.
Use consistent naming conventions for Subnet-Site Name to support filtering and reporting.
Create and configure the connector
Follow these steps to create and configure the Balbix Subnet connector.
You can also add subnets manually by adding the IP range. See Subnet Management.