Search results

Prof. Avishai Wool, AlgoSec co-founder and CTO, breaks down the truths and myths about micro-segmentation and how organizations can... Micro-segmentation Why Microsegmentation is Still a Go-To Network Security Strategy 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 5/3/22 Published Prof. Avishai Wool, AlgoSec co-founder and CTO, breaks down the truths and myths about micro-segmentation and how organizations can better secure their network before their next cyberattack Network segmentation isn’t a new concept. For years it’s been the go-to recommendation for CISOs and other security leaders as a means of securing expansive networks and breaking large attack surface areas down into more manageable chunks. Just as we separate areas of a ship with secure doors to prevent flooding in the event of a hull breach, network segmentation allows us to seal off areas of our network to prevent breaches such as ransomware attacks, which tend to self-propagate and spread laterally from machine to machine. Network segmentation tends to work best in controlling north-south traffic in an organization. Its main purpose is to segregate and protect key company data and limit lateral movement by attackers across the network. Micro-segmentation takes this one step further and offers more granular control to help contain lateral east-west movement. It is a technique designed to create secure zones in networks, allowing companies to isolate workloads from one another and introduce tight controls over internal access to sensitive data. Put simply, if network segmentation makes up the floors, ceilings and protective outer hull, micro-segmentation makes up the steel doors and corridors that allow or restrict access to individual areas of the ship. Both methods can be used in combination to fortify cybersecurity posture and reduce risk vulnerability across the security network. How does micro-segmentation help defend against ransomware? The number of ransomware attacks on corporate networks seems to reach record levels with each passing year. Ransomware has become so appealing to cybercriminals that it’s given way to a whole Ransomware-as-a-Service (RaaS) sub-industry, plying would-be attackers with the tools to orchestrate their own attacks. When deploying micro-segmentation across your security network, you can contain ransomware at the onset of an attack. When a breach occurs and malware takes over a machine on a given network, the policy embedded in the micro-segmented network should block the malware’s ability to propagate to an adjacent micro-segment, which in turn can protect businesses from a system-wide shutdown and save them a great financial loss. What does Zero Trust have to do with micro-segmentation? Zero trust is a manifestation of the principle of “least privilege” security credentialing. It is a mindset that guides security teams to not assume that people, or machines, are to be trusted by default. From a network perspective, zero-trust implies that “internal” networks should not be assumed to be more trustworthy than “external” networks – quotation marks are intentional. Therefore, micro-segmentation is the way to achieve zero trust at the network level: by deploying restrictive filtering policy inside the internal network to control east-west traffic. Just as individuals in an organization should only be granted access to data on a need-to-know basis, traffic should only be allowed to travel from one area of the business to another only if the supporting applications require access to those areas. Can a business using a public cloud solution still use micro-segmentation? Prior to the advent of micro-segmentation, it was very difficult to segment networks into zones and sub-zones because it required the physical deployment of equipment. Routing had to be changed, firewalls had to be locally installed, and the segmentation process would have to be carefully monitored and managed by a team of individuals. Fortunately for SecOps teams, this is no longer the case, thanks to the rapid adoption of cloud technology. There seems to be a misconception associated with micro-segmentation where it might be thought of as a strictly private cloud environment network security solution, whereas in reality, micro-segmentation can be deployed in a hybrid cloud environment – public cloud, private cloud and on-premise. In fact, all public cloud networks, including those offered by the likes of Azure and AWS, offer “baked in” filtering capabilities that make controlling traffic much easier. This lends itself well to the concept of micro-segmentation, so even those businesses that use a hybrid cloud setup can still benefit enormously. The Bottom Line Micro-segmentation presents a viable and scalable solution to tighten network security policies, despite its inherent implementation challenges. While many businesses may find it hard to manage this new method of security, it’s nevertheless a worthwhile endeavor. By utilizing a micro-segmentation method as part of its network security strategy, an organization can immediately bolster its network security against possible hackers and potential data breaches. To help you navigate through your micro-segmentation fact-finding journey, watch this webcast or read more in our resource hub . 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

