Search results

Webinars Panel: 5 ways to Better Manage your Network Security in 2020 Is your network ready for 2020? What practical steps are you taking to prepare for even more demanding security management in the new year? In this live panel discussion, Yitzy Tannenbaum, Product Marketing Manager and Avishai Wool, AlgoSec’s co-founder and CTO, will cover 5 practicalsteps to help you better manage your network security in the new year. Address these pressing network security challenges: Preventing breaches due to network misconfigurations Managing complex compliance requirements Determine the intention of your security controls and embracing intent-based network security Implementing datacenter micro-segmentation Understanding the shared responsibility model and effectively managing cloud security Kick off the new year better prepared to face the network security management challenges – don’t miss this important discussion. January 9, 2020 Prof. Avishai Wool CTO & Co Founder AlgoSec Yitzy Tannenbaum Product Marketing Manager Relevant resources Network security management: Components & features Keep Reading 5 Network Security Management Predictions for 2020 Watch Video 2020 vision predictions for the year ahead in network security 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

Azure Security Best Practices: Don't Get Caught with Your Cloud Pants Down   Executive Summary   The cloud isn't some futuristic fantasy... Cloud Security Azure Security Best Practices Asher Benbenisty 2 min read Asher Benbenisty 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 11/25/24 Published Azure Security Best Practices: Don't Get Caught with Your Cloud Pants Down Executive Summary The cloud isn't some futuristic fantasy anymore, folks. It's the backbone of modern business, and Azure is charging hard, fueled by AI, to potentially dethrone AWS by 2026. But with this breakneck adoption comes a harsh reality: security can't be an afterthought. This article dives deep into why robust security practices are non-negotiable in Azure and how tools like Microsoft Sentinel and Defender XDR can be your digital bodyguards. Introduction Let's face it, organizations are flocking to the cloud like moths to a digital flame. Why? Cost savings, streamlined operations, and the ability to scale at warp speed. We're talking serious money here – a projected $805 billion spent on public cloud services in 2024! The cloud's not just disrupting the game; it is the game. And the playing field is shifting. AWS might be the king of the hill right now, but Azure's hot on its heels, thanks to some serious AI muscle. ( As of 2024, they hold market shares of 31%, 24%, and 11%, respectively .) Forbes even predicts an Azure takeover by 2026. Exciting times, right? Hold your horses. This rapid cloud adoption has a dark side. Security threats are lurking around every corner, and sticking to best practices is more crucial than ever. Cloud service managers, listen up: you need to wrap your heads around the shared responsibility model (Figure 1). Think of it like this: you and Azure are partners in crime prevention. You're both responsible for keeping your digital assets safe, but you need to know who's holding which piece of the security puzzle. Don't assume security is built-in – it's a team effort, and you need to pull your weight. Figure 1: The shared responsibility model Azure's Security Architecture: A Fortress in the Cloud Okay, I get it. The shared responsibility model can feel like navigating a maze blindfolded. But here's the deal: whether you're dabbling in IaaS, PaaS, or SaaS, Azure's got your infrastructure covered. Their global network of data centers is built like Fort Knox, meeting industry standards like ISO/IEC 27001:2022 , HIPAA , and NIST SP 800-53 . But remember your part of the bargain! Azure provides a killer arsenal of security products to protect your workloads, both in Azure and beyond. Figure 2: Azure’s security architecture Take Microsoft Sentinel, for example. This superhero of a tool automatically sniffs out threats, investigates them, and neutralizes them before they can wreak havoc. It's like having a 24/7 security team with superhuman senses. And don't forget about Microsoft Defender XDR. This comprehensive security suite is like a digital Swiss Army knife, protecting your identities, endpoints, applications, email, and cloud apps. It's got your back, no matter where you turn. With Sentinel and Defender XDR in your corner, you're well-equipped to tackle the security challenges that come with cloud adoption. But don't get complacent! Let's dive into some core security best practices that will make your Azure environment an impenetrable fortress. Core Security Best Practices: Lock Down Your Secrets Protecting Secrets: Best Practices Using Azure Key Vault We all have secrets, right? In the digital world, those secrets are things like passwords, API keys, and encryption keys. You can't just leave them lying around for any cybercriminal to snatch. That's where Azure Key Vault comes in. This secure vault is like a digital safe deposit box for your sensitive data. It uses hardware security modules (HSMs) to keep your secrets locked down tight, even if someone manages to breach your defenses. Big names like Victoria's Secret & Co , Evup, and Sage trust Key Vault to keep their secrets safe. Figure 3: A new Key Vault named “algosec-kv” Here's a pro tip: once you've stashed your secrets in Key Vault, use a managed identity to access them. This eliminates the need to hardcode credentials in your code, minimizing the risk of exposure. var client = new SecretClient(new Uri("https://. vault.azure.net/ "), new DefaultAzureCredential(),options); KeyVaultSecret secret = client.GetSecret(""); string secretValue = secret.Value; Key Vault is a fantastic tool, but it's not a silver bullet. Download our checklist of additional best practices to keep your secrets safe: Database and Data Security: More Than Just Locking the Door Azure offers a smorgasbord of data storage solutions, from Azure SQL Database to Azure Blob Storage. But securing your data isn't just about protecting it at rest. You need to think about data in use and data in transit, too. Download our checklist for a full action plan: Identity Management: Who Are You, and What Are You Doing Here? Encryption is great, but it's only half the battle. You need to know who's accessing your resources and what they're doing. That's where identity access management (IAM) comes in. Think of IAM as a digital bouncer, controlling access to your network resources. It's all about verifying identities and granting the right level of access – no more, no less. Zero-trust network access (ZTNA) is your secret weapon here. It's like having a security checkpoint at every corner of your network, ensuring that only authorized users can access your resources. Figure 4: Zero-trust security architecture Remember the Capital One breach? A misconfigured firewall and overly broad permissions led to a massive data leak. Don't let that be you! Follow Azure's IAM documentation to build a robust and secure identity management system. Network Security: Building a Digital Moat Your network architecture is the foundation of your security posture. Choose wisely, my friends! The hub-spoke model is a popular choice in Azure, centralizing common services in a secure hub and isolating workloads in separate spokes. Figure 5: Hub-spoke network architecture in Azure (Source: Azure documentation ) For a checklist of how the hub-spoke model can boosts your security, download our checklist here. Digital Realty , a real estate investment giant, uses the hub-spoke model to secure its global portal and REST APIs. It's a testament to the power of this architecture for both security and performance. Figure 6: Digital Realty’s use of hub-spoke architecture (Adapted from Microsoft Customer Stories ) Operational Security: Stay Vigilant, Stay Secure (Continued) When a security incident strikes, your response time is critical. Think of operational security as your digital first aid kit. It's about minimizing human error and automating processes to speed up threat detection and response. We've already talked about MFA, password management, and the dynamic duo of Defender XDR and Sentinel. Download our checklist for a few more operational security essentials to add to your arsenal. Figure 7: Build-deploy workflow automation (Source: Azure documentation ) Think of these best practices as guardrails, guiding you toward secure decisions. But remember, flexibility is key. Adapt these practices to your specific environment and architecture. Conclusion As Azure's popularity skyrockets, so do the stakes. The shared responsibility model means you're not off the hook when it comes to security. Azure provides powerful tools like Sentinel and Defender XDR, but it's up to you to use them wisely and follow best practices. Protect your secrets like they're buried treasure, secure your data with Fort Knox-level encryption, implement identity management that would make a border patrol agent proud, and build a network architecture that's a digital fortress. And don't forget about operational security – it's the glue that holds it all together. But let's be real, managing security policies across multiple clouds can be a nightmare. That's where tools like AlgoSec CloudFlow come in. They provide a clear view of your security landscape, helping you identify vulnerabilities and streamline policy management. It's like having a security command center for your entire cloud infrastructure. So, what are you waiting for? Request a demo today and let AlgoSec help you build an Azure environment that's so secure, even the most determined cybercriminals will be left scratching their heads. 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

