Rumble 1.12: One Year Later

October 13, 2020

Rumble v1.12

What a year! It is hard to believe that Rumble 1.0 went live only 12 months ago. We wouldn’t be here without our amazing community – Thank you! The 1.12 release work was focused on the less visible parts of the platform; consistency, reliability, performance, bug fixes, infrastructure, and security-related efforts.

Read on for the full list of changes since v1.11.

Consistency & Reliability

The scan engine now splits the discovery process into three distinct stages (ARP/ICMP), UDP discovery, and TCP scanning. All stages are still run for every target address, but this helps to warm the remote ARP cache, and generally improves reliability without drastically increasing scan times.

The UDP probes will now retry up to two times, similar to the TCP SYN scanner defaults. This helps in cases where a single missed UDP reply could cause an asset to flap.

On the Windows platform, the Rumble Agent and Rumble Scanner now bundle npcap 1.00, which includes a number of reliability and performance improvements.

Most users should see a reduced number of changes between scans as a result of these updates.

Screenshot of Rumble Scan Results

Authentication & Access Control

Users with the Viewer role now have a reduced navigation view, limiting their access to just the inventory, reports, agents, and exports. A big thanks to all of the folks who shared feedback on this feature and helped drive the current implementation.

Single Sign On support received a number of small bug fixes related to the default “No Access” role and support for a wider range of SAML assertion signatures.

We really appreciate all of the feedback received on our SSO implementation and will continue working to make this as painless as possible with all SAML/2.0 compliant IdPs.

Screenshot of Rumble View-Only User

Binaries & Installers

All Rumble executables (scanners, agents, etc) include an internal codesigning signature. This signature is in addition to the Authenticode signature present on the Windows binaries and is verified as part of every download and upgrade. This process has been reworked to separate license validation from code validation. As a result, folks using the Rumble Verifier prior to version 1.0.4 will need to upgrade to the latest version in order to verify new binaries.

The Rumble Scanner can now automatically update itself when run with the upgrade argument. Binaries prior to version 1.11.9 will require a manual upgrade to receive this functionality.

The Rumble Agent can now be installed through a MSI wrapper. This static wrapper uses the same Rumble Agent download URLs as before (tied to your active organization), but can be used with automated installers, will verify the signature of all downloads, and can load agent binaries from arbitrary locations, such as internal webservers.

Screenshot of Rumble Scanner Upgrade

Fingerprints & Bug Fixes

A huge thank you to everyone who submitted new fingerprints and bug fixes during this release cycle. We are still a little behind on the queue, but really appreciate the time and effort it takes to submit these, and are looking forward to rolling them out as we get started on the 1.12.x point releases.

Screenshot of Rumble Improve Fingerprint Form

Release Notes

The complete release notes for v1.12.0 can be found in our documentation

If you haven’t had a chance to try Rumble before, or would like to play with the new features, sign up for a free trial and let us know what you think!