Search results

AlgoSec Horizon platform empowers organizations to seamlessly secure applications across complex, converging cloud and on-premise network environments with AI-driven visibility, automation and risk mitigation AlgoSec Launches AlgoSec Horizon, its Most Advanced Application-Centric Security Platform for Converging Cloud and On-Premise Environments AlgoSec Horizon platform empowers organizations to seamlessly secure applications across complex, converging cloud and on-premise network environments with AI-driven visibility, automation and risk mitigation February 11, 2025 Speak to one of our experts RIDGEFIELD PARK, NJ, February 11, 2025 – AlgoSec , a global cybersecurity leader, today announced the launch of AlgoSec Horizon , the industry's first and only application-centric security management and automation platform designed for hybrid networks. By applying an application-centric approach to security, the AlgoSec Horizon platform enables security teams to manage application connectivity and security policies consistently across both cloud and data center environments. Gartner predicts that by 2027 , 50% of critical enterprise applications will reside outside of centralized public cloud locations, underscoring the ongoing expansion, evolution and complexity of today’s network infrastructures. Yet, many businesses still have a segmented team that splits focus between development and security teams in an effort to ensure holistic protection. To combat these challenges, businesses are embracing unified platforms that converge cloud and data center security teams to align strategies, unify policy enforcement and ensure consistent security within hybrid environments. “Today's networks are 100x more complex as a result of the rapid acceleration of application deployment and network complexity, requiring organizations to embrace platformization to unify security operations, automate policies and enhance visibility across infrastructures,” said Eran Shiff , VP Product of AlgoSec. “With the launch of the AlgoSec Horizon Platform, organizations now have full visibility into their hybrid-cloud network, allowing for increased security without business productivity interference.” As the first and only application-centric security management and automation platform for the hybrid network, AlgoSec Horizon utilizes advanced AI capabilities to automatically discover and identify an organization’s business applications across multi-clouds and data centers, and remediate risks more effectively. The platform serves as a single source for visibility into security and compliance issues across hybrid network environments to ensure adherence to security standards and regulations. Through AlgoSec Horizon, organizations are able to: ● Visualize application connectivity: Utilize advanced AI modules to discover and identify running business applications within an organization’s network, including their connectivity, network zones, risks, vulnerabilities and resources, to reduce operational complexity and simplify management. ● Securely automate application connectivity changes: Ensure smooth business operations by intelligently automating security policy changes with a focus on business applications. AlgoSec’s intelligent automation minimizes misconfigurations and enhances operational resilience to accelerate application delivery from weeks to hours. ● Prioritize risk mitigation based on business context: Prioritize remediation efforts based on the criticality of affected applications and associated risks, to ensure resources are effectively allocated to protect vital business processes. AlgoSec helps prioritize security efforts based on the criticality of business applications, industry best practices, relevant regulations and specific security policies, to ensure the most severe vulnerabilities are addressed first. ● Maintain application-centric compliance: Streamline regulatory adherence, make audits faster and easier to manage, and ensure that organizations remain compliant with minimal effort and reduce the risk of non-compliance penalties across the entire hybrid environment. During Cisco Live 2025 Amsterdam , AlgoSec will invite attendees to experience and demo the Horizon Platform at stand C05. To request a media briefing with AlgoSec at the show, please email [email protected] . About AlgoSec AlgoSec, a global cybersecurity leader, empowers organizations to securely accelerate application delivery up to 10 times faster by automating application connectivity and security policy across the hybrid network environment. With two decades of expertise securing hybrid networks, over 2,200 of the world's most complex organizations trust AlgoSec to help secure their most critical workloads. AlgoSec Horizon platform utilizes advanced AI capabilities, enabling users to automatically discover and identify their business applications across multi-clouds and datacenters, and remediate risks more effectively. It serves as a single source for visibility into security and compliance issues across the hybrid network environment, to ensure ongoing adherence to internet security standards, industry, and internal regulations. Additionally, organizations can leverage intelligent change automation to streamline security change processes, thus improving security and agility. Learn how AlgoSec enables application owners, information security experts, SecOps and cloud security teams to deploy business applications faster while maintaining security at www.algosec.com . MEDIA CONTACT: Michelle Rand Alloy, on behalf of AlgoSec [email protected] 855-300-8209

