AlgoSec’s latest product release delivers automated application connectivity and security policy changes, deepens application visibility and discovery, and extends application risk analysis across multi-clouds and hybrid environments. Securely Accelerate Application Delivery and Policy Management with AlgoSec ASMS A32.10 AlgoSec’s latest product release delivers automated application connectivity and security policy changes, deepens application visibility and discovery, and extends application risk analysis across multi-clouds and hybrid environments. September 8, 2021 Speak to one of our experts RIDGEFIELD PARK, N.J., September 8, 2021 – AlgoSec , the application connectivity and security policy company, has introduced enhanced automated application connectivity and security policy changes, and deepened application visibility and discovery, in the latest version of its Network Security Management Solution. AlgoSec Security Management Suite (ASMS) A32.10 builds on previous versions to give IT and security experts the most comprehensive visibility and control over security across their entire hybrid environment. With A32.10, organizations can align network security with their overall business objectives, automating the process in a single platform for a seamless, zero-touch experience. The key benefits that AlgoSec ASMS A32.10 delivers to IT, network and security experts include: Intelligent application connectivity in SDNs and the cloud AlgoSec ASMS A32.10 introduces intelligent application connectivity management and enhanced security policy automation to leading SDN and cloud platforms, including VMware’s NSX-T. It also extends support for MSO-managed Cisco ACI devices, Cisco’s leading SDN platform. Application discovery and visibility across hybrid networks With A32.10 enterprises can use traffic logs to automatically discover applications on the network, providing enriched mapping across hybrid network estates. It provides a seamless and complete picture of the network across multiple public clouds including Google Cloud (GCP) and AWS Transit Gateway as well as Check Point R80 Inline and Ordering Layers. Extended application risk analysis A32.10 extends cloud risk management with new risk triggers of interest and unique filtering capabilities. When using A32.10, VMware NSX-T users can receive risk notifications, so they are aware of the potential compliance violations introduced by applications. “In this fast pace era of digital transformation, speed is of the essence. Unfortunately, many organizations confuse this for agility and take too many risks with their security, leaving them vulnerable to attack.” said Eran Shiff, Vice President, Product, of AlgoSec. “A32.10 makes it easier for organizations to securely accelerate application connectivity, enabling them to move fast across multi-cloud and hybrid environments and stay ahead of security threats, increasing business agility and compliance.” AlgoSec ASMS A32.10 is generally available. About AlgoSec AlgoSec, a global cybersecurity leader, empowers organizations to securely accelerate application delivery by automating application connectivity and security policy, anywhere. The AlgoSec platform enables the world’s most complex organizations to gain visibility, reduce risk and process changes at zero-touch across the hybrid network. AlgoSec’s patented application-centric view of the hybrid network enables business owners, application owners, and information security professionals to talk the same language, so organizations can deliver business applications faster while achieving a heightened security posture. Over 1,800 of the world’s leading organizations trust AlgoSec to help secure their most critical workloads across public cloud, private cloud, containers, and on-premises networks, while taking advantage of almost two decades of leadership in Network Security Policy Management. See what securely accelerating your digital transformation, move-to-cloud, infrastructure modernization, or micro-segmentation initiatives looks like at www.algosec.com Media Contacts: Tsippi Dach AlgoSec [email protected] Jenni Livesley Context Public Relations [email protected] +44(0)300 124 6100

A network security policy is a critical part of your IT cyber policy It helps determine what traffic is allowed on your network, keeping critical assets secure Network security policy examples & procedures ---- ------- Schedule a Demo Select a size ----- Get the latest insights from the experts Application-aware network security! Securing the business applications on your network Keep Reading Avoiding the Security/Agility Tradeoff with Network Security Policy Automation Keep Reading Examining the Security Policy Management Maturity Model Keep Reading Choose a better way to manage your network

Explore top-rated FireMon alternatives for firewall security management. Find the best solutions for your needs based on our ranked and rated comparison. Top 10 FireMon competitors & alternatives (ranked & rated) ---- ------- Schedule a Demo Select a size ----- Get the latest insights from the experts Use these six best practices to simplify compliance and risk mitigation with the AlgoSec platform White paper Learn how AlgoSec can help you pass PCI-DSS Audits and ensure continuous compliance Solution overview See how this customer improved compliance readiness and risk Case study Choose a better way to manage your network

