Skip to content

Honeypot

A honeypot is a decoy system, service or application deliberately set up to look like a valuable, vulnerable target so that attackers interact with it instead of real assets. Because no legitimate user should ever touch a honeypot, every connection to it is suspicious and worth investigating. Security teams use honeypots to detect intrusions, divert attackers and study their tools and techniques.

A honeypot is a decoy system, service, or data set up to look like a real target, so that any interaction with it signals an attacker. For smaller decoy artifacts, see our glossary pages on honeytokens and canary tokens.

At a glance

  • What it is: a decoy system, service, or data set up to look like a real target, so any interaction with it signals an attacker.
  • Interaction levels: low-interaction honeypots simulate limited services, mid-interaction honeypots emulate a convincing service without a real operating system, and high-interaction honeypots run real systems.
  • Honeypot vs. honeytoken or canary token: a honeypot is a full decoy system; honeytokens and canary tokens are single pieces of fake data or credentials placed inside real environments.
  • Where it fits: honeypots add to firewalls, EDR, and SIEM rather than replacing them. In the U.S. Navy ANTX FY25 exercise, Acalvio’s automated deception produced 100% true positive alerts and 80% denial of attacker objectives against automated, credential-driven techniques.

Types of honeypots

Honeypots are grouped by interaction level, purpose, functionality, and deployment.

Based on interaction level

Low-interaction honeypots

  • Simulate limited services and functionalities of a system.
  • Easier to deploy and manage.
  • Provide basic information about attack vectors and methods.
  • Example: Honeyd, which simulates network services and devices.

Mid-interaction (medium-interaction) honeypots

  • Emulate a service convincingly enough for an attacker to log in and run commands, without exposing a real operating system.
  • Example: Cowrie, which describes itself as a medium to high interaction SSH and Telnet honeypot.

High-interaction honeypots

  • Offer a full-fledged environment with real operating systems and applications.
  • More complex and resource-intensive.
  • Provide detailed insights into attackers’ behaviors and techniques.
  • Example: A real server set up with monitoring tools to track intrusions.

Based on purpose

Research honeypots

  • Used by researchers to study attack patterns, malware behavior, and new exploits.
  • Not typically used for direct defense but for gathering intelligence.
  • Example: A network of honeypots designed to study botnet behavior.

Production honeypots

  • Deployed within an organization’s network to improve security by detecting intrusions.
  • Act as an early warning system for real threats.
  • Example: An email server set up as a honeypot to detect phishing attempts.

Based on functionality

Malware honeypots

  • Designed to attract and capture malware for analysis.
  • Example: Systems configured to download and execute malware samples safely.

Database honeypots

  • Simulate vulnerable databases to attract SQL injection attacks.
  • Help in understanding database exploitation techniques.

Client honeypots

  • Simulate client-side software like web browsers to detect attacks targeting end users.
  • Example: A browser configured to visit potentially malicious websites to identify drive-by download attacks.

Spam honeypots

  • Used to detect and analyze spam and phishing attacks.
  • Example: Fake email addresses set up to receive and study malicious emails.

Based on deployment

Honeynet

  • Networks of honeypots designed to monitor complex attack patterns.
  • Provide a broader perspective on coordinated attacks.
  • Consist of multiple honeypots with various roles.

Pure honeypots

  • Complete systems with all services and applications running.
  • Offer attackers a real target, providing comprehensive data on their methods.
  • Highly resource-intensive.

Related: honeytokens are a separate, parallel artifact type: fake credentials or data placed inside real systems rather than a full decoy system.

How do honeypots work?

A honeypot works by simulating a vulnerable system, network, or application environment to attract attackers and analyze their behavior.

The honeypot is set up to resemble a legitimate target. This could be a server, application, database, or network service. The honeypot is populated with realistic but fake data, such as user accounts, files, or network traffic, to make it appear as a genuine system. The honeypot is equipped with monitoring tools to capture all incoming and outgoing traffic. This includes network packets, login attempts, and any other interactions. All actions taken by an intruder within the honeypot are logged meticulously. This includes commands executed, files accessed or modified, and any malware dropped.

Once an attacker engages with the honeypot, the system records their methods and techniques. Low-interaction honeypots might only simulate basic responses, while high-interaction honeypots can provide a more realistic environment. Real-time alerts can be configured to notify security personnel of any suspicious activity detected within the honeypot.

The information gathered from honeypots contributes to threat intelligence, helping to identify new vulnerabilities, malware, and attack vectors.

Honeypot network security: where honeypots sit

Where a honeypot sits in the network decides what it detects.

