-
Request_ID header add ability
For full visibility the ability to dynamicaly include the request_id value as a header would allow users to have full visibility through a single place. Requests dropped from F5 XC can be identified through the request_id, requests dropped within ...1
-
Add ability to "skip" IP Reputation as option in custom policy rule similar to how WAF, MUM and Bot can be skipped
why - its awkward and inefficient to have skip logic spread across multi areas (custom policies rules and trusted client rules). We have to define the identifying criteria for safe clients in two places. who - security engineers will benefit from ...0
-
Show new endpoints immediately in API discovery
The lag on discovery to showing endpoints outside of a configured API Spec file is very long (if it ever shows up). It would be very useful to see new endpoints immediately without waiting on the results of the machine learning/anomaly-detection w...0
-
response code 0
When a response is generated by F5 XC LB, "Error 504 - Gateway Timeout" for example, the response code in a security event is 0 ("rsp_code": "0"). Could we have the response code of the reponse generated by F5 XC LB?0
-
Intregatrion with logrhythm
Intregatrion with logrhythm on premise0
-
Add Route feature in TCP LB
Currently the TCP LB seems not support Route feature as HTTP LB. Please add this feature so we can use the TCP LB integrate with port range to forward the traffic to specific origin pool0
-
DNS primary zone search field to lookup for DNS records
When we have just few DNS records at a zone it is easy to manage. When we have few pages of records it is easier to have a search field where we can look up by the record we want to modify or check if it exists.1 Planned
-
Pool, Public IP and Virtual Site
If a customer needs to control egress traffic, to limit egress source to a subset of REs, a Virtual Site must be set. If the origin pool is an IP, the customer has to choose "Private IP", even if the origin pool is a Public IP. That's not obvious.... -
API Protection (Discovery) - Path Case Normalization
Requested Enhancement Add a method to enabled case Normalization for API Protection (Discovery), which will resolve the following gap. Current Behavior API Discovery is case sensitive, regarding the PATH. This impacts Discovery/Inventory/Shado...0
-
Allowed for multiple SSO providers
Distributed Cloud customers often have multiple directories that they would like to link to a single tenant. For example, a customer may have one AAD environment for Dev, and another for Prod. Or some may have PCI, and non-PCI.2