Scott Behrens edited this page Aug 20, 2018 · 42 revisions


We're starting to change directions with our security automation approach and are actively looking for a maintainer for the Scumblr project. We're going to leave Scumblr code online but are not planning on adding any new features or addressing open issues and pull requests. If you are interested in maintaining this project, please reach out to me (



Join the chat at

What is Scumblr 2?

Scumblr is a web application that allows performing periodic syncs of data sources (such as Github repositories and URLs) and performing analysis (such as static analysis, dynamic checks, and metadata collection) on the identified results. Scumblr helps you streamline proactive security through an intelligent automation framework to help you identify, track, and resolve security issues faster.

Scumblr ships with a number of tasks to help you streamline security automation including:

Sync Tasks

  • Github - Sync results from github Repositories
  • Route53 DNS - Sync FQDNs from Route53 DNS
  • Manual Result Upload - Specify a new line delimited list of results you'd like to sync into Scumblr

Security Tasks

  • Github Search - Search Github for secrets, anti-patterns, and vulnerabilities in your repositories
  • Curl - Execute curl commands to identify vulnerabilities or issues against Scumblr results
  • Bandit - Perform static code analysis against Python projects
  • Brakeman - Perform static code analysis against Ruby on Rails projects.

Search Tasks (legacy)

  • Google
  • Facebook
  • Twitter
  • iTunes Store
  • Certificate Transparency
  • Ebay
  • Google Play
  • Reddit
  • RSS Feeds (useful for full disclosure searches)
  • YouTube

Scumblr also provides a number of novel features that streamline security automation including:

  • Tracking, ticketing, regression monitoring, and auto-remediation of security vulnerabilities
  • Metadata storage in results to allow for advanced result filtering
  • Customizable views and sorting of results and tasks to get you to the important details faster
  • Saveable result filters that can be shared with collegues
  • Event model for auditing changes to results so you can keep an eye on what is happening
  • Email subscriptions for specific results or tasks you care about (such as monitoring when a security task finds a new vulnerablity)
  • Advanced asynchronous task scheduling to allow for task chaining and task batching

Scumblr uses the Workflowable gem to allow setting up flexible workflows for different types of results.

How do I use Scumblr?

Scumblr is a web application based on Ruby on Rails. In order to get started, you'll need to setup / deploy a Scumblr environment and configure it to search and analyze the things you care about. Setup information is described in great detail on the wiki.

You'll optionally want to setup and configure workflows so that you can track the status of identified results through your triage process.

What can Scumblr look for and analyze?

Just about anything! Scumblr searches utilize plugins called Tasks. Each Task knows how to perform a search or sync via a certain site or API (Github, Route53, Google, Pastebin, Twitter, etc.). Tasks can be configured from within Scumblr based on the options available by the Task. What are some things you might want to look for or analyze? How about:

  • Your organization's public or private github repositories
  • When new FQDNS are created in your organization's DNS
  • Detection of anti-patterns in source code
  • Dynamic checks against running web servers for security issues
  • Static code analysis across a large number of repositories using Brakeman or Bandit
  • Get an alert on full disclosure security reports on vulnerabilities in your team's version of Apache

These are just a few examples of things that you may want to keep an eye on!

Scumblr found stuff, now what?

Scumblr provides a handy vulnerablity object you can use to monitor a particular result security issues. You can also create Status fields to associate with results, allowing you to track the state of a result or it's remediation over time.

You can create simple or complex workflows to be used along with your results. This can be as simple as marking results as "Reviewed" once they've been looked at, or much more complex involving multiple steps with automated actions occurring during the process.

Sounds great! How do I get started?

Take a look at the wiki for detailed instructions on setup, configuration, and use!


Pull requests welcome! See the Contributing doc for details.

You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Press h to open a hovercard with more details.