Securely accelerate application delivery by automating application connectivity and security policy across the hybrid network estate. Solución de gestión de seguridad Algosec Bienvenue! Gestionar sus políticas de seguridad de redes en todos los cortafuegos de las instalaciones y en controles de seguridad de la nube es un acto que debe llevarse a cabo de manera equilibrada. Por un lado, debe reducir los riesgos y minimizar la superficie de ataque, y por el otro, debe permitir la productividad al brindar conectividad para sus aplicaciones empresariales más importantes. Sin embargo, los procesos de gestión de políticas de seguridad siempre han sido complejos, prolongados y plagados de errores. No debería ser así. Tanto en las instalaciones como en la nube, AlgoSec simplifica y automatiza la gestión de políticas de seguridad en las redes para que su empresa se vuelva más ágil, más segura y más eficiente, ¡todo el tiempo! Un enfoque de la inigualable vida útil para la gestión de políticas de seguridad AlgoSec es inigualable por el hecho de que gestiona toda la vida útil de las políticas de seguridad para garantizar conectividad constante y segura para sus aplicaciones empresariales. Con muchísima claridad podrá descubrir automáticamente los requerimientos de conectividad de la aplicación, analizar los riesgos proactivamente, planificar y ejecutar cambios de seguridad en la red rápidamente, y desactivar reglas del cortafuegos de manera segura, todo en cero toques y dinámicamente orquestado en su entorno heterogéneo. Con AlgoSec usted puede Unificar la gestión de políticas de seguridad de redes en nubes heterogéneas, y en entornos definidos por software o en instalaciones Garantice el cumplimiento continuo y reduzca drásticamente los esfuerzos de preparación para auditorías del cortafuegos Proporcione conectividad a las aplicaciones de manera rápida y segura y evite interrupciones en las redes linee la seguridad, las redes y los equipos de aplicación e impulse las operaciones de seguridad de los programadores Automatice la gestión de cambios en el cortafuegos y elimine las configuraciones incorrectas Reduzca el riesgo a través de la configuración de seguridad correcta y la segmentación de red efectiva La Solución de gestión de seguridad AlgoSec Análisis de red de políticas de seguridad Más información Firewall Analyzer Automatización de cambios en las políticas de seguridad Más información FireFlow Calculadora de Retorno de inversión (ROI) Folleto de la solución AlgoSec Representante local Gil Kremer Phone: +55-11-991068906
Email: [email protected] Relevant links TELEFÓNICA MÉXICO Estudio de caso NATURA Estudio de caso Schedule time with one of our experts

