A Virtual Honeypot Framework honeyd

Category: Entertainment

Presentation Description

No description available.


Presentation Transcript

A Virtual Honeypot Framework----Honeyd: 

A Virtual Honeypot Framework ----Honeyd Zhiyin Liang 2004-10-23


Overview Introduction About Honeyd What’s Honeyd Design and Implementation Applications Relative work Conclusion Discussion


Introduction Security Situations Internet-wide scans for vulnerabilities are more frequent and attacks increased rapidly,while internet security become more and more important It’s necessary to research new attacks and threats Security is an iterative process. Unserstanding motivation Get early warnings of new vulnerabilities Learning by observing attackers Honeypots are virtual doll houses that permit detection and research of new attack methods


Introduction What’s a honeypot Honeypot is a security resource whose value lies in being probed,attacked,or compromised. Network decoy to deter from real targets Network sensor monitoring blackhole Provide IDS functionality All data entering or leaving a honeypot is closely monitored and collected for forensic analysis Honeypots have a low false positive rate All connections are suspicious


Introduction Different types of honeypots: interaction: High-interaction Low-interaction Implement: Physical honeypots Virtual honeypots Physical honeypots have a high deployment cost Low-interaction honeypots do not allow full compromise Honeyd is a low-interaction virtual honeypot

About Honeyd: 

About Honeyd

Honeyd Overview: 

Honeyd Overview Honeyd is a low-interaction virtual honeypot Simulate arbitrary TCP/UDP service IIS, Telnet, pop3… Supports multiple IP addresses Test up to 65536 addresses simultanenously Supports ICMP Virtual machines answer to pings and traceroutes Supports subsystem Supports integration of real system,Service can be proxied and redirected. add windows tcp port 23 proxy ' 23'

Honeyd Overview: 

Honeyd Overview Logging support Simple connection log Compete packet log Configuration via simple configuration file Template: static template, dynamic Template Route topology Support 'include' Limitations Available services still small Does not simulate the whole operating system

Honeyd Design: 

Honeyd Design Considerations Network Data Receiving Simulation honeypots Simulate only network stack behavior Instead of simulating every aspect of an operating system Simulate arbitrary network topologies Security of the honeyd host Limit adversaries to interacting with honeypots only at the network level. An adversary never gains access to a complete system Connection and compromise attempts capturing LOGS

Honeyd Design: 

Honeyd Design Design and Implementation Receiving Network Data Architecture Personality Engine Routing Topology Logging

Receiving Network Data: 

Receiving Network Data Three ways for Honeyd to receives traffic for its virtual honeypots Special route lead data to honeyd host Proxy ARP for honeypots Support Network Tunnels(GRE)

Ex : Arpd: 

Proxy ARP tool: Arpd Arpd is a daemon that listens to ARP requests and answers for IP addresses that are unallocated. Using Arpd in conjunction with Honeyd, it is possible to populate the unallocated address space in a production network with virtual honeypots. Cmd line: $andgt; arpd Ex : Arpd


Architecture Configuration database Store the personalities of the configured network stack. Central packet dispatcher Dispatch Incoming packets to the correct protocol handler. Protocol handles Personality engine Option routing component

Personality Engine: 

Personality Engine Why do we need Personality Engine? Different operating system have different network stack behaviors. Adversaries commonly run fingerprinting tools like Xprobe or Nmap to gather information about a target system. Personality Engine make honeypots appear like real target to a probe. Every packet generated by honeyd passes through the personality engine Introduces operating system specific quirks into packets for Nmap/Xprobe identification. Nmap fingerprint database reference for TCP/UDP connection. Xprobe fingerprint database reference for ICMP request.

Personality Engine: 

Personality Engine Ex:Personalities defined via Nmap fingerprint file Creat windows Set windows personality 'Microsoft windows NT 4.0 SP5-SP6' add windows tcp port 80 'perl scripts/iis-0.95/iisemul8.pl' add windows tcp port 139 open add windows udp port 137 open set windows default tcp action reset set windows default udp action reset bind windows bind windows

Routing Topology: 

Routing Topology Honeyd supports the creation of a complete network topology including routing Simulation of route tree Configure a router entry point Configurable latency and packet loss Simulation of arbitrary route Extension Integrate physical machines into topology Distributed Honeyd via GRE tunneling

Routing Topology Define: 

Routing Topology Define route entry route add net latency 55ms loss 0.1 route add net latency 55ms loss 0.1 route link route link create routerone set routeone personality 'Cisco 7206 router (IOS 11.1(17)' set routerone default tcp action reset set routerone default udp action reset bind routerone bind routerone bind routerone

Logging : 

Logging The Honeyd framework supports several ways of logging network activity. Honeyd creat connection logs to report attempted and completed connections for all protocols. Information also can be gathered from the services themselves and be reported to Honeyd via stderr. Honeyd can be runs in conjunction with a NIDS.


Applications Network Decoys Instrument the unallocated addresses of a production network, confuse and deterr adversaries scaning the production network Conjunction with a NIDS, the resulting network traffic may help in getting early warning of attacks. Detecting and Countering new Worms Deploy a large number of virtual honeypots as gateways in front of a smaller number of high-interaction honeypots. Use Honeyd’s subsystem support to expose regular UNIX applications like OpenSSH to worms.


Applications Spam prevention Spammers abuse two Internet services proxy servers and open mail relays. To understand how spammers operate we use the Honeyd framework to instrument networks with open proxy servers and open mail relays. Use of Honeyd’s GRE tunneling capabilities and tunnel several C-class networks to a central Honeyd host. Using the Honeyd framework, it is possible to instrument networks to automatically capture spam and submit it to collaborative filtering systems.

Relation Work: 

Relation Work Improve Honeyd by creating useful feature additions More feather, More Services scripts,…. TCP/IP stack fingerprinting Researching and defeat fingerprinting tools. Fingerprinting: Xprobe, Nmap, P0f … defeat fingerprinting: Conjunction honeyd with High-interaction honeypots. Honeyfarm… Other virtual honeypot tools DTK(Deception toolkit)




Conclusion Honeyd is a small little program with great effects A virtual honeypot framework An application enables the setup of multiple virtual honeypots with different characteristics and services on a single machine Flexible and extensible, can be applicated in many area of information security.


Conclusion Limitation Open source make it easy to be detect. Available services still small. Does not simulate the whole operating system.



authorStream Live Help