Web Application Firewall
- Last Updated: December 11, 2024
- 1 minute read
- LoadMaster
- LoadMaster LTSF
- Documentation
Note: Utilizing WAF can have a significant performance impact on the LoadMaster deployment. Please ensure that the appropriate resources are allocated.
For virtual and bare metal LoadMaster instances, a minimum of 2GB of allocated RAM is required for the operation of WAF. The default memory allocation for Virtual LoadMasters and LoadMaster Bare Metal instances before LoadMaster Operating System version 7.1-22 is 1 GB of RAM. If this default allocation has not been changed, modify the memory settings before proceeding with the WAF configuration. If the check box to enable WAF is grayed out, it could mean that the LoadMaster does not have enough memory to run WAF.
There is a WAF engine open connection limit of 64000 per Virtual Service.
Note: To reduce the risk of the WAF connection limit being reached, the open connections will be closed after 20 seconds when a remote log server is too slow to respond. There is no impact on connections in use.
CAUTION: Legacy WAF rules were retired on 29th June 2021 and no further updates are available. Progress Kemp encourages users to migrate their configuration to the new WAF service.