Learn about the nuances of cloud network security and why it’s a strategic imperative. Cloud network security strategic imperative 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. Cloud network security explained What is cloud network security? Core components of cloud network security Why is cloud network security critical? Recommendations for cloud network security How AlgoSec tackles complex cloud network security challenges Conclusion FAQs Get the latest insights from the 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

AlgoSec FireFlow Automate and secure policy changes 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

Industry’s First Dynamic Analysis of 4 million Publicly Available Docker Hub Container Images 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

Security Policy Management with Professor Wool Network Security for VMware NSX Network Security for VMware NSX with Professor Wool is a whiteboard-style series of lessons that examine the some of the challenges of and provide technical tips for managing security policies across the VMware NSX software-defined data center and traditional data center. Lesson 1 VMware’s NSX enables datacenter owners to secure East-West traffic using filtering policies that are enforced by the VMware infrastructure. However, migrating from existing traditional filtering technologies to VMware NSX can be a daunting task. In this lesson Professor will discuss why it’s important to understand the motivations for a migration to NSX in order to successfully plan and implement the actual migration to the VMware NSX platform. Migrating to NSX: Understanding the Why in Order to Figure Out the How Watch Lesson 2 When setting up an NSX data center you need to write filtering policies for any traffic that goes into an NSX data center, exits from it, or moves between different servers inside the NSX data center. In this lesson, Professor Wool recommends a multi-stage process to help users write secure and effective policies for east East-West traffic. Tips on How to Create Filtering Policies for NSX Watch Lesson 3 Once the NSX environment is up and running it needs to be part of the organization’s network security policy change process, and subject to the organization’s governance, audit, and regulatory compliance requirements. In this lesson Professor Wool discusses how to approach managing changes, auditing and compliance when the security team doesn’t ‘own’ the virtual environment. Best Practices for Bringing NSX Security Policy Management into the InfoSec Fold Watch Have a Question for Professor Wool? Ask him now 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

What to do if your network is infected by ransomware How to prepare a ransomware playbook, using the existing capabilities of network security policy management tools Webinars How to stop ransomware in its tracks Stop ransomware in its tracks. Yes, it’s possible. But the time to prepare is now — before it strikes. In this session, security expert Dania Ben Peretz will demonstrate what to do if your network is infected by ransomware. She will show how to prepare a ransomware playbook, using the existing capabilities of network security policy management tools, so you can handle a ransomware incident as it happens. Join us and learn: The dangers of ransomware How to prepare the playbook How to stop ransomware when it strikes March 31, 2021 Dania Ben Peretz Product Manager Relevant resources Reducing your risk of ransomware attacks Keep Reading Ransomware Attack: Best practices to help organizations proactively prevent, contain and respond Keep Reading Fighting Ransomware - CTO Roundtable Insights Keep Reading Choose a better way to manage your network Choose a better way to manage your network Work email* First name* Last name* Company* country* Select country... Short answer* By submitting this form, I accept AlgoSec's privacy policy Continue

