-
Add prefix traffic filter to Routed DDoS Traffic Visibility
In the Traffic Visibility panel of the Routed DDoS workspace add the ability to filter the traffic view by prefix giving DDoS incident management teams the ability to see realtime traffic statistics and graphs for a prefix. When viewing Traffic by...0
-
DDOS protection dashboard
There is currently no dashboard displaying the status of the DDOS protection. It would be nice to have some metrics like standard traffic levels, usual attack types, burst absorbed, etc.0
-
We need to give read only access of dashboard to customer namespace.
We need to give read only access of dashboard to customer namespace.Right now, if we want to give access to user then customer will be able to see all config.0
-
show HTTP body payload of response and request in the request log
No description provided3
-
Support using FQDN/Hostname as the remote endpoint for CE - RE IPsec tunnels.
Today, when configuring an IPsec tunnel between a Customer Edge (CE) and a Regional Edge (RE), the XC Console requires the Remote IP Address field to be a static IPv4/IPv6 address. Hostnames/FQDNs are not accepted. For customers operating in dynam...0
-
DNS Load Balancers - CNAME Pool Health Check support
Add Support for health checks for CNAME Pools in the DNS Load Balancers section2 Planned
-
Console access logs with IP, Failed attempts,invalid credentials
i like to have audit logs or access logs, with failed attempts, invalid users along with IP's they are accessed. to my F5 XC portal/console2
-
Make the WAF exclusion rule statistics
We would like to track and get a statistics report for all the WAF exclusions we might have added to our Tenant. That way we can also get an idea on how to remediate and remove that exclusion in future.0
-
Add multiple decoding check
Malicious payloads decoded more than 3 times are passing without any violation raised for example:":path\":\"/item/57328/1/59721?test=%2e%252e%2e%252e%2f%252f%2e%252e%2e%252e%2f%252f%2e%252e%2e%252e%2f%252f%2e%252e%2e%252e%2f%252f%2e%252e%2e%252e%...0
-
GEO balancing for HTTP LB on route level
In case that that two origin servers are located in two regions of the world (for example EU and US) there is no possibility to define rule with geo definition that users from US should access origin in US and not in EU. In generally would be poss...0