1) Fully integrate Geo Protection into the Access Control policy layers; make country objects directly selectable in the source/destination of rules.
2) Perform Geo Protect drops in SecureXL (if enabled), not the Firewall Path. SecureXL already performs antispoofing drops and country-based drops with fw samp in the Accelerated Path, this shouldn't be difficult to do with Geo Protection as well.
3) Improve reporting done by fwaccel stat indicating why templating rate (Connections/sec) is zero (i.e. Anti-bot enabled, more than just "Firewall" checked in first policy layer).
4) Permit use of Security Zones in NAT rules, would make converting NAT rules from other vendors' zone-based firewalls much easier.
5) Add support for what other vendors call "NAT Oversubscription" that generally allows more than 50k concurrent hidden connections behind a single IP address.
7) Directly publish CPU and memory specifications of appliances, instead of users having to figure it out on their own
😎 Permit the definition of "FastXL templates" directly in SecureXL that forces internal, trusted traffic (i.e. backups) into the Accelerated path with a minimum of inspection. Add all the warnings and caveats you want...
9) By default force all gateway kernel syslog messages issued by INSPECT/SecureXL into the regular firewall logs visible through SmartConsole/SmartLog.
--
Second Edition of my "Max Power" Firewall Book
Now Available at http://www.maxpowerfirewalls.com
Gateway Performance Optimization R81.20 Course
now available at maxpowerfirewalls.com