F5 Distributed Cloud - a view from an InfoSec standpoint
Use Cases and Deployment Scope
What I personally love about it is the ease to create new infrastructure and configure domains, routes and rules to protect any web app or API. WAAP is a necessity on todays landscape and the ability to summon it on the cloud in an cloud agnostic solution is really a blessing.
Pros
- Cloud agnostic. I like that no matter where the Web app lives, it can be protected with F5 WAAP.
- Easy creation of F5 infrastructure and deployment.
- Ability to give our clients or developers visibility on statistics about their web app performance and traffic events on f5.
- Many services all can be used and seen on one central dashboard. Since is cloud. We dont need diferent tools or logon into many others dashboard to work. Like WAP, DNS, CDN, load balancing. All is intigrated into one dashboard.
Cons
- User roles. Current API groups and Elements are not clear nor intuitive to use. Is very difficult to give granular level access to users on each service. For example. Access to import TLS certificates but not able to do or see anything else.
- GUI overall is a bit clunky. Load Balancer configuration window could be better organized. Or streamline.
- Lack of built in global dashboard and reports. Something useful would be a Global report listing the status of all TLS certificates imported and in use on the platform. Same with the status of WAF on Load Balancers.
Return on Investment
- Accelerated time of deployment of protection
- Lower total cost of ownership.
- Streamline our work. Instead of many dashboard from many BigIps, we use only one dashboard. F5XC.
- The WAAP solution is one of the best for is granular ability.