Like all modern cloud providers, Amazon adopts the shared responsibility model for cloud security. Amazon guarantees secure... AWS NACL best practices: How to combine security groups with network ACLs effectively Prof. Avishai Wool 2 min read Prof. Avishai Wool Short bio about author here Lorem ipsum dolor sit amet consectetur. Vitae donec tincidunt elementum quam laoreet duis sit enim. Duis mattis velit sit leo diam. Tags Share this article 8/28/23 Published Like all modern cloud providers, Amazon adopts the shared responsibility model for cloud security. Amazon guarantees secure infrastructure for Amazon Web Services, while AWS users are responsible for maintaining secure configurations. That requires using multiple AWS services and tools to manage traffic. You’ll need to develop a set of inbound rules for incoming connections between your Amazon Virtual Private Cloud (VPC) and all of its Elastic Compute (EC2) instances and the rest of the Internet. You’ll also need to manage outbound traffic with a series of outbound rules. Your Amazon VPC provides you with several tools to do this. The two most important ones are security groups and Network Access Control Lists (NACLs). Security groups are stateful firewalls that secure inbound traffic for individual EC2 instances. Network ACLs are stateless firewalls that secure inbound and outbound traffic for VPC subnets. Managing AWS VPC security requires configuring both of these tools appropriately for your unique security risk profile. This means planning your security architecture carefully to align it the rest of your security framework. For example, your firewall rules impact the way Amazon Identity Access Management (IAM) handles user permissions. Some (but not all) IAM features can be implemented at the network firewall layer of security. Before you can manage AWS network security effectively , you must familiarize yourself with how AWS security tools work and what sets them apart. Everything you need to know about security groups vs NACLs AWS security groups explained: Every AWS account has a single default security group assigned to the default VPC in every Region. It is configured to allow inbound traffic from network interfaces assigned to the same group, using any protocol and any port. It also allows all outbound traffic using any protocol and any port. Your default security group will also allow all outbound IPv6 traffic once your VPC is associated with an IPv6 CIDR block. You can’t delete the default security group, but you can create new security groups and assign them to AWS EC2 instances. Each security group can only contain up to 60 rules, but you can set up to 2500 security groups per Region. You can associate many different security groups to a single instance, potentially combining hundreds of rules. These are all allow rules that allow traffic to flow according the ports and protocols specified. For example, you might set up a rule that authorizes inbound traffic over IPv6 for linux SSH commands and sends it to a specific destination. This could be different from the destination you set for other TCP traffic. Security groups are stateful, which means that requests sent from your instance will be allowed to flow regardless of inbound traffic rules. Similarly, VPC security groups automatically responses to inbound traffic to flow out regardless of outbound rules. However, since security groups do not support deny rules, you can’t use them to block a specific IP address from connecting with your EC2 instance. Be aware that Amazon EC2 automatically blocks email traffic on port 25 by default – but this is not included as a specific rule in your default security group. AWS NACLs explained: Your VPC comes with a default NACL configured to automatically allow all inbound and outbound network traffic. Unlike security groups, NACLs filter traffic at the subnet level. That means that Network ACL rules apply to every EC2 instance in the subnet, allowing users to manage AWS resources more efficiently. Every subnet in your VPC must be associated with a Network ACL. Any single Network ACL can be associated with multiple subnets, but each subnet can only be assigned to one Network ACL at a time. Every rule has its own rule number, and Amazon evaluates rules in ascending order. The most important characteristic of NACL rules is that they can deny traffic. Amazon evaluates these rules when traffic enters or leaves the subnet – not while it moves within the subnet. You can access more granular data on data flows using VPC flow logs. Since Amazon evaluates NACL rules in ascending order, make sure that you place deny rules earlier in the table than rules that allow traffic to multiple ports. You will also have to create specific rules for IPv4 and IPv6 traffic – AWS treats these as two distinct types of traffic, so rules that apply to one do not automatically apply to the other. Once you start customizing NACLs, you will have to take into account the way they interact with other AWS services. For example, Elastic Load Balancing won’t work if your NACL contains a deny rule excluding traffic from 0.0.0.0/0 or the subnet’s CIDR. You should create specific inclusions for services like Elastic Load Balancing, AWS Lambda, and AWS CloudWatch. You may need to set up specific inclusions for third-party APIs, as well. You can create these inclusions by specifying ephemeral port ranges that correspond to the services you want to allow. For example, NAT gateways use ports 1024 to 65535. This is the same range covered by AWS Lambda functions, but it’s different than the range used by Windows operating systems. When creating these rules, remember that unlike security groups, NACLs are stateless. That means that when responses to allowed traffic are generated, those responses are subject to NACL rules. Misconfigured NACLs deny traffic responses that should be allowed, leading to errors, reduced visibility, and potential security vulnerabilities . How to configure and map NACL associations A major part of optimizing NACL architecture involves mapping the associations between security groups and NACLs. Ideally, you want to enforce a specific set of rules at the subnet level using NACLs, and a different set of instance-specific rules at the security group level. Keeping these rulesets separate will prevent you from setting inconsistent rules and accidentally causing unpredictable performance problems. The first step in mapping NACL associations is using the Amazon VPC console to find out which NACL is associated with a particular subnet. Since NACLs can be associated with multiple subnets, you will want to create a comprehensive list of every association and the rules they contain. To find out which NACL is associated with a subnet: Open the Amazon VPC console . Select Subnets in the navigation pane. Select the subnet you want to inspect. The Network ACL tab will display the ID of the ACL associated with that network, and the rules it contains. To find out which subnets are associated with a NACL: Open the Amazon VPC console . Select Network ACLS in the navigation pane. Click over to the column entitled Associated With. Select a Network ACL from the list. Look for Subnet associations on the details pane and click on it. The pane will show you all subnets associated with the selected Network ACL. Now that you know how the difference between security groups and NACLs and you can map the associations between your subnets and NACLs, you’re ready to implement some security best practices that will help you strengthen and simplify your network architecture. 5 best practices for AWS NACL management Pay close attention to default NACLs, especially at the beginning Since every VPC comes with a default NACL, many AWS users jump straight into configuring their VPC and creating subnets, leaving NACL configuration for later. The problem here is that every subnet associated with your VPC will inherit the default NACL. This allows all traffic to flow into and out of the network. Going back and building a working security policy framework will be difficult and complicated – especially if adjustments are still being made to your subnet-level architecture. Taking time to create custom NACLs and assign them to the appropriate subnets as you go will make it much easier to keep track of changes to your security posture as you modify your VPC moving forward. Implement a two-tiered system where NACLs and security groups complement one another Security groups and NACLs are designed to complement one another, yet not every AWS VPC user configures their security policies accordingly. Mapping out your assets can help you identify exactly what kind of rules need to be put in place, and may help you determine which tool is the best one for each particular case. For example, imagine you have a two-tiered web application with web servers in one security group and a database in another. You could establish inbound NACL rules that allow external connections to your web servers from anywhere in the world (enabling port 443 connections) while strictly limiting access to your database (by only allowing port 3306 connections for MySQL). Look out for ineffective, redundant, and misconfigured deny rules Amazon recommends placing deny rules first in the sequential list of rules that your NACL enforces. Since you’re likely to enforce multiple deny rules per NACL (and multiple NACLs throughout your VPC), you’ll want to pay close attention to the order of those rules, looking for conflicts and misconfigurations that will impact your security posture. Similarly, you should pay close attention to the way security group rules interact with your NACLs. Even misconfigurations that are harmless from a security perspective may end up impacting the performance of your instance, or causing other problems. Regularly reviewing your rules is a good way to prevent these mistakes from occurring. Limit outbound traffic to the required ports or port ranges When creating a new NACL, you have the ability to apply inbound or outbound restrictions. There may be cases where you want to set outbound rules that allow traffic from all ports. Be careful, though. This may introduce vulnerabilities into your security posture. It’s better to limit access to the required ports, or to specify the corresponding port range for outbound rules. This establishes the principle of least privilege to outbound traffic and limits the risk of unauthorized access that may occur at the subnet level. Test your security posture frequently and verify the results How do you know if your particular combination of security groups and NACLs is optimal? Testing your architecture is a vital step towards making sure you haven’t left out any glaring vulnerabilities. It also gives you a good opportunity to address misconfiguration risks. This doesn’t always mean actively running penetration tests with experienced red team consultants, although that’s a valuable way to ensure best-in-class security. It also means taking time to validate your rules by running small tests with an external device. Consider using AWS flow logs to trace the way your rules direct traffic and using that data to improve your work. How to diagnose security group rules and NACL rules with flow logs Flow logs allow you to verify whether your firewall rules follow security best practices effectively. You can follow data ingress and egress and observe how data interacts with your AWS security rule architecture at each step along the way. This gives you clear visibility into how efficient your route tables are, and may help you configure your internet gateways for optimal performance. Before you can use the Flow Log CLI, you will need to create an IAM role that includes a policy granting users the permission to create, configure, and delete flow logs. Flow logs are available at three distinct levels, each accessible through its own console: Network interfaces VPCs Subnets You can use the ping command from an external device to test the way your instance’s security group and NACLs interact. Your security group rules (which are stateful) will allow the response ping from your instance to go through. Your NACL rules (which are stateless) will not allow the outbound ping response to travel back to your device. You can look for this activity through a flow log query. Here is a quick tutorial on how to create a flow log query to check your AWS security policies. First you’ll need to create a flow log in the AWS CLI. This is an example of a flow log query that captures all rejected traffic for a specified network interface. It delivers the flow logs to a CloudWatch log group with permissions specified in the IAM role: aws ec2 create-flow-logs \ –resource-type NetworkInterface \ –resource-ids eni-1235b8ca123456789 \ –traffic-type ALL \ –log-group-name my-flow-logs \ –deliver-logs-permission-arn arn:aws:iam::123456789101:role/publishFlowLogs Assuming your test pings represent the only traffic flowing between your external device and EC2 instance, you’ll get two records that look like this: 2 123456789010 eni-1235b8ca123456789 203.0.113.12 172.31.16.139 0 0 1 4 336 1432917027 1432917142 ACCEPT OK 2 123456789010 eni-1235b8ca123456789 172.31.16.139 203.0.113.12 0 0 1 4 336 1432917094 1432917142 REJECT OK To parse this data, you’ll need to familiarize yourself with flow log syntax. Default flow log records contain 14 arguments, although you can also expand custom queries to return more than double that number: Version tells you the version currently in use. Default flow logs requests use Version 2. Expanded custom requests may use Version 3 or 4. Account-id tells you the account ID of the owner of the network interface that traffic is traveling through. The record may display as unknown if the network interface is part of an AWS service like a Network Load Balancer. Interface-id shows the unique ID of the network interface for the traffic currently under inspection. Srcaddr shows the source of incoming traffic, or the address of the network interface for outgoing traffic. In the case of IPv4 addresses for network interfaces, it is always its private IPv4 address. Dstaddr shows the destination of outgoing traffic, or the address of the network interface for incoming traffic. In the case of IPv4 addresses for network interfaces, it is always its private IPv4 address. Srcport is the source port for the traffic under inspection. Dstport is the destination port for the traffic under inspection. Protocol refers to the corresponding IANA traffic protocol number . Packets describes the number of packets transferred. Bytes describes the number of bytes transferred. Start shows the start time when the first data packet was received. This could be up to one minute after the network interface transmitted or received the packet. End shows the time when the last data packet was received. This can be up to one minutes after the network interface transmitted or received the data packet. Action describes what happened to the traffic under inspection: ACCEPT means that traffic was allowed to pass. REJECT means the traffic was blocked, typically by security groups or NACLs. Log-status confirms the status of the flow log: OK means data is logging normally. NODATA means no network traffic to or from the network interface was detected during the specified interval. SKIPDATA means some flow log records are missing, usually due to internal capacity restraints or other errors. Going back to the example above, the flow log output shows that a user sent a command from a device with the IP address 203.0.113.12 to the network interface’s private IP address, which is 172.31.16.139. The security group’s inbound rules allowed the ICMP traffic to travel through, producing an ACCEPT record. However, the NACL did not let the ping response go through, because it is stateless. This generated the REJECT record that followed immediately after. If you configure your NACL to permit output ICMP traffic and run this test again, the second flow log record will change to ACCEPT. azon Web Services (AWS) is one of the most popular options for organizations looking to migrate their business applications to the cloud. It’s easy to see why: AWS offers high capacity, scalable and cost-effective storage, and a flexible, shared responsibility approach to security. Essentially, AWS secures the infrastructure, and you secure whatever you run on that infrastructure. However, this model does throw up some challenges. What exactly do you have control over? How can you customize your AWS infrastructure so that it isn’t just secure today, but will continue delivering robust, easily managed security in the future? The basics: security groups AWS offers virtual firewalls to organizations, for filtering traffic that crosses their cloud network segments. The AWS firewalls are managed using a concept called Security Groups. These are the policies, or lists of security rules, applied to an instance – a virtualized computer in the AWS estate. AWS Security Groups are not identical to traditional firewalls, and they have some unique characteristics and functionality that you should be aware of, and we’ve discussed them in detail in video lesson 1: the fundamentals of AWS Security Groups , but the crucial points to be aware of are as follows. First, security groups do not deny traffic – that is, all the rules in security groups are positive, and allow traffic. Second, while security group rules can be set to specify a traffic source, or a destination, they cannot specify both on the same rule. This is because AWS always sets the unspecified side (source or destination) as the instance to which the group is applied. Finally, single security groups can be applied to multiple instances, or multiple security groups can be applied to a single instance: AWS is very flexible. This flexibility is one of the unique benefits of AWS, allowing organizations to build bespoke security policies across different functions and even operating systems, mixing and matching them to suit their needs. Adding Network ACLs into the mix To further enhance and enrich its security filtering capabilities AWS also offers a feature called Network Access Control Lists (NACLs). Like security groups, each NACL is a list of rules, but there are two important differences between NACLs and security groups. The first difference is that NACLs are not directly tied to instances, but are tied with the subnet within your AWS virtual private cloud that contains the relevant instance. This means that the rules in a NACL apply to all of the instances within the subnet, in addition to all the rules from the security groups. So a specific instance inherits all the rules from the security groups associated with it, plus the rules associated with a NACL which is optionally associated with a subnet containing that instance. As a result NACLs have a broader reach, and affect more instances than a security group does. The second difference is that NACLs can be written to include an explicit action, so you can write ‘deny’ rules – for example to block traffic from a particular set of IP addresses which are known to be compromised. The ability to write ‘deny’ actions is a crucial part of NACL functionality. It’s all about the order As a consequence, when you have the ability to write both ‘allow’ rules and ‘deny’ rules, the order of the rules now becomes important. If you switch the order of the rules between a ‘deny’ and ‘allow’ rule, then you’re potentially changing your filtering policy quite dramatically. To manage this, AWS uses the concept of a ‘rule number’ within each NACL. By specifying the rule number, you can identify the correct order of the rules for your needs. You can choose which traffic you deny at the outset, and which you then actively allow. As such, with NACLs you can manage security tasks in a way that you cannot do with security groups alone. However, we did point out earlier that an instance inherits security rules from both the security groups, and from the NACLs – so how do these interact? The order by which rules are evaluated is this; For inbound traffic, AWS’s infrastructure first assesses the NACL rules. If traffic gets through the NACL, then all the security groups that are associated with that specific instance are evaluated, and the order in which this happens within and among the security groups is unimportant because they are all ‘allow’ rules. For outbound traffic, this order is reversed: the traffic is first evaluated against the security groups, and then finally against the NACL that is associated with the relevant subnet. You can see me explain this topic in person in my new whiteboard video: Schedule a demo Related Articles Q1 at AlgoSec: What innovations and milestones defined our start to 2026? AlgoSec Reviews Mar 19, 2023 · 2 min read 2025 in review: What innovations and milestones defined AlgoSec’s transformative year in 2025? AlgoSec Reviews Mar 19, 2023 · 2 min read Navigating Compliance in the Cloud AlgoSec Cloud Mar 19, 2023 · 2 min read Speak to one of our experts Speak to one of our experts Work email* First name* Last name* Company* country* Select country... Short answer* By submitting this form, I accept AlgoSec's privacy policy Schedule a call

