Feature Requests

It would be excellent if we can get the HA status for fortigates into the data prints. This would help identify risks of non-HA devices. I would have expected to see HA status and config in the data prints (Same as Sonicwall)

Currently the inspector does not support HA pair information retrieval from the secondary firewall. It would be useful to have this functuionality. Inspector retrieves information for both firewalls in the HA pair.

We are unable to see the list of DHCP IPs and associate device information (mac address), including IP reservations in the data that is collected from the inspectors. We need this to track changes against IP reservations, and well as reporting on the DHCP lists for the CIS compliance standard. We can return some limited information from the network inspector, but it is much more important to get this from our firewall. It currently shows DHCP servers and the IP range, but not the specific list of each IP address given out and the associated information Add in the DHCP IP and Device information so that we can build metrics and actionable alerts around this.

To have a daily backup of the configuration file in order to monitor changes in the configuration file. Implement a daily configuration dump in Liongard just like the Cisco Small Business and Cisco ASA inspectors do.

Because we're using IPv6 at a lot of our customer sites including /48 subnets divided into several /64 subnets using Inter-VLAN routing. Currently the IPv6 IP address is displayed as my current WAN IP address and not the IPv4 address when IPv6 is implemented. Implement proper IPv6 support and IPv6 routing support in the Fortinet Fortigate inspector.

Can we add data for Administrators and trusted hosts?

I want to be able to track changes in Web & DNS filter profiles (e.g. someone changes a category from block to allow) The Web & DNS filter profiles are recorded in the device's dataprint

Currently in the dataprint, the information about the auto-upgrade of the firmware is not present. I would like it to be present. See attachements to know how to get the information. Available via the CLI I would expect that the data is added in the data print so I can create metrics to know if auto-upgrade is enabled or not.

Hi - The existing FortiGate inspector is pretty good for FortiGate firewalls, but it has no support for FortiSwitches or FortiAPs. All of Fortinet's switches and wireless access points are managed BY FortiGate firewalls, and it would be great if we could also see all the info for those for clients who utilize them. Since they are managed in the FortiGate firewalls themselves, I suspect it would be far less effort to add FortiSwitch and FortiAP data/support into the FortiGate inspector compared to the original effort of building the FortiGate inspector from scratch. I'm attaching a variety of screenshot examples, sanitized, from a client environment of ours who has some FortiSwitches and FortiAPs so you can see what I mean. The FortiGate inspector including managed FortiSwitches and FortiAPs would be a big value add to this inspector. The FortiGate inspector called "FortiGate 100F - Toppings Plant - S.A. Piazza" under the environment named "S.A. Piazza (Wild Mike's Ultimate Pizza)" in our tenant has several managed FortiSwitches and at least half a dozen managed FortiAPs, but you can't tell that or see anything about them in the FortiGate inspector. Support for FortiSwitches and FortiAPs gets added to the FortiGate inspector. (Or, that they are made as new separate inspectors if you prefer.)

We perform work for a lot of government contractors, all who require FIPS-mode on their networking equipment. FIPS-mode disables the API on Fortigate devices; therefore, Liongard has no way of retrieving data from these devices. Using a different communication protocol such as SNMP or SSH would allow for data collection when the API isn't available. Additional parsing would be required for SSH; however, SNMPv3 may offer more formatting that makes it easier to represent this data.