Explore upcoming Algosec events to learn about the latest in network security, policy management, and compliance from industry experts Events Exhibition Frankfurt May 22, 2024 - May 23, 2024 Cloud and Cyber Expo – Frankfurt Messe Frankfurt Booth L070 Hall 8 Read More AlgoSec Events London June 05, 2024 Algocity London Good Hotel Western Gateway, Royal Victoria Dock London, E16 1FA 5th of June, 6PM. Read More Exhibition National Harbor, MD June 03, 2024 - June 05, 2024 Gartner Security & Risk Management Summit – US Gaylord National Resort & Convention Center, National Harbor, MD Read More Exhibition London June 04, 2024 - June 06, 2024 Infosec London Booth B69 Read More Exhibition Las Vegas June 02, 2024 - June 06, 2024 Cisco Live US 2024 Mandalay Bay Convention Center, Las Vegas, NV Booth 5960 in World of Solutions Read More Exhibition Philadelphia June 10-12, 2024 AWS re:Inforce Pennsylvania Convention Center, Philadelphia, PA AlgoSec Booth: 501 Read More Exhibit, Speaking Session Las Vegas August 27-29, 2024 Cisco GSX FY25 Mandalay Bay Hotel, Las Vegas, NV Booth number: 23 Read More Exhibition Bengaluru August 30th, 2024 Dine With DevOps Sheraton Grand Whitefield Hotel, Bengaluru Read More AlgoSec Event Riyadh September 3rd, 2024 AlgoCity Riyadh Voco, Riyadh Read More AlgoSec Event Dubai September 5th, 2024 AlgoCity Dubai Ritz Carlton, JBR, Dubai Read More Exhibition Atlanta, GA, US September 5, 2024 Mission Security 2024 The Westin Atlanta Perimeter North, Atlanta, GA, US Read More Exhibition Riyadh September 10th, 2024 MENA ISC with Amiviz 2024 Hilton Riyadh Hotel & Residences, Riyadh Booth number – P01 Booth: Pod 4 Read More Exhibition Toronto September 11, 2024 AWS Summit Toronto 2024 Metro Toronto Convention Centre, Toronto, Canada Booth number: 325 Read More Exhibition Montreal, QC, Canada September 11-12, 2024 GoSec 24 Palais des Congrès de Montréal, Montreal, QC, Canada Read More Exhibition Kansas City, MO, US September 18, 2024 2024 OptivCon Kansas City Arrowhead Stadium, Kansas City, MO, US Read More Exhibition Monaco 9th – 12th October, 2024 Les Assises Monaco Booth number: B08 Read More Exhibition Singapore October 15th -17th GovWare Singapore Sands Expo and Convention Centre Booth number – F20 | Booth E Read More Exhibition Dubai October 14th -18th Gitex Dubai World Trade Center Booth number – Hall 24 | A45 | Booth 7 Read More Exhibition Nurenberg Messe 22nd – 24th October , 2024 IT-SA 2024 Nurenberg Messe Booth number 7A-614 Read More Exhibition Melbourne, MCEC November 11th -14th Nov CISCO Live Melbourne Booth number – Stand S1 Read More Exhibition Malham | Saudi Arabia November 26th -28th Nov Black HAT MEA Booth number – Hall 1 | G 10 | Booth 7 Read More AlgoSec Event Washington, DC June 10th, 2025 Gartner Happy Hour Event Washington, DC Read More Exhibition San Diego, CA 8-12 June, 2025 Cisco Live San Diego, CA San Diego, CA Booth #2041 Read More Exhibition Ontario, CA June 13th, 2025 CXO Cyber Training Day & Dinner Ontario, CA Read More Exhibition Indiana, US July 31st, 2025 (IN) Nug Indianapolis Indiana, US Read More Exhibit Atlanta August 20th, 2025 Mission: Security’ 25 Westin Atlanta Perimeter North, Atlanta, GA Read More Exhibit, Speaking Session Las Vegas 26-28 of August, 2025 Cisco GSX FY26 Mandalay Bay Hotel Read More Exhibit Minneapolis September 10th, 2025 OptivCon Minneapolis US Bank Stadium Read More Exhibit, Speaking Session Mexico City, Mexico September 30 – October 1, 2025 Infosecurity Mexico Centro Banamex, Mexico City, Mexico Read More AlgoSec Event Nurenburg October 7th, 2025 ITSA EXPO Nurenburg Read More Exhibition Monaco 8-11 October, 2025 Les Assises Monaco Read More Exhibition Dubai 13-17 October, 2025 GITEX Dubai Read More Exhibition Orlando, FL 27-29 October, 2025 InfoSec World Orlando, FL Read More Exhibit Philadelphia October 29th, 2025 GPSEC Philadelphia Convene, Philadelphia, PA Read More Exhibit Phoenix October 30, 2025 OptivCon Phoenix Phoenix, AR Read More Exhibit Wastlake October 29-31, 2025 ISS+ Cleveland Wastlake, Ohio Read More Exhibition Melbourne 10-13 November, 2025 Cisco Live Melbourne Read More Exhibition Riyadh 24-26 November, 2025 Black Hat Riyadh Read More Exhibit Philadelphia December 5th, 2025 B Sides Philly 2025 Live Casino Hotel, 900 Packer Ave., Philadelphia, PA 19148 Read More Exhibit Las Vegas, NV March 9-13th, 2026 Fortinet Acceleter Mandalay Bay Convention Center Read More Exhibit San Francisco, CA March 23-26th, 2026 RSA Conference 2026 Moscone Center Read More Exhibit Las Vegas, NV May 31-June 4th, 2026 Cisco Live 2026 Mandalay Bay Convention Center Read More Exhibit Vancouver, Canada 2. FutureCon Vancouver The Westin Bayshore, Vancouver Canada Read More Exhibit Virginia, USA June 9-10, 2026 RVASec 500 East Broad Street, Richmond, Virginia, USA, 23219 Read More Summit Washington, DC June 30-July 1, 2026 2026 AWS Summit Walter E. Washington Convention Center Read More Region Event type Date No upcoming events. Visit us soon for new events 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