Efficiently improve network security and performance by cleaning up and optimizing your firewall rules Streamline operations and meet compliance requirements with ease Firewall rule cleanup & performance optimization tool Select a size Which network Can AlgoSec be used for continuous compliance monitoring? Yes, AlgoSec supports continuous compliance monitoring. As organizations adapt their security policies to meet emerging threats and address new vulnerabilities, they must constantly verify these changes against the compliance frameworks they subscribe to. AlgoSec can generate risk assessment reports and conduct internal audits on-demand, allowing compliance officers to monitor compliance performance in real-time. Security professionals can also use AlgoSec to preview and simulate proposed changes to the organization’s security policies. This gives compliance officers a valuable degree of lead-time before planned changes impact regulatory guidelines and allows for continuous real-time monitoring. Streamlining firewall policies: cleanup & optimization Dangers of outdated firewall rulesets How to audit your existing firewall policy How to properly perform a firewall cleanup Firewall optimization best practices Automate firewall configurations with AlgoSec Get the latest insights from the experts Use these six best practices to simplify compliance and risk mitigation with the AlgoSec Copy White paper Learn how AlgoSec can help you pass PCI-DSS Audits and ensure Copy Solution overview See how this customer improved compliance readiness and risk Copy Case study Schedule time with one of our experts Work email* First name* Last name* Company* country* Select country... Short answer* By submitting this form, I accept AlgoSec's privacy policy Continue

