Honeypots
A honeypot is a decoy system or resource designed to attract attackers. It appears to be a legitimate, valuable target (a server, database, or file share) but is actually isolated, monitored, and contains no real data. Any access to a honeypot is a high-confidence indicator of malicious activity — legitimate users have no reason to access it.
Types: Low-interaction honeypot: simulates a few services (emulated, not real), minimal risk of attacker using it as a pivot point. High-interaction honeypot: a real system with real services — more realistic, captures more attacker behavior, but riskier if attacker escapes the isolated environment. Honeynets: multiple honeypots in a network simulating an entire environment.
Deployment uses: Early detection of lateral movement — an attacker scanning the network will probe the honeypot. Intelligence gathering — capture attacker tools, techniques, and procedures (TTPs). Delay attackers — time spent on the honeypot is time not spent on real targets.
Broader Deception Technologies
Honey credentials: fake credentials (username/password pairs) planted in files or databases. If someone attempts to use these credentials, it's a strong indicator of compromise. Used to detect credential harvesting attacks and insider threats.
Honey tokens: fake API keys, URLs, or documents that generate alerts when accessed. If a document with embedded tracking pixels is sent to an attacker, the tracking pixel fires when the document is opened — alerting the security team. Dark web monitoring services watch for honey credentials appearing in underground markets.
Honeypot ethical considerations: in production networks, honeypots must be properly isolated to prevent attackers from pivoting to real systems. Legal considerations: passive monitoring of attacker activity is generally acceptable; active entrapment (inducing attacks) may have legal complications. Consult legal counsel before deployment.