Minimize risks and maximize benefits with a successful data center migration Explore key considerations and strategies Data center migration checklist + project plan template 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. Data center migration What is a data center migration? What are the four types of data center migration? What are data center migration best practices? How to plan for a successful data center migration? What are some common challenges of a data center migration? What are some common drawbacks of a data center migration? Checklist for a successful data center migration What are some data center migration tools? Get the latest insights from the experts Use these six best practices to simplify compliance and risk mitigation with the AlgoSec White paper Learn how AlgoSec can help you pass PCI-DSS Audits and ensure Solution overview See how this customer improved compliance readiness and risk Case study Schedule time with one of our experts Work email* First name* Last name* Company* country* Select country... Short answer* By submitting this form, I accept AlgoSec's privacy policy Continue

AlgoSec security management solution for Juniper Networks Solution Brief Download PDF Download PDF Add a Title Add a Title Add a Title 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

Attacks on water treatment plants show just how vulnerable critical infrastructure is to hacking – here’s how these vital services should... Cyber Attacks & Incident Response Stop hackers from poisoning the well: Protecting critical infrastructure against cyber-attacks 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/31/21 Published Attacks on water treatment plants show just how vulnerable critical infrastructure is to hacking – here’s how these vital services should be protected. Criminals plotting to poison a city’s water supply is a recurring theme in TV and movie thrillers, such as 2005’s Batman Begins. But as we’ve seen recently, it’s more than just a plot device: it’s a cyber-threat which is all too real. During the past 12 months, there have been two high-profile attacks on water treatment systems that serve local populations, both with the aim of causing harm to citizens. The first was in April 2020, targeting a plant in Israel . Intelligence sources said that hackers gained access to the plant and tried altering the chlorine levels in drinking water – but luckily the attack was detected and stopped. And in early February, a hacker gained access to the water system of Oldsmar, Florida and tried to pump in a dangerous amount of sodium hydroxide. The hacker succeeded in starting to add the chemical, but luckily a worker spotted what was happening and reversed the action. But what could have happened if those timely interventions had not been made? These incidents are a clear reminder that critical national infrastructure is vulnerable to attacks – and that those attacks will keep on happening, with the potential to impact the lives of millions of people.  And of course, the Covid-19 pandemic has further highlighted how essential critical infrastructure is to our daily lives. So how can better security be built into critical infrastructure systems, to stop attackers being able to breach them and disrupt day-to-day operations?  It’s a huge challenge, because of the variety and complexity of the networks and systems in use across different industry sectors worldwide. Different systems but common security problems For example, in water and power utilities, there are large numbers of cyber-physical systems consisting of industrial equipment such as turbines, pumps and switches, which in turn are managed by a range of different industrial control systems (ICS). These were not designed with security in mind:  they are simply machines with computerized controllers that enact the instructions they receive from operators.  The communications between the operator and the controllers are done via IP-based networks – which, without proper network defenses, means they can be accessed over the Internet – which is the vector that hackers exploit. As such, irrespective of the differences between ICS controls, the security challenges for all critical infrastructure organizations are similar:  hackers must be stopped from being able to infiltrate networks; if they do succeed in breaching the organization’s defenses, they must be prevented from being able to move laterally across networks and gain access to critical systems. This means  network segmentation  is one of the core strategies for securing critical infrastructure, to keep operational systems separate from other networks in the organization and from the public Internet and surround them with security gateways so that they cannot be accessed by unauthorized people. In the attack examples we mentioned earlier, properly implemented segmentation would prevent a hacker from being able to access the PC which controls the water plant’s pumps and valves. With damaging ransomware attacks increasing over the past year, which also exploit internal network connections and pathways to spread rapidly and cause maximum disruption,  organizations should also employ security best-practices to block or limit the impact of ransomware attacks  on their critical systems. These best practices have not changed significantly since 2017’s massive WannaCry and NotPetya attacks, so organizations would be wise to check and ensure they are employing them on their own networks. Protecting critical infrastructure against cyber-attacks is a complex challenge because of the sheer diversity of systems in each sector.  However, the established security measures we’ve outlined here are extremely effective in protecting these vital systems – and in turn, protecting all of us. 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