The Web application and service business loves containers, but they present a security challenge. Prevasio has the skills and experience... Cloud Security Don’t Neglect Runtime Container Security 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 9/21/20 Published The Web application and service business loves containers, but they present a security challenge. Prevasio has the skills and experience to meet the challenge. Its runtime scanning technology and techniques will let you avoid the serious risks of vulnerable or compromised containers. The very thing that makes Docker containers convenient — their all-in-one, self-contained structure — makes them opaque to traditional security tests. Instances come and go as needed, sometimes deleting themselves within seconds. This scalable and transient nature isn’t amenable to the usual tools. Prevasio’s approach is specifically designed to analyze and test containers safely, finding any problems before they turn into security incidents. The container supply chain Container images put together code from many sources. They include original source or binary code, application libraries,language support, and configuration data. The developer puts them all together and delivers the resulting image. A complex container has a long supply chain,and many things can go wrong. Each item in the image could carry a risk. The container developer could use buggy or outdated components, or it could use them improperly. The files it imports could be compromised. A Docker image isn’t a straightforward collection of files, like a gzip file. An image may be derived from another image. Extracting all its files and parameters is possible but not straightforward. Vulnerabilities and malicious actions We can divide container risks into two categories: vulnerabilities and malicious code. Vulnerabilities A vulnerability unintentionally introduces risk. An outsider can exploit them to steal information or inflict damage. In a container, they can result from poor-quality or outdated components. The building process for a complex image is hard to keep up to date. There are many ways for something to go wrong. Vulnerability scanners don’t generally work on container images. They can’t find all the components. It’s necessary to check an active container to get adequate insight. This is risky if it’s done in a production environment. Container vulnerabilities include configuration weaknesses as well as problems in code. An image that uses a weak password or unnecessarily exposes administrative functions is open to attacks. Malicious code Malware in a container is more dangerous than vulnerabilities. It could intrude at any point in the supply chain. The developer might receive a compromised version of a runtime library. A few unscrupulous developers put backdoors into code that they ship. Sometimes they add backdoors for testing purposes and forget to remove them from the finished product. The only way to catch malware in a container is by its behavior. Monitoring the network and checking the file system for suspicious changes will discover misbehaving code. The Prevasio solution Security tools designed for statically loaded code aren’t very helpful with containers. Prevasio has created a new approach that analyzes containers without making any assumptions about their safety. It loads them into a sandboxed environment where they can’t do any harm and analyzes them.The analysis includes the following: Scanning of components for known vulnerabilities Automated pen-test attacks Behavioral analysis of running code Traffic analysis to discover suspicious data packets Machine learning to identify malicious binaries The analysis categorizes an image as benign,vulnerable, exploitable, dangerous, or harmful. The administrator looks at agraph to identify any problems visually, without digging through logs. They can tell at a glance whether an image is reasonably safe to run, needs to be sent back for fixes, or should be discarded on the spot. If you look at competing container security solutions, you’ll find that the key is runtime technology. Static analysis, vulnerability scans, and signature checking won’t get you enough protection by themselves. Prevasio gives you the most complete and effective checking of container images, helping you to avoid threats to your data and your business. 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

The persistence of sophisticated ransomware In 2023, organizations faced a surge in ransomware attacks, prompting a reevaluation of... Network Segmentation Navigating the Cybersecurity Horizon in 2024 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 12/17/23 Published The persistence of sophisticated ransomware In 2023, organizations faced a surge in ransomware attacks, prompting a reevaluation of cybersecurity readiness. The focus on high-value assets and critical infrastructure indicated an escalating threat landscape, demanding stronger preemptive measures. This trend is expected to continue in 2024 as cybercriminals exploit vulnerabilities. Beyond relying on technology alone, organizations must adopt strategies like Zero Trust and Micro-segmentation for comprehensive preparedness, fortifying data security. A resolute and practical response is crucial to safeguard critical assets in the evolving cybersecurity landscape. DevSecOps Integration DevSecOps is set to become a cornerstone in software development, integrating security practices proactively. As Infrastructure as a Service (IaaS) popularity rises, customizing security settings becomes challenging, necessitating a shift from network perimeter reliance. Anticipating an “Always-on Security” approach like Infrastructure as Code (IaC), companies can implement policy-based guardrails in the CI/CD pipeline. If risks violating the guardrails are identified, automation should halt for human review. Cloud-Native Application Protection Platforms (CNAPP): The CNAPP market has advanced from basic Cloud Security Posture Management (CSPM) to include varied vulnerability and malware scans, along with crucial behavioral analytics for cloud assets like containers. However, few vendors emphasize deep analysis of Infrastructure as a Service (IaaS) networking controls in risk and compliance reporting. A more complete CNAPP platform should also provide comprehensive analytics of cloud applications’ connectivity exposure. Application-centric approach to network security will supersede basic NSPM Prepare for the shift from NSPM to an application-centric security approach, driven by advanced technologies, to accelerate in 2024. Organizations, grappling with downsizing and staff shortages, will strategically adopt this holistic approach to improve efficiency in the security operations team. Emphasizing knowledge retention and automated change processes will become crucial to maintain security with agility. AI-based enhancements to security processes Generative AI, as heralded by Chat-GPT and its ilk, has made great strides in 2023, and has demonstrated that the technology has a lot of potential. I think that in 2024 we will see many more use cases in which this potential goes from simply being “cool” to a more mature technology that is brought to market to bring real value to owners of security processes. Any use case that involves analyzing, summarizing, or generalizing text, can potentially benefit from a generative AI assist. The trick will be to do so in ways that save human time, without introducing factual hallucinations. 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