AlgoSec Resident Engineer Services provides a dedicated onsite remote engineer for support, maintenance, management issues to fit your network security needs AlgoSec resident engineer AlgoSec resident engineer service Dedicated onsite/remote engineer The AlgoSec Resident Engineer Service Pack is a comprehensive service with a dedicated technical engineer that acts as a partner and advisor. The AlgoSec Resident Engineer (ARE) typically devotes at least one day a week to helping you accelerate your network security management and achieve immediate success. The AlgoSec Resident Engineer becomes the expert in your organization’s processes and requirements as well as in your network’s specific configurations and challenges – delivering higher business value faster. Even when your organization has staffing changes, the AlgoSec Resident Engineer preserves organizational memory, ensuring a seamless transition and accelerating the onboarding of new employees so you aren’t left behind. View detailed information The business impact: Exclusive access to AlgoSec R&D and product management Consultancy to address your business needs Dedicated technical engineer Expertise, training, and knowledge sharing Accelerate adoption Business continuity during staffing transitions Enhance workforce productivity AlgoSec resident
engineer Read document Relevant resources Choose a better way to manage your network Choose a better way to manage your network Work email* First name* Last name* Company* country* Select country... Short answer* Long answer Send message

View AlgoSec s press releases to stay on top of the latest company announcements Press releases Filter by release year AlgoSec Horizon A33.30 eliminates security silos, accelerates application delivery, automates policy management and continuously reduces cyber risk July 22, 2026 Horizon unifies application connectivity governance across hybrid and multi-cloud environments through AI-powered automation 2026 AlgoSec Posts 37% YoY new Business Growth in 2025 as Enterprises Prioritize Application-Centric Security February 18, 2026 Over 90% gross dollar retention and 37% year-over-year new business growth reflect demand for visibility across complex hybrid environments 2024 AlgoSec’s 2026 State of Network Security Report Reveals Rising Demand for Consolidation and Control February 4, 2026 One of the market’s most comprehensive annual vendor-agnostic studies found that rapid cloud expansion, distributed workloads, and AI-driven traffic patterns are driving increased demand for unified policy control and end-to-end transparency 2024 AlgoSec Security Management Solution A33.20 removes network security change friction across hybrid and multi-cloud networks January 22, 2026 The new capabilities empower teams to move faster with clarity, control, and business-aligned risk prioritization 2024 AlgoSec’s Horizon Platform Fuels Company Growth and Global Application-Centric Security September 9, 2025 A gross dollar retention rate of over 90% and 36% year-over-year new business growth highlight adoption across industries 2025 AlgoSec Security Management solution A33.10 delivers new compliance reporting and precise discovery of application connectivity May 20, 2025 The new product version release provides extended multi-cloud hybrid network visibility, reduces risk exposure and addresses new compliance regulations in a unified platform 2024 AlgoSec Wins SC Award for Best Security Company, Global InfoSec Award for Best Service Cybersecurity Company May 14, 2025 These award wins follow a year of double-digit year-on-year annual recurring revenue growth and the launch of the AlgoSec Horizon Platform 2024 AlgoSec’s 2025 State of Network Security Report Reveals Growing Adoption of Zero-Trust Architecture and Multi-Cloud Environments April 3, 2025 Annual vendor-agnostic research found businesses continue to prioritize multi-cloud environments, with Cisco, Microsoft Azure, AWS, Palo Alto Networks and Fortinet leading the way 2024 AlgoSec Achieves Strong Growth in 2024, Expands Customer Partnerships and Services Driven by Application-Centric Vision March 20, 2025 Continued growth underscores AlgoSec’s commitment to innovation and leadership in application-centric security to drive business value 2024 2023 AlgoSec Horizon A33.30 eliminates security silos, accelerates application delivery, automates policy management and continuously reduces cyber risk Date Horizon unifies application connectivity governance across hybrid and multi-cloud environments through AI-powered automation AlgoSec Posts 37% YoY new Business Growth in 2025 as Enterprises Prioritize Application-Centric Security Date Over 90% gross dollar retention and 37% year-over-year new business growth reflect demand for visibility across complex hybrid environments AlgoSec’s 2026 State of Network Security Report Reveals Rising Demand for Consolidation and Control Date One of the market’s most comprehensive annual vendor-agnostic studies found that rapid cloud expansion, distributed workloads, and AI-driven traffic patterns are driving increased demand for unified policy control and end-to-end transparency AlgoSec Security Management Solution A33.20 removes network security change friction across hybrid and multi-cloud networks Date The new capabilities empower teams to move faster with clarity, control, and business-aligned risk prioritization AlgoSec’s Horizon Platform Fuels Company Growth and Global Application-Centric Security Date A gross dollar retention rate of over 90% and 36% year-over-year new business growth highlight adoption across industries AlgoSec Security Management solution A33.10 delivers new compliance reporting and precise discovery of application connectivity Date The new product version release provides extended multi-cloud hybrid network visibility, reduces risk exposure and addresses new compliance regulations in a unified platform AlgoSec Wins SC Award for Best Security Company, Global InfoSec Award for Best Service Cybersecurity Company Date These award wins follow a year of double-digit year-on-year annual recurring revenue growth and the launch of the AlgoSec Horizon Platform AlgoSec’s 2025 State of Network Security Report Reveals Growing Adoption of Zero-Trust Architecture and Multi-Cloud Environments Date Annual vendor-agnostic research found businesses continue to prioritize multi-cloud environments, with Cisco, Microsoft Azure, AWS, Palo Alto Networks and Fortinet leading the way AlgoSec Achieves Strong Growth in 2024, Expands Customer Partnerships and Services Driven by Application-Centric Vision Date Continued growth underscores AlgoSec’s commitment to innovation and leadership in application-centric security to drive business value 2022 AlgoSec Horizon A33.30 eliminates security silos, accelerates application delivery, automates policy management and continuously reduces cyber risk Date Horizon unifies application connectivity governance across hybrid and multi-cloud environments through AI-powered automation AlgoSec Posts 37% YoY new Business Growth in 2025 as Enterprises Prioritize Application-Centric Security Date Over 90% gross dollar retention and 37% year-over-year new business growth reflect demand for visibility across complex hybrid environments AlgoSec’s 2026 State of Network Security Report Reveals Rising Demand for Consolidation and Control Date One of the market’s most comprehensive annual vendor-agnostic studies found that rapid cloud expansion, distributed workloads, and AI-driven traffic patterns are driving increased demand for unified policy control and end-to-end transparency AlgoSec Security Management Solution A33.20 removes network security change friction across hybrid and multi-cloud networks Date The new capabilities empower teams to move faster with clarity, control, and business-aligned risk prioritization AlgoSec’s Horizon Platform Fuels Company Growth and Global Application-Centric Security Date A gross dollar retention rate of over 90% and 36% year-over-year new business growth highlight adoption across industries AlgoSec Security Management solution A33.10 delivers new compliance reporting and precise discovery of application connectivity Date The new product version release provides extended multi-cloud hybrid network visibility, reduces risk exposure and addresses new compliance regulations in a unified platform AlgoSec Wins SC Award for Best Security Company, Global InfoSec Award for Best Service Cybersecurity Company Date These award wins follow a year of double-digit year-on-year annual recurring revenue growth and the launch of the AlgoSec Horizon Platform AlgoSec’s 2025 State of Network Security Report Reveals Growing Adoption of Zero-Trust Architecture and Multi-Cloud Environments Date Annual vendor-agnostic research found businesses continue to prioritize multi-cloud environments, with Cisco, Microsoft Azure, AWS, Palo Alto Networks and Fortinet leading the way AlgoSec Achieves Strong Growth in 2024, Expands Customer Partnerships and Services Driven by Application-Centric Vision Date Continued growth underscores AlgoSec’s commitment to innovation and leadership in application-centric security to drive business value Choose a better way to manage your network Work email* First name* Last name* Company* country* Select country... Short answer* By submitting this form, I accept AlgoSec's privacy policy Continue