Update : Next two parts of the analysis are available here and here . As earlier reported by FireEye, the actors behind a global... Cloud Security Sunburst Backdoor: A Deeper Look Into The SolarWinds’ Supply Chain Malware 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/15/20 Published Update : Next two parts of the analysis are available here and here . As earlier reported by FireEye, the actors behind a global intrusion campaign have managed to trojanise SolarWinds Orion business software updates in order to distribute malware. The original FireEye write-up already provides a detailed description of this malware. Nevertheless, as the malicious update SolarWinds-Core-v2019.4.5220-Hotfix5.msp was still available for download for hours since the FireEye’s post, it makes sense to have another look into the details of its operation. The purpose of this write-up is to provide new information, not covered in the original write-up. Any overlaps with the original description provided by FireEye are not intentional. For start, the malicious component SolarWinds.Orion.Core.BusinessLayer.dll inside the MSP package is a non-obfuscated .NET assembly. It can easily be reconstructed with a .NET disassembler, such as ILSpy , and then fully reproduced in C# code, using Microsoft Visual Studio. Once reproduced, it can be debugged to better understand how it works. In a nutshell, the malicious DLL is a backdoor. It is loaded into the address space of the legitimate SolarWinds Orion process SolarWinds.BusinessLayerHost.exe or SolarWinds.BusinessLayerHostx64.exe . The critical strings inside the backdoor’s class SolarWinds.Orion.Core.BusinessLayer.OrionImprovementBusinessLayer are encoded with the DeflateStream Class of the .NET’s System.IO.Compression library, coupled with the standard base64 encoder. Initialisation Once loaded, the malware checks if its assembly file was created earlier than 12, 13, or 14 days ago. The exact number of hours it checks is a random number from 288 to 336. Next, it reads the application settings value ReportWatcherRetry . This value keeps the reporting status, and may be set to one of the states: New (4) Truncate (3) Append (5) When the malware runs the first time, its reporting status variable ReportWatcherRetry is set to New (4) . The reporting status is an internal state that drives the logic. For example, if the reporting status is set to Truncate , the malware will stop operating by first disabling its networking communications, and then disabling other security tools and antivirus products. In order to stay silent, the malware periodically falls asleep for a random period of time that varies between 30 minutes and 2 hours. At the start, the malware obtains the computer’s domain name . If the domain name is empty, the malware quits. It then generates a 8-byte User ID, which is derived from the system footprint. In particular, it is generated from MD5 hash of a string that consists from the 3 fields: the first or default operational (can transmit data packets) network interface’s physical address computer’s domain name UUID created by Windows during installation (machine’s unique ID) Even though it looks random, the User ID stays permanent as long as networking configuration and the Windows installation stay the same. Domain Generation Algorithm The malware relies on its own CryptoHelper class to generate a domain name. This class is instantiated from the 8-byte User ID and the computer’s domain name, encoded with a substitution table: “rq3gsalt6u1iyfzop572d49bnx8cvmkewhj” . For example, if the original domain name is “ domain “, its encoded form will look like: “ n2huov “. To generate a new domain, the malware first attempts to resolve domain name “ api.solarwinds.com “. If it fails to resolve it, it quits. The first part of the newly generated domain name is a random string, produced from the 8-byte User ID, a random seed value, and encoded with a custom base64 alphabet “ph2eifo3n5utg1j8d94qrvbmk0sal76c” . Because it is generated from a random seed value, the first part of the newly generated domain name is random. For example, it may look like “ fivu4vjamve5vfrt ” or “ k1sdhtslulgqoagy “. To produce the domain name, this string is then appended with the earlier encoded domain name (such as “ n2huov “) and a random string, selected from the following list: .appsync-api.eu-west-1[.]avsvmcloud[.]com .appsync-api.us-west-2[.]avsvmcloud[.]com .appsync-api.us-east-1[.]avsvmcloud[.]com .appsync-api.us-east-2[.]avsvmcloud[.]com For example, the final domain name may look like: fivu4vjamve5vfrtn2huov[.]appsync-api.us-west-2[.]avsvmcloud[.]com or k1sdhtslulgqoagyn2huov[.]appsync-api.us-east-1[.]avsvmcloud[.]com Next, the domain name is resolved to an IP address, or to a list of IP addresses. For example, it may resolve to 20.140.0.1 . The resolved domain name will be returned into IPAddress structure that will contain an AddressFamily field – a special field that specifies the addressing scheme. If the host name returned in the IPAddress structure is different to the queried domain name, the returned host name will be used as a C2 host name for the backdoor. Otherwise, the malware will check if the resolved IP address matches one of the patterns below, in order to return an ‘address family’: IP Address Subnet Mask ‘Address Family’ 10.0.0.0 255.0.0.0 Atm 172.16.0.0 255.240.0.0 Atm 192.168.0.0 255.255.0.0 Atm 224.0.0.0 240.0.0.0 Atm fc00:: fe00:: Atm fec0:: ffc0:: Atm ff00:: ff00:: Atm 41.84.159.0 255.255.255.0 Ipx 74.114.24.0 255.255.248.0 Ipx 154.118.140.0 255.255.255.0 Ipx 217.163.7.0 255.255.255.0 Ipx 20.140.0.0 255.254.0.0 ImpLink 96.31.172.0 255.255.255.0 ImpLink 131.228.12.0 255.255.252.0 ImpLink 144.86.226.0 255.255.255.0 ImpLink 8.18.144.0 255.255.254.0 NetBios 18.130.0.0 255.255.0.0 NetBios 71.152.53.0 255.255.255.0 NetBios 99.79.0.0 255.255.0.0 NetBios 87.238.80.0 255.255.248.0 NetBios 199.201.117.0 255.255.255.0 NetBios 184.72.0.0 255.254.0.0 NetBios For example, if the queried domain resolves to 20.140.0.1 , it will match the entry in the table 20.140.0.0 , for which the returned ‘address family’ will be ImpLink . The returned ‘address family’ invokes an additional logic in the malware. Disabling Security Tools and Antivirus Products If the returned ‘address family’ is ImpLink or Atm , the malware will enumerate all processes and for each process, it will check if its name matches one of the pre-defined hashes. Next, it repeats this processed for services and for the drivers installed in the system. If a process name or a full path of an installed driver matches one of the pre-defined hashes, the malware will disable it. For hashing, the malware relies on Fowler–Noll–Vo algorithm. For example, the core process of Windows Defender is MsMpEng.exe . The hash value of “ MsMpEng ” string is 5183687599225757871 . This value is specifically enlisted the malware’s source under a variable name timeStamps : timeStamps = new ulong[1] { 5183687599225757871uL } The service name of Windows Defender is windefend – the hash of this string ( 917638920165491138 ) is also present in the malware body. As a result, the malicioius DLL will attempt to stop the Windows Defender service. In order to disable various security tools and antivirus products, the malware first grants itself SeRestorePrivilege and SeTakeOwnershipPrivilege privileges, using the native AdjustTokenPrivileges() API. With these privileges enabled, the malware takes ownership of the service registry keys it intends to manipulate. The new owner of the keys is first attempted to be explicitly set to Administrator account. If such account is not present, the malware enumerates all user accounts, looking for a SID that represents the administrator account. The malware uses Windows Management Instrumentation query “ Select * From Win32_UserAccount ” to obtain the list of all users. For each enumerated user, it makes sure the account is local and then, when it obtains its SID, it makes sure the SID begins with S-1-5- and ends with -500 in order to locate the local administrator account. Once such account is found, it is used as a new owner for the registry keys, responsible for manipulation of the services of various security tools and antivirus products. With the new ownership set, the malware then disables these services by setting their Start value to 4 (Disabled): registryKey2.SetValue(“Start”), 4, RegistryValueKind.DWord); HTTP Backdoor If the returned ‘address family’ for the resolved domain name is NetBios , as specified in the lookup table above, the malware will initialise its HttpHelper class, which implements an HTTP backdoor. The backdoor commands are covered in the FireEye write-up, so let’s check only a couple of commands to see what output they produce. One of the backdoor commands is CollectSystemDescription . As its name suggests, it collects system information. By running the code reconstructed from the malware, here is an actual example of the data collected by the backdoor and delivered to the attacker’s C2 with a separate backdoor command UploadSystemDescription : 1. %DOMAIN_NAME% 2. S-1-5-21-298510922-2159258926-905146427 3. DESKTOP-VL39FPO 4. UserName 5. [E] Microsoft Windows NT 6.2.9200.0 6.2.9200.0 64 6. C:\WINDOWS\system32 7. 0 8. %PROXY_SERVER% Description: Killer Wireless-n/a/ac 1535 Wireless Network Adapter #2 MACAddress: 9C:B6:D0:F6:FF:5D DHCPEnabled: True DHCPServer: 192.168.20.1 DNSHostName: DESKTOP-VL39FPO DNSDomainSuffixSearchOrder: Home DNSServerSearchOrder: 8.8.8.8, 192.168.20.1 IPAddress: 192.168.20.30, fe80::8412:d7a8:57b9:5886 IPSubnet: 255.255.255.0, 64 DefaultIPGateway: 192.168.20.1, fe80::1af1:45ff:feec:a8eb NOTE: Field #7 specifies the number of days (0) since the last system reboot. GetProcessByDescription command will build a list of processes running on a system. This command accepts an optional argument, which is one of the custom process properties enlisted here . If the optional argument is not specified, the backdoor builds a process list that looks like: [ 1720] svchost [ 8184] chrome [ 4732] svchost If the optional argument is specified, the backdoor builds a process list that includes the specified process property in addition to parent process ID, username and domain for the process owner. For example, if the optional argument is specified as “ ExecutablePath “, the GetProcessByDescription command may return a list similar to: [ 3656] sihost.exe C:\WINDOWS\system32\sihost.exe 1720 DESKTOP-VL39FPO\UserName [ 3824] svchost.exe C:\WINDOWS\system32\svchost.exe 992 DESKTOP-VL39FPO\UserName [ 9428] chrome.exe C:\Program Files (x86)\Google\Chrome\Application\chrome.exe 4600 DESKTOP-VL39FPO\UserName Other backdoor commands enable deployment of the 2nd stage malware. For example, the WriteFile command will save the file: using (FileStream fileStream = new FileStream(path, FileMode.Append, FileAccess.Write)) { fileStream.Write(array, 0, array.Length); } The downloaded 2nd stage malware can then the executed with RunTask command: using (Process process = new Process()) { process.StartInfo = new ProcessStartInfo(fileName, arguments) { CreateNoWindow = false, UseShellExecute = false }; if (process.Start()) … Alternatively, it can be configured to be executed with the system restart, using registry manipulation commands, such as SetRegistryValue . 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

