14 July 2008 | 8,959 views

FWAuto v1.1 – Firewall Auditing & Ruleset Analyzer Tool

Prevent Network Security Leaks with Acunetix

FWAuto (Firewall Rulebase Automation) is a Perl script and should work on any system with Perl installed. Provide the running config of a PIX firewall to fwauto. It will analyze and give you a list of weak rules in your rule base and store the result in multiple output files.

Maybe there have been times when you have pentested a firewall. As part of a grey box engagement you were assigned the task of auditing that HUGE firewall rulebase and were stuck on how to proceed, just because of the sheer volume of information. This tool in Perl is created to help in auditing a rulebase and helping you to narrow down on the weak rules. Current support is just for Cisco PIX though the framework was designed to scale across multiple firewalls and no major changes need to be made.

Updates

  • Outputs now available in reasonably neat HTML format
  • No more complex command line arguments, everything’s in a config file
  • More ports added in vulnerable ports section
  • Options available to obtain detailed/non detailed output

You can download fwauto v.1.1 here:

fwauto_v1.1.zip

Or read more here.



Recent in Network Hacking:
- IPFlood – Simple Firefox Add-on To Hide Your IP Address
- masscan – The Fastest TCP Port Scanner
- BurpSentintel – Vulnerability Scanning Plugin For Burp Proxy

Related Posts:
- Lynis – Security & System Auditing Tool for UNIX/Linux
- Firewalk – Firewall Ruleset Testing Tool
- Lynis 1.2.6 Released – UNIX System & Security Auditing Tool

Most Read in Network Hacking:
- Brutus Password Cracker – Download brutus-aet2.zip AET2 - 1,059,884 views
- Wep0ff – Wireless WEP Key Cracker Tool - 511,619 views
- THC-Hydra – The Fast and Flexible Network Login Hacking Tool - 314,338 views

Low-cost VPS Hosting

3 Responses to “FWAuto v1.1 – Firewall Auditing & Ruleset Analyzer Tool”

  1. Changlinn 20 July 2008 at 11:03 pm Permalink

    Now if only they could do checkpoint too, it is supposedly the most common firewall in enterprise.

  2. zupakomputer 21 July 2008 at 4:03 pm Permalink

    Regarding firewalls – found two unrelated websites become unloadable when running a Firestarter config. Other sites were fine. But the interesting part being – the same IP B block showed up as loading alongside the various traffic on those two websites when the firewall was turned off. And it only shows up the first time you try to connect – cache emptying is needed (if the browser saves the pages)to get it to show up again….which made me think ‘DNS then’ – but, why only on pages that can’t get by the firewall?

    So of course I had to see who that was, and the router trace won’t go past 15 hops which just gets you the info you had already, that it belongs to a big B block of IPs (24.64.*.*) and only some vague ARIN info on the owner details of that and a bunch of other IP blocks.

    What does this smell like – both sites could certainly be having their visitors monitored given what kind of sites they were (hacking, and ecology / green), but it definitely sounds dodgy to me – the same unexact-traceable IP block shows up in both, and both can’t get past a standard firewall config – somones thar is doing some probing and they don’t want to be probed back themselves. I think that calls for some How Not To Be Seen treatment going their way.

    Two e-mail providers don’t get past the firewall either, which in some ways sounds ok because you’re logging in – but it’s the login screens that get blocked. And guess what IP block shows up on one of them.

    & it just showed up again right before my connection dialed off. Always different host numbers each time it shows up.

    And also since I began writing this – the firewall is now blocking all webpages, on the same setting that was fine for them before (see above) – and that IP block 24.64.*.* is showing up again.

    What does a high-speed Canadian internet company have to do with my firewall settings? It connects directly to my ISP with ICMP and UDP traffic.

  3. zupakomputer 22 July 2008 at 11:08 am Permalink

    Look who popped up during a scan of the aforementioned B block – and they ‘just happen’ to have exactly the same services running on the same ports,

    http://centralops.net/co/DomainDossier.aspx?addr=218.10.111.106&dom_dns=true&dom_whois=true&net_whois=true&go=Submit