Cyber Services / All lessons / CEH — Ethical Hacking / Honeypot Lab Guide for CEH Students

Honeypot Lab Guide for CEH Students

Module 105 of 130 · 6 min read · Free to read

MODULES ↓ Command blocks have a COPY button

This lab explores the deployment and analysis of T-Pot, a powerful, modern, multi-honeypot platform. Unlike simpler honeypots, T-Pot integrates various honeypot daemons (emulating services like SSH, Telnet, web servers, industrial protocols), network intrusion detection (Suricata), and log aggregation/visualization (Elastic Stack). This provides a comprehensive view of attacker activities, making it an excellent learning tool for CEH students.

Why Use a Multi-Honeypot Platform?

  • Broader Attack Surface Simulation: Emulates multiple common targets (SSH, web, SMB, etc.) simultaneously, attracting a wider range of scans and attacks.
  • Rich Data Collection: Captures diverse interaction data, including login attempts (Cowrie), malware samples (Dionaea), network exploits (Honeytrap), web attacks (Elasticpot), and IDS alerts (Suricata).
  • Centralized Logging & Visualization: Utilizes the Elastic Stack (ELK - Elasticsearch, Logstash, Kibana) to aggregate logs from all components and provide powerful dashboards (Kibana) for easy analysis and threat intelligence gathering.
  • Modern Relevance: Reflects more sophisticated deception strategies compared to older, single-service honeypots.

Lab Objectives

  • Understand the components and architecture of the T-Pot platform.
  • Deploy T-Pot using the standard installation method on a dedicated VM.
  • Access the T-Pot web interfaces (Cockpit, Kibana).
  • Interact with the honeypot services from an attacker VM (Kali Linux).
  • Analyze captured attack data using Kibana dashboards.
  • Identify common attack vectors, source IPs, targeted services, and attacker TTPs.

Lab Requirements

  • Two Virtual Machines:
    1. T-Pot Host VM: A dedicated VM with a fresh install of Debian 11/12 or Ubuntu 20.04/22.04 LTS (recommended). Minimum: 8GB RAM (16GB+ recommended), 2+ vCPUs, 128GB+ Disk Space (SSD preferred). This VM needs internet access during installation.
    2. Attacker VM: Your standard Kali Linux VM.
  • Network Configuration: Both VMs must be on the same isolated virtual network (e.g., VirtualBox Host-only Adapter or NAT Network, VMware equivalent). The T-Pot VM's IP address needs to be reachable from the Kali VM. Do NOT expose the T-Pot VM directly to the internet or your production network without extreme caution and security measures (firewalling, segmentation).
  • Basic Linux & Networking Skills: Command line proficiency, understanding IP addresses/subnets, SSH.
  • Time: T-Pot installation can take a significant amount of time (30-60+ minutes depending on hardware and network speed).
CRITICAL SECURITY WARNING: T-Pot is designed to be attacked. Deploy it **only** on a dedicated, isolated virtual machine on a network segment completely separated from any sensitive systems or production environments. A misconfigured or compromised T-Pot *could* potentially be used as a pivot point. **ISOLATE YOUR LAB ENVIRONMENT!**

Lab Steps: Deploying T-Pot

T-Pot Installation via Script
  1. 1. Prepare T-Pot Host VM

    Boot up your fresh Debian/Ubuntu VM dedicated for T-Pot. Log in and open a terminal.

  2. 2. Update System & Install Git

    Ensure the system is up-to-date and `git` is installed.

    sudo apt update && sudo apt upgrade -y
    sudo apt install -y git
  3. 3. Clone T-Pot Repository

    Clone the official T-Pot repository from GitHub.

    git clone https://github.com/telekom-security/tpotce.git
  4. 4. Run Installation Script

    Navigate into the cloned directory and run the installer script.

    cd tpotce
    sudo ./install.sh

    The script will guide you through the installation process:

    • Choose Installation Type: Select the edition. For this lab, choose `Standard` (which includes multiple honeypots and the ELK stack).
    • Set Username/Password: You will be prompted to create a username and a strong password for accessing the T-Pot web UI (Cockpit/Kibana) and SSH. **Record these credentials securely!**
    • Confirmation:** Review the settings and confirm to proceed.

    The installation will download required packages, configure Docker containers, and set up the system. This will take considerable time. Monitor the progress in the terminal.

  5. 5. Reboot and Initial Access

    Once the installation completes successfully, the script will prompt you to reboot.

    sudo reboot

    After rebooting, T-Pot will be running. You need the IP address of the T-Pot VM (ip addr).

    • Web Admin UI (Cockpit): Access via `https://T-POT_IP:64297` (Accept the self-signed certificate warning). Log in with the user/password created during installation.
    • Kibana Dashboard: Also accessible via `https://T-POT_IP:64297` through the Cockpit interface or directly (check Cockpit links).
    • SSH Access: Use the user/password created during installation: `ssh your_user@T-POT_IP -p 64295` (Note the non-standard SSH port).