Product Marketing Manager AlgoSec Cloud Navigating Compliance in the Cloud 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/29/25 Published Cloud adoption isn't just soaring; it's practically stratospheric. Businesses of all sizes are leveraging the agility, scalability, and innovation that cloud environments offer. Yet, hand-in-hand with this incredible growth comes an often-overlooked challenge: the increasing complexities of maintaining compliance. Whether your organization grapples with industry-specific regulations like HIPAA for healthcare, PCI DSS for payment processing, SOC 2 for service organizations, or simply adheres to stringent internal governance policies, navigating the ever-shifting landscape of cloud compliance can feel incredibly daunting. It's akin to staring at a giant, knotted ball of spaghetti, unsure where to even begin untangling. But here’s the good news: while it demands attention and a strategic approach, staying compliant in the cloud is far from an impossible feat. This article aims to be your friendly guide through the compliance labyrinth, offering practical insights and key considerations to help you maintain order and assurance in your cloud environments. The foundation: Understanding the Shared Responsibility Model Before you even think about specific regulations, you must grasp the Shared Responsibility Model . This is the bedrock of cloud compliance, and misunderstanding it is a common pitfall that can lead to critical security and compliance gaps. In essence, your cloud provider (AWS, Azure, Google Cloud, etc.) is responsible for the security of the cloud – that means the underlying infrastructure, the physical security of data centers, the global network, and the hypervisors. However, you are responsible for the security in the cloud . This includes your data, your configurations, network traffic protection, identity and access management, and the applications you deploy. Think of it like a house: the cloud provider builds and secures the house (foundation, walls, roof), but you’re responsible for what you put inside it, how you lock the doors and windows, and who you let in. A clear understanding of this division is paramount for effective cloud security and compliance. Simplify to conquer: Centralize your compliance efforts Imagine trying to enforce different rules for different teams using separate playbooks – it's inefficient and riddled with potential for error. The same applies to cloud compliance, especially in multi-cloud environments. Juggling disparate compliance requirements across multiple cloud providers manually is not just time-consuming; it's a recipe for errors, missed deadlines, and a constant state of anxiety. The solution? Aim for a unified, centralized approach to policy enforcement and auditing across your entire multi-cloud footprint. This means establishing consistent security policies and compliance controls that can be applied and monitored seamlessly, regardless of which cloud platform your assets reside on. A unified strategy streamlines management, reduces complexity, and significantly lowers the risk of non-compliance. The power of automation: Your compliance superpower Manual compliance checks are, to put it mildly, an Achilles' heel in today's dynamic cloud environments. They are incredibly time-consuming, prone to human error, and simply cannot keep pace with the continuous changes in cloud configurations and evolving threats. This is where automation becomes your most potent compliance superpower. Leveraging automation for continuous monitoring of configurations, access controls, and network flows ensures ongoing adherence to compliance standards. Automated tools can flag deviations from policies in real-time, identify misconfigurations before they become vulnerabilities, and provide instant insights into your compliance posture. Think of it as having an always-on, hyper-vigilant auditor embedded directly within your cloud infrastructure. It frees up your security teams to focus on more strategic initiatives, rather than endless manual checks. Prove it: Maintain comprehensive audit trails Compliance isn't just about being compliant; it's about proving you're compliant. When an auditor comes knocking – and they will – you need to provide clear, irrefutable, and easily accessible evidence of your compliance posture. This means maintaining comprehensive, immutable audit trails . Ensure that all security events, configuration changes, network access attempts, and policy modifications are meticulously logged and retained. These logs serve as your digital paper trail, demonstrating due diligence and adherence to regulatory requirements. The ability to quickly retrieve specific audit data is critical during assessments, turning what could be a stressful scramble into a smooth, evidence-based conversation. The dynamic duo: Regular review and adaptation Cloud environments are not static. Regulations evolve, new services emerge, and your own business needs change. Therefore, compliance in the cloud is never a "set it and forget it" task. It requires a dynamic approach: regular review and adaptation . Implement a robust process for periodically reviewing your compliance controls. Are they still relevant? Are there new regulations or updates you need to account for? Are your existing controls still effective against emerging threats? Adapt your policies and controls as needed to ensure continuous alignment with both external regulatory demands and your internal security posture. This proactive stance keeps you ahead of potential issues rather than constantly playing catch-up. Simplify Your Journey with the Right Tools Ultimately, staying compliant in the cloud boils down to three core pillars: clear visibility into your cloud environment, consistent and automated policy enforcement, and the demonstrable ability to prove adherence. This is where specialized tools can be invaluable. Solutions like AlgoSec Cloud Enterprise can truly be your trusted co-pilot in this intricate journey. It's designed to help you discover all your cloud assets across multiple providers, proactively identify compliance risks and misconfigurations, and automate policy enforcement. By providing a unified view and control plane, it gives you the confidence that your multi-cloud environment not only meets but also continuously maintains the strictest regulatory requirements. Don't let the complexities of cloud compliance slow your innovation or introduce unnecessary risk. Embrace strategic approaches, leverage automation, and choose the right partners to keep those clouds compliant and your business secure. 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

