Quick Start
Panguard Trap requires a Pro plan or above. Status, profile, and intelligence viewing are available on all plans.
How Honeypots Work
A honeypot is a deliberately exposed fake service. It looks real to an attacker but is completely isolated from your actual infrastructure. Any interaction with a honeypot is inherently suspicious because no legitimate user would connect to it. Panguard Trap goes beyond simple connection logging:- Captures credentials — records every username/password combination attempted
- Logs commands — tracks all commands executed after a successful (fake) login
- Identifies tools — detects attacker tooling (Hydra, Metasploit, custom scripts)
- Profiles attackers — classifies skill level and intent using behavioral analysis
- Shares intelligence — feeds captured IoCs into Guard and Threat Cloud
Architecture
Key Capabilities
| Capability | Details |
|---|---|
| Honeypot types | 8 service emulators (SSH, HTTP, FTP, SMB, MySQL, RDP, Telnet, Redis) |
| Attacker profiling | Skill classification (Script Kiddie, Advanced, APT) |
| Credential capture | All attempted usernames and passwords logged |
| Command logging | Full session transcripts for interactive services |
| Threat Cloud feed | Anonymized attacker data shared with collective intelligence |
| Guard integration | Attacker IPs auto-added to Guard block list |
Integration with Guard and Threat Cloud
Guard Integration
- Attacker IPs from Trap are automatically added to Guard’s block list
- Attack patterns are converted into Sigma rule candidates
- Captured IoCs are added to the local threat intelligence database
Threat Cloud Integration
Safety
- Honeypot ports must differ from real service ports (e.g., SSH honeypot on 2222, not 22)
- Honeypots are fully isolated — attackers cannot access your real system
- Each honeypot has memory and CPU resource limits to prevent abuse