In the previous parts of our blog ( part I and part II ), we have described the most important parts of the Sunburst backdoor... Cloud Security Sunburst Backdoor, Part III: DGA & Security Software 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 12/22/20 Published In the previous parts of our blog ( part I and part II ), we have described the most important parts of the Sunburst backdoor functionality and its Domain Generation Algorithm (DGA). This time, let’s have a deeper look into the passive DNS requests reported by Open-Source Context and Zetalytics . The valid DNS requests generated by the malware fall into 2 groups: DNS requests that encode a local domain name DNS requests that encode data The first type of DNS requests allows splitting long domain names into separate requests. These requests are generated by the malware’s functions GetPreviousString() and GetCurrentString() . In general, the format of a DNS request that encodes a domain name may look like: USER_ID.NUM.COMPUTER_DOMAIN[.]appsync-api.us-west-2[.]avsvmcloud[.]com where: USER_ID is an 8-byte user ID that uniquely identifies a compromised host, encoded as a 15-character string NUM is a number of a domain name – either 0 or 1, encoded as a character COMPUTER_DOMAIN is an encoded local computer domain Let’s try decoding the following 3 DNS requests: olc62cocacn7u2q22v02eu.appsync-api.us-west-2.avsvmcloud.com r1qshoj05ji05ac6eoip02jovt6i2v0c.appsync-api.us-west-2.avsvmcloud.com lt5ai41qh5d53qoti3mkmc0.appsync-api.us-west-2.avsvmcloud.com String 1 Let’s start from the 1st string in the list: olc62cocacn7u2q22v02eu.appsync-api.us-west-2.avsvmcloud.com. In this string, the first 15-character string is an encoded USER_ID : “olc62cocacn7u2q” . Once it is base-64 decoded, as explained in the previous post, it becomes a 9-byte byte array: 86 7f 2f be f9 fb a3 ae c4 The first byte in this byte array is a XOR key: 0x86 . Once applied to the 8 bytes that follow it, we get the 8-byte user ID – let’s take a note and write it down, we will need it later: f9 a9 38 7f 7d 25 28 42 Next, let’s take the NUM part of the encoded domain: it’s a character “2” located at the position #15 (starting from 0) of the encrypted domain. In order to decode the NUM number, we have to take the first character of the encrypted domain, take the reminder of its division by 36 , and subtract the NUM ‘s position in the string “0123456789abcdefghijklmnopqrstuvwxyz” : num = domain[0] % 36 – “0123456789abcdefghijklmnopqrstuvwxyz”.IndexOf(domain.Substring(15, 1)); The result is 1 . That means the decrypted domain will be the 2nd part of a full domain name. The first part must have its NUM decoded as 0. The COMPUTER_DOMAIN part of the encrypted domain is “2v02eu” . Once decoded, using the previously explained method, the decoded computer domain name becomes “on.ca” . String 2 Let’s decode the second passive DNS request from our list: r1qshoj05ji05ac6eoip02jovt6i2v0c.appsync-api.us-west-2.avsvmcloud.com Just as before, the decoded 8-byte user ID becomes: f9 a9 38 7f 7d 25 28 42 The NUM part of the encoded domain, located at the position #15 (starting from 0), is a character “6” . Let’s decode it, by taking the first character ( “r” = 114 ), take the reminder of its division by 36 ( 114 % 36 = 6 ), and subtracting the position of the character “6” in the “0123456789abcdefghijklmnopqrstuvwxyz” , which is 6 . The result is 0 . That means the decrypted domain will be the 1st part of the full domain name. The COMPUTER_DOMAIN part of the encrypted domain is “eoip02jovt6i2v0c” . Once decoded, it becomes “city.kingston.” Next, we need to match 2 decrypted domains by the user ID, which is f9 a9 38 7f 7d 25 28 42 in both cases, and concatenate the first and the second parts of the domain. The result will be “city.kingston.on.ca” . String 3 Here comes the most interesting part. Lets try to decrypt the string #3 from our list of passive DNS requests: lt5ai41qh5d53qoti3mkmc0.appsync-api.us-west-2.avsvmcloud.com The decoded user ID is not relevant, as the decoded NUM part is a number -29 . It’s neither 0 nor 1 , so what kind of domain name that is? If we ignore the NUM part and decode the domain name, using the old method, we will get “thx8xb” , which does not look like a valid domain name. Cases like that are not the noise, and are not some artificially encrypted artifacts that showed up among the DNS requests. This is a different type of DNS requests. Instead of encoding local domain names, these types of requests contain data. They are generated by the malware’s function GetNextStringEx() . The encryption method is different as well. Let’s decrypt this request. First, we can decode the encrypted domain, using the same base-64 method, as before . The string will be decoded into 14 bytes: 7c a5 4d 64 9b 21 c1 74 a6 59 e4 5c 7c 7f Let’s decode these bytes, starting from the 2nd byte, and using the first byte as a XOR key. We will get: 7c d9 31 18 e7 5d bd 08 da 25 98 20 00 03 In this array, the bytes marked in yellow are an 8-byte User ID, encoded with a XOR key that is selected from 2 bytes marked in red. Let’s decode User ID: for ( int i = 0 ; i < 8 ; i++) { bytes[i + 1 ] ^= bytes[ 11 - i % 2 ]; } The decoded byte array becomes: 7c f9 a9 38 7f 7d 25 28 42 25 98 20 00 03 The User ID part in marked in yellow. Does it look familiar? Indeed, it’s the same User ID we’ve seen before, when we decoded “city.kingston.on.ca” . The next 3 bytes marked in red are: 25 98 20 . 2 0x59820 The first number 2 stands for the size of data that follows – this data is 00 03 (selected in green). The number 0x59820 , or 366,624 in decimal, is a timestamp. It’s a number of 4-second periods of time since 1 January 2010. To obtain the real time stamp, we need to multiple it by 15 to get minutes, then add those minutes to 1 January 2010: var date = ( new DateTime( 2010 , 1 , 1 , 0 , 0 , 0 , DateTimeKind.Utc)).AddMinutes(timestamp * 15 ); For the number 0x59820 , the time stamp becomes 16 July 2020 12:00:00 AM – that’s the day when the DNS request was made. The remaining 2 bytes, 00 03 , encrypt the state of 8 security products, to indicate whether each one of them is running or whether it is stopped. The 8 security products are: Windows Live OneCare / Windows Defender Windows Defender Advanced Threat Protection Microsoft Defender for Identity Carbon Black CrowdStrike FireEye ESET F-Secure 2 states for 8 products require 2 * 8 = 16 bits = 2 bytes. The 2 bytes 00 03 in binary form are: 00 00 00 00 00 00 00 11 Here, the least-significant bits 11 identify that the first product in the list, Windows Live OneCare / Windows Defender, is reported as ‘running’ ( 1 ) and as ‘stopped’ ( 1 ). Now we know that apart from the local domain, the trojanised SolarWinds software running on the same compromised host on “city.kingston.on.ca” domain has also reported the status of the Windows Defender software. What Does it Mean? As explained in the first part of our description, the malware is capable of stopping the services of security products, be manipulating registry service keys under Administrator account. It’s likely that the attackers are using DNS queries as a C2 channel to first understand what security products are present. Next, the same channel is used to instruct the malware to stop/deactivate these services, before the 2nd stage payload, TearDrop Backdoor, is deployed. Armed with this knowledge, let’s decode other passive DNS requests, printing the cases when the compromised host reports a running security software. NOTES: As a private case, if the data size field is 0 or 1 , the timestamp field is not followed with any data. Such type of DNS request is generated by the malware’s function GetNextString() . It is called ‘a ping’ in the listing below. If the first part of the domain name is missing, the recovered domain name is pre-pended with ‘*’ . The malware takes the time difference in minutes, then divides it by 30 and then converts the result from double type to int type; as a result of such conversion, the time stamps are truncated to the earliest half hour. 2D82B037C060515C SFBALLET Data: Windows Live OneCare / Windows Defender [running] 11/07/2020 12:00:00 AM Pings: 12/07/2020 12:30:00 AM 70DEE5C062CFEE53 ccscurriculum.c Data: ESET [running] 17/04/2020 4:00:00 PM Pings: 20/04/2020 5:00:00 PM AB902A323B541775 mountsinai.hospital Pings: 4/07/2020 12:30:00 AM 9ACC3A3067DC7FD5 *ripta.com Data: ESET [running] 12/09/2020 6:30:00 AM Pings: 13/09/2020 7:30:00 AM 14/09/2020 9:00:00 AM CB34C4EBCB12AF88 DPCITY.I7a Data: ESET [running] 26/06/2020 5:00:00 PM Pings: 27/06/2020 6:30:00 PM 28/06/2020 7:30:00 PM 29/06/2020 8:30:00 PM 29/06/2020 8:30:00 PM E5FAFE265E86088E *scroot.com Data: CrowdStrike [running] 25/07/2020 2:00:00 PM Pings: 26/07/2020 2:30:00 PM 26/07/2020 2:30:00 PM 27/07/2020 3:00:00 PM 27/07/2020 3:00:00 PM 426030B2ED480DED *kcpl.com Data: Windows Live OneCare / Windows Defender [running] 8/07/2020 12:00:00 AM Carbon Black [running] 8/07/2020 12:00:00 AM Full list of decoded pDNS requests can be found here . An example of a working implementation is available at this repo. 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

