Rumble Scanner Updates & Data Transparency

January 28, 2020, by

HD Moore

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.

Rumble Scanner Data

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.gz 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.

If you haven’t had a chance to try the Rumble Scanner yet, you can sign up for a free trial and then download the binary for your platform of choice from the Scanner section of the console. For additional information about the Scanner, including the command-line options, take a look at the documentation. We hope you find these additions useful and would love your feedback about what we can do to make Rumble work even better for your use case.

Happy scanning!

-HD

Similar Content

April 13, 2021

Rumble 2.1: Notification Templates, AWS EC2 Enrichment, and Cisco SNTC Exports

Rumble Network Discovery 2.1 Rumble 2.1 is now live with support for custom notification templates, AWS EC2 scan enrichment, Cisco serial number exports for SNTC, faster exports, more flexible imports, an updated Splunk Addon, and much more! Custom notification emails and …

Read More

March 16, 2021

Rumble 2.0: Automation, Subnet Discovery, ServiceNow, and More!

Rumble Network Discovery 2.0 Rumble 2.0 is now live with alert and asset automation via the Rules Engine, ridiculously fast scans with subnet discovery, cross-organization management via the Account API, support for ServiceNow CMDB integration, an automated query dashboard, …

Read More

August 6, 2020

Recog Development with Rumble

Overview Recog may be one of the most underrated open source security projects of all time. Recog started off in the early 2000s as the fingerprinting backend for Rapid7’s Nexpose (aka InsightVM) vulnerability scanner. It was released as open source in 2014 and …

Read More