비즈니스 속도에 따른 맞춤형 보안 관리 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

The new capabilities empower teams to move faster with clarity, control, and business-aligned risk prioritization AlgoSec Security Management Solution A33.20 removes network security change friction across hybrid and multi-cloud networks The new capabilities empower teams to move faster with clarity, control, and business-aligned risk prioritization January 22, 2026 Speak to one of our experts RIDGEFIELD PARK, NJ, January 22, 2026 – Global cybersecurity leader AlgoSec has released version A33.20 of its Security Management Solution , as a part of the AlgoSec Horizon platform. The new version introduces capabilities designed to remove friction from network security operations, providing teams with clearer visibility, better control, and faster, more confident decision-making. With 90% of organizations expected to adopt a hybrid cloud approach by 2027, security teams must manage more complex and distributed network environments. Security changes are often required on tight timelines, frequently without full visibility into how policy modifications impact critical applications. At the same time, evolving governance and compliance requirements place added demands on maintaining precise and consistent security controls. “Security teams today are being asked to move faster than ever, but speed without clarity, especially across complex environments, creates risk,” said Eran Shiff , Chief Product Officer at AlgoSec. “With A33.20, we’re removing unnecessary complexity and delays from change management by giving teams visibility and control across environments, helping them focus on the risks that truly matter to the business and making every change faster and more secure.” ASMS A33.20 delivers these outcomes through four key areas: Simplifying alignment and execution: Algo, an AI-powered bot, simplifies workflows and streamlines manual repetitive tasks, including change ticket creation, risk and compliance analysis and validation of consistent application connectivity flows. Algo allows stakeholders to interact using their own language, improving alignment across the enterprise and simplifying execution of application connectivity and security management tasks. Improving visibility and control across hybrid environments: Expanded cloud policy support for AWS, Azure and Google Cloud, delivering traffic simulation query and impact analysis uniquely for Google Load Balancer, for AWS native firewall, and enabling full support of policy visibility for Palo Alto Networks NGFWs through Strata Cloud Manager. Automating security changes to reduce manual effort: AlgoSec FireFlow support for Google Cloud Network Firewall Policy provides work order recommendations for traffic change requests, while report-based automation enables remediation directly from analytics such as Disabled Rules and Unused Rules reports. Focusing risk and compliance efforts on business priorities: The only solution in which risk and compliance are evaluated in the context of enterprise applications, enabling prioritization based on business criticality and simplifying rule recertification. Additionally, out-of-the-box compliance assessments now include CIS Baseline for Palo Alto Networks, NIS2 and SOC 2-mapped controls with reporting across supported vendors. To learn more about the new A33.20 product release, click here . 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 2200 of the world's most complex organizations trust AlgoSec to help secure their most critical workloads. AlgoSec Horizon platform utilizes advanced AI capabilities, enabling users to automatically discover and identify their business applications across multi-clouds, and remediate risks more effectively. It serves as a single source for visibility into security and compliance issues across the hybrid network environment, to ensure ongoing adherence to internet security standards, industry, and internal regulations. Additionally, organizations can leverage intelligent change automation to streamline security change processes, thus improving security and agility. Learn how AlgoSec enables application owners, information security experts, SecOps and cloud security teams to deploy business applications faster while maintaining security at www.algosec.com . MEDIA CONTACT: Megan Davis Alloy, on behalf of AlgoSec [email protected]

