What is our primary use case?
Our company uses the solution for customer use cases to replicate environments, perform integrations, and check for changes or issues. We have many internal users because we have a wide database of customers.
Most customers have WAF or Advanced WAF but if you dig deep from a high-level perspective, then you find issues with configurations or missing security enhancements.
The platform is capable of doing many API integrations and other things. Customers with public websites use our client-facing service to upload attachments. Often, customers are not integrating the solution with a malware sandboxing tool. This feature is natively in-the-box so protection can be enabled with a few steps. We determine if attachments are uploading malicious files because there isn't protection in the normal solution. We find out if customers are doing vulnerability or risk assessments. Integration tools such as Qualys help because we can import a file to resolve F5 issues.
For one use case, a customer might have enabled the tech signature for a specific tech but an IP exclusion or public IP exclusion is a bit risky.
Another use case is for database security where we utilize the solution's very comprehensive security features. We can make a SQL database more visible to database security and order logs for the logins to the station tool.
What is most valuable?
It is very powerful to be able to enable database security integration for an administrator or customers.
The integration between modules is good. You can license the APM policy manager, integrate, and make security posters for VPN clients. You can natively integrate the login pages to ensure client machines and websites are protected.
The solution includes the typical load balancing offered by other vendors but has enhanced security compliance features that are powerful and easy to configure.
It is easy to obtain dashboard compliance because security policy views are included.
What needs improvement?
The solution requires a bit of advanced knowledge. They are trying to make configurations less complicated by including guides, particularly for application protection in the cloud. Nothing is complicated but it takes a hands-on approach and a few hours to a few months to become familiar with how the solution works.
The solution should include RASP which is runtime application security protection. Imperva includes RASP but the solution does not at this point. RASP would provide another level of application protection at the code itself.
For how long have I used the solution?
I am a certified F5 engineer and have been using the solution for four years.
I am a partner so I use both the on-premises and the public cloud solution. To get certification, you need to complete a lot of labs and training on your own. You must go into detail with everything and get your hands dirty.
I use the public cloud solution for my own labs. There is a free F5 public cloud tenant that includes other features for setting up a lab or application.
The solution's virtual edition can be deployed in other cloud services such as Azure, AWS, and OCI. The virtual edition takes the on-premises version to the cloud so it is not difficult to implement. The only difference is the cloud-native version includes the WARP feature that is used for web application API protection.
What do I think about the stability of the solution?
The solution is definitely stable so I rate stability a nine out of ten.
What do I think about the scalability of the solution?
The solution is quite scalable so I rate scalability a nine out of ten.
How are customer service and support?
To be honest, I have not needed support because I have the knowledge to fix anything unless it is a bug within the solution.
How was the initial setup?
The initial setup is not complex so I rate it a ten out of ten.
For on-premises, it might take two weeks to deploy security policies which depend on application traffic. You choose a policy set type from fundamental, comprehensive, or rapid according to your needs. Then, you apply the policy.
For example, you can deploy a quick policy for a nonfinancial side to protect from common threats. In this case, you choose the rapid security policy, choose the application language, and add the SQL or PHP server technology to implement the attack signature. This is helpful because you don't need to apply all of the OS signatures if you only have Windows. Just pull the Windows signature and it will be plugged.
Then you proceed to the staging model for awhile to pick up the negative security model. You can proceed with a mix of negative and unboxing security models. After that, you start deploying, defining URL parameters, and setting other policies. You put it to staging and make edits. If you don't find too many suggestions or false positives, then you deploy it in blocking mode to the vendor.
After two or three weeks, if the owner is fine with the policies and number of false positives, then you put it to blocking.
What about the implementation team?
We implement the solution for customers. Implementation can be done by one person who is knowledgeable about the product and procedures.
IT managers generally do not dig deep inside the solution because there is quite a bit of detail. They have a high-level overview but certified experts dig deep into configurations.
What's my experience with pricing, setup cost, and licensing?
I am not sure about pricing but licenses are available on Google.
What other advice do I have?
The solution is not about improving functionality but about improving the security of an infrastructure itself. You are improving the security profile so that data is not exposed to an attacker.
I definitely recommend that everyone use the solution and rate it a nine out of ten.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Other
Disclosure: My company has a business relationship with this vendor other than being a customer: