Heralding vs MedPot
Heralding
github.comMedPot
github.comSide by side
| Figure | Heralding | MedPot |
|---|---|---|
| Price from | Free | Free |
| Free plan | Yes | Yes |
| Free trial | — | — |
| Open source | — | — |
| Linux | Yes | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 1 |
| Spec score · Honeypot Software | 7.5 (#12) | 7.5 (#13) |
| Installation | The README gives pip installation instructions and describes running Heralding on a Debian-based system. | The project requires Go 1.17 or newer and provides instructions to run it or compile it into a binary. |
| Intended users | The project describes itself as a honeypot for users who want to collect credentials. | The project describes itself as an HL7 / FHIR honeypot; its README does not specify a narrower user group. |
| Purpose | Heralding is a simple honeypot that collects credentials. | MedPot is a honeypot that emulates HL7 / FHIR. |
Plans
In their own words
Heralding
Heralding is a free, self-hosted network honeypot that collects credentials. It runs on Linux and supports FTP, Telnet, SSH, HTTP, HTTPS, POP3, POP3S, IMAP, IMAPS, SMTP, VNC, PostgreSQL and SOCKS5. When a protocol makes them available, its authentication log records usernames and plaintext passwords. It also writes authentication attempts, session summaries and full session data to CSV and JSON Lines files. Session details can include timestamps, duration, source and destination IP addresses and ports, protocol, authentication attempts and protocol-specific auxiliary data. Session log entries are written after sessions end; authentication entries appear once a password has been transmitted. The README describes pip installation on Debian-based systems and Docker deployment using port mapping. Python 3.7.0 or higher is required. For separate packet captures per session, the README points to Curisoum and says it must be enabled in Heralding.yml. GitHub identifies the project as GPL-3.0 licensed.
MedPot
MedPot is a free, open-source honeypot that emulates HL7 and FHIR services. It is intended for self-hosted use on Linux as an application-level decoy. The project documents running it with Go or a script, compiling it into a binary, and building a Docker container; installation requires Go 1.17 or newer. By default, it listens on port 2575 and writes logs to /var/log/medpot.log. Command-line arguments can change the listening port and log location, and choose between two boot logos. Templates and configuration files are located in /etc/medpot/. An example log record includes a timestamp, port, IP address, message, level, and captured data. Docker is the documented deployment option. The project does not specify a narrower target audience. Its README does not specify support terms, security certifications, or compliance standards.