Webinars Tightening security posture with micro-segmentation Micro-segmentation protects your network by limiting the lateral movement of ransomware and other threats in your network. Yet successfully implementing a defense-in-depth strategy using micro-segmentation may be complicated. In this second webinar in a series of two webinars about ransomware, Yitzy Tannenbaum, Product Marketing Manager from AlgoSec and Jan Heijdra, Cisco Security Specialist, will provide a blueprint to implementing micro-segmentation using Cisco Secure Workload (formerly Cisco Tetration) and AlgoSec Network Security Policy Management. Join our live webinar to learn: Why micro-segmentation is critical to fighting ransomware Understand your business applications to create your micro-segmentation policy Validate your micro-segmentation policy is accurate Enforce these granular policies on workloads and summarized policies across your infrastructure Use risk and vulnerability analysis to tighten your workload and network security Identify and manage security risk and compliance in your micro-segmented environment January 27, 2021 Jan Heijdra Cisco Security Specialist Yitzy Tannenbaum Product Marketing Manager Relevant resources Micro-segmentation – from strategy to execution Keep Reading Defining & Enforcing a Micro-segmentation Strategy Read Document Building a Blueprint for a Successful Micro-segmentation Implementation 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

Explore Algosec's customer success stories to see how organizations worldwide improve security, compliance, and efficiency with our solutions. Arcon Maintains Security Across Diverse Customer Networks With AlgoSec Organization ARCON Industry Financial Services Headquarters Rio de Janeiro, Brazil Download case study Share Customer
success stories "Using AlgoSec is a double benefit to us because we can reduce the cost and number of errors in our daily operation and also expand our offerings to our customers" Global Managed Services Company Optimizes Firewall Policies and Reduces Risks AlgoSec Business Impact • Improve security and assure compliance of its customers • Deliver comprehensive reports • Reduce costs and misconfiguration errors • Expand offerings to Arcon’s customers Background Founded in 1995, Arcon is the leading MSSP in Brazil. The company operates facilities in Rio de Janeiro, Sao Paulo, Brasília, Flórida, Salvador and Belém, managing the networks of many of Brazil’s top 100 companies, including banks, retailers, manufacturers and telecom companies. Arcon protectsmore than 600,000 users across five continents and processes more than one billion transactions each day. In addition to strategic management of IT security, Arcon protects data, servers, workstations and mobile devices and helps customers identify and control access to their systems. The company also evaluates risks in applications and provides technology infrastructure to support its customers’ businesses. Challenge Arcon provides security services to hundreds of other companies, including major retailers and banks, which require the tools that enable it to rapidly identify compliance issues and assess risks associated with network configurations. It must also be able to determine how to best optimize customers’ security policies and track changes made to firewall rules. With so many customers and service level agreements that require near immediate responses, Arcon needed visibility across the networks it manages and into reports allowing them to quickly find and fix issues and to counsel customers on changes that would improve their systems’ security. Solution Flavio Carvalho, the Security Management Services Director at Arcon, was charged with maintaining security across its own network, as well as diverse customers’ networks. Carvalho and his team selected the AlgoSec Security Management solution. “The combination of ease-of-use and the value add of AlgoSec’s reports, the ability to manage different technologies from multiple vendors, the cost per device managed, and the visibility across customer’s networks were key for us,” comments Carvalho.The quality of the AlgoSec’s reports clinched the deal. “With AlgoSec, we can quickly and easily provide PCI compliance reports to our customers, including banks and large retail stores. The excellent quality of the reports adds value to the services we manage for them,” says Carvalho. Results Arcon’s clients expect regular updates on the security of their networks — including recommendations for policy optimization, risk mitigation strategies, compliance verification and the impact of rule changes. “It would be impossible for us to deliver all of these in monthly reports without AlgoSec,” Carvalho notes. We have a big retail customer with SLAs of just one hour. “With AlgoSec we have been able to meet these SLAs much more easily than before. A report that previously took a day to generate can now be completed in a few minutes at the click of a button,” Carvalho notes.Shortly after implementation, Arcon’s experience with one large bank customer validated their decision to use AlgoSec — and made their customer very happy. “Our customer was under pressure because of high CPU utilization in their main firewall cluster,” explains Carvalho. “They needed us to investigate what was going on and to solve the issue as quickly and cost-effectively as possible. Using AlgoSec, we were able to easily identify a series of duplicate and poorly-written rules that were causing the trouble, and we solved the problem at no cost to the customer.”“Using AlgoSec is a double benefit to us because we can reduce the cost and number of errors in our daily operations and also expand our offerings to our customers,” adds Carvalho. “It’s easy to work with AlgoSec, as we have a direct contact and an excellent AlgoSec support team, which is always available to help us when necessary” concludes Carvalho. Schedule time with one of our experts

