Recently active topics

NetBrain currently requires removal of the entire Azure Cloud instance in order to release licenses associated with individual VNets, since there is no option to delete a specific VNet on its own. This enhancement would introduce the ability to select and delete individual VNets within an Azure Cloud instance, without impacting the remaining discovered resources. Customers managing large or evolving Azure environments would benefit from more precise license management and reduced administrative effort when decommissioning specific network segments.

NetBrain currently does not provide a reliable plugin-based method to retrieve the complete list of discoverable VPC resource IDs for Google Cloud (GCP), which limits the accuracy of include/exclude VPC discovery scoping in GCP environments. This enhancement would introduce a GCP-specific mechanism to fetch and validate discoverable VPC resource IDs, aligning GCP discovery capabilities with those already available for AWS and Azure. Customers managing GCP infrastructure would benefit from more accurate and dependable control over which VPCs are included or excluded during discovery, reducing errors caused by incomplete or outdated resource ID lists.

We use inventory reports to gather data on our network and would like some of our other tools to use that data as well for management dashboards.  It would be great to get this data via inventory reports.

QApp input dialogs currently support only static, pre-defined dropdown lists for parameter selection, with no mechanism to refresh the available options from an external data source before the QApp runs. This enhancement would allow a QApp input to call an API at runtime to retrieve a current set of selectable values, populate the dropdown with those items, and let the user choose one before execution. Customers whose valid input values change frequently would be able to select accurate, up-to-date options without manually editing the QApp definition each time the underlying list changes, reducing maintenance effort and the risk of running a QApp against stale input values.

Summary Dashboards currently present results only as raw numbers, without an option to display values as percentages. This enhancement would allow Summary Dashboard results to be shown in percentage format in addition to or instead of numeric counts. Presenting data as percentages would give management-level stakeholders a clearer, faster overview of network status when reviewing dashboards.

When creating a new device group using the Static, Dynamic Search, or Exclude options, the Select dialog for choosing devices or interfaces does not support full RegEx pattern matching. Users are limited to basic filtering and cannot construct precise expressions to target device or interface subsets. This enhancement proposes adding full RegEx search capability to these Select dialogs across all three device group creation methods, for both device and interface selection. Customers managing large or complex environments would gain a more precise and efficient way to build device groups without relying on manual selection or workarounds.

NetBrain currently does not provide a way to monitor user seat license consumption or notify administrators as usage approaches the licensed limit. Administrators can only observe seat usage manually and have no visibility until the limit is fully reached, which does not allow time to plan for additional capacity. This enhancement would add configurable threshold-based alerting for user seat consumption, notifying administrators when usage reaches defined levels below the full seat count. Customers would gain advance visibility into approaching seat limits, allowing them to budget and procure additional seats before running out.

NetBrain currently skips hostname change detection and handling for devices that share a serial number with another device, such as virtual systems on a Checkpoint firewall sharing the serial number of the physical firewall. When the hostname changes on one of these devices, administrators must manually remove and rediscover it to resume configuration retrieval, which results in the loss of historical data for that device. This enhancement would extend hostname change detection and in-place hostname update support to devices with shared serial numbers, allowing NetBrain to recognize the hostname change and update the device record without requiring removal and rediscovery. Customers managing these device types would benefit from continuous configuration retrieval and preserved historical data when hostnames change.

NetBrain's OneIP Table export currently produces a full data set without an option to limit results to IP addresses associated with a specific group of devices, such as a Device Group. Users who need IP data for only a subset of their environment must export the complete table and manually filter it afterward. This enhancement would add the ability to select a Device Group as a filter criterion prior to export, so that only IP addresses related to devices in that group are included in the output. Customers managing large or segmented environments would benefit from reduced manual post-processing and more efficient access to relevant IP data for audits, troubleshooting, or reporting.

NetBrain currently applies a single global forced CLI timeout setting of 600 seconds, which is shared across all modules and cannot be adjusted specifically for Change Management operations such as image uploads or other tasks that require longer execution windows. This enhancement would introduce a dedicated, configurable CLI timeout setting for the Change Management module, independent of the global forced CLI timeout value. Providing this control would allow administrators to accommodate longer-running change tasks without altering timeout behavior for other parts of the product, reducing task failures caused by premature timeouts during change execution.

