Deploying Rumble

As you get started with Rumble, it is helpful to start with our standard deployment plan and expand or adjust as needed. The plan is broken out into 6 stages which will help you plan out your requirements, execute the deployment, and optimize your environment based on Rumble’s best practices.


The first step of any project is to make a plan, and onboarding Rumble is no different. This first set of tasks will help your team identify target results, get ahead of potential blockers, and help you avoid misconfigurations.



Once you have a plan in place, it’s time to execute. The configuration tasks are in a prioritized order to help you avoid having to reconfigure things down the road.



Now that you have done some initial discovery, it’s time to review the results. We have some best practices to follow to help you identify key issues, expand scan scope, and better understand your network.



After initial analysis, you will want to optimize your scans and configure external integrations to expand your asset inventory.



Now that you understand your Rumble data, you can put some tasks on schedules to avoid manual effort. You can schedule scans, automate queries, and also generate alerting for the team.



As your Rumble deployment comes to a close, you will want to ensure all users have followed the training and ensure anyone that would get value from Rumble has access.


  • Ensure all users are trained on Rumble
  • Identify other teams interested in the asset inventory data