PlacementWhat it catches
Internet-facing, in the DMZScanning, brute-force logins, and exploit attempts. High volume, useful for threat intelligence.
Internal, on user and server segmentsLateral movement and insider activity. The question becomes: why did anything touch an asset no legitimate process should need?
Near high-value assetsAttackers targeting Active Directory, databases, cloud workloads, or OT systems.

Every honeypot must be segmented, with restricted outbound traffic, so an attacker who compromises it cannot use it to reach real systems.

Honeypot software and solutions

Popular open-source honeypot projects include:

ToolWhat it emulates
CowrieA medium to high interaction SSH and Telnet honeypot
DionaeaA malware-capture honeypot, built as a successor to nepenthes
ConpotAn ICS honeypot for studying attacks on industrial control systems
OpenCanaryA multi-protocol network honeypot
T-PotAn all-in-one honeypot platform that bundles many honeypots

Organizations usually move to a commercial deception platform when they need decoys at scale across many segments, automatic refresh so decoys do not go stale and become easy to fingerprint, and integration with the SOC’s SIEM and SOAR workflows.

Benefits of using honeypots

Honeypots offer several benefits in an enterprise network:

Early threat detection: Honeypots can detect malicious activity before it reaches critical systems, including zero-day exploits that are hard to spot through signatures alone.

Analysis: Honeypots reveal attackers’ tactics, techniques, and procedures (TTPs), which improves defenses and threat intelligence.

Vulnerability identification: Honeypots can highlight network weaknesses that need fixing.

Deception: Honeypots can waste attackers’ time and resources, diverting them from actual targets. They can also help detect malicious insiders who interact with them.

Focused analyst time: Because legitimate users have no reason to touch a honeypot, its alerts point analysts toward high-confidence threats, alongside the controls already in place.

Are there any risks when using honeypots?

Honeypots have real risks and challenges:

Detection by attackers: Sophisticated attackers may recognize a honeypot and avoid it, or probe it to learn about the organization’s defenses.

Escalation of attacks: If not properly isolated, a honeypot, especially a high-interaction one, can become a launchpad for attacks on legitimate systems.

Maintenance: High-interaction honeypots require significant time and money to set up, maintain, and monitor.

Data volume: Internet-facing research honeypots can collect large amounts of scanning noise, and analyzing it takes effort.

Performance: Poorly managed honeypots can consume network resources.

Misconfiguration: An incorrectly configured honeypot can expose the organization to unintended vulnerabilities. For more, see our post on the evolution of honeypots.

Trust: Over-reliance on honeypots can breed complacency about other controls.

Learn more about Acalvio’s deception technology

Attackers now automate reconnaissance and credential use, so hand-built, hand-maintained honeypots go stale faster than teams can refresh them. Automation is the entry requirement for deception today.

Acalvio operationalizes and automates the next generation of honeypots, called deceptions, retaining the detection advantages of deception while addressing the operational challenges of traditional honeypots: deploying at scale, keeping decoys fresh so they are harder to fingerprint, and limiting the risk that a decoy is used to compromise real systems. Acalvio’s patented approach, Fluid Deception, combines scale and depth by escalating a deception’s level of interaction dynamically as needed.

The ShadowPlex Preemptive Cybersecurity Platform deploys and maintains dynamic deceptions automatically, mimicking a wide range of enterprise resources. Deception farms and projection points mitigate the risk of compromise, and ShadowPlex runs alongside the existing security stack. Learn more about ShadowPlex Advanced Threat Defense, or read how this approach performed in the U.S. Navy ANTX cyber challenge.

To protect identities, ShadowPlex Identity Protection offers deception-based Identity Threat Detection and Response (ITDR) and identity attack surface management to protect identities and accelerate Zero Trust. Honey accounts and honeytokens detect a wide variety of identity threats.

See how ShadowPlex deception works: schedule a demo →

 

Frequently asked questions

A common example is a decoy internal file server with realistic share names and fake documents that no one uses. Because no legitimate user or application needs it, any login or file access strongly signals an attacker exploring the network.

A honeypot is a single decoy system, while a honeynet is a network of honeypots working together, often with different roles. Observing a honeynet shows how an attacker moves between systems, which a single honeypot cannot reveal.

“Decoy” is a more accurate description than “trap”: a honeypot does not force or induce anyone to act, it simply records who interacts with a system no one should use. Before capturing attacker data, teams should review privacy, data-protection, and monitoring rules with legal counsel, especially for internet-facing honeypots that log traffic from third parties.

A honeypot is a full decoy system, while a honeytoken is a small piece of fake or deliberately misleading information, such as a fake credential or file, placed inside real systems to detect unauthorized access. Canary tokens work the same way as lightweight tripwires that alert on access.

Acalvio, the Ultimate Preemptive Cybersecurity Solution.