Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
A honeynet is a whole decoy network of realistic systems, instrumented so that every action an intruder takes is recorded. It buys intelligence, and it carries real risk.

What Is a Honeynet?
A honeypot is one decoy system. A honeynet is a network of them — servers, workstations, a directory service, perhaps a database and a file share — built to look like a real environment and instrumented so that every packet, keystroke, and file change is recorded. Nothing in it is production, so any interaction at all is unauthorised by definition. The Honeynet Project, founded by Lance Spitzner in 1999, established the architecture and most of the terminology still in use.
A single decoy service tells you that someone scanned a port and perhaps tried a credential. It cannot show you what an intruder does once inside, because there is nowhere to go. A honeynet gives an attacker room to behave normally: to enumerate the domain, move between hosts, escalate, stage data, and attempt exfiltration. That is where the intelligence is. You learn the tooling, the command-and-control infrastructure, the dwell pattern, and the specific techniques — all of which map directly onto MITRE ATT&CK and can be turned into detection rules for the real estate.
The Honeynet Project framed honeynet design around two obligations, and both still define a competent build.
Data control. The honeynet must not become a platform for attacking someone else. A compromised decoy with unrestricted outbound access is a liability you have created deliberately, and in the UK it is one you may struggle to defend afterwards. The standard approach is a gateway, historically called a honeywall, that permits enough outbound connectivity for the attacker to behave naturally while rate-limiting connections, blocking or mangling recognisable outbound exploit traffic, and cutting the environment off entirely above a threshold.
Data capture. Logging must happen where the attacker cannot see or alter it. That means full packet capture at the gateway, flow records, and host instrumentation that reports out of band — the Sebek kernel module was the classic tool, with modern deployments using hypervisor-level introspection or an EDR agent reporting to a collector the decoy cannot reach.
Low-interaction decoys emulate services and are safe but shallow; an attacker usually recognises them within a few commands. High-interaction decoys are real operating systems with real software, which is what makes the observations worth having and what makes the deployment risky.
Practical tooling has improved considerably. T-Pot bundles more than a dozen honeypots with an Elasticsearch stack and is a reasonable starting point. Cowrie records full SSH and Telnet sessions, Dionaea collects malware samples, Conpot emulates industrial protocols for OT environments, and OpenCanary provides lightweight internal decoys. Commercial deception platforms handle the deployment and lifecycle management that makes a honeynet sustainable rather than a project that decays after three months.
A honeynet is deliberately vulnerable infrastructure you have connected to a network. If an attacker pivots out of it into production, you have manufactured your own breach. Isolate it at layer two and layer three, give it its own address space and its own internet connection or a strictly filtered path, and never let it hold credentials that work anywhere real.
There is also a legal and regulatory dimension that UK organisations should consider before deployment. You may capture personal data belonging to third parties, including attackers, which engages UK GDPR and requires a lawful basis and a data protection impact assessment. If your decoys are used to attack others, questions under the Computer Misuse Act may follow. Get the design reviewed by legal counsel and document the decision — this is not a reason to avoid honeynets, but it is a reason not to build one quietly over a weekend.
Honeynets reward organisations with a mature SOC, a threat intelligence function, and the analyst time to study what comes back. For everyone else, canary tokens and a handful of internal decoy hosts deliver most of the detection value for a fraction of the effort and almost none of the risk. Start there, and build the full environment only when you have a specific question you want answered.
If you want to see how an attacker moves through your real network rather than a decoy one, our Red Team Services answer that directly.
A honeypot is a single decoy system or service. A honeynet is an entire decoy network containing multiple hosts, services, and often a directory, with a controlling gateway that manages outbound traffic and captures data. The difference matters because an intruder can only demonstrate lateral movement, privilege escalation, and staging behaviour if there is somewhere to move to.
That is the principal risk, and preventing it is the data control requirement. The gateway must rate-limit outbound connections, block recognisable outbound attack traffic, and be able to isolate the environment entirely. Without those controls you have created attack infrastructure on your own address space, with consequences that are both reputational and potentially legal.
Running decoy systems on your own infrastructure is lawful, but two areas need attention. Capturing traffic may collect personal data, which engages UK GDPR and generally warrants a data protection impact assessment and a documented lawful basis. If your decoys are used to attack third parties, Computer Misuse Act questions can arise. Obtain legal review before deployment.
Usually not as a first step. Detection and response tooling covers the production estate, which is where attacks actually matter. A honeynet answers a different question: what do intruders do when they think nobody is watching. That is valuable for a threat intelligence function with analyst capacity, and largely wasted effort for a team still tuning its core alerting.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.