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, and its one file!
Read Policy and Logs for:
Checkpoint FW1 (in odumper.csv / logexport format),
Netscreen ScreenOS (in get config / syslog format),
Cisco ASA (show run / syslog format),
360-FAAR uses both inclusive and exclusive CIDR and text filters, permitting you to split large policies into smaller ones for virutalisation at the same time as removing unused connectivity.
360-FAAR supports, policy to log association, object translation, rulebase reordering and simplification, rule moves and duplicate matching automatically. Allowing you to seamlessly move rules to where you need them.
Read Policy and Logs for:
Checkpoint FW1 (in odumper.csv / logexport format),
Netscreen ScreenOS (in get config / syslog format),
Cisco ASA (show run / syslog format),
360-FAAR uses both inclusive and exclusive CIDR and text filters, permitting you to split large policies into smaller ones for virutalisation at the same time as removing unused connectivity.
360-FAAR supports, policy to log association, object translation, rulebase reordering and simplification, rule moves and duplicate matching automatically. Allowing you to seamlessly move rules to where you need them.
TRY: 'print' mode. One command, and spreadsheet for your audit needs!
Features
- WRITTEN IN SIMPLE Perl - NEEDS ONLY STANDARD MODULES - IS ONE FILE
- .
- Easy to Edit Menu Driven Text Interface
- Capable of manipulating tens of thousands of rules, objects and groups
- Handles infinitely deep groups
- Capable of CIDR filtering connectivity in/out of policy rulebases.
- Capable of merging rulebases.
- Identifies existing connectivity in rulebases and policies
- Automatically performs cleanup if a log file is provided.
- Keeps DR connecitvity via any text or IP tag
- Encryption rules can be added during policy moves to remove the "merge from" rules for traffic that would be encrypted by the time it reached the firewall on which the "merge to" policy is to be installed - sounds complicated but its not in practice - apropriate ike and esp rules should be added manually
- Runs consistency checks on its own objects and rule definitions
- Extendable via a simple elsif in the user interaction loop section.
- .
- EASY TO EXECUTE:
- ./360-faar.pl <FW CONFIG TYPE> <log> <config> <nats> <FW CONFIG TYPE> <log> <config> <nats> <FW CONFIG TYPE> <log> <config> <nats>
- .
- CONFIG TYPES: - cisco soon!
- od = logexported logs, object dumper format config, fwdoc format nat rules csv
- ns = syslog format logs, screenos6 format config, nats are included in policy but not processed fuly yet, fwdoc format nats can be used though
- cs = cisco asa syslog file, cisco ASA format config, - not ready yet
- .
- OUTPUT TYPES:
- od = output an odumper/ofiller format config to file, and print the dbedit for the rulebase creation to screen
- ns = outputs netscreen screenos6 objects and policies (requires a netscreen config or zone info)
- cs = cisco asa format config - not ready yet
- .
- By default 360-FAAR accepts exactly 3 configs on the command line.
- Make an empty file called "fake" and and use this as the file name, for log config and nats if you want to process less than 3 configs at once.
- Log file headders in fw1 logexported logs are found automatically so many files can be cated together
- .
- FUTHER PROCESSING AND MANUAL EDITING:
- Output odumper/ofiller format files and make them more readable (watchout for spaces in names) using the numberrules helper script
- Edit these csv's in Openoffice or Excell using any of the object or group definitions from the three loaded configs.
- You can then use this file as a template to translate to many different firewalls using the 'bldobjs' mode
Screens
