HoneyClient::Manager::FW

HoneyClient::Manager::FW is a Perl module to remotely handle firewall rule/chain creation.
Download

HoneyClient::Manager::FW Ranking & Summary

Advertisement

  • Rating:
  • License:
  • Perl Artistic License
  • Price:
  • FREE
  • Publisher Name:
  • JD Durick and Xeno Kovah
  • Publisher web site:
  • http://search.cpan.org/~mitrehc/HoneyClient-Manager-0.99/lib/HoneyClient/Manager/FW.pm

HoneyClient::Manager::FW Tags


HoneyClient::Manager::FW Description

HoneyClient::Manager::FW is a Perl module to remotely handle firewall rule/chain creation. Additionally, it will provide protection when the honeyclients become compromised by enabling static rate limiting(tcp/udp/icmp) and MAC address filtering.CREATING THE SOAP SERVER # Make sure HoneyClient::Util::Config loads properlyuse HoneyClient::Util::Config qw(getVar);# Make sure IPTables::IPv4 loads use IPTables::IPv4;# Make sure HoneyClient::Manager::FW can load use HoneyClient::Manager::Firewall::FW;# Make sure HoneyClient::Util::SOAP loads properly require_ok('HoneyClient::Util::SOAP');package HoneyClient::Manager::Firewall::FW; use HoneyClient::Util::SOAP qw(getClientHandle getServerHandle); my $daemon = getServerHandle(); $daemon->handle;The SOAP firewall server will boot up when the honeywall is started by the HoneyClient manager. The main directory that holds all the listener code is the /hc directory. startFWListener.pl is located in the /etc/rc.d/rc3.d directory and will boot up when the honeywall starts up in run level three. After start up, the firewall listener will await calls from the HoneyClient manager so that the firewall may be configured properly and dynamically updated when crawling begins.Steps to get honeyclient listening:1. Boot up honeyclient honeywall vmware image. 2. Start up our SOAP firewall and SOAP log listener /usr/bin/perl /hc/startFWListener.pl > /dev/null 2> /dev/null & These will start upon boot of the honeywall so you will not have to do anything except boot the image. 3. Now the firewall is listening for all SOAP client calls 4. Do a "ps -xf" to confirm that your firewall is listening It should show something like: 7580 pts/0 S 0:01 /usr/bin/perl /hc/startFWListener.pl 5. Make your FW calls now from honeyclient-client.pl.INTERACTING WITH SOAP SERVER use HoneyClient::Util::SOAP qw(getClientHandle); use HoneyClient::Util::Config qw(getVar);After the honeywall boots up, startFWListerner.pl will be executed and begin listening. From here we want to start interacting with our SOAP FW server. # Create a new SOAP client, to talk to the HoneyClient::Manager::FW module # @initlist will contain all the return values sent back from the server (PID of startFWListerner.pl on server and status message) # Lets set our default honeyclient ruleset: my $stub = getClientHandle(namespace => "HoneyClient::Manager::FW"); my $som = $stub->fwInit(); my @initlist = $som->paramsall; print "$_n" foreach (@initlist); # To dynamically append new rules to the iptables ruleset, do the following$hashref = this data structure will be passed from the manager to the HoneyClient::Manager::FW $som = $stub->addRule( $hashref ); print $stub->result; print "n";# To dynamically delete rules, all you need to do is delete the user-defined chain that was originally created.$som = $stub->deleteChain( $hashref ); print $stub->result; print "n";# To get the status of the current iptables ruleset, this function prints to hard disk the working iptables ruleset $som = $stub->getStatus(); print $stub->result; print "n";# For all new VM's that we plan to add later on, we will have to add new VM chains: $som = $stub->addChain( $hashref); print $stub->result; print "n"; # To shutdown the Firewall SOAP listner on the Honeywall$som = $stub->FWShutdown();print $stub->result;print "n"; Requirements: · Perl


HoneyClient::Manager::FW Related Software