Our company uses the solution as a data center firewall. 

It is hard to determine all users within our infrastructure. It depends on systems we put behind the solution. Its internal but also a data center firewall. Sometimes, there are hooks from the solution to our external infrastructure or external into internal. A ballpark range is that we have 10,000 users. 

I am using F5 BIG-IP AFM as a proxy in relation to a code decrypt traffic and analysis for the web application signatures on different published websites in our company. Additionally, I can customize iRules to inspect traffic or redial traffic to another reach. I can use it for text signatures and it can provide a security profile.

We use these as our data center firewalls. At the time of our analysis of the systems, they were the ones able to process the large load of traffic that we needed over any other systems out there. So, capacity-wise, these were able to address our needs.

We have version 12, version 13, version 14, and version 15.

We use the solution to establish a clientless VPN and the client VPN. We also use the solution to monitor traffic, block traffic, and filter traffic between the external and internal fixed environments.

In the past three years, I implemented Advanced Firewall Manager to safeguard our clients' DNS solutions and protect applications from DDoS and BPOS attacks. This involved securing DNS queries and ensuring resilience against various cyber threats.

I am using F5 BIG-IP Advanced Firewall Manager (AFM) for load balancing and an IP gateway.

We use AFM mainly for web and mobile application security. We use the DDoS protection feature as well.

We primarily use the solution as a firewall. 

We use it to block or allow traffic inside the infrastructure.

Usually, if we want to tie it up to another service, we usually use AFM. The reason we use AFM is due to the fact that we have Anti-DDoS equipment and the components in order to mitigate those attacks, we use a combination of AFM, ATM, and GTM.

We primarily use the solution as a data center firewall. 

F5 BIG-IP AFM is deployed on-premise and in the cloud.

We are using F5 BIG-IP AFM mostly for financial services.

We use the on-prem model of this solution. Our primary use case is to protect our software with a firewall.

I am using this solution to protect my web services.

We primarily use the solution to protect and to divide cells. We are not using AFM as a standalone product. We are using AFM with the LTM module, as a module. The main purpose of F5 is to use it as an ADC application to deal with the console.

I use F5 AFM (Advanced Firewall Manager) for several solutions including firewall, load balancing, and security.

We use three main features. The first one is access control. Access control would mainly use the IP geolocation feature. This feature in AFM lets you limit access to some countries and allow other countries. Some countries can access your service while others cannot access it. This is one feature which is called IP geolocation. 

The second feature we use is called IP intelligence. It's another feature of F5. It's like a straight feed for all blacklisted IP addresses in the world. They make categories for the blacklisted IP addresses, such as blacklists to a channel, blacklisted proxies, blacklisted malicious malware, and blacklisted spammers. If anyone of these IPs is trying to hurt your service, we are able to just block it with the AFM firewall, which is a separate license in essence. We utilize this license as well. 

Finally, we have a DDoS safety feature. AFM provides protection for the network from a DDoS attack. We use this feature at times too. These are the only three features we utilize: IP geolocation, IP intelligence, and DDoS.

The solution is primarily used as a web application firewall.

We are using this solution for protection and blocking IPs for our customers.