-
API request rejection should be based on response code as well
On coming up with Lack of Resources and Rate Limiting DC article for F5 XC I come across the situation where user should be rate limited based on invalid authentication credentials for requested resources. We have the feature to Rate Limit the use...0
-
Don't hardcode 'ves-system' namespace in vp-manager
It's currently not possible to have more than one instance of 'ves' running in a cluster. The root issue is the namespace 'ves-system' is hardcoded in vp-manager-0 during bootstrapping tasks. This is a poor practice and limits possible use cases. ...
0
-
Restrict user from seeing other Namespaces which is meaningless to them
Provide option or default user experience that users has their own namespaces and not seeing others. This is unecessary if they don't interact to each other. Potentially can improve security also. Furthermore MSP can just use 1 tenant to house all...0 Already exists
-
Add Rate Limiting & IP Rep to list of controls that can be "skipped" via Policy in Common Security Controls
To disable security controls for a PCI scanner I have to make at least 2 config changes on the LB. Since IP rep can only be done via Trusted clients and Trusted Clients only allows a single IP/range per config, we must create a config for each IP ...0
-
F5XC MSSP - Increase the limit of LB that can be bought in the SMB plan to 4
The current proposal is built around using the SMB plan that includes Console + maximum 1 load balancer. The ask is to increase the limit of possible additional load balancers that can be bought in the SMB plan to 4.
0