360-FAAR (Firewall Analysis Audit and Repair) is an offline, command line, Perl firewall policy manipulation tool to filter, compare to logs, merge, translate, and output firewall commands for new policies, in Checkpoint dbedit, Cisco ASA, or ScreenOS commands. It is all contained in one file. It can read policy and logs for: Checkpoint FW1 (in odumper.csv / logexport format), Netscreen ScreenOS (in get config / syslog format), and Cisco ASA (show run / syslog format). It uses both inclusive and exclusive CIDR and text filters, permitting you to split large policies into smaller ones for virutalization at the same time as removing unused connectivity. It supports policy to log association, object translation, rulebase reordering and simplification, rule moves, and duplicate matching automatically. It allows you to seamlessly move rules to where you need them. 'print' mode creates a spreadsheet for your audit needs with one command.
fwlogwatch is a packet filter and firewall log analyzer with support for Linux ipchains, Linux netfilter/iptables, Solaris/BSD/HP-UX/IRIX ipfilter, Cisco IOS, Cisco PIX/ASA, Netscreen, Elsa Lancom router, and Snort IDS log files. It can output its summaries in text and HTML and has a lot of options. fwlogwatch also features a realtime anomaly response capability with a Web interface.
EtherApe is a GNOME/pcap-based etherman, interman, and "tcpman" clone. It displays network activity graphically. Active hosts are shown as circles of varying size, and traffic among them is shown as lines of varying width. It supports Ethernet, FDDI, Token Ring, ISDN, PPP, WLAN, and SLIP transports. It knows about VLANs, IP, IPv6, TCP, UDP, FTP, and a number of other protocols. Additional statistics windows will let you concentrate on protocols or nodes.
jWatchdog delivers a simple watchdog to actively monitor your infrastructure and send you notifications in case something goes wrong. It is configured using a simple XML configuration file. This configuration file can be changed on-the-fly without a need to restart the watchdog. jWatchdog does not offer data collection itself. It assumes that you already collected the data on which you want to run jWatchdog. The de facto standard tool Collectd is recommended for data collection. jWatchdog assumes that you use the RRDTool collectd output plugin to store the collected data in RRD files, or use Graphite as a datasource.