We are thrilled to announce the general availability of Rumble Network Discovery!

This release is the result of six months of beta testing by nearly 3,000 users tracking almost 3,000,000 assets. We feel like the product is finally taking shape and are more excited than ever to tackle the problem of unauthenticated network discovery and asset inventory.

A HUGE thanks to our beta community for their relentless (and awesome) feedback about every part of the product, from specific network probes to the look and feel of the inventory. This feedback has driven our development process and helped us define the roadmap ahead.

For those who have already subscribed or started the purchasing process, we really appreciate your support, and are looking forward to working with you as we continue to improve the platform.

If you haven’t had a chance to try Rumble before, or just haven’t seen a recent version, we recommend signing up for a free trial and taking this release for a spin.

Release Notes Since Beta 6

  • Rumble scans now pull the ARP cache, MAC table, and VLAN table of SNMP v2 network devices when a community string is available (or the device responds to public). This feature allows Rumble to obtain even more MAC addresses from routed networks. ARP entries found in another device’s cache are noted in the source field of the ARP service.

  • The Inventory now offers a Screenshots tab that can be sorted by image size (the screenshots column). This makes it easy to browse all screenshots quickly. A gallery-mode experience can be achieved removing all columns from the table except for the screenshot itself.

  • Rumble now uses an IPSEC IKE probe to identify responsive hosts. This helps find even more devices, especially VPN gateways with minimal services exposed.

  • The Rumble agent now reports additional data about scans as they are running. This includes finer-grained estimate of the completion time, the total runtime, and the number of datapoints gathered so far.

  • Asset correlation now takes into account SMB computer names and TLS certificates for RDP when deciding whether a newly found asset matches an existing entry. This should result in less churn for DHCP environments with short leases.

  • Asset correlation now looks at a broader set of TCP/IP stack fingerprints when determining whether an IP-based match is credible. This should result in less churn for highly-filtered environments (many external networks).

  • Rumble now intentionally skips sending probes to and reporting results from network broadcast addresses. The benefits of identifying a few extra systems were outweighed by buggy behavior by certain networking equipment.

  • Security improvements were made in response to our first third-party security assessment.

  • Bug fixes for occasional deadlocks in the Rumble Scanner (CLI).

Similar Content

Overview Version 1.7.0 of Rumble Network Discovery is live with big updates to reporting. The Analysis Reports introduced in version 1.6.2 are now joined by a new Subnet Grid Report, linked off the main Subnets Report under the Explore menu. The Query Library has been updated with small tweaks and new built-in query for finding expired TLS certificates, supported by improvements to the scan engine. The Rumble backend has been upgraded to support our larger customers as well as all of our new Starter Edition users.
Overview Today’s update comes with two significant features: Analysis Reports and the Query Library. This work brings practical analytic capabilities to the inventory data and makes it easier than ever to create and share custom queries with your team and the wider community. Analysis Reports Analysis Reports are now accessible via the Explore link in the navigation menu. This section includes the three existing reports (Topology, Subnets, Bridges) and introduces two new ones.
Overview Version 1.6.0 of Rumble Network Discovery is live with support for configurable scan grace periods, data retention policies, additional protocol support, enhanced fingerprint coverage, new search keywords, and much more. Scan Grace Periods Starting with the 1.3.2 release, Rumble would automatically cancel a scheduled or recurring scan if the intended agent was not available after four hours. This fixed grace period prevented scans from stacking up in the case of a slow scan or offline agent, but it didn’t work for all use cases, and this is now configurable at the scan level.