Overcome hybrid and multi-cloud security challenges with strategies to enhance visibility, enforce policies, and protect data across diverse cloud environments. Hybrid & multi-cloud Security challenges ---- ------- Schedule a Demo Select a size ----- Get the latest insights from the experts Choose a better way to manage your network

Looking to learn about cloud security compliance requirements and standards This article covers everything you need to know how AlgoSec can help your company Cloud compliance standards & security best practices ---- ------- Schedule a Demo Select a size ----- Get the latest insights from the experts Use these six best practices to simplify compliance and risk White paper Choose a better way to manage your network

Explore Algosec's customer success stories to see how organizations worldwide improve security, compliance, and efficiency with our solutions. Leading Life Insurance Company Ensures Security and Compliance Organization Life Insurance Industry Financial Services Headquarters Texas, USA Download case study Share Customer
success stories "AlgoSec worked right out of the box. We got started quickly and never looked back.” A leading insurance provider of life, disability and other benefits for individuals increases efficiency and ensures continuous compliance on their networks. Background This life insurance company provides insurance and wealth-management products and services to millions of Americans. The company employs thousands of people and maintains a network of several thousand financial representatives. They offer a wide range of insurance products and services that include life insurance, disability income insurance, annuities, investments, dental and vision. Challenges For decades, the company operated a large and growing data center in Bethlehem, PA which they recently transferred to Dallas, TX. During and since the transfer, the company has been replacing much of its multi-vendor network infrastructure, consolidating on Cisco Firepower technology, but still maintaining vestiges of other routers, firewalls and network equipment. At the new data center, the company’s IT staff maintains more than 100 firewalls that host some 10,000 rules. The company’s network security engineer described the considerable pressure on the security staff: “Change requests are frequent, 25-30 per week, demanding considerable time and effort by the security team.” Due to the presence of firewalls from multiple vendors, change requests were analyzed manually and pushed to devices with great care so as not to interrupt the operation of a rapidly growing body of applications. “The change–request process was tedious and very time consuming,” declared the engineer. “as was the pressure to maintain a strong compliance posture at all times.” The company is subject to a litany of demanding insurance-industry regulations that concern the care of personal information and processes. Managing risk is critical to the success of the business and being able to ascertain compliance with regulations is always vital. Solution The security team turned to AlgoSec to help them manage network security policy across the large data center that includes firewalls from multiple vendors. After a careful review, the security team acquired AlgoSec’s Horizon Security Analyzer to speed up the process of firewall change management as well as to continuously quantify the degree of compliance and level of risk. Vendor-agnostic AlgoSec Horizon Security Analyzer delivers visibility and analysis of complex network security policies across on–premise and cloud networks. It automates and simplifies security operations including troubleshooting, auditing and risk analysis. Horizon Security Analyzer optimizes the configuration of firewalls, routers, web proxies and related network infrastructure to ensure security and compliance. Results After a very short installation and learning period, the security staff became proficient at operating Horizon Security Analyzer helpful capabilities. Soon thereafter, staff members undertook AlgoSec certification courses to become experts in using the solution for firewall analysis. “AlgoSec worked right out of the box,” said the engineer. “We got started quickly and never looked back.” The AlgoSec solution has significantly improved processes, delivering significantly improved results for their security team: Reduced time to analyze and optimize firewall rules, automatically checking for shadow rules and discovering other rules eligible for consolidation or deletion. Continual optimization of firewall rules across their entire network estate. Increased efficiency of security staff, enabling them to keep up with the volume of change requests. Accelerated and more accurate change verification. Audit-readiness, generating scheduled and on-demand compliance reports. The security staff looks forward to implementing AlgoSec Horizon FireFlow (AFF), that will enable them to push changes automatically to their population of firewalls, eliminating errors and further reducing risk. With AFF, the staff will be able to respond to changing business requirements with increased speed and agility. They added: “We are also checking out AlgoSec’s new cloud-security solution since we are migrating a growing number of applications to AWS.” Schedule time with one of our experts