Discover AlgoSec's transformative 2024 journey: innovation in secure connectivity, industry leadership, and a bold vision for an empowered, Network Security 2024 in review: A transformative year for AlgoSec in secure application connectivity 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/16/24 Published As we close out 2024, I find myself reflecting on what has truly been a transformative journey for AlgoSec . This year has been filled with ground-breaking innovation, meaningful industry recognition, and a deep commitment to our vision of secure application connectivity. It has been a year where every challenge was met with determination, every milestone became a stepping-stone toward a greater future, and every success strengthened our resolve to lead in secure connectivity. Q1: Redefining secure application connectivity. We started the year by challenging traditional approaches to secure application connectivity, setting the tone for everything that followed. State of Network Security Report : The release of our State of Network Security Report was the first major milestone, quickly becoming a cornerstone of our thought leadership. This report highlighted major trends such as the enduring importance of hybrid networks and the growing shift toward multi-cloud strategies. We emphasized that security could—and should—be a driver of digital transformation. The findings made it clear that advanced tools like SD-WAN and SASE are no longer optional but essential for navigating today’s increasingly complex connectivity landscape. Launch of AlgoSec A33: In March, we launched AlgoSec A33, an application-first approach to security management. This was not just another product release; it was a clear statement of our belief that security should be an enabler of business growth. With A33, we offered seamless integration into business processes, aligning security with broader organizational goals. This launch symbolized our commitment to making secure application connectivity the foundation for organizational success. Q2: Advancing security automation and building connections. Building on the momentum from Q1, the second quarter was about advancing our automation capabilities and strengthening connections within our community. Recognition from GigaOm and Gartner : During Q2, we received meaningful recognition from GigaOm and Gartner, being named an Established Vendor in Gartner Peer Insights Voice of the Customer for Secure Connectivity Automation Platforms. This recognition validated our dedication to combining intelligent automation with human expertise, simplifying network security across increasingly complex multi-cloud environments. It was a proud moment that affirmed our efforts and pushed us to do even more. Industry Conversations on Secure Connectivity: We also took the lead in important industry conversations during this period. From enhancing visibility to tackling the challenges of multi-cloud security, AlgoSec was at the forefront—delivering solutions that drove operational efficiency while addressing the real-world challenges faced by our customers. These conversations reinforced our position as a proactive leader committed to shaping the future of secure connectivity. Q3: Setting new standards in secure connectivity. Moving into Q3, our goal was to push the boundaries further and set new industry standards for secure connectivity. Introduction of Security Application Connectivity. Anywhere (SACA): One of the major highlights of the third quarter was the introduction of our Security Application Connectivity Anyware (SACA) framework. SACA embodied our vision that secure connectivity is fundamental to digital transformation. By providing our customers with confidence in their application flows—without sacrificing performance or agility—we enabled them to innovate with assurance. AlgoSummit 2024: In September, we hosted AlgoSummit 2024—our flagship event that brought together customers, partners, and industry experts. AlgoSummit was not just an event but a collaborative platform for shared learning and innovation. Together, we explored the evolving landscape of secure connectivity in hybrid and multi-cloud environments. This summit further solidified AlgoSec's role as a visionary leader in the industry, committed to both solving today’s challenges and anticipating those of tomorrow. Q4: Expanding Zero Trust and navigating regulatory changes. As we entered the final quarter, our focus shifted to expanding our Zero Trust offerings and helping customers prepare for upcoming regulatory changes. Zero Trust Architecture Expansion: We made significant strides in advancing our Zero Trust network architecture initiatives in Q4. As hybrid environments grow more complex, we understood the need to simplify Zero Trust adoption for our customers. By leveraging both micro and macro-segmentation strategies, we offered a streamlined, application-centric approach that provided greater visibility and control—ensuring that connectivity remained secure, segmented, and compliant. Navigating DORA Compliance : Another key focus for Q4 was helping our customers navigate the requirements of the Digital Operational Resilience Act (DORA). With the compliance deadline fast approaching, we used our intelligent automation tools to make the transition as smooth as possible. Our solutions offered comprehensive visibility, automated risk assessments, and policy recertification, allowing financial institutions to meet DORA’s stringent standards confidently and strengthen their resilience. Recognition for innovation and ethical leadership Throughout the year, our commitment to responsible innovation and ethical leadership did not go unnoticed. SC Awards Finalist in Application Security: Being named a finalist in the SC Awards for Application Security was a significant milestone, reaffirming our dedication to protecting the applications that drive business growth and innovation. Top InfoSec Innovator Award from CyberDefense Magazine: In November, we were recognized as a Top InfoSec Innovator by CyberDefense Magazine. This accolade underscored our focus on ethical innovation—delivering security solutions that are trustworthy, responsible, and aligned with global standards. Accolades in Network and Application Security : Additionally, we were named a Hot Company in Secure Application Connectivity and recognized as the Most Innovative in Application Security. These awards were not just acknowledgments of our technology but a testament to our ongoing commitment to setting new standards of transparency, accountability, and secure connectivity. Cisco Meraki Marketplace Tech Partner of the Month : In October 2024, we were honored as the Cisco Meraki Marketplace Tech Partner of the Month based on our continued innovation and dedication to application security . This recognition highlights our ability to deliver holistic visibility, automate security policy changes, reduce risks, and ensure continuous compliance through seamless integration with Cisco Meraki solutions. Looking to the future: building on the foundations of 2024 Reflecting on 2024, it’s clear that this has been a year of significant growth, innovation, and resilience. The lessons we’ve learned and the progress we’ve made have laid a strong foundation for the future. As we look ahead to 2025, our mission remains clear: to continue providing application-centric security solutions that not only protect but also empower our customers to achieve their strategic objectives. I am incredibly grateful for the dedication of our team, the trust our customers have placed in us, and the opportunity to continue shaping the future of secure connectivity. Here’s to another year of impactful innovation, collaboration, and leadership as we step confidently into 2025. 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

