

DNS and NTP are also being used as methods of command and control for adversaries. Organizations need to also ensure that they are synchronizing their devices to the same internal NTP sources in order to make sure that events can be correlated during an incident investigation. Devices should not be allowed to make external DNS queries without passing through the organization’s internal DNS servers.


There are a few things I look for in firewall rules, including: The syntax is not difficult to read, but when a larger device ends up with 100+ rules it can be cumbersome to try and read all of them at once. I routinely perform audits on FortiGate firewalls. Windows users need to install ActivePerl.FortiGate firewalls built by Fortinet provide organizations with a robust next-generation firewall platform to secure networks with Unified Threat Management (UTM) features. This perl script does run without modification or additional installation on Mac and on Linux. _.csvĬonfig files not containing a firewall policy do not create an output file at all. If your file contains VDOMS, the VDOM name is appended to the hostname. If your config does not contain any VDOMs, you get the output in a file like this. The TXT version shows you every configured detail of the policy. While CSV and HTML give you formatted output, which does not contain every parameter configured, you can output to TXT. On Windows you need to install ⇒Perl first to make it work. On Linux and MacOS perl is already available. This script does not only show the policies, it also displays the details of the objects used by the policy. You can import HTML into Excel or you can use the HTML output directly. So I appended the script to output HTML too.

Microsoft Excel cannot import CSV with mulitline cells. Importing CSV into a spreadsheet is a good way for all users which prefer Apple Numbers, OpenOffice or LibreOffice. To do this, I wrote a perl-script to create a CSV file. Sometimes you need to document your firewall rules.