The Business benefits of application centric zero trust E-BOOK 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

Learn how Google Cloud and AlgoSec solutions help companies improve visibility and reduce risk in large complex hybrid networking environments Webinars Hybrid Cloud Security with Google and AlgoSec Learn how Google Cloud and AlgoSec solutions help companies improve visibility and reduce risk in large complex hybrid networking environments Learn how Google Cloud and AlgoSec solutions help companies improve visibility and reduce risk in large complex hybrid networking environments November 15, 2023 Faye Feng Product Manager at Google Ava Chawla Global Head of Cloud Security Relevant resources Why misconfigurations continue to plague public cloud network services and how to avoid them? Keep Reading Security policy management for the hybrid cloud environment Read an Ebook 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

Explore Algosec's customer success stories to see how organizations worldwide improve security, compliance, and efficiency with our solutions. Reece Group Gets Change Requests Flowing Organization Reece Group Industry Retail & Manufacturing Headquarters Victoria, Australia Download case study Share Customer
success stories "The reason we chose AlgoSec is because we saw the benefits of what it would give us for the business. The time it has taken to make a change has dropped significantly..." Leading plumbing and HVAC company empowers business and IT teams with ChatOps, reduce troubleshooting time, so they can focus on building their business. Background The Reece Group is a leading distributor of plumbing, waterworks and HVAC-R products to commercial and residential customers through 800 branches in Australia, New Zealand and the United States.Established in 1920, this includes 10 specialized business units servicing the plumbing, bathroom, building, civil, irrigation, heating, air conditioning and refrigeration industries. The Challenge Some of the Reece Group’s challenges included: Commissioning and decommissioning – As firewall upgrades and migrations were frequently handled by third-party suppliers, there was a lack of business alignment and visibility into their entire multi-vendor hybrid network. Clarity and understanding of security rules – They had difficulty understanding what rules were in place across their entire network and understanding and what services the rules applied to. The Solution The Reece Group searched for a solution that provided: Baseline compliance – To ensure that their rules did not introduce unnecessary risk or compliance violations. Visibility into risk – So they could understand what their rules did in order to not cause an outage. They implemented AlgoSec Firewall Analyzer and AlgoSec FireFlow. They also use AlgoBot, AlgoSec’s ChatOps solutions. AlgoSec Firewall Analyzer provides visibility and analyzes complex network security policies across on-premise, cloud, and hybrid networks. It automates and simplifies security operations including troubleshooting, auditing, and risk analysis. Using Firewall Analyzer, the client can optimize the configuration of firewalls, and network infrastructure to ensure security and compliance. AlgoSec FireFlow enables security staff to automate the entire security policy change process from design and submission to proactive risk analysis, implementation, validation, and auditing. Its intelligent, automated workflows save time and improve security by eliminating manual errors and reducing risk. AlgoBot is an intelligent chatbot that handles network security policy management tasks for you. AlgoBot answers your questions, submitted in plain English, and personally assists with security policy change management processes – without requiring manual inputs or additional research. The Result Reece Group choose AlgoSec because it aligned with their business needs. Some of benefits they got by using AlgoSec include: Empowering application developers – Developers are able to proactively check within Slack if the reason an application isn’t working is because of the firewall is blocking traffic or if the application is misconfigured. Faster request and response time – Application developers are quickly able to identify if a network change request is needed. They spend less time on troubleshooting and can proactively make valid change requests. IT also ceased becoming a bottleneck for application developers and were able to complete firewall changes in less than two hours from the initial change request. Reduced firewall ruleset by 85% –Rules declined from 3,000 rules to 450 rules. More time to work on business-critical projects – Firewall administrators are able to save time with easy-to-understand dashboards and automation, freeing up time to work on other business-critical projects. Clear understanding of risks and compliance – Easy out-of-the box dashboards and flags for risk and compliance issues make it easy for the company to understand and identify risks and compliance violations Schedule time with one of our experts

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