Continued growth underscores AlgoSec’s commitment to innovation and leadership in application-centric security to drive business value AlgoSec Achieves Strong Growth in 2024, Expands Customer Partnerships and Services Driven by Application-Centric Vision Continued growth underscores AlgoSec’s commitment to innovation and leadership in application-centric security to drive business value March 20, 2025 Speak to one of our experts RIDGEFIELD PARK, NJ, March 20, 2025 – AlgoSec , a global cybersecurity leader, today announced a double-digit year-on-year annual recurring revenue growth and a gross dollar retention of over 90%. The company has consistently generated positive cash flow and remained debt-free since it was founded in 2004. The company also saw an increase in multiple industry verticals, including Finance, Government, Telecommunications, Healthcare, Retail, Utilities and Transportation. These accomplishments are a testament to AlgoSec’s strong market position, customer satisfaction and application-centric approach to cybersecurity across the hybrid environment. To effectively execute and meet the needs of the world’s largest organizations, AlgoSec has the highest number of employees and 70% more research and development engineers than any competitor. According to Gartner , the fast-evolving threat environment is changing the cybersecurity industry, as a result of increases in generative AI, cloud adoption and regulations. As the cybersecurity industry continues to evolve and the needs of businesses change, AlgoSec remains committed to investing heavily in product innovation and development. Stemming directly from these market shifts, AlgoSec recently launched the AlgoSec Horizon Platform , the industry's first application-centric security management platform for the hybrid network environment. The AlgoSec Horizon platform serves as a single source for visibility into security and compliance issues across the hybrid network environment to automatically discover and identify their business applications across multi-clouds, and remediate risks more effectively. “As a company led by its founders and focused on its customers, AlgoSec’s consistent growth showcases our ability to empower the most complex organizations to securely accelerate their application delivery,” said Chris Thomas , Chief Revenue Officer at AlgoSec. “Heading into our 21st year of business, we look forward to pushing these efforts even further to help organizations future-proof their network security through our unique application-centric approach.” Additional 2024 AlgoSec milestones and company accomplishments include: Winning two Cisco Partnership Awards , recognizing the value for securing application connectivity across hybrid networks Being recognized with Established Vendor Designation in 2024 Gartner® Peer Insights™ Voice of the Customer for Network Automation Platforms Listing as a 2024 SC Awards Finalist: Best Enterprise Security Solution for AlgoSec’s application-centric platform Launching the company’s AI-powered security platform to securely manage application-centric connectivity and remediate risk in real time Ranking as the #1 network security management solution in the market by real users on Gartner Peer Insights, G2 and Peerspot For more information on AlgoSec’s vision for 2025 and beyond, and to discover why over 2,200 of the world's most complex organizations trust AlgoSec to help secure their most critical workloads, visit www.algosec.com . About AlgoSec AlgoSec, a global cybersecurity leader, empowers organizations to securely accelerate application delivery up to 10 times faster by automating application connectivity and security policy across the hybrid network environment. With two decades of expertise securing hybrid networks, over 2,200 of the world's most complex organizations trust AlgoSec to help secure their most critical workloads. AlgoSec Horizon platform utilizes advanced AI capabilities, enabling users to automatically discover and identify their business applications across multi-clouds, and remediate risks more effectively. It serves as a single source for visibility into security and compliance issues across the hybrid network environment, to ensure ongoing adherence to internet security standards, industry, and internal regulations. Additionally, organizations can leverage intelligent change automation to streamline security change processes, thus improving security and agility. Learn how AlgoSec enables application owners, information security experts, SecOps and cloud security teams to deploy business applications faster while maintaining security at www.algosec.com . MEDIA CONTACT: Michelle Williams Alloy, on behalf of AlgoSec [email protected] 855-300-8209