What is your primary use case for Prevasio?

We use AFA (AlgoSec Firewall Analyzer), FireFlow, AppViz, and CloudFlow. Our use cases depend on the customer. In general, we use it for rule optimizations, security risks, to manage rules with FireFlow, and for application visibility, as well as for optimization and automation.

We use AlgoSec to monitor multiple firewalls. AlgoSec makes it very easy to maintain and manage our policies, the configuration, and various other maintenance of a particular firewall. It fulfills our requirement and monitors the configuration as well as the policies which have been made by the network team or the administrator of the existing environment.

We use several of the AlgoSec components including the firewall analyzer (AFA) and FireFlow. We may also use CloudFlow. We use AlgoSec primarily for Check Point. We run a script that works with Check Point and spits out rules. We also use it to create changes. Specifically, it will create new roles and we can use it to check if there are blocks on Check Point, as well. In the future, we may use it with Palo Alto.

I use AlgoSec Firewall Analyzer, BusinessFlow, AppViz, AppChange and CloudFlow. We use the appliances from the AlgoSec framework and the AlgoSec Firewall. The customer environment is mostly managed on-premise.

We are a retail company with about 2,500 stores, and we have at least 5,000 devices just on the retail side of it. We mostly use Cisco products in our organization. From the firewall perspective, we have a multi-vendor architecture. We have Check Point, Palo Alto, and FortiGate. We are using AlgoSec Firewall Analyzer to identify the risks, do some quality assessment of the firewall, and then do our troubleshooting. We are working towards automating our firewall process that is currently manual. We are also enabling AppViz with different application teams. So far, we have onboarded a couple of them from the SAP team. The whole idea is to keep the firewall rules transparent and relevant to the application that an application team supports. AlgoSec FireFlow is going to be adopted soon. I'm working on the project right now, and it is almost at the end stage where we're going to deploy it to the business. We are in a hybrid environment, and we have our presence in multiple cloud vendors such as Azure, Google, and Oracle. We have our on-prem computing systems, and we are working towards migrating most of our on-prem computing systems to the cloud. AlgoSec's deployment in our environment is a high-availability deployment. We have active and standby nodes. We also have a load distribution node, which is a virtual system. The active and standby systems are AlgoSec appliances.

We are using the FireFlow and Firewall Analyzer components. I'm not the manager of the project, so I don't know if we are using any other module. We use FireFlow to make our firewall change requests. As an architect, if I'm deploying something and a flow needs to be put in place, I need to go into the tool and specify the details about the flow that needs to be set in place. I also need to provide some contextual information, and then there is a whole workflow that gets started. It will first analyze the flow to determine which firewalls and modifications are required, and then there is an approval step for which someone responsible for security needs to give approval. After that, it goes to the implementation team that does the actual implementation. In the end, there is a validation step where when they say it has been implemented, you can check that the flow is open, and it works fine. You can then either close the ticket or say that it's not working and please check again or perform additional tests. We have a mixed proprietary network. We have stuff in private clouds, and we have stuff in public clouds with major cloud providers. We have a very global and complicated network in more than 60 countries.

We needed something to tell us the quality of our firewall rules in terms of their implementation. We use the following components of AlgoSec: AlgoSec Firewall Analyzer (AFA), FireFlow, AppChange, and CloudFlow.

We use FireFlow. Our environment is a mixture of private and public platforms. We have been aggressively moving infrastructure up to the cloud, so everything that used to be on-prem now is all pretty much in the cloud. We have hundreds of servers and instances up in the cloud. On-prem, we still have the same. It's a couple of hundred servers on-prem that we use for the day-to-day business functions as well. AlgoSec would help to manage our multiple environments if we had CloudFlow but we don't have that license. Back in 2016, we migrated firewall vendors over to Palo Alto Networks. During that time when we migrated, we had over 4,000 security rules. Using AlgoSec, we were able to trim it down by some ridiculous amount, around 72%.

We use it for firewall ruleset management. It's mainly to manage the firewall ruleset changes and for monitoring compliance. In our environment we use Algosec Firewall Analyzer. Our network environment is a mixture of public and private clouds. We have more than 3,000 network switches and we are managing almost 20 firewalls that are on-premises. That doesn't include the cloud firewalls because AlgoSec does not extend to that area.

It helps us load the bulk of organizations. We can maintain policies using AlgoSec's fine-tuning, which is why we use its automation. Once a request has been approved and it is in our queue, we check the parts of the firewalls between source and destinations. It also helps us push policy and remove unnecessary rules. I have used Algosec Firewall Analyzer (AFA) and FireFlow. We also use AppChange for its automation, where we can integrate our MDT tools with our AlgoSec project. Our customers have on-premises data centers as well as infrastructure in the cloud: hybrid. We are the service provider for the cloud and our data centers are also on the cloud.