Insecure Service Protocols and Ports Okay, we all have them… they’re everyone’s dirty little network security secrets that we try not to... Risk Management and Vulnerabilities Removing insecure protocols In networks Matthew Pascucci 2 min read Matthew Pascucci Short bio about author here Lorem ipsum dolor sit amet consectetur. Vitae donec tincidunt elementum quam laoreet duis sit enim. Duis mattis velit sit leo diam. Tags Share this article 7/15/14 Published Insecure Service Protocols and Ports Okay, we all have them… they’re everyone’s dirty little network security secrets that we try not to talk about. They’re the protocols that we don’t mention in a security audit or to other people in the industry for fear that we’ll be publicly embarrassed. Yes, I’m talking about cleartext protocols which are running rampant across many networks. They’re in place because they work, and they work well, so no one has had a reason to upgrade them. Why upgrade something if it’s working right? Wrong. These protocols need to go the way of records, 8-tracks and cassettes (many of these protocols were fittingly developed during the same era). You’re putting your business and data at serious risk by running these insecure protocols. There are many insecure protocols that are exposing your data in cleartext, but let’s focus on the three most widely used ones: FTP, Telnet and SNMP. FTP (File Transfer Protocol) This is by far the most popular of the insecure protocols in use today. It’s the king of all cleartext protocols and one that needs to be smitten from your network before it’s too late. The problem with FTP is that all authentication is done in cleartext which leaves little room for the security of your data. To put things into perspective, FTP was first released in 1971, almost 45 years ago. In 1971 the price of gas was 40 cents a gallon, Disneyland had just opened and a company called FedEx was established. People, this was a long time ago. You need to migrate from FTP and start using an updated and more secure method for file transfers, such as HTTPS, SFTP or FTPS. These three protocols use encryption on the wire and during authentication to secure the transfer of files and login. Telnet If FTP is the king of all insecure file transfer protocols then telnet is supreme ruler of all cleartext network terminal protocols. Just like FTP, telnet was one of the first protocols that allowed you to remotely administer equipment. It became the defacto standard until it was discovered that it passes authentication using cleartext. At this point you need to hunt down all equipment that is still running telnet and replace it with SSH, which uses encryption to protect authentication and data transfer. This shouldn’t be a huge change unless your gear cannot support SSH. Many appliances or networking gear running telnet will either need the service enabled or the OS upgraded. If both of these options are not appropriate, you need to get new equipment, case closed. I know money is an issue at times, but if you’re running a 45 year old protocol on your network with the inability to update it, you need to rethink your priorities. The last thing you want is an attacker gaining control of your network via telnet. Its game over at this point. SNMP (Simple Network Management Protocol) This is one of those sneaky protocols that you don’t think is going to rear its ugly head and bite you, but it can! escortdate escorts . There are multiple versions of SNMP, and you need to be particularly careful with versions 1 and 2. For those not familiar with SNMP, it’s a protocol that enables the management and monitoring of remote systems. Once again, the strings can be sent via cleartext, and if you have access to these credentials you can connect to the system and start gaining a foothold on the network, including managing, applying new configurations or gaining in-depth monitoring details of the network. In short, it a great help for attackers if they can get hold of these credentials. Luckily version 3.0 of SNMP has enhanced security that protects you from these types of attacks. So you must review your network and make sure that SNMP v1 and v2 are not being used. These are just three of the more popular but insecure protocols that are still in heavy use across many networks today. By performing an audit of your firewalls and systems to identify these protocols, preferably using an automated tool such as AlgoSec Firewall Analyzer , you should be able to pretty quickly create a list of these protocols in use across your network. It’s also important to proactively analyze every change to your firewall policy (again preferably with an automated tool for security change management ) to make sure no one introduces insecure protocol access without proper visibility and approval. Finally, don’t feel bad telling a vendor or client that you won’t send data using these protocols. If they’re making you use them, there’s a good chance that there are other security issues going on in their network that you should be concerned about. It’s time to get rid of these protocols. They’ve had their usefulness, but the time has come for them to be sunset for good. Schedule a demo Related Articles 2025 in review: What innovations and milestones defined AlgoSec’s transformative year in 2025? AlgoSec Reviews Mar 19, 2023 · 2 min read Navigating Compliance in the Cloud AlgoSec Cloud Mar 19, 2023 · 2 min read 5 Multi-Cloud Environments Cloud Security Mar 19, 2023 · 2 min read Speak to one of our experts Speak to one of our experts Work email* First name* Last name* Company* country* Select country... Short answer* By submitting this form, I accept AlgoSec's privacy policy Schedule a call

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

