
Offensive security platform that automates attack surface discovery and vulnerability management
Automate the recon, keep your time for the part that actually needs a hacker
Think about how an assessment really starts. You gather public information about the target. You discover its hosts, enumerate their ports and identify the services behind them. Then you run a more specific tool against each service, scan for known vulnerabilities and look for public exploits. It's almost the same sequence every time, it takes hours of watching terminals, waiting for executions to finish and copying results from one tool into the next one, and none of it is the part where your skills make the difference.
Rekono does that work for you. You define a target and it chains the hacking tools by itself, what one tool discovers becomes the input of the ones that come next. So, the ports found are scanned by the right tools, the technologies detected are checked for known vulnerabilities, and the vulnerabilities are matched against public exploit databases. Everything lands in one place, deduplicated, linked to the host and the port where it lives, and enriched with the information that you would otherwise look up by hand.
It's a platform, not a script. Projects for your engagements, roles for your team, notes to write down what you are thinking, collaborative triage, automatic resolution of findings, metrics, reports for your deliverables, and scheduled or repeated scans to keep watching an attack surface over time.
Best of all, you don't have to wait in front of it. Rekono notifies you by email or Telegram as soon as something worth your attention shows up, so when you sit down, you already have an attack surface mapped, prioritized and full of leads.
docker compose up -d --scale executions-worker=5
Go to https://127.0.0.1 and log in with rekono:rekono. Change that password the first time you log in
Upgrading from Rekono 1.x? Read the upgrade guide first. The database migration runs on its own, but there are things that you should know
Rekono supports the execution of 19 hacking tools:
The findings detected by the hacking tools are nothing if we don't enrich them with information from external sources or if we don't share them with the right people at the right time. This is why Rekono supports multiple integrations:
Join our community in Discord and follow us on
.
Rekono is an open source project with only one maintainer, working in his free time and with no external funds. You can support the project or simply appreciate our work with your donations on Ko-fi or
Buy me a Coffee.
Rekono is open to suggestions and improvements, don't hesitate to create an issue or contribute something cool to the project. Check our CONTRIBUTING guidelines
Do you want to know more? The Rekono name comes from Esperanto and it means recon
Rekono is licensed under the GNU GENERAL PUBLIC LICENSE Version 3
Rekono is intended only for authorized security testing, education and research, so you must have explicit permission to test every target that you add to it. You are solely responsible for the use that you make of the project, which its authors, maintainers and contributors provide as is, without warranty of any kind, and for which they accept no liability for any damage or legal consequence arising from its misuse.
| Integration | Type | Purpose |
|---|
| DefectDojo | Vulnerability Management | Findings detected by Rekono executions are shipped to DefectDojo, to make their management and reporting easier |
| Virus Total | Malware Analysis | Identified hosts are verified in VirusTotal to get metadata about their reputation and malware analysis conclusions |
| HackTricks | Hacking Wiki | The findings that have a related page in HackTricks will be linked to it, for auditors to get more information easily |
| CVE Crowd | Trending CVEs | Detected CVEs are marked as trending if CVE Crowd identifies them as so |
| FIRST EPSS | EPSS provider | We get EPSS scores and percentiles for the detected CVEs from this source |
| NVD NIST | CVE provider | We get updated information for the detected CVEs from this source |
| VulnCheck NVD++ | CVE provider | We get updated information for the detected CVEs from this source |
| OSV | CVE provider | We get updated information for the detected CVEs from this source |
| GHSA | CVE provider | We get updated information for the detected CVEs from this source |
| EU Vulnerability Database | CVE provider | We get updated information for the detected CVEs from this source |
| SMTP | Notifications | Notifications about the user account, executions, alerts, etc |
| Telegram | Notifications | Notifications about executions and alerts |