AlgoSec’s latest product release provides application-based identification and risk analysis in multi-cloud environments and on-premises. Gain more insights into multi cloud application connectivity with AlgoSec A32.50 AlgoSec’s latest product release provides application-based identification and risk analysis in multi-cloud environments and on-premises. January 10, 2023 Speak to one of our experts RIDGEFIELD PARK, N.J., January 10, 2023 – AlgoSec, a global cybersecurity leader in securing application connectivity, announced today the release of its latest product version A32.50. AlgoSec A32.50 provides a powerful solution for organizations to secure application connectivity in their hybrid and multi-cloud estate. With A32.50, organizations obtain granular visibility and discovery of applications, enabling identification and risk analysis in multi-cloud environments and on-premises. The key benefits that AlgoSec A32.50 delivers to IT, network, and security experts include: Application awareness for Cisco Firepower and Palo Alto’s Panorama as part of the change management cycle Enables SecOps teams to update firewall application information as part of the firewall rules in the workflow automation Extended SASE/SSE management Provides Zscaler users management capabilities focused on risk, regulatory compliance, and policy optimization. As an early availability, A32.50 supports Prisma Access visibility of mobile users. Ensure ongoing regulatory compliance with new and updated out of the box reports Generate full audit report for the ECB security of internet payments and maintain ongoing compliance with the regulatory requirements. Additionally, utilize updated PCI and SWIFT requirement reports. Integrate cloud security into your IaC initiative while streamlining processes Embed cloud security checks into the DevSecOps native tools, allowing them to proactively identify and mitigate risk as part of their ongoing process. About AlgoSec AlgoSec, a global cybersecurity leader, empowers organizations to secure application connectivity by automating connectivity flows and security policy, anywhere. The AlgoSec platform enables the world’s most complex organizations to gain visibility, reduce risk, and process changes at zero-touch across the hybrid network. AlgoSec’s patented application-centric view of the hybrid network enables business owners, application owners, and information security professionals to talk the same language, so organizations can deliver business applications faster while achieving a heightened security posture. Over 1,800 of the world’s leading organizations trust AlgoSec to help secure their most critical workloads across public cloud, private cloud, containers, and on-premises networks while taking advantage of almost two decades of leadership in Network Security Policy Management. See what securely accelerating your digital transformation, move-to-cloud, infrastructure modernization, or micro-segmentation initiatives looks like at www.algosec.com