Firewall misconfigurations are one of the most common and preventable security issues that organizations face. Comprehensively managing... Firewall Change Management How to fix misconfigured firewalls (and prevent firewall breaches) Kyle Wickert 2 min read Kyle Wickert 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 Firewall misconfigurations are one of the most common and preventable security issues that organizations face. Comprehensively managing access control, addressing vulnerabilities, and detecting configuration mistakes under these conditions is not easy It’s especially challenging for organizations that use the default firewall rules provided by their vendor. Your firewall policies should reflect your organization’s unique cybersecurity risk profile. This requires some degree of customization, and intelligence into kinds of cyber attacks hackers use to target your organization. Understanding security misconfigurations and their impact on network security Security misconfigurations happen when elements of your security tech stack expose preventable vulnerabilities that hackers can exploit. These misconfigurations can take a variety of forms, putting a wide range of security tools and open ports at risk. Network firewall misconfigurations can have a wide-ranging impact on your organization’s overall security posture. Hackers that target vulnerable infrastructure pose a threat to the entire application stack. They may be able to gain access to network services, application servers, and virtual machines. Depending on the specific misconfiguration, they may be able to compromise hardware routers and endpoints as well. In organizations with complex firewall deployments, attackers may be able to exploit misconfigurations, bypass security policies, and escalate their own privileges to make arbitrary changes to firewall security. From this point, attackers can easily modify access control lists (ACLs) to specifically allow the malware they wish to run, compromising the first line of defense against data breaches. This is exactly why Gartner recommends implementing a centralized solution for firewall management . Centralized visibility and control is crucial for maintaining effective firewall configurations and updating them accordingly. Otherwise, ensuring compliance with security best practices like the principle of least privilege becomes difficult or impossible. Routing network traffic through complex cloud-native infrastructure securely requires deep visibility into firewall configuration status, effective authentication processes, and automation-friendly security solutions. How hackers exploit misconfigured firewalls Common misconfigurations include implementing overly permissive rules, disabling critical security features, and neglecting to protect open ports against unauthorized access. This leaves organizations vulnerable to Distributed Denial-of-Service (DDoS) attacks, remote control, and data breaches . Here are some of the ways cybercriminals can exploit misconfigured firewalls: 1. Taking advantage of permissions misconfigurations Overly permissive firewall rules are a common problem among organizations with complex cloud-enabled infrastructure. Often, the organization’s demand for productivity and connectivity take precedence over the need to protect sensitive data from unauthorized network traffic. Additionally, IT team members may misunderstand the cloud provider’s shared responsibility model and assume that the provider has already secured the data center from all potential threats. These situations are particularly risky when the organization is undergoing change. For example, many security professionals start with completely open permissions and tighten them as they learn more about the network’s needs. Obvious and highly visible permissions get secured first, while less visible parts of the security framework are deprioritized – or never addressed at all. Hackers can exploit this situation by focusing on less obvious access points first. Instead of sending malicious traffic to IP addresses associated with core business servers, they might infiltrate the network through an unsecured API, or look for an unpatched operating system somewhere in the network. 2. Exploiting disabled security features Many firewalls offer advanced security features to organizations willing to configure them. However, security teams are often strained for time and resources. They may already be flooded with a backlog of high-priority security alerts to address, making it challenging to spend extra time configuring advanced firewall policies or fine-tuning their security posture. Even organizations that can enable advanced features don’t always do it. Features like leak detection and port scan alerts can put additional strain on limited computing resources, impacting performance. Other features may generate false positives, which only add to the security workload. But many of these features offer clear benefits to organizations that use them. Sophisticated technologies like application and identity-based inspection allow organizations to prioritize firewall performance more efficiently throughout the network. If threat actors find out that advanced security features like these are disabled, they are free to deploy the attack techniques these features protect against. For example, in the case of identity-based inspection, a hacker may be able to impersonate an unidentified administrator-level account and gain access to sensitive security controls without additional authentication. 3. Scanning for unsecured open ports Hackers use specialized penetration testing tools to scan for open ports. Tools like Nmap, Unicornscan , and Angry IP Scanner can find open ports and determine the security controls that apply to them. If a hacker finds out that your ACLs neglect to cover a particular port, they will immediately look for ways to exploit that vulnerability and gain access to your network. These tools are the same network discovery tools that system administrators and network engineers use on a routine basis. Tools like Nmap allow IT professionals to run security audits on local and remote networks, identifying hosts responding to network requests, discovering operating system names and versions, and more. Threat actors can even determine what kind of apps are running and find the version number of those apps. They also allow threat actors to collect data on weak points in your organization’s security defenses. For example, they might identify a healthcare organization using an outdated app to store sensitive clinical trial data. From there, it’s easy to look up the latest patch data to find out what exploits the outdated app is vulnerable to. How to optimize firewall configuration Protecting your organization from firewall breaches demands paying close attention to the policies, patch versions, and additional features your firewall provider offers. Here are three steps security leaders can take to address misconfiguration risks and ensure a robust security posture against external threats: 1. Audit your firewall policies regularly This is especially important for organizations undergoing the transition to cloud-native infrastructure. It’s virtually guaranteed that certain rules and permissions will no longer be needed as the organization adjusts to this period of change over time. Make sure that your firewall rules are constantly updated to address these changes and adapt to them accordingly. Auditing should take place under a strict change management framework . Implement a change log and incorporate it into your firewall auditing workflow so that you can easily access information about historical configuration changes. This change log will provide security professionals with readymade data about who implemented configuration changes, what time those changes took place, and why they were made in the first place. This gives you at-a-glance coverage of historical firewall performance, which puts you one step closer to building a unified, centralized solution for handling firewall policies. 2. Update and patch firewall software frequently Like every element in your security tech stack, firewall software needs to be updated promptly when developers release new patches. This applies both to hardware firewalls operating on-premises and software firewalls working throughout your network. These patches address known vulnerabilities, and they are often the first line of defense against rapidly emerging threats. The sooner you can deploy software patches to your firewalls, the more robust your network security posture will be. These changes should also be noted in a change log. This provides valuable evidence for the strength of your security posture against known emerging threats. If hackers start testing your defenses by abusing known post-patch vulnerabilities, you will be prepared for them. 3. Implement an intrusion detection system (IDS) Firewalls form the foundation of good network security, and intrusion detection systems supplement their capabilities by providing an additional line of defense. Organizations with robust IDS capabilities are much harder to compromise without triggering alerts. IDS solutions passively monitor traffic for signs of potential threats. When they detect a threat, they generate an alert, allowing security operations personnel to investigate and respond. This adds additional layers of value to the basic function of the firewall – allowing or denying traffic based on ACLs and network security rules. Many next-generation firewalls include intrusion detection system capabilities as part of an integrated solutions. This simplifies security management considerably and reduces the number of different devices and technologies security teams must gain familiarity with. Pay attention to firewall limitations – and prepare for them Properly configured firewalls offer valuable security performance to organizations with complex network infrastructure. However, they can’t prevent every cyber attack and block every bit of malicious code. Security leaders should be aware of firewall limitations and deploy security measures that compensate appropriately. Even with properly configured firewalls, you’ll have to address some of the following issues: Zero-day attacks Firewalls may not block attacks that exploit new and undiscovered vulnerabilities. Since these are not previously known vulnerabilities, security teams have not yet had time to develop patches or fixes that address them. These types of attacks are generally able to bypass more firewall solutions. However, some next-generation firewalls do offer advanced features capable of addressing zero-day attacks. Identity-based inspection is one example of a firewall technology that can detect these attacks because it enforces security policies based on user identity rather than IP address. Sandboxes are another next-generation firewall technology capable of blocking zero-day attacks. However, no single technology can reliably block 100% of all zero-day attacks. Some solutions are better-equipped to handle these types of attacks than others, but it takes a robust multi-layered security posture to consistently protect against unknown threats. Timely incident response Firewall configuration plays an important role in incident response. Properly configured firewalls help provide visibility into your security posture in real-time, enabling security teams to create high-performance incident response playbooks. Custom playbooks ensure timely incident response by prioritizing the types of threats found in real-world firewall data. If your firewalls are misconfigured, your incident response playbooks may reflect a risk profile that doesn’t match with your real-world security posture. This can lead to security complications that reduce the effectiveness of incident response processes down the line. Planned outages when updating firewalls Updating firewalls is an important part of maintaining an optimal firewall configuration for your organization. However, the update process can be lengthy. At the same time, it usually requires scheduling an outage in advance, which will temporarily expose your organization to the threats your firewall normally protects against. In some cases, there may be compatibility issues with incoming version of the firewall software being updated. This may lengthen the amount of time that the organization has to endure a service outage, which complicates firewall security. This is one reason why many security leaders intentionally delay updating their firewalls. As with many other aspects of running and maintaining good security policies, effective change management is an important aspect of planning firewall updates. Security leaders should stagger their scheduled updates to avoid reducing risk exposure and provide the organization with meaningful security controls during the update process. Automate change management and avoid misconfigurations with algoSec AlgoSec helps organizations deploy security policy changes while maintaining accuracy and control over their security posture. Use automation to update firewall configuration policies, download new security patches, and validate results without spending additional time and energy on manual processes. AlgoSec’s Firewall Analyzer gives you the ability to discover and map business applications throughout your network. Find out how new security policies will impact traffic and perform detailed simulations of potential security scenarios with unlimited visibility. Schedule a demo to see AlgoSec in action for yourself. Schedule a demo Related Articles 2025 in review: What innovations and milestones defined AlgoSec’s transformative year in 2025? AlgoSec Reviews Mar 19, 2023 · 2 min read Navigating Compliance in the Cloud AlgoSec Cloud Mar 19, 2023 · 2 min read 5 Multi-Cloud Environments Cloud Security Mar 19, 2023 · 2 min read Speak to one of our experts Speak to one of our experts Work email* First name* Last name* Company* country* Select country... Short answer* By submitting this form, I accept AlgoSec's privacy policy Schedule a call

