How I Design My Prefect Bug Bounty Automation(3)

This article I will tell you what I think is the prefect Bug Bounty automatiion architecture, It doesn’t require you code much, only takes very little time to integrate many excellent tools quickly which no matter which programming language is used to write.

Fast, stable and easy to modify, let’s start.

using the bash command has made a qualitative change in my development thinking, but how to solve the problem of concurrent execution tools?

I plan to use the go machinery framework to solve this problem, each oneforall service is transformed with machinery and run in docker. when a task arrives, if there is a free worker, the worker will take this task, but if a worker has not finished executing the task, then the following tasks need to be queued.

And some people will ask, so the speed of task execution will slow down? Don’t worry, we can run more workers, And let each task not only searching a domain, but multiple domains to improve efficiency.

machinery + redis + workers running multiple tools, the logic layer allows workers to work and obtain data through queues, and the results are stored in DB(mongo, mysql or other, according to your preference).

Because of it is in the form of microservices, not a single architecture, so single error occur in one worker will not cause a catastrophic system crash.

The following figure is the architecture diagram I designed:

base on above idea, I develop oneforall service quickly, there is my demo video:

When I finish the development and run it stably, I will open source it on github, please keep looking forward my github repo.

https://github.com/miniboom360?tab=repositories