Securely accelerate application delivery by automating application connectivity and security policy across the hybrid network estate. Solução de gestão de segurança Algosec Bem-vindo! Administrar sua política de segurança de rede em firewalls locais e controles de segurança na nuvem é um delicado ato de equilíbrio. Por um lado, é preciso reduzir o risco, minimizando a superfície de ataque; por outro, deve-se viabilizar a produtividade ao prover conectividade para suas aplicações comerciais críticas. No entanto, processos de administração de política de segurança de rede sempre foram complexos, demorados e cheio de erros. Não precisa ser assim. No local e na nuvem, a AlgoSec simplifica e automatiza a administração de política de segurança de rede para tornar sua empresa mais ágil, mais segura e mais compatível, o tempo todo. Uma abordagem única de ciclo de vida para a administração de Política de Segurança AlgoSec é única no que tange a administração de todo o ciclo de vida da política de segurança para garantir uma conectividade contínua e segura para seus aplicativos comerciais. Através de um único painel de vidro você pode detectar automaticamente os requisitos de conectividade de aplicativos, fazer uma análise de risco proativa e rapidamente planejar e executar alterações na segurança da rede e desativar com segurança as regras do firewall, todos isso sem contato físico e orquestrado de maneira transparente em seu ambiente heterogêneo. Com AlgoSec você pode Unificar a administração de política de segurança de rede em ambientes heterogêneos de nuvem, em ambientes definidos por software e locais Garantir a conformidade contínua e reduzir drasticamente os esforços de preparação de auditoria de firewall Prover conectividade para aplicativos de forma rápida e segura, e evitar interrupções relacionadas com a rede Alinhar equipes de segurança, de rede e de aplicações, e adotar DevSecOps Automatizar a administração de alterações no firewall e eliminar erros de configuração Reduzir o risco através da configuração correta de segurança e segmentação eficaz de rede A Solução de Gestão de Segurança AlgoSec Análise de Política de Segurança de Rede Mais informações Firewall Analyzer Automação de Mudanças de Política de Segurança Mais informações FireFlow Calculadora ROI Brochura de Soluções AlgoSec Representante local Test name Phone: +55-11-991068906
Email: [email protected] Algosec Korea 정욱 이사 (Sales Engineer) Phone: +82-10-9953-5717
Email: [email protected] Links relevantes TELEFONICA Estudo de Caso NATURA Estudo de Caso AlgoSec Para LGPD Schedule time with one of our experts

