Conpot vs Heralding
Conpot
github.comHeralding
github.comSide by side
| Figure | Conpot | Heralding |
|---|---|---|
| Price from | — | Free |
| Free plan | — | Yes |
| Free trial | — | — |
| Open source | — | — |
| Linux | Yes | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 0 | 1 |
| Spec score · Honeypot Software | 7.3 (#15) | 7.5 (#12) |
| Intended users | The project describes its purpose as gathering intelligence on attacks against industrial control systems, making it relevant to ICS security research and honeypot operators. | The project describes itself as a honeypot for users who want to collect credentials. |
| License | The GitHub repository identifies the project license as GPL-2.0. | GitHub identifies the project as GPL-3.0 licensed. |
| Purpose | Conpot is an ICS honeypot designed to collect intelligence about adversaries targeting industrial control systems. | Heralding is a simple honeypot that collects credentials. |
Plans
In their own words
Conpot
Conpot is a free, open-source, self-hosted honeypot for gathering intelligence about attacks against industrial control systems. Its default profile emulates a Siemens S7-200 CPU with expansion modules and exposes Modbus, HTTP, SNMP, and S7comm. The project is a Linux/POSIX console application, with developers listed as its intended audience. Deployment is available through Docker or host installation from PyPI or source; the host guide requires Python 3.10 or newer. Operators can create templates and change ports. ConpotFS proxies files from a controlled location so protocol operations do not alter actual filesystem permissions. HPFeeds support is included but disabled by default, and shared data is raw JSON. Accessing shared data requires an HPFriends account, accepting the share, and creating an authentication key. The project uses GPL-2.0, provides no warranty, and links documentation, a FAQ, and GitHub issues.
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.