Lab Steps: Interacting with the Honeypot

Generating Attack Data (from Kali VM)

From your separate Kali Linux VM (on the same isolated network), perform reconnaissance and interaction attempts against the T-Pot VM's IP address (T-POT_IP).

  1. 1. Basic Nmap Scan

    Scan for common open ports. T-Pot exposes many!

    sudo nmap -sS -F T-POT_IP
  2. 2. Service Version Scan

    Scan specific interesting ports found.

    sudo nmap -sV -p 21,22,23,80,135,443,445 T-POT_IP # Example ports
  3. 3. Attempt SSH/Telnet Login (Common Credentials)

    Try logging in with default/weak credentials (these will likely be captured by Cowrie honeypot).

    ssh root@T-POT_IP # Try password 'root', 'password', 'toor', etc.
    telnet T-POT_IP # Try common logins like admin/admin, root/root
  4. 4. Probe Web Server

    Access the HTTP/HTTPS ports in a browser or use curl.

    curl http://T-POT_IP
    curl -k https://T-POT_IP # -k for self-signed certs
  5. 5. Run Vulnerability Scan (Optional & Careful)

    A Nikto scan will generate lots of web-related logs.

    nikto -h http://T-POT_IP

Lab Steps: Analyzing Captured Data

Using the Kibana Dashboard

The primary way to analyze T-Pot data is through the Kibana web interface.

  1. Access Kibana: Log into the T-Pot Admin UI (`https://T-POT_IP:64297`) and find the link to Kibana, or access it directly if the port mapping is known (often also port 64297, but check Cockpit). Log in using the credentials created during installation.
  2. Explore Dashboards: Navigate the dashboards using the left-hand menu (often under "Analytics" or "Dashboard"). Key dashboards include:
    • T-Pot Overview: High-level summary of attacks, sources, targets.
    • Cowrie: Details on SSH/Telnet attempts, including usernames, passwords tried, source IPs, and commands executed by successful logins (if any).
    • Dionaea: Information on connections to SMB/HTTP/FTP etc., often showing malware download attempts (hashes may be available).
    • Elasticpot / Honeytrap / etc.: Dashboards for other specific honeypots included in your T-Pot edition.
    • Suricata: Network Intrusion Detection alerts triggered by the traffic hitting T-Pot.
    • GeoIP Visualizations: Maps showing the geographic origin of source IPs.
  3. Analyze the Data: Look for patterns and specific events:
    • Source IPs: Where are the connections originating from? Use GeoIP data. Are there repeat offenders?
    • Targeted Services: Which honeypot services (ports) are receiving the most traffic?
    • Credentials (Cowrie): What usernames/passwords are commonly tried in brute-force attacks?
    • Commands Executed (Cowrie): If an attacker "successfully" logs in, what commands do they run first (`uname -a`, `wget`, `curl`, etc.)?
    • Malware Hashes (Dionaea): Can you look up captured file hashes on VirusTotal?
    • IDS Alerts (Suricata): What kind of malicious signatures are matching the traffic?
    • Timelines: When are attacks most frequent?
  4. Filtering and Searching: Use Kibana's powerful search bar and filtering capabilities (KQL - Kibana Query Language) to drill down into specific events, time ranges, source IPs, or usernames.

Advanced: Raw Logs

For deeper analysis, you can SSH into the T-Pot server (port 64295) and inspect the raw log files, typically stored within Docker volumes (locations may vary, consult T-Pot documentation).

Conclusion

Deploying T-Pot provides a rich, interactive environment for observing real-world scanning and attack techniques safely. By analyzing the aggregated data in Kibana, you gain valuable insights into common attacker TTPs, the importance of monitoring, and how different types of honeypots capture different kinds of malicious activity. This practical experience directly complements the theoretical knowledge required for the CEH certification.

Modules (130) ← CEH — Ethical Hacking