Partner solution brief AlgoSec and VMware 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

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 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

Learn how ESG principles are driving sustainable environmental strategies Discover how companies integrate ESG to reduce footprint and contribute to a greener future Our environmental strategy 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 Environmental commitment and vision AlgoSec recognizes the importance of protecting the environment, we at AlgoSec are committed to reducing our carbon footprint and our waste by efficiently coding our product. For minimal environmental impact, the company has defined a long-term strategy, which includes working towards reinforcing its reduction goals and strengthening them through information and employee awareness. Our goal AlgoSec is determined to reduce our environmental impact, by striving to decrease the GHG emissions from our worldwide operations and from our products (as applicable), thus ensuring a safer and more sustainable future for us all. We are continuously looking for ways to maximize energy efficiency while minimizing water consumption and waste accumulation throughout our operations. Our next steps We are committed to infusing as part of our business plan strategic actions to advance reduction in GHG emissions, as part of Scope 1&2. We will continue to reduce our environmental impact by monitoring our progress and taking strategic actions to help achieve our goals. What we have achieved so far Implementation of a worldwide hybrid model since 2020, thus inducing a reduction in emissions spent on employee commuting, as well as electricity usage and water consumption. Waste management program – Reduce trash and the use of plastic at the office, in addition to recycling or reusing 99% of our electronic waste Raising employee awareness of effective use of energy in the office Product sustainability – we strive to increase the energy efficiency of our products by advanced product coding. Certification Verification Statement for GHG Scope 1&2: Additional related links: AA1000AS Reports | Accountability Global Sustainability Consultancy and Standards New York, London, Dubai, Riyadh BDO has conducted the assurance for AlgoSec Greenhouse Gas inventory for scopes 1 and 2 according to GHG protocola The assurance procedure was done according to the disclosures required by the AccountAbility AA1000AS v3 standard and the ISO 14064-3 verification methodology. The assurance process was conducted professionally, impartially and independently.