NetBrain currently applies the CLI support setting at the device type level, so all devices sharing a type are treated identically for CLI access, even when certain individual devices should only be monitored via SNMP or other non-CLI methods. This enhancement would allow administrators to override the CLI support setting on a per-device basis, letting specific devices be flagged as not supporting CLI without changing the behavior for the rest of the device type. Customers managing mixed environments, such as servers intended for SNMP-only data collection, would benefit from more accurate device configuration and would avoid unnecessary CLI connection attempts on devices that do not require or support such access.

NetBrain currently falls back to Telnet for device connections when SSH fails, even when administrators have configured SSH as the preferred or forced protocol. This enhancement would introduce a setting that fully disables Telnet at the system level, preventing any fallback attempt regardless of SSH connection outcome. Organizations with security policies that prohibit Telnet use need assurance that no Telnet sessions can occur, and this control would let them enforce compliance without manual verification.

NetBrain currently does not allow users to filter or search for devices by Last Discovery Time when building a Device Group, and it does not provide a bulk action to remove outdated devices directly from the Inventory Report. As a result, administrators must manually identify and delete stale or offline devices one at a time, or rely on manual CSV export and custom API scripting to clean up the domain. This enhancement would add Last Discovery Time as a searchable criterion for Device Group creation and introduce a bulk 'Remove from Domain' action available from the Inventory Report or a resulting Device Group. Customers managing large device inventories would benefit from a streamlined, repeatable method to identify and remove outdated or retired devices, reducing manual effort and improving overall inventory accuracy.

NetBrain's Change Management module currently requires an approval step for every change task regardless of whether the change is classified as service-impacting or non-service-impacting, which can delay routine maintenance activities that carry minimal risk. This enhancement would allow administrators to designate certain change templates or tasks as non-service-impacting and permit those changes to be executed without requiring approval, while retaining the approval requirement for changes that carry service impact. Reducing unnecessary approval overhead for low-risk, routine changes would allow teams to execute maintenance work more efficiently while preserving governance controls for changes that carry higher risk.

NetBrain Change Management currently does not support executing configuration changes through API-driven firewall management platforms such as FortiManager, Palo Alto Panorama, and Cisco Firepower Management Center. As a result, customers managing firewalls through these centralized platforms cannot leverage CM automation and must rely on manual, out-of-band change processes for these devices. This enhancement would extend Change Management to integrate with the APIs of FortiManager, Panorama, and Firepower Management Center, allowing changes to be pushed and tracked through these platforms in the same manner as other supported device types. This would give customers consistent, automated change workflows across multi-vendor firewall environments, reducing manual effort and improving change tracking and compliance for security infrastructure.

NetBrain currently restricts editing, disabling, or deleting a Change Analysis task to the user who originally created it. When that user is no longer part of the organization or is unavailable, no other user can manage the task through the application, requiring direct database access to remove or modify it. This enhancement would allow a user with System Admin rights to edit or delete any Change Analysis task regardless of who created it. This would give administrators a supported way to maintain task hygiene and continuity without relying on direct database intervention.

NetBrain currently relies on CLI-based or SNMP-based polling to retrieve BGP routing information and does not support BMP (BGP Monitoring Protocol) as a data collection method for BGP route monitoring. This enhancement would add BMP support, allowing NetBrain to receive real-time BGP route updates and state changes directly from routers configured as BMP stations. Customers with large or dynamic BGP environments would benefit from more timely and lower-overhead BGP route visibility, reducing dependence on repeated polling and improving the accuracy of route change detection.

Chat Bot automation currently executes only one Network Intent at a time, even when multiple intents share a matching tag or are selected together within an Automated Data Table. This enhancement would allow multiple intents to be triggered and run concurrently, either through tag-based matching or by selecting multiple intents within the ADT for simultaneous execution. Enabling concurrent intent execution would allow end users to perform multiple diagnostic checks in a single automation cycle, reducing troubleshooting time and improving overall efficiency of automated workflows.

When installing rules through Rule Discovery, users must manually unselect each rule individually if they only want to install a subset, such as vendor-specific rules. This enhancement would add an 'Unselect All' or 'Clear Selection' action to the Config Rule Template selection interface, allowing the full list to be cleared in a single action before filtering and selecting the desired rules. Customers installing targeted rule subsets would benefit from a faster, less error-prone selection workflow.

NetBrain currently requires each Golden Intent to be scheduled individually, with no option to configure scheduling across multiple intents at once. This enhancement would allow users to select multiple Golden Intents and apply or update scheduling settings simultaneously in a single action. Customers managing large numbers of Golden Intents would benefit from reduced administrative effort and faster configuration of recurring checks.