Prof. Avishai Wool, AlgoSec co-founder and CTO, stresses the importance of getting the often-overlooked function of managing network... Professor Wool Bridging Network Security Gaps with Better Network Object Management 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 4/13/22 Published Prof. Avishai Wool, AlgoSec co-founder and CTO, stresses the importance of getting the often-overlooked function of managing network objects right, particularly in hybrid or multi-vendor environments Using network traffic filtering solutions from multiple vendors makes network object management much more challenging. Each vendor has its own management platform, which often forces network security admins to define objects multiple times, resulting in a counter effect. First and foremost, this can be an inefficient use of valuable resources from a workload bottlenecking perspective. Secondly, it creates a lack of naming consistency and introduces a myriad of unexpected errors, leading to security flaws and connectivity problems. This can be particularly applicable when a new change request is made. With these unique challenges at play, it begs the question: Are businesses doing enough to ensure their network objects are synchronized in both legacy and greenfield environments? What is network object management? At its most basic, the management of network objects refers to how we name and define “objects” within a network. These objects can be servers, IP addresses, or groups of simpler objects. Since these objects are subsequently used in network security policies, it is imperative to simultaneously apply a given rule to an object or object group. On its own, that’s a relatively straightforward method of organizing the security policy. But over time, as organizations reach scale, they often end up with large quantities of network objects in the tens of thousands, which typically lead to critical mistakes. Hybrid or multi-vendor networks Let’s take name duplication as an example. Duplication on its own is bad enough due to the wasted resource, but what’s worse is when two copies of the same name have two distinctly different definitions. Let’s say we have a group of database servers in Environment X containing three IP addresses. This group is allocated a name, say “DBs”. That name is then used to define a group of database servers in Environment Y containing only two IP addresses because someone forgot to add in the third. In this example, the security policy rule using the name DBs would look absolutely fine to even a well-trained eye, because the names and definitions it contained would seem identical. But the problem lies in what appears below the surface: one of these groups would only apply to two IP addresses rather than three. As in this case, minor discrepancies are commonplace and can quickly spiral into more significant security issues if not dealt with in the utmost time-sensitive manner. It’s important to remember that accuracy is the name in this game. If a business is 100% accurate in the way it handles network object management, then it has the potential to be 100% efficient. The Bottom Line The security and efficiency of hybrid multi-vendor environments depend on an organization’s digital hygiene and network housekeeping. The naming and management of network objects aren’t particularly glamorous tasks. Having said that, everything from compliance and automation to security and scalability will be far more seamless and risk averse if taken care of correctly. To learn more about network object management and why it’s arguably more important now than ever before, watch our webcast on the subject or read more in our resource hub . 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