Last week our CTO, Professor Avishai Wool, presented a technical webinar on the do’s and don’ts for managing external connectivity to and... Auditing and Compliance 4 tips to manage your external network connections Joanne Godfrey 2 min read Joanne Godfrey 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/10/15 Published Last week our CTO, Professor Avishai Wool, presented a technical webinar on the do’s and don’ts for managing external connectivity to and from your network . We kicked off our webinar by polling the audience (186 people) on how many external permanent connections into their enterprise network they have. 40% have less than 50 external connections 31% have 50-250 external connections 24% have more than 250 external connections 5% wish they knew how many external connections they have! Clearly this is a very relevant issue for many enterprises, and one which can have a profound effect on security. The webinar covered a wide range of best practices for managing the external connectivity lifecycle and I highly recommend that you view the full presentation. But in the meantime, here are a few key issues that you should be mindful of when considering how to manage external connectivity to and from your network: Network Segmentation While there has to be an element of trust when you let an external partner into your network, you must do all you can to protect your organization from attacks through these connections. These include placing your servers in a demilitarized zone (DMZ), segregating them by firewalls, restricting traffic in both directions from the DMZ as well as using additional controls such as web application firewalls, data leak prevention and intrusion detection. Regulatory Compliance Bear in mind that if the data being accessed over the external connection is regulated, both your systems and the related peer’s systems are now subject t. So if the network connection touches credit card data, both sides of the connection are in scope, and outsourcing the processing and management of regulated data to a partner does not let you off the hook. Maintenance Sometimes you will have to make changes to your external connections, either due to planned maintenance work by your IT team or the peer’s team, or as a result of unplanned outages. Dealing with changes that affect external connections is more complicated than internal maintenance, as it will probably require coordinating with people outside your organisation and tweaking existing workflows, while adhering to any contractual or SLA obligations. As part of this process, remember that you’ll need to ensure that your information systems allow your IT teams to recognize external connections and provide access to the relevant technical information in the contract, while supporting the amended workflows. Contracts In most cases there is a contract that governs all aspects of the external connection – including technical and business issues. The technical points will include issues such as IP addresses and ports, technical contact points, SLAs, testing procedures and the physical location of servers. It’s important, therefore, that this contract is adhered to whenever dealing with technical issues related to external connections. These are just a few tips and issues to be aware of. To watch the webinar from Professor Wool in full, check out the recording here . 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 aim of this post is to provide a very high-level illustration of the DNS Tunneling method used in the SolarWinds supply chain attack.... Cloud Security DNS Tunneling In The SolarWinds Supply Chain Attack 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/23/20 Published The aim of this post is to provide a very high-level illustration of the DNS Tunneling method used in the SolarWinds supply chain attack . An Attacker compromises SolarWinds company and trojanizes a DLL that belongs to its software. Some of the customers receive the malicious DLL as an update for the SolarWinds Orion software. “Corporation XYZ” receives the malicious and digitally signed DLL via update. SolarWinds Orion software loads the malicious DLL as a plugin. Once activated, the DLL reads a local domain name “local.corp-xyz.com” (a fictious name). The malware encrypts the local domain name and adds it to a long domain name. The long domain name is queried with a DNS server (can be tapped by a passive DNS sensor). The recursive DNS server is not authorized to resolve avsvmcloud[.]com, so it forwards the request. An attacker-controlled authoritative DNS server resolves the request with a wildcard A record. The Attacker checks the victim’s name, then adds a CNAME record for the victim’s domain name. The new CNAME record resolves the long domain name into an IP of an HTTP-based C2 server. The malicious DLL downloads and executes the 2nd stage malware (TearDrop, Cobalt Strike Beacon). A Threat Researcher accesses the passive DNS (pDNS) records. One of the long domain names from the pDNS records is decrypted back into “local.corp-xyz.com”. The Researcher deducts that the decrypted local domain name belongs to “Corporation XYZ”. 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

DORA compliance with AlgoSec Datasheet Download PDF Download PDF Add a Title Add a Title Add a Title 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

One fabric every app Download PDF Download PDF Add a Title Add a Title Add a Title 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