# Rumble Scanner Updates & Data Transparency

January 28, 2020

Data transparancy is one of the key drivers of Rumble development. We do our best to ensure that any data gathered, transmitted, or downloaded is easy to view, import, export, and reprocess. Data generated by the Rumble Agent can be downloaded and reprocessed by the Rumble Scanner. Raw data from the Rumble Scanner can be imported into the Rumble Console. This data is consistently formatted and almost always backwards compatible between versions.

This week we released version 1.3.1 of the Rumble Scanner, which adds even more features for working with data and bringing that data back into the cloud console. The new additions include:

• Support for the --baseline option, which accepts an assets.jsonl file from a previous run, or a JSONL export from the Rumble Console, and uses this as a baseline for normalizing and deduplicating assets. Assets matched against the baseline will carry forward the same UUID values, as well as tags and comments, in the resulting assets.jsonl of the new scan. For folks who primarily use the Scanner (and our OEM integrators), this simplifies the process of asset tracking between scans, allowing the same logic as the cloud backend to be applied to local scan data.

• Support for the --upload option. The Rumble Scanner can now upload data directly to the cloud console. If you want more flexibility for how scans are run, when they are run, and from what systems, the Scanner can now be used as a primary driver of scan data for the console. To use this option, specify an Organization API key for the --api-key parameter and optionally, set the --upload-site name to the Site to populate. If you want to send data to your own endpoint, you can override the --api-host parameter and build your own handler for the Import API.

• Support for multiple --import options. This change allows the Rumble Scanner to consolidate raw scan data (scan.rumble or the raw task data from the console) into a single output. This works with the --baseline option to track and correlate assets and with the --upload option. The import option works with or without new scan parameters. If you would like to import one more previous scans into a remote site, specify each --import file, set the --api-key, and an optional --upload-site.

Happy scanning!

-HD

### 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 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.
Scanning & Searching Version 1.5.0 of Rumble Network Discovery is live with updates in two major areas; wider scanning, through improved protocol support, scan engine enhancements, and more comprehensive decoders; and deeper searching, with the addition of a dozen new search filters and other enhancements to the web console. Wider Scanning Whether you use the Rumble Agent or the Rumble Scanner, the scan engine improvements in v1.5.0 make discovery more reliable, predictable, and comprehensive.