Top 5 misconfigurations to avoid for robust security Multi-cloud environments have become the backbone of modern enterprise IT, offering unparalleled flexibility, scalability, and access to a diverse array of innovative services. This distributed architecture empowers organizations to avoid vendor lock-in, optimize costs, and leverage specialized functionalities from different providers. However, this very strength introduces a significant challenge: increased complexity in security... Cloud Security 5 Multi-Cloud Environments Iris Stein 2 min read Iris Stein 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 6/23/25 Published Top 5 misconfigurations to avoid for robust security Multi-cloud environments have become the backbone of modern enterprise IT, offering unparalleled flexibility, scalability, and access to a diverse array of innovative services. This distributed architecture empowers organizations to avoid vendor lock-in, optimize costs, and leverage specialized functionalities from different providers. However, this very strength introduces a significant challenge: increased complexity in security management. The diverse security models, APIs, and configuration nuances of each cloud provider, when combined, create a fertile ground for misconfigurations. A single oversight can cascade into severe security vulnerabilities, lead to compliance violations, and even result in costly downtime and reputational damage. At AlgoSec, we have extensive experience in navigating the intricacies of multi-cloud security. Our observations reveal recurring patterns of misconfigurations that undermine even the most well-intentioned security strategies. To help you fortify your multi-cloud defences, we've compiled the top five multi-cloud misconfigurations that organizations absolutely must avoid. 1. Over-permissive policies: The gateway to unauthorized access One of the most pervasive and dangerous misconfigurations is the granting of overly broad or permissive access policies. In the rush to deploy applications or enable collaboration, it's common for organizations to assign excessive permissions to users, services, or applications. This "everyone can do everything" approach creates a vast attack surface, making it alarmingly easy for unauthorized individuals or compromised credentials to gain access to sensitive resources across your various cloud environments. The principle of least privilege (PoLP) is paramount here. Every user, application, and service should only be granted the minimum necessary permissions to perform its intended function. This includes granular control over network access, data manipulation, and resource management. Regularly review and audit your Identity and Access Management (IAM) policies across all your cloud providers. Tools that offer centralized visibility into entitlements and highlight deviations can be invaluable in identifying and rectifying these critical vulnerabilities before they are exploited. 2. Inadequate network segmentation: Lateral movement made easy In a multi-cloud environment, a flat network architecture is an open invitation for attackers. Without proper network segmentation, a breach in one part of your cloud infrastructure can easily lead to lateral movement across your entire environment. Mixing production, development, and sensitive data workloads within the same network segment significantly increases the risk of an attacker pivoting from a less secure development environment to a critical production database. Effective network segmentation involves logically isolating different environments, applications, and data sets. This can be achieved through Virtual Private Clouds (VPCs), subnets, security groups, network access control lists (NACLs), and micro-segmentation techniques. The goal is to create granular perimeters around critical assets, limiting the blast radius of any potential breach. By restricting traffic flows between different segments and enforcing strict ingress and egress rules, you can significantly hinder an attacker's ability to move freely within your cloud estate. 3. Unsecured storage buckets: A goldmine for data breaches Cloud storage services, such as Amazon S3, Azure Blob Storage, and Google Cloud Storage, offer incredible scalability and accessibility. However, their misconfiguration remains a leading cause of data breaches. Publicly accessible storage buckets, often configured inadvertently, expose vast amounts of sensitive data to the internet. This includes customer information, proprietary code, intellectual property, and even internal credentials. It is imperative to always double-check and regularly audit the access controls and encryption settings of all your storage buckets across every cloud provider. Implement strong bucket policies, restrict public access by default, and enforce encryption at rest and in transit. Consider using multifactor authentication for access to storage, and leverage tools that continuously monitor for publicly exposed buckets and alert you to any misconfigurations. Regular data classification and tagging can also help in identifying and prioritizing the protection of highly sensitive data stored in the cloud. 4. Lack of centralized visibility: Flying blind in a complex landscape Managing security in a multi-cloud environment without a unified, centralized view of your security posture is akin to flying blind. The disparate dashboards, logs, and security tools provided by individual cloud providers make it incredibly challenging to gain a holistic understanding of your security landscape. This fragmented visibility makes it nearly impossible to identify widespread misconfigurations, enforce consistent security policies across different clouds, and respond effectively and swiftly to emerging threats. A centralized security management platform is crucial for multi-cloud environments. Such a platform should provide comprehensive discovery of all your cloud assets, enable continuous risk assessment, and offer unified policy management across your entire multi-cloud estate. This centralized view allows security teams to identify inconsistencies, track changes, and ensure that security policies are applied uniformly, regardless of the underlying cloud provider. Without this overarching perspective, organizations are perpetually playing catch-up, reacting to incidents rather than proactively preventing them. 5. Neglecting Shadow IT: The unseen security gaps Shadow IT refers to unsanctioned cloud deployments, applications, or services that are used within an organization without the knowledge or approval of the IT or security departments. While seemingly innocuous, shadow IT can introduce significant and often unmanaged security gaps. These unauthorized resources often lack proper security configurations, patching, and monitoring, making them easy targets for attackers. To mitigate the risks of shadow IT, organizations need robust discovery mechanisms that can identify all cloud resources, whether sanctioned or not. Once discovered, these resources must be brought under proper security governance, including regular monitoring, configuration management, and adherence to organizational security policies. Implementing cloud access security brokers (CASBs) and network traffic analysis tools can help in identifying and gaining control over shadow IT instances. Educating employees about the risks of unauthorized cloud usage is also a vital step in fostering a more secure multi-cloud environment. Proactive management with AlgoSec Cloud Enterprise Navigating the complex and ever-evolving multi-cloud landscape demands more than just awareness of these pitfalls; it requires deep visibility and proactive management. This is precisely where AlgoSec Cloud Enterprise excels. Our solution provides comprehensive discovery of all your cloud assets across various providers, offering a unified view of your entire multi-cloud estate. It enables continuous risk assessment by identifying misconfigurations, policy violations, and potential vulnerabilities. Furthermore, AlgoSec Cloud Enterprise empowers automated policy enforcement, ensuring consistent security postures and helping you eliminate misconfigurations before they can be exploited. By providing this robust framework for security management, AlgoSec helps organizations maintain a strong and resilient security posture in their multi-cloud journey. Stay secure out there! The multi-cloud journey offers immense opportunities, but only with diligent attention to security and proactive management can you truly unlock its full potential while safeguarding your critical assets. 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

