-
Provide key exchange logging via Console and GLR logs
The current GLR and console logs do log the TLS versions and SSL ciphers used in an inbound connection but it'd also be nice to see the key exchange used. Especially with more organizations adopting ML-KEM, we'd like to be able to represent that a... -
Rate Limit custom response page
Without it, clients that are hit with the limit are left clueless on how to contact us. -
IP Reputation in non-blocking mode
We would like the option to enable IP Reputation in a monitoring / non-blocking mode. Following some disruption caused by false-positive blocks due to the brightcloud IP reputation status's, we've had to disable this feature temporarily on our HTT... -
Choose or pin a Common-Name on autocerts
For HTTP Load Balancers using auto-cert with multiple unrelated FQDNs, we would like the option to choose and pin a particular domain as the common name. This is required for load balancers configured to host many FQDNs for single-tenanted applica... -
Certificate expiration alerting - Alerting needs to say the exact count of days before expiration
Currently certificate expiration alerts describe "TLS Custom Certificate for virtual host <name> expires in less than 15 days". Customer would like the exact number of days until expiration for each certificate to be reported rather than all...
-
Feature Request: Native OPSWAT MetaDefender Integration for F5 Distributed Cloud
We would like to request a native integration between F5 Distributed Cloud HTTP Load Balancer/WAF and OPSWAT MetaDefender for inline file security. Our use case is to protect web applications hosted behind F5 Distributed Cloud from malicious file ... -
Custom Error Response Page for Threat Mesh block
Hello I'd like Threat Mesh to use the custom Error Response page configured on the LB. We've had some false positives where customers don't know how to react. Regards Peter -
API Protection/Validation - Allow empty values by default for non-mandatory discovered parameters/headers
Problem: When a parameter or header is identified through API Discovery and is not marked as mandatory, the system currently does not allow that field to accept an empty value by default. This forces users to manually edit the API definition just ... -
Provide the ability to toggle WAF base64 encoding on/off
Be able to define an exception or an option, so that customers can define something like: If FQDN == www.example.com && URI == /parent/directory/filename.com && Parameter == example --- THEN do not decode Base64
-
Provide Recommendations For XC configurations
Provide useful recommendations for items that could or should be configured, like health montiors or moving WAF from monitoring to blocking etc. See example attached
