AGENT SKILL

implementing-network-deception-with-honeypots

Deploy and manage network honeypots using OpenCanary, T-Pot, or Cowrie to detect unauthorized access, lateral movement, and attacker reconnaissance.

License 许可
Apache-2.0
最近更新
2026-09-11
Stars
★ 0
Forks
0

01 前言 Front Matter

name
implementing-network-deception-with-honeypots
tags
[ "deception", "honeypot", "opencanary", "cowrie", "t-pot", "detection", "lateral-movement", "network-security" ]
author
mahipal
domain
cybersecurity
license
Apache-2.0
version
1.0
nist_csf
[ "DE.CM-01", "DE.AE-06", "PR.IR-01" ]
subdomain
deception-technology
description
Deploy and manage network honeypots using OpenCanary, T-Pot, or Cowrie to detect unauthorized access, lateral movement, and attacker reconnaissance.
mitre_attack
[ "T1078", "T1190", "T1059", "T1021", "T1550" ]

02 资源文件 3

03 SKILL.md 正文

Implementing Network Deception with Honeypots

When to Use

  • When deploying deception technology to detect lateral movement
  • To create early warning indicators for network intrusion
  • During security architecture design to add detection depth
  • When monitoring for unauthorized internal scanning or credential theft
  • To gather threat intelligence on attacker techniques and tools

Prerequisites

  • Linux server or VM for honeypot deployment (Ubuntu 22.04+ recommended)
  • Python 3.8+ with pip for OpenCanary installation
  • Docker for T-Pot or containerized deployment
  • Network segment with appropriate VLAN configuration
  • SIEM integration for alert forwarding (syslog, webhook, or file-based)
  • Firewall rules allowing inbound connections to honeypot services

Workflow

  1. Plan Deployment: Select honeypot types and network placement strategy.
  2. Install Honeypot: Deploy OpenCanary, Cowrie, or T-Pot on dedicated host.
  3. Configure Services: Enable emulated services (SSH, HTTP, SMB, FTP, RDP).
  4. Set Up Alerting: Configure log forwarding to SIEM and alert channels.
  5. Deploy Canary Tokens: Place credential files, shares, and DNS entries.
  6. Monitor Interactions: Analyze honeypot logs for attacker activity.
  7. Tune and Maintain: Update configurations based on detection results.

Key Concepts

Concept Description
OpenCanary Lightweight Python honeypot with modular service emulation
Cowrie Medium-interaction SSH/Telnet honeypot capturing commands
T-Pot Multi-honeypot platform with ELK stack visualization
Canary Token Tripwire credential or file that alerts when accessed
Low-Interaction Emulates services at protocol level without full OS
High-Interaction Full OS honeypot capturing complete attacker sessions

Tools & Systems

Tool Purpose
OpenCanary Modular honeypot daemon with service emulation
Cowrie SSH/Telnet honeypot with session recording
T-Pot All-in-one multi-honeypot platform
Dionaea Malware-capturing honeypot for exploit detection
Splunk/Elastic SIEM for honeypot alert aggregation

Output Format

Alert: HONEYPOT-[SERVICE]-[DATE]-[SEQ]
Honeypot: [Hostname/IP]
Service: [SSH/HTTP/SMB/FTP/RDP]
Source IP: [Attacker IP]
Interaction: [Login attempt/Port scan/File access]
Credentials Used: [Username:Password if applicable]
Commands Executed: [For SSH honeypots]
Risk Level: [Critical/High/Medium/Low]

04 同仓库更多 Skills

NeelakshSaxena
NeelakshSaxena/Vayu

runpodctl

Runpod CLI for managing GPU/CPU workloads from the terminal — pods, serverless endpoints, templates, network volumes, Hub deploys, models, SSH, and file transfer (send/receive). Use for terminal/CI/scripting, Hub browse/deploy, SSH setup, `doctor`, or when the Runpod MCP tools are not connected. For structured tool calls in an MCP-enabled session, prefer runpod-mcp.

★ 0
NeelakshSaxena
NeelakshSaxena/Vayu

runpod

Start here for any Runpod task — running GPU/CPU pods, deploying serverless endpoints, templates, network volumes, building images, or understanding how Runpod works. Routes to the right skill (runpod-mcp, runpodctl, flash, companion-clis, runpod-usage, runpod-templates, runpod-migrate) and indexes two dozen live-verified end-to-end examples (golden paths) — use it when the lane is unclear, and for any multi-step or provisioning task even when it is not.

★ 0
NeelakshSaxena
NeelakshSaxena/Vayu

runpod-usage

How Runpod works and how to work it — pods vs serverless, GPU/VRAM selection, storage, building a container, networking, plus the agentic pod development loop (provision → ssh-exec → set up → poll readiness) and on-pod install hygiene (uv/apt). Use to answer "how does X work", "which GPU", "how do I build a container", or "how do I stand up a workload on a pod". Guidance, not a tool — execute with runpodctl, runpod-mcp, or flash.

★ 0
NeelakshSaxena
NeelakshSaxena/Vayu

runpod-templates

Runpod's official prebuilt pod templates (ComfyUI, PyTorch, and others): what each image ships, which ports and paths it uses, how to pick one, how to pin a version, and what is missing on first boot. Use when a task says "run <X> on a pod" and an official template already covers it, instead of building an image — and when a user needs help with or wants to fix something about a Runpod template they are already running (won't boot, can't reach the UI, missing models, wrong CUDA line, broken ComfyUI workflow metadata on imported workflows): start here and route onward. Deploy with runpodctl or runpod-mcp; end-to-end walkthroughs live in the runpod router's golden paths.

★ 0
NeelakshSaxena
NeelakshSaxena/Vayu

runpod-migrate

Migrate a codebase from the Runpod GraphQL API or REST v1 to REST v2 — inventory which parts use which API version, rewrite the call sites, flag breaking changes, and verify. Use when someone asks to move to v2, asks what v2 would change, or asks which Runpod API their code is on. For managing infrastructure rather than migrating code, use runpod-mcp or runpodctl.

★ 0
NeelakshSaxena
NeelakshSaxena/Vayu

runpod-mcp

Manage Runpod infrastructure — pods, serverless endpoints, jobs, templates, network volumes, container-registry auth, GPU/CPU catalog, and billing — via the Runpod MCP server's structured tool calls. Use when the Runpod MCP tools (create-pod, list-endpoints, …) are connected in this session, or to connect them (hosted OAuth or local npx). Prefer this over runpodctl for plain infra CRUD when MCP is available; use runpodctl for the terminal, file transfer, or SSH setup.

★ 0