AFA is helpful when finding duplicate rules, subnets, and policies for your ports that have not been used in the last six months. It also helps to find out which ports have been opened for all firewalls. After that, we run the reports and share them with the customer. After getting approval from the customer, if there is a block on a particular port or ports not used in a current environment, Analyzer is helpful when placing the change request of the users. In this case, AlgoSec provides the link to the user who raises the request though the automation, which is the change request. From that change request, it comes through our ticketing tools, e.g., BMC Remedy. Then, we have to check and approve it. Once it gets approved, we deploy the particular policies, as per the user's request. It provides visibility for the risk. Whenever unnecessary ports have been opened in our environment, whether by mistake or human error, a support ticket gets opened so we can find out about it in an easy way. After that, we can implement or block the particular ports if they are not necessary for the organization's production. The solution has become more helpful during the cleanup rules for the firewall, when we do those activities twice a month. For example, if a user raises a request two to three months ago, then we forget to block the particular port by human error. During the client's cleanup workshop, we can make things clearer, which is more useful for us when cleaning up unnecessary rules and ports from the firewall. AlgoSec enables us to manage these hybrid environments in a single pane of glass. It is an excellent, intelligent tool. The console is user-friendly for understanding and implementing things on firewalls. It is helpful for finding duplicate rules.
