Here is a list of various tools that allow you to work with policies and Elasticsearch databases containing logs from different firewalls.
Below, you will find the objectives of each tool.
This algorithm counts the flows traversing traffic using a simplified policy in the form of a CSV file. It will return both a CSV and an HTML file containing the previous information as well as the count of the different flows.
This version is precise and flexible, allowing the user to select the fields of interest, which will be searched in Elasticsearch. However, it sacrifices speed and reliability as it becomes slower and more prone to bugs as the policy grows larger.
This algorithm counts the flows traversing traffic using a simplified policy in the form of a CSV file. It will return both a CSV and an HTML file containing the previous information as well as the count of the different flows.
This version gains in speed and reliability. Each Elasticsearch query is independent and depends only on a single field, making it much faster and less prone to bugs. However, it loses the precision and flexibility of the first program, as it relies solely on the field corresponding to the ID/TAG of the different rules
The algorithm identifies network flows from an Elasticsearch database. It generates both an HTML and a CSV file summarizing the used services, source and destination IP addresses, the action applied by the firewall, as well as a counter for each flow.
It extracts the following information: Service, source and destination IP address, action, log count associated with the generated rule
This algorithm generates a simplified policy using a Forcepoint firewall configuration file in XML format. It produces a CSV and an HTML file for viewing and analyzing the rules.
It extracts the following information: Rule tag, name of the policy containing the rule, source and destination IP address, NAT address, service, action
This algorithm generates a simplified policy using a Fortigate firewall configuration file in CONF format. It produces a CSV and an HTML file for viewing and analyzing the rules.
It extracts the following information: Rule ID, rule name, source and destination interface, source and destination IP address, service, action, schedule, log traffic