Reckoning is an orchestrator designed for offensive operations, reconnaissance, and monitoring. However, its modular nature allows you to create workflows for any and all types of tools accessible via the command line. Naturally, its development focuses on facilitating the creation of Red Team, Penetration Testing, and Threat Intelligence operations. Share your workflow configurations, tools, wordlists, etc. with the community.
- Clone this repo -
git clone https://github.com/rf-peixoto/reckoning - Install -
install.sh - Start -
start.sh - Point your browser -
http://localhost:5000
- Go to the Settings page.
- Define the name, path, arguments, and update command.
- Reckoning uses a string substitution system accessible to all tools in a running workflow.
{0}is equivalent to the initial domain specified at the start of execution. The outputs of each tool can be accessed by their number in the workflow order:{1},{2},{3}...
- Go to the Settings page.
- To avoid having to type
/usr/share/seclists...for every command, you can define names for wordlists by choosing their name and path. This way, to call the wordlist in a command, simply type{name}. - You can use this mechanism to define API keys. It's a simple string substitution; just set the PATH value as your key or token.
- Reckoning currently has three workflow execution modes:
- Run Once (default): Executes only once.
- Recurring: Runs continuously every N minutes.
- Run N Times: executes at intervals of N minutes until N(2) executions are completed.
- Choose which tools to use and in what order. You can completely change the options or use the pre-configured base on the Settings page. You can also set a color for organizational purposes.
- Follow the progress on the Executions page.
Reckoning is sponsored by: the-street.xyz, a private forum for cybersecurity, threat intelligence, and cipherpunk culture. Feel free to support us too. Brazillian users can support us via apoia.se.
Bitcoin [BTC] bc1qflkwmca89fzw9gfpg6dkf0es9ctnm2ktcq03dp