Partner solution brief AlgoSec and Illumio: stronger together 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

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 2025 in review: What innovations and milestones defined AlgoSec’s transformative year in 2025? AlgoSec Reviews Mar 19, 2023 · 2 min read Navigating Compliance in the Cloud AlgoSec Cloud Mar 19, 2023 · 2 min read 5 Multi-Cloud Environments Cloud Security Mar 19, 2023 · 2 min read Speak to one of our experts Speak to one of our experts Work email* First name* Last name* Company* country* Select country... Short answer* By submitting this form, I accept AlgoSec's privacy policy Schedule a call

Explore micro-segmentation: a powerful security strategy. Discover real-world examples, top solutions, and key benefits for enhanced security and reduced risk. Micro-segmentation: Examples, solutions & top benefits Micro-segmentation: What it is, how it works, benefits Micro-segmentation means breaking down enterprise networks into multiple segments and using security policies to dictate how the data and applications in each segment will be accessed. These determinations are made by limiting traffic based on zero trust and least privilege principles. It provides a viable solution to flawed network security policies that weaken enterprise security. A micro-segmentation strategy enables organizations to reduce the size of their attack surface and make their networks safer against potential breaches. It also allows them to improve incident response, contain the impact of breaches, and maintain compliance with relevant laws and regulations. Schedule a Demo The need for micro-segmentation All organizations must protect their data centers with robust and effective firewall policies. Without these policies and associated security controls, smart and devious cybercriminals can easily hack into enterprise networks and systems. Micro-segmentation provides an effective way to install strong, clean, and easily-manageable security policies that help to create a more secure on-prem or hybrid cloud environment. This environment can keep traffic safe and block potential breaches from corrupting servers or compromising data. Moreover, creating multiple logical segments that are isolated from each other and enforced with least-privileged access keeps threat actors out of the network and also helps to contain a breach if it does happen. Schedule a Demo How micro-segmentation works Micro-segmentation can be applied in both on-prem data centers and cloud environments. It isolates network workloads which enable security teams to create security policies. These policies dictate the type of traffic passing in and out of each micro-segment. The policies are used to manage and create secure network segments and determine how these segments or zones will be accessed. They dictate how applications and workloads will access the resources they need, how they will share data within a system, and in which direction. Micro-segmentation also enables security teams to determine what kind of security or authentication measures are required for the environment. There are three main micro-segmentation approaches. Micro-segmentation works differently depending on which approach is adopted. Agent-based/host-based micro-segmentation Agent-based micro-segmentation utilizes a software agent deployed on the workload. It doesn’t rely on static network-level rules based on network ports or IP addresses. The agent allows security teams to enforce granular isolation, better control individual hosts, and implement automated segmentation policies with human-readable labels. Agent-based micro-segmentation security solutions are infrastructure-independent so they can be deployed across both data center and cloud infrastructure. One drawback of the method is that not all workloads can have an agent installed on them. Also, attackers can exploit the trust in the network with host firewall-based micro-segmentation. Network-based micro-segmentation Network-based micro-segmentation leverages the network infrastructure to enforce security policies. The policies are configured and enforced using access control lists (ACLs) or IP constructs. There’s no need to deploy agents on workloads. A drawback of this method is that the policies can only be enforced per endpoint, so network firewalls cannot distinguish between legitimate software and malware and will therefore block or allow both. Also, the policies are static, which can cause performance issues in more dynamic (e.g., cloud) environments. Finally, the approach can be complicated to manage when more granular micro-segments and a higher number of firewall rules are created. Hypervisor-based micro-segmentation This method depends on virtualized environments and hypervisors to create overlay networks and enforce micro-segmentation. The approach does not require network hardware changes. Also, its policy constructs are easy to learn for security teams. The chief drawback of the approach is that it doesn’t support bare metal servers, container workloads, or public cloud environments. Also, it doesn’t provide host-level visibility into its software, processes, vulnerabilities, etc. Schedule a Demo Examples of micro-segmentation One common example of micro-segmentation is the separation of development and testing environments from production environments. Granularly limiting the connections between these environments prevents careless or dangerous activities, such as using sensitive/live data for testing. Other examples include: Application micro-segmentation: Restricting access to sensitive data in applications to prevent unauthorized use or malicious exfiltration User micro-segmentation: Leveraging user identity services to control access to applications and services Tier-level micro-management: Separating application components to allow only authorized users to access specific components and keep unauthorized users out Schedule a Demo Network segmentation vs. Micro-segmentation Network segmentation divides the enterprise network into multiple security zones. In traditional data center environments, network segmentation is usually accomplished using firewalls, VLANs, and access control lists (ACLs). In more modern, cloud-based environments, Virtual Private Clouds (VPCs), subnets, and Security Groups (SGs). Microsoft Azure, for example, provides numerous network segmentation options, such as subscriptions (platform-powered separation between entities), virtual networks (isolated and secure networks to run virtual machines and applications), network security groups (access control mechanisms to control traffic between resources within a virtual network), and Azure firewall (a cloud-native stateful firewall-as-a-service to filter traffic flowing between cloud resources, the Internet, and on-premise). Regardless of the environment type, the zones created with network segmentation consist of multiple devices and applications. Admins can set access controls that permit only specific traffic between zones. Micro-segmentation is a more granular form of network segmentation. It involves placing each device or application within its own logically isolated segment instead of simply breaking a network into multiple, large segments. It thus provides more granular visibility and greater control than network segmentation. Unlike network segmentation which breaks the network based on north-south traffic (traffic running between clients and servers and crossing the security perimeter), micro-segmentation focuses on east-west traffic that moves laterally across and within the network. Moreover, it usually uses software policies and software-defined networking (SDN). With SDN, all network traffic is routed through an inspection point (e.g., a next-generation firewall) that can identify an attacker’s lateral movement and block inappropriate accesses to the network and its resources. Some SDN solutions, such as Cisco Application Centric Infrastructure (ACI), can automatically assign endpoints to logical security zones called endpoint groups (EPGs). These EPGs may have a contract that is used to control traffic flow between EPGs within the ACI fabric. Schedule a Demo Network segmentation challenges and how micro-segmentation Helps Dividing a network into multiple smaller segments can improve both its security and performance. Effective network segmentation allows security teams to spot an attack and act early to mitigate its impact and prevent its spread across the network. Even so, it can be challenging to implement network segmentation. For one, dividing the network into many VLANs and subnets requires a lot of manual effort. Also, the network may need to be re-architected, which can be difficult, time-consuming, and expensive. Micro-segmentation is a better and easier approach to securing a network, especially if host-based micro-segmentation is adopted. This is because the host-based approach is infrastructure-independent, provides more granular control, and enables micro-segmentation based on human-understandable policies instead of static network-level rules. Plus, the model can be deployed across both, cloud and data center environments without “coupling” to them. In addition, it decouples security policy enforcement from the physical infrastructure, simplifying administration and allowing more granular control. Also, it does not require network re-architecting so it is less time-consuming, less complex, and more cost-effective than network segmentation. Schedule a Demo Micro-segmentation: Essential for zero trust security Micro-segmentation is increasingly used to implement zero trust security . This new security model considers all users and devices untrustworthy by default. To gain access to network resources and become “trusted”, the user or device must meet the network’s conditions, for example, undergo a virus scan or complete multi-factor authentication (MFA). The zero trust model enables organizations to move away from traditional perimeter-based network security which is inadequate for modern-day remote workers and cloud environments. And micro-segmentation supports the model by: Dividing the network into smaller zones Creating a mini-perimeter around each endpoint to secure it individually Providing enhanced network visibility and stronger access controls In sum, zero trust, and micro-segmentation work in tandem by securing workloads in dynamic environments and preventing the lateral movement of unauthorized users in the network. Schedule a Demo The top 7 benefits of micro-segmentation The need for micro-segmentation is increasing because it provides all these benefits: Effective security through enhanced endpoint protection Micro-segmentation provides effective and cost-efficient security, particularly in modern network environments that are complex, dynamic, and fast-expanding. By logically dividing the data center into distinct security segments, it enables security architects to define security controls for each segment. This then reduces the size of the attack surface and enables the organization to better resist attacks or intrusions. Protection against network-based threats Micro-segmentation protects networks against network-based threats like DDoS attacks and WiFI attacks. It also allows admins to implement robust controls to restrict the flow of traffic on detecting a threat. Protection for cloud workloads and data Micro-segmentation can secure dynamic cloud systems, workloads, and data. With granular microsegments, security teams can easily monitor cloud traffic, identify suspicious or malicious traffic, and respond quickly once they detect dangerous breaches. Protection from advanced persistent threats (APTs) Individual micro-segments contain security checkpoints that help to keep cyber threats from spreading across the network. So, even if one part of a network is compromised, attackers cannot move laterally and reach or persist in other parts of the network. Thus, micro-segmentation protects the network from APTs. Improves breach containment Even if the network is breached, security staff can contain its impact with micro-segmentation. By monitoring traffic against secure policies, they can reduce the impact of a breach as well as their response time. Support for centralized policy management Organizations can use micro-segmentation to create and enforce granular security policies and to centralize policy management across networks. Without it, they would have to manually manage policies across a large fleet of devices and resources, which is a complex and time-consuming task. In addition, they can enforce zero-trust security policies, where access is allowed based on need, which can reduce the organization’s cyber risk. Endpoint separation enables regulatory compliance Micro-segmentation using the host-based approach helps isolate separately-secured endpoints, allowing security staff to easily control the traffic in systems that are subject to regulations. Policy granularity and visibility ensure that distributed devices are always protected by unified network security and also reduce the risks of non-compliant usage. Schedule a Demo Near-effortless micro-segmentation with AlgoSec By utilizing AlgoSec’s micro-segmentation method of network security, businesses can immediately feel safer against possible hackers and potential data breaches. Our application workload security platform will secure your compute instances across any infrastructure and any cloud. It will also enable trusted access through automated, exhaustive context from various systems to automatically adapt security policies. But there are always obstacles when installing new systems on existing servers, whether it’s evolving the firewalls already in place to accept the micro-segmented data center or navigating possible network segmentation pitfalls. Our team can work with you all the way from strategy to execution to ensure these challenges are met and handled with ease so your security improves and your data is confidently protected. We will make sure that all your segmentation policies will be applied beyond the native software and hardware sensors, extending them to all supported on-premise, cloud, and SDN technologies. By using AlgoSec, you will get consistent and defense-in-depth security across your entire hybrid network. You can also maximize your current investment by leveraging existing security technologies for micro-segmentation. Plus, we will help you secure your environment in minutes rather than days or weeks. Talk to us to know more about our business-driven security management. Schedule a Demo Select a size Micro-segmentation: What it is, how it works, benefits The need for micro-segmentation How micro-segmentation works Examples of micro-segmentation Network segmentation vs. Micro-segmentation Network segmentation challenges and how micro-segmentation Helps Micro-segmentation: Essential for zero trust security The top 7 benefits of micro-segmentation Near-effortless micro-segmentation with AlgoSec Get the latest insights from the experts Use these six best practices to simplify compliance and risk mitigation with the AlgoSec platform White paper Learn how AlgoSec can help you pass PCI-DSS Audits and ensure continuous compliance Solution Overview See how this customer improved compliance readiness and risk management with AlgoSec Case study Choose a better way to manage your network