Skip to content

SecurityWard/honeyman-Project

Repository files navigation

Honeyman Project - Advanced Multi-Vector Threat Detection System

Honeyman Project Logo

A comprehensive honeypot and threat detection system designed for real-time monitoring of wireless, network, and web-based attacks. Built for deployment on resource-constrained environments like Raspberry Pi while maintaining enterprise-grade threat intelligence capabilities.

🎯 Project Overview

The Honeyman Project is an advanced cybersecurity monitoring platform that combines multiple detection vectors to identify, analyze, and correlate cyber threats in real-time. The system integrates honeypot services, wireless protocol monitoring, and behavioral analysis to provide comprehensive threat intelligence.

Key Features

  • Multi-Vector Threat Detection: WiFi, Bluetooth LE, AirDrop, USB, and web-based attack monitoring
  • Advanced Correlation: Cross-protocol threat correlation and behavioral analysis
  • Real-time Dashboard: Professional web-based threat visualization and analytics
  • Resource Optimized: Designed for Raspberry Pi deployment with intelligent resource management
  • Enterprise Integration: APIs for SIEM integration and threat intelligence sharing
  • Noise Reduction: Advanced filtering achieving 99% false positive reduction

πŸ—οΈ Architecture

graph TB
    subgraph "Detection Layer"
        BLE[BLE Enhanced Detector]
        WiFi[WiFi Enhanced Detector] 
        AirDrop[AirDrop Threat Detector]
        USB[USB Detection System]
        Web[OpenCanary Honeypots]
    end
    
    subgraph "Processing Layer"
        Multi[Multi-Vector Correlator]
        Filter[Noise Filter & Aggregator]
        Forwarder[Data Forwarder]
    end
    
    subgraph "Storage Layer"
        ES[Elasticsearch]
        Kibana[Kibana Dashboard]
    end
    
    subgraph "VPS Infrastructure"
        API[Dashboard API Server]
        Dashboard[Enhanced Dashboard]
        Intel[Threat Intelligence]
    end
    
    subgraph "Services Layer"
        SSH[SSH Honeypot]
        FTP[FTP Honeypot]
        SMB[SMB Honeypot]
        Portal[Corporate Web Portal]
        Canary[Canary Documents]
    end
    
    BLE --> Multi
    WiFi --> Multi
    AirDrop --> Multi
    USB --> Multi
    Web --> Multi
    
    Multi --> Filter
    Filter --> Forwarder
    Filter --> ES
    
    ES --> Kibana
    Forwarder --> API
    API --> Dashboard
    API --> Intel
    
    SSH --> ES
    FTP --> ES
    SMB --> ES
    Portal --> ES
    Canary --> ES
    
    style BLE fill:#e1f5fe
    style WiFi fill:#e1f5fe
    style AirDrop fill:#e1f5fe
    style USB fill:#e1f5fe
    style Web fill:#e1f5fe
    style Dashboard fill:#f3e5f5
    style API fill:#f3e5f5
Loading

πŸ“¦ Installation

Prerequisites

  • Raspberry Pi 4 (8GB RAM recommended) or compatible Linux system
  • Docker and Docker Compose
  • Python 3.8+
  • Node.js 16+
  • WiFi adapter with monitor mode support
  • Bluetooth adapter

Quick Start

  1. Clone the repository

    git clone <repository-url>
    cd honeypot-minimal
  2. Install dependencies

    sudo apt update
    sudo apt install -y python3-pip docker.io docker-compose nodejs npm
    pip3 install -r requirements.txt
  3. Start core services

    docker-compose up -d
  4. Deploy detection systems

    ./honeypot-manager.sh start-all
  5. Configure systemd services

    ./install-systemd-services.sh
    sudo systemctl enable honeypot.target
    sudo systemctl start honeypot.target

VPS Dashboard Deployment

  1. Configure VPS environment

    # On your VPS
    git clone <repository-url>
    cd honeypot-minimal/dashboard
    npm install
  2. Set environment variables

    export HOSTINGER_API_KEY="your-api-key"
    export DASHBOARD_URL="https://your-domain.com"
  3. Start dashboard server

    node api/server.js

πŸ”§ Configuration

Core Configuration Files

  • opencanary.conf - Honeypot service configuration
  • log_config.json - Logging and filtering configuration
  • wifi_whitelist.json - Trusted network whitelist
  • docker-compose.yml - Container orchestration

Detection System Configuration

Each detection system can be configured through its respective configuration file:

{
  "max_log_size_mb": 50,
  "max_log_files": 5,
  "compression_enabled": true,
  "noise_filters": {
    "duplicate_threshold_seconds": 300,
    "min_threat_score": 0.3,
    "rate_limit_per_hour": {
      "weak_security": 5,
      "hidden_ssid": 3,
      "suspicious_ssid": 10
    }
  }
}

πŸš€ Usage

Starting the System

# Start all detection systems
sudo systemctl start honeypot.target

# Check system status
sudo systemctl status honeypot.target

# View real-time logs
sudo journalctl -f -u honeypot-*

Accessing Dashboards

API Endpoints

  • GET /api/threats/stats - Threat statistics
  • GET /api/threats/recent - Recent threats
  • GET /api/threats/correlations - Threat correlations
  • GET /api/threats/intelligence - Threat intelligence feed
  • POST /api/honeypot/data - Submit threat data

πŸ“Š Monitoring & Analytics

Real-time Metrics

The system tracks comprehensive metrics including:

  • Threat Velocity: Threats detected per hour
  • Attack Sources: Unique attacking entities
  • Threat Severity Distribution: Critical, High, Medium, Low
  • Protocol Analysis: Attack vectors by protocol type
  • Geographic Analysis: Attack source estimation

Correlation Analysis

Advanced correlation features include:

  • Cross-Protocol Correlation: Linking attacks across WiFi, BLE, and web vectors
  • Temporal Analysis: Time-based attack pattern recognition
  • Behavioral Profiling: Device and network behavior analysis
  • Threat Intelligence: IOC extraction and threat actor identification

πŸ” Detection Capabilities

What the System WILL Detect

WiFi Threats

  • Evil twin access points
  • Beacon flooding attacks
  • Deauthentication attacks
  • WEP/WPS vulnerabilities
  • Suspicious SSID patterns
  • Signal manipulation attacks

Bluetooth LE Threats

  • Flipper Zero and similar devices
  • Suspicious BLE beaconing patterns
  • Device fingerprint spoofing
  • Proximity-based attacks
  • Service enumeration attempts
  • MAC address randomization abuse

AirDrop Threats

  • Suspicious AirDrop service names
  • Generic device name spoofing
  • TXT record manipulation
  • Rapid service announcements (attack patterns)
  • Unusual port usage detection
  • Evil twin AirDrop services

Web & Network Threats

  • Credential harvesting attempts
  • Port scanning activities
  • Service enumeration
  • Directory traversal attempts
  • Canary document access
  • SSH/FTP/SMB brute force

USB Threats

  • Unknown device insertion
  • Mass storage enumeration
  • HID device emulation
  • Device fingerprint analysis

What the System WON'T Detect

  • Advanced Persistent Threats (APTs): Complex, multi-stage attacks
  • Zero-day Exploits: Unknown vulnerabilities and exploits
  • Encrypted Traffic Analysis: Deep packet inspection of encrypted data
  • Social Engineering: Human-based attack vectors
  • Physical Security Bypasses: Physical access control circumvention
  • Memory-based Attacks: Rootkits, memory corruption exploits
  • Application-layer Vulnerabilities: Specific software vulnerabilities

πŸ“ˆ Performance & Resource Usage

Resource Requirements

  • Minimum: 4GB RAM, 32GB storage, 1GB/month bandwidth
  • Recommended: 8GB RAM, 100GB storage, 5GB/month bandwidth
  • CPU Usage: ~15-25% average on Raspberry Pi 4
  • Memory Usage: ~3-4GB active, ~1-2GB cached
  • Network Usage: ~100MB/day logging, ~500MB/day with packet capture

Optimization Features

  • Intelligent Filtering: 99% noise reduction
  • Resource Management: Dynamic memory allocation
  • Compression: Log compression and rotation
  • Rate Limiting: API and processing rate controls
  • Efficient Storage: Elasticsearch optimization

πŸ”’ Security Considerations

Deployment Security

  1. Network Isolation: Deploy in isolated network segment
  2. Access Control: Restrict API access with authentication
  3. Encryption: Use TLS for all external communications
  4. Monitoring: Monitor the monitoring system itself
  5. Updates: Regular system and dependency updates

Data Privacy

  • No personal data collection beyond attack metadata
  • Configurable data retention policies
  • Anonymization of non-essential identifying information
  • Compliance with local data protection regulations

πŸ›£οΈ Roadmap

Phase 1: Core Enhancement (Completed)

  • βœ… Multi-vector detection integration
  • βœ… Advanced correlation engine
  • βœ… Professional dashboard interface
  • βœ… Noise reduction optimization

Phase 2: Intelligence Integration (In Progress)

  • πŸ”„ Machine learning threat classification
  • πŸ”„ Threat intelligence feed integration
  • πŸ”„ Automated IOC generation
  • πŸ”„ Advanced behavioral analysis

Phase 3: Enterprise Features (Planned)

  • πŸ“‹ SIEM integration modules
  • πŸ“‹ Automated incident response
  • πŸ“‹ Threat hunting capabilities
  • πŸ“‹ Multi-sensor deployment management

Phase 4: Advanced Analytics (Future)

  • πŸ“‹ Predictive threat modeling
  • πŸ“‹ Attribution analysis
  • πŸ“‹ Campaign tracking
  • πŸ“‹ Advanced visualization

🀝 Contributing

  1. Fork the repository
  2. Create a feature branch: git checkout -b feature-name
  3. Commit changes: git commit -am 'Add feature'
  4. Push to branch: git push origin feature-name
  5. Submit a pull request

πŸ“„ License

This project is licensed under the MIT License - see the LICENSE file for details.

⚠️ Disclaimer

This system is designed for defensive security purposes only. Use responsibly and in compliance with applicable laws and regulations. The authors are not responsible for misuse or any legal implications of deployment.

πŸ“ž Support

  • Documentation: See /docs directory for detailed guides
  • Issues: Report issues via GitHub Issues
  • Community: Join our community discussions
  • Security: Report security issues privately to [email protected]

Honeyman Project - Building Trust Through Advanced Threat Detection

About

No description, website, or topics provided.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Contributors 2

  •  
  •