-
Client Side Defense - Add ability to filter by IP address on "Script List" dashboard
For troubleshooting purpose, it would be handy to have the ability to filter by IP on "Script List" dashboard. This will enable admin to identify users affted by the malicious script.0
-
allow customer to configure which headers are logged and which end points include payload logging to be available in both performance console and GLR HTTP events
As of July 2024, the majority of http request headers have been removed from being displayed in the performance console and GLR. The LB can still create rules to act on any header but engineers have no way to view logs in or from XC to determine i...1
-
Add tool for checking TCP port of origin servers
There is no capability for checking status of origin server's TCP port with currently available site tools (capture attached). The idea is to provide a new site tool to help faster checking status of origin's TCP port without waiting for healthche...0
-
TLS Load-balancer certificate issuance via CSR
A Silverline "feature" (Certificate keeper) that would be nice to have in F5XC would be an additional way to install a certificate on a load-balancer with F5XC providing a CSR. Steps: customer choose this option in the load-balancer form they’re p...2 Planned
-
Granular reports for WAF/BOT/DDOS activity
It would better enable customers to visualize specific traffic patterns and block patterns of F5. Often times these high-level reports are generated regularly to track changes and show long winded changes in risk over time. An example would be; "S...0
-
Create custom API groups
To be able to create more specific roles. For example one requirement that we have is for devops users to be able to create WAF exclusion rules. Desire is not to have access to change anything else on the LB.0
-
LB HTTP health monitor - no receive string
XC's synthetic monitors include the capability to specify a regex pattern against response body. This is helpful in general for targeted probing, i.e. common application-side built-in health checks that report on critical backend system resources/...0
-
injecting JA4 TLS fingerprint into every HTTP request as header
I'd like to inject the Ja4 tls fingerprint as a request header into every request sent to the origin. why: to have a relatively unique signature we can track that will be included in all the stacks upstream for correlation and to allow upstream ac... -
Allow searching of matching criteria within route rule configuration
Currently the search function at the top of the Routes only searches the pool name assigned to each rule. It does not allow you to search for values in the header for example. If a rule has a Host header match you cannot search for that domain.0
-
Origin Pool TLS Configuration "Auto-Diagnostic" Button
Issue: Troubleshooting a lot with customers and they keep running into 503 errors due to misconfigured TLS on the Origin Pool, and then its a hassle to figure out which settings are the right ones. They constantly need to go back and check the req...0