As organizations respond to an ever-evolving set of security threats, network teams are scrambling to find new ways to keep up with... Auditing and Compliance Continuous compliance monitoring best practices 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 3/19/23 Published As organizations respond to an ever-evolving set of security threats, network teams are scrambling to find new ways to keep up with numerous standards and regulations to dodge their next compliance audit violation. Can this nightmare be avoided? Yes, and it’s not as complex as one might think if you take a “compliance first” approach . It may not come as a surprise to many, but the number of cyber attacks is increasing every year and with it the risk to companies’ financial, organizational, and reputational standing. What’s at stake? The stakes are high when it comes to cyber security compliance. A single data breach can result in massive financial losses, damage to a company’s reputation, and even jail time for executives. Data breaches: Data breaches are expensive and becoming even more so by the day. According to the Ponemon Institute’s 2022 Cost of a Data Breach Report , the average cost of a data breach is $4.35 million. Fraud: Identity fraud is one of the most pressing cybersecurity threats today. In large organizations, the scale of fraud is also usually large, resulting in huge losses causing depletion of profitability. In a recent survey done by PwC, nearly one in five organizations said that their most disruptive incident cost over $50 million*. Theft: Identity theft is on the rise and can be the first step towards compromising a business. According a study from Javelin Strategy & Research found that identity fraud costs US businesses an estimated total of $56 billion* in 2021. What’s the potential impact? The potential impact of non-compliance can be devastating to an organization. Financial penalties, loss of customers, and damage to reputation are just a few of the possible consequences. To avoid these risks, organizations must make compliance a priority and take steps to ensure that they are meeting all relevant requirements. Legal impact:  Regulatory or legal action brought against the organization or its employees that could result in fines, penalties, imprisonment, product seizures, or debarment.  Financial impact:  Negative impacts with regard to the organization’s bottom line, share price, potential future earnings, or loss of investor confidence.  Business impact:  Adverse events, such as embargos or plant shutdowns, could significantly disrupt the organization’s ability to operate.  Reputational impact:  Damage to the organization’s reputation or brand—for example, bad press or social-media discussion, loss of customer trust, or decreased employee morale.  How can this be avoided? In order to stay ahead of the ever-expanding regulatory requirements, organizations must adopt a “compliance first” approach to cyber security. This means enforcing strict compliance criteria and taking immediate action to address any violations to ensure data is protected. Some of these measures include the following: Risk assessment: Conduct ongoing monitoring of compliance posture (risk assessment) and conduct regular internal audits (ensuring adherence with regulatory and legislative requirements (HIPAA, GDPR, PCI DSS, SOX, etc.) Documentation: Enforce continuous tracking of changes and intent Annual audits: Commission 3rd party annual audits to ensure adherence with regulatory and legislative requirements (HIPAA, GDPR, PCI DSS, SOX, etc.) Conclusion and next steps Compliance violations are no laughing matter. They can result in fines, business loss, and even jail time in extreme cases. They can be difficult to avoid unless you take the right steps to avoid them. You have a complex set of rules and regulations to follow as well as numerous procedures, processes, and policies. And if you don’t stay on top of things, you can end up with a compliance violation mess that is difficult to untangle. Fortunately, there are ways to reduce the risk of being blindsided by a compliance violation mess with your organization. Now that you know the risks and what needs to be done, here are six best practices for achieving it. External links: $50 million $56 billion 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

Safeguarding the network architecture is the need of the hour. According to a study, the average cost of a data breach is at an all-time... Network Security Policy Management Network segmentation vs. VLAN explained 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 Safeguarding the network architecture is the need of the hour. According to a study, the average cost of a data breach is at an all-time high of $4.35 million. And this figure will only increase with governments and regulators becoming ever stricter on data breaches. The go-to method IT administrators adopt to safeguard their networks is network segmentation. By segmenting a larger network into smaller chunks, it becomes much more manageable to secure the entire network. But network segmentation is a broad concept and doesn’t refer to a single procedure. In fact, there are several segmentation processes — one of them being VLAN. Instead of simplifying, this adds to the complexity. In this article, we will explain the core difference between network segmentation and VLAN and when you should opt for a particular one over the other. What is network segmentation? Let’s start with the definitions of network segmentation and VLAN. By definition, network segmentation is the practice of compartmentalizing a network according to firewall rules . In other words, it’s about dividing a computer network into subnetworks. The subnetworks, at the IP level, are known as subnets. Each of the subnets then works independently and in isolation. Think of how a nation is split into various states and provinces for better management at the local level. Running an entire nation at the federal level is too much work. In addition to subnetting, there are other segmentation options like firewall segmentation and SDN (Software Defined Network) segmentation. But for this article’s sake, we will focus on subnets since those are the most common. What is VLAN? VLAN or Virtual LAN (Virtual Local Area Network) is also a type of network segmentation approach where the main physical network is divided into multiple smaller virtual networks. The division is done logically or virtually, not requiring buying additional physical resources. The same resource is divided using computer logic. There are several benefits to dividing the parts of the network, either using VLAN segmentation or subnet techniques. Some of them are: Broadcast domain isolation Both subnets and VLAN isolate broadcast domains. This way, broadcasting network traffic is contained in a single segment instead of being exposed to the entire network. This reduces the chance of network congestion during peak hours and unnecessary server overload, thereby maximizing efficiency. Enhanced security The isolation by subnets or VLAN enhances the IT network’s security policies. This is achieved through various factors that are at play. But primarily, the creation of subnetworks makes the flat network more secure. With multiple subnetworks, you can regulate the security parameters. Thus, those subnets containing critical data (like that of healthcare) can have enhanced cybersecurity measures more than others, making them harder to crack. So, from a security perspective, both subnets and VLAN are a must. Better network management With digitization and IT modernization, the IT infrastructure is growing. Concurrently, it’s getting harder to manage them. Microsegmentation is one way of managing the ever-growing infrastructure. By segmenting, you can deploy teams to each segment, thereby strengthening their management and accountability. With the implementation of SDN, you can even configure and automate the management of some of the subnetworks. Flexibility in scalability Many network administrators face network performance and scalability issues expanding resources. The issues are a mix of technical and economical. Network segmentation offers a solution to such issues. By segmenting the entire data center network, you can choose which segments to expand and control the resources granted to each segment. This also makes scalability more economical. While both offer scalability opportunities, VLAN offers superior functionality than subnets. Reduced scope of compliance Compliance is another area that IT execs need to work on. And network segmentation, either via subnets or VLAN, can help in this regard. By having subnets, you don’t have to audit your entire segmented network as required by regulators. Just audit the necessary subnets and submit the reports to the regulators for approval. This takes far less time and costs significantly less than auditing the entire network. Differences between network segmentation and VLAN By definition, network segmentation (subnetting) and VLAN sound pretty similar. After all, there’s a division of the main network into subnetworks or smaller networks. But besides the core similarities mentioned above, there are a few critical differences. Let’s dive into the differences between the two. The primary difference between the two subnets are layer 3 divisions, while VLANs are layer 2 divisions. As you may recall, networks are layer 1 (device), layer 2 (data link), layer 3 (IP, routers), and so on, up to layer 7 (application). TCP/IP is the newer framework with four layers only. So, when you divide a network at a data link, you need to adopt VLAN. With VLAN, several networks exist on the same physical network but may not be connected to the same fiber switch. In subnets, the division occurs at IP level. Thus, the independent subnets are assigned their IP addresses and communicate with others over layer 3. Besides this significant difference, there are other dissimilarities you should know. Here’s a table to help you understand: VLAN Subnet 1 Divides the network within the same physical network using logic. Divides the IP network into multiple IP networks 2 VLANs communicate with other devices within the same LAN The communication between the subnets is carried out over layer 3 3 It is configured at the switch side It is configured at IP level 4 VLAN divisions are software-based terminology since they’re divided logically. Subnets can be both hardware- of software-based 5 VLAN provides better network access and tend to be more stable Subnets offer limited control When to adopt a subnet? There are use cases when subnets are more suited, while there are cases when you’re better off with Virtual LANs. As per the definition, you need to adopt a subnet when dividing different networks at IP level. So, if you want to create multiple IP addresses for each partition, implement subnets. The subnets are essentially networks within a network with their own IP addresses. Thus, they divide the broadcast domain and improve speed and efficiency. Subnets are also the go-to segmentation method when you need to make the sub-networks available over layer 3 to the outside world. With appropriate access control lists, anyone with an internet connection would be able to access the subnets But subnetting is also used to prevent access to a particular subnet. For example, you may want to limit access to the company’s software codebase to anyone outside the development department. So, only network devices with approved IP addresses used by the developer network are approved to access the codebase. But there are two downsides to subnets you should know. The first one is increased time complexity. When dealing with a single network, three steps are in place to reach the Process (Source Host, Destination Network, and Process). In subnets, there’s an additional step involved (Source Host, Destination Network, Subnet, Process). This extra step increases time complexity, requiring more time for data transfer and connectivity. It also affects stability. Subnetting also increases the number of IP addresses required since each subnet requires its own IP address. This can become hard to manage over time. When to adopt VLAN? Virtual LANs are internal networks within the same physical network. They interact with one another, not with other devices on the same network or outside the world. Think of VLAN as a private wireless network at home. Your neighbors don’t have access to it, but everyone in your home has. If that sounds like your desired result, you should adopt VLAN. There are three types of VLANs (basic, extended, and tagged). In basic VLAN, you assign IDs to each switch port or PCI . Once assigned, you can’t change them. Extended VLAN has more functionalities like priority-based routing. Lastly, tagged VLAN enables you to create multiple VLANs with IEEE 802.1Q. The main advantages of different VLANs over subnet are speed and stability. Since endpoints do not have to resolve IP addresses every time, they tend to be faster. But there’s a significant disadvantage to VLANs: It’s easier to breach multiple partitions if there’s a malicious injection. Without proper network security controls, it is easier to exploit vulnerabilities using malware and ransomware , putting your entire network at risk. Having ACLs (access control lists) can help in such situations. Furthermore, there are issues arising out of physical store requirements. Connecting two segments in VLAN requires you to use routers and IoT. Routers are physical devices that take up space. The more segments you create, the more routers you need to use. Over time, management can become an issue. The bottom line Both subnets and VLANs are network segmentation approaches that improve security and workload management. It’s not a given that you can’t have both. Some companies benefit from the implementation of VLAN and subnets simultaneously. But there are specific times when IT service providers prefer one over the other. Consider your requirements to select the approach that’s right for you. 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