Search results

Partner solution brief AlgoSec & Zscaler Download PDF Download PDF Add a Title Add a Title Add a Title Schedule time with one of our experts Work email* First name* Last name* Company* country* Select country... Short answer* By submitting this form, I accept AlgoSec's privacy policy Continue

The AlgoSec Security Management Suite provides you with complete visibility and control of your security policy CIO / SVP Infrastructure Schedule a demo Watch a video Do you struggle with Getting the Security team to focus on protecting critical business processes instead of broadly protecting all servers and data? Business application outages as a result of misconfigured security devices? Tying cyber threats and risk to business applications and business outcomes? Accelerating business application delivery, and slow response to business connectivity change requests? Supporting business transformation initiatives such as cloud and SDN? Fostering collaboration across the security, networking and application delivery teams? Hiring and limited availability of skilled employees? Through a single pane of glass, AlgoSec provides organizations with holistic, business-level visibility across cloud and on-premise environments, including its business processes, the business applications that power them, the servers that host them and their connectivity flows. With intelligent, zero touch automation AlgoSec discovers business applications, proactively assesses risk from the business perspective and processes security policy changes. AlgoSec’s business-driven approach to security policy management enables you to reduce business risk, ensure security and continuous compliance, and drive business agility. With AlgoSec you can View and analyze risk from the business application perspective Intelligently automate time-consuming security processes to free up time and eliminate manual errors Proactively analyze changes before they are implemented to avoid outages and ensure compliance Get a single pane of glass to manage security uniformly across cloud and on-premise network Automate the audit process for all major regulations, including PCI, HIPAA, SOX, NERC and many others, at a click of a button The Business Impact Prioritize risk from the business perspective Enable a business-driven approach to security policy management Avoid costly business application outages Improve business agility with intelligent automation Reduce the attack surface to help prevent cyber-attacks Ensure continuous compliance and reduce the risk audit failure Help address the security talent shortage through intelligent automation Foster collaboration between security, networking and application delivery teams and enable DevSecOps initiatives Resources Learn from the experts. Get the latest industry insights The state of automation in security 2016 Read 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 Firewall Management 201 Firewall Management with Professor Wool is a whiteboard-style series of lessons that examine the challenges of and provide technical tips for managing security policies in evolving enterprise networks and data centers. Lesson 1 In this lesson, Professor Wool discusses his research on different firewall misconfigurations and provides tips for preventing the most common risks. Examining the Most Common Firewall Misconfigurations Watch Lesson 2 In this lesson, Professor Wool examines the challenges of managing firewall change requests and provides tips on how to automate the entire workflow. Automating the Firewall Change Control Process Watch Lesson 3 In this lesson, Professor Wool offers some recommendations for simplifying firewall management overhead by defining and enforcing object naming conventions. Using Object Naming Conventions to Reduce Firewall Management Overhead Watch Lesson 4 In this lesson, Professor Wool examines some tips for including firewall rule recertification as part of your change management process, including questions you should be asking and be able to answer as well as guidance on how to effectively recertify firewall rules Tips for Firewall Rule Recertification Watch Lesson 5 In this lesson, Professor Wool examines how virtualization, outsourcing of data centers, worker mobility and the consumerization of IT have all played a role in dissolving the network perimeter and what you can do to regain control. Managing Firewall Policies in a Disappearing Network Perimeter Watch Lesson 6 In this lesson, Professor Wool examines some of the challenges when it comes to managing routers and access control lists (ACLs) and provides recommendations for including routers as part of your overall security policy with tips on change management, auditing and ACL optimization. Analyzing Routers as Part of Your Security Policy Watch Lesson 7 In this lesson, Professor Wool examines the complex challenges of accurately simulating network routing, specifically drilling into three options for extracting the routing information from your network: SNMP, SSH and HSRP or VRPP. Examining the Challenges of Accurately Simulating Network Routing Watch Lesson 8 In this lesson, Professor Wool examines the complex challenges of accurately simulating network routing, specifically drilling into three options for extracting the routing information from your network: SNMP, SSH and HSRP or VRPP. NAT Considerations When Managing Your Security Policy Watch Lesson 9 In this lesson, Professor Wool explains how you can create templates - using network objects - for different types of services and network access which are reused by many different servers in your data center. Using this technique will save you from writing new firewall rules each time you provision or change a server, reduce errors, and allow you to provision and expand your server estate more quickly. How to Structure Network Objects to Plan for Future Policy Growth Watch Lesson 10 In this lesson, Professor Wool examines the challenges of migrating business applications and physical data centers to a private cloud and offers tips to conduct these migrations without the risk of outages. Tips to Simplify Migrations to a Virtual Data Center Watch Lesson 11 In this lesson, Professor Wool provides the example of a virtualized private cloud which uses hypervisor technology to connect to the outside world via a firewall. If all worksloads within the private cloud share the same security requirements, this set up is adequate. But what happens if you want to run workloads with different security requirements within the cloud? Professor Wool explains the different options for filtering traffic within a private cloud, and discusses the challenges and solutions for managing them. Tips for Filtering Traffic within a Private Cloud Watch Lesson 12 In this lesson Professor Wool discusses ways to ensure that your security policy on your primary site and on your disaster recovery (DR) site are always sync. He presents multiple scenarios: where the DR and primary site use the exact same firewalls, where different vendor solutions or different models are used on the DR site, and where the IP address is or is not the same on the two sites. Managing Your Security Policy for Disaster Recovery Watch Lesson 13 In this lesson, Professor Wool highlights the challenges, benefits and trade-offs of utilizing zero-touch automation for security policy change management. He explains how, using conditional logic, its possible to significantly speed up security policy change management while maintaining control and ensuring accuracy throughout the process. Zero-Touch Change Management with Checks and Balances Watch Lesson 14 Many organizations have different types of firewalls from multiple vendors, which typically means there is no single source for naming and managing network objects. This ends up creating duplication, confusion, mistakes and network connectivity problems especially when a new change request is generated and you need to know which network object to refer to. In this lesson Profession Wool provides tips and best practices for how to synchronize network objects in a multi-vendor environment for both legacy scenarios, and greenfield scenarios. Synchronized Object Management in a Multi-Vendor Environment Watch Lesson 15 Many organizations have both a firewall management system as well as a CMDB, yet these systems do not communicate with each other and their data is not synchronized. This becomes a problem when making security policy change requests, and typically someone needs to manually translate the names used by in the firewall management system to the name in the CMDB, which is a slow and error-prone process, in order for the change request to work. In this lesson Professor Wool provides tips on how to use a network security policy management to coordinate between the two system, match the object names, and then automatically populate the change management process with the correct names and definitions. How to Synchronize Object Management with a CMDB Watch Lesson 16 Some companies use tools to automatically convert firewall rules from an old firewall, due to be retired, to a new firewall. In this lesson, Professor Wool explains why this process can be risky and provides some specific technical examples. He then presents a more realistic way to manage the firewall rule migration process that involves stages and checks and balances to ensure a smooth, secure transition to the new firewall that maintains secure connectivity. How to Take Control of a Firewall Migration Project Watch Lesson 17 PCI-DSS 3.2 regulation requirement 6.1 mandates that organizations establish a process for identifying security vulnerabilities on the servers that are within the scope of PCI. In this new lesson, Professor Wool explains how to address this requirement by presenting vulnerability data by both the servers and the by business processes that rely on each server. He discusses why this method is important and how it allows companies to achieve compliance while ensuring ongoing business operations. PCI – Linking Vulnerabilities to Business Applications Watch Lesson 18 Collaboration tools such as Slack provide a convenient way to have group discussions and complete collaborative business tasks. Now, these automated chatbots can be used for answering questions and handling tasks for development, IT and infosecurity teams. For example, enterprises can use chatbots to automate information-sharing across silos, such as between IT and application owners. So rather than having to call somebody and ask them “Is that system up? What happened to my security change request?” and so on, tracking helpdesk issues and the status of help requests can become much more accessible and responsive. Chatbots also make access to siloed resources more democratic and more widely available across the organization (subject, of course to the necessary access rights). In this video, Prof. Wool discusses how automated chatbots can be used to help a wide range of users for their security policy management tasks – thereby improving service to stakeholders and helping to accelerate security policy change processes across the enterprise. Sharing Network Security Information with the Wider IT Community With Team Collaboration Tools 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

AlgoSec Horizon Tour 2025 Coming to a city near you Connect. Explore. Secure Reserve your spot now Discover the future of hybrid security in a city-specific, invite-only experience featuring demos, customer stories, and exclusive insights into ACE and Horizon. 6 cities 2 weeks - Get onboard today Choose the city you want to join us in and register GB London Sep 9 NL UTRECHT Sep 10 DE Munich Sep 11 DK Copenhagen Sep 17 NO Oslo SEP 18 SE Stockholm Sep 23 Reserve your spot now What is Horizons platform? AlgoSec Horizon is the industry's first application-centric security management platform for the hybrid network environment. Gain deep visibility, automate security changes, prioritize risk, and ensure continuous compliance in your datacenter and multi-cloud network And ACE? AlgoSec Cloud Enterprise (ACE) is another core component of the AlgoSec Horizon platform, extending its application-centric security capabilities into cloud environments Why else to join? Expert Insights Engage with AlgoSec leaders and real customers for deep technical and strategic insights Product Innovation Experience live demos of Horizon and ACE in action, solving real-world challenges Unforgettable Experiences Enjoy curated venues and memorable moments — from unique experiences to delicious meals Reserve your spot now Where would you like to meet us? Select city* Select city Your personal details First name* Last name* Work email* Company* Short answer Job title country* Select country... Multi choice I‘m an AlgoSec customer I’m a channel partner I want to bring a guest By submitting this form, I accept AlgoSec's privacy policy Continue Thank you for registering!

2024 just started but cloud network security insights are already emerging. Amongst all the research and insights GigaOm’s comprehensive... Cloud Network Security Understanding the human-centered approach for cloud network security with GigaOm’s 2024 insights Adel Osta Dadan 2 min read Adel Osta Dadan Short bio about author here Lorem ipsum dolor sit amet consectetur. Vitae donec tincidunt elementum quam laoreet duis sit enim. Duis mattis velit sit leo diam. Tags Share this article 1/23/24 Published 2024 just started but cloud network security insights are already emerging. Amongst all the research and insights GigaOm’s comprehensive research emerges as a vital compass. More than just a collection of data and trends, it’s a beacon for us – the decision-makers and thought leaders – guiding us to navigate these challenges with a focus on the human element behind the technology. GigaOm showcased indicators to where the market is heading. Understanding multi-cloud complexity : GigaOm’s insights highlight the intricacies of multi-cloud environments. It’s about recognizing the human factor in these ecosystems – how these technologies affect our teams and processes, and ultimately, our business objectives. Redefining security boundaries : The shift to adaptive security boundaries, as noted by GigaOm, is a testament to our evolving work environments. This new perspective acknowledges the need for flexible security measures that resonate with our changing human interactions and work dynamics. The human impact of misconfigurations : Focusing on misconfiguration and anomaly detection goes beyond technical prowess. GigaOm’s emphasis here is about protecting our digital world from threats that carry significant human consequences, such as compromised personal data and the resulting erosion of trust. To learn more about cloud misconfigurations and risk check out our joint webinar with SANS . Leadership in a digitally transformed world Cultivating a Zero Trust culture : Implementing Zero Trust, as GigaOm advises, is more than a policy change. It’s about cultivating a mindset of continuous verification and trust within our organizations, reflecting the interconnected nature of our modern workspaces. Building relationships with vendors : GigaOm’s analysis of vendors reminds us that choosing a security partner is as much about forging a relationship that aligns with our organizational values as it is about technical compatibility. Security as a core organizational value : According to GigaOm, integrating security into our business strategy is paramount. It’s about making security an inherent part of our organizational ethos, not just a standalone strategy. The human stories behind vendors GigaOm’s insights into vendors reveal the visions and values driving these companies. This understanding helps us see them not merely as service providers but as partners sharing our journey toward a secure digital future. Embracing GigaOm’s vision: A collaborative path forward GigaOm’s research serves as more than just guidance; it’s a catalyst for collaborative discussions among us – leaders, innovators, and technologists. It challenges us to think beyond just the technical aspects and consider the human impacts of our cybersecurity decisions. Schedule a demo Related Articles Q1 at AlgoSec: What innovations and milestones defined our start to 2026? AlgoSec Reviews Mar 19, 2023 · 2 min read 2025 in review: What innovations and milestones defined AlgoSec’s transformative year in 2025? AlgoSec Reviews Mar 19, 2023 · 2 min read Navigating Compliance in the Cloud AlgoSec Cloud Mar 19, 2023 · 2 min read Speak to one of our experts Speak to one of our experts Work email* First name* Last name* Company* country* Select country... Short answer* By submitting this form, I accept AlgoSec's privacy policy Schedule a call

Avivi Siman-Tov, Director of Product Management at AlgoSec, discusses the benefits of network automation and takes us through a... Firewall Change Management Change automation: A step-by-step guide to network security policy change management Avivi Siman Tov 2 min read Avivi Siman Tov 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 10/21/21 Published Avivi Siman-Tov, Director of Product Management at AlgoSec, discusses the benefits of network automation and takes us through a step-by-step process to standardize change management In today’s fast-paced, data-driven environment, the only constant that businesses can bank on is change. For organizations to function and compete in the modern digital landscape, they need their data to be able to move freely and unobstructed through every branch of their business, unimpeded by security issues that require constant manual attention. The network is arguably the beating heart of an organization but keeping it ticking requires more maintenance than it once did, owing to constantly changing risk profiles and circumstances. That’s why a greater number of businesses are turning to change automation to bridge the gap between network alerts and the action that needs to be taken. Barriers to automation According to Gartner , organizations that can automate more than 70% of their network changes can reduce the number of outages by at least 50% and deliver services up to 50% faster. That’s because a lot of legacy solutions tend to take a reactive rather than proactive approach to dealing with security. There are multiple controls in place that simply don’t talk to each other. While most businesses get alerts from SIEM solutions and vulnerability scanners, responding to them turns into a full-time job, distracting your team from other important work they could be doing. Most organizations know that manual policy changes impact their productivity, but they’re afraid to take the leap to automation because of an ill-placed perception around security. Production environments in all organizations are maintained by different teams — for example, DevOps, maintenance, cloud security, IT, and more. Not all of these teams are educated to the same level in security matters, and some see it as a constraint that slows their work. This can lead to conflict between teams, which means that automation is not always welcome. Despite some resistance to change, enterprise-wide change automation makes it possible to transform network security policies without needing to reinvent the wheel or replace existing business processes. Automation and actionable intelligence are proven to enhance security and business agility without the stress often associated with misconfigurations caused by manual, ad-hoc processes. A typical network change workflow By elevating firewall change management from a manual, arduous task to a fully automated, zero-touch process, networks can become more agile and organizations far more adaptive. There are several steps that organizations need to take towards complete network security automation, from a simple change request through to implementation and validation. Let’s take a look at the most common steps in establishing automation for a simple change request. Step 1 – Request a network change Every change begins with a request. At this stage, you need to clarify who is asking for the amendment and why because sometimes the request is unnecessary or covered by an existing ruleset. Step 2 – Find relevant security devices Once this request is translated, the change automation platform will handle the request and implement the changes to hybrid networks. The administrator will be able to see which firewall and routing devices are involved and what impact the change will have. Step 3 – Plan change The change automation platform understands how to deal with different vendor-specific settings and how to implement the requests in a way that avoids creating any duplicates. Step 4 – Risk check The administrator will get a ‘ what if’ analysis, which checks the change for any risks. In this phase, the decision as to whether to allow the change and expose the network to the risk mentioned is in the hands of the network admin or security manager, depending on who is handling this phase. Step 5 – Push change to device Once planned changes are approved, the ‘magic’ happens. The change automation platform implements and pushes the changes to the desired devices automatically, either through APIs or directly to the device (CLI). This is a fully automated action that can be conducted on multiple devices, whether cloud-based or on-premises. The push can be done in a scheduled manner, in your maintenance window, or on-demand. Step 6 – Validate change At the end of each request, the solution will check that the request was successfully implemented across all devices. The solution also provides ongoing audits of the whole process, enabling easy checking of each stage. Step 7 – Documentation and logging Network security automation platforms can provide you with a full, automated audit trail. Documentation happens on the go, saving IT and security teams time and accelerating tedious network compliance management tasks. Put your trust in network automation While change management is complex stuff, the decision for your business is simple. It’s like the engine of an expensive car. Would you drive at high speeds if you didn’t have your brakes tested or a steering wheel to keep your course straight? Hopefully, the answer is no. With AlgoSec FireFlow , you can automate the security policy change process without introducing any element of risk, vulnerability, or compliance violation. AlgoSec FireFlow allows you to analyze every change before it is introduced, and validate successful changes as intended, all within your existing IT Service Management (ITSM) solutions . By putting your trust in us we can put you firmly in the driving seat with zero-touch change management and secure application deployment. For more information, or to arrange a demo , visit our website . Schedule a demo Related Articles Q1 at AlgoSec: What innovations and milestones defined our start to 2026? AlgoSec Reviews Mar 19, 2023 · 2 min read 2025 in review: What innovations and milestones defined AlgoSec’s transformative year in 2025? AlgoSec Reviews Mar 19, 2023 · 2 min read Navigating Compliance in the Cloud AlgoSec Cloud Mar 19, 2023 · 2 min read Speak to one of our experts Speak to one of our experts Work email* First name* Last name* Company* country* Select country... Short answer* By submitting this form, I accept AlgoSec's privacy policy Schedule a call

Robert Bigman is uniquely equipped to share actionable tips for hardening your network security against vulnerabilities Don’t miss this opportunity to learn the latest threats and how to handle them Webinars Measures that actually DO reduce your hacking risk Learn from the best how to defeat hackers and ransomware As incidents of ransomware attacks become more common, the time has come to learn from the best how to defeat hackers. Join us as Robert Bigman, the former CISO of the CIA, presents his webinar Measures that Actually do Reduce your Hacking Risk. Robert Bigman is uniquely equipped to share actionable tips for hardening your network security against vulnerabilities. Don’t miss this opportunity to learn the latest threats and how to handle them. April 20, 2022 Robert Bigman Consultant; Former CISO of the CIA Relevant resources Ensuring critical applications stay available and secure while shifting to remote work Keep Reading Reducing risk of ransomware attacks - back to basics Keep Reading Ransomware Attack: Best practices to help organizations proactively prevent, contain and 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

NOW AVAILABLE ON DEMAND Missed Operation Horizon?
Explore it on Your Schedule. The live event may be over, but the mission continues. Browse Zero Trust topics on demand, download the latest eBook, and schedule a demo to discuss your next steps with an AlgoSec expert. Schedule a demo Explore Operation Horizon videos Browse individual segments and watch the ones most relevant to your organization’s goals and challenges INTRO Zero Trust
overview Identity & App
Centric security Microsegmentation Cloud
Security Zero Trust
Implementation 04:58 min Zero Trust overview Traditional perimeter-based security models are no longer effective. Learn why Zero Trust has become essential and how organizations must adapt. “For decades now, security was built around the idea of inside vs. the outside. Today, that assumption is no longer valid.” Gavriel Sofer | CTO | 2Bsecure 5:18 min From Network-Centric to Identity & Application-Centric security Security must shift from static network boundaries to dynamic identity and application awareness. Discover how this transition enables stronger, more adaptive protection. “The network perimeter is gone. The system needs to verify who you are—not just where you are standing.” Dor Kviatkovski | Regional Sales Manager | Palo Alto Networks 7:23 min What is Microsegmentation
and why it matters Without visibility into application communications, enforcing security is nearly impossible. Learn how microsegmentation provides clarity, control, and reduced risk. “Many organizations are essentially operating in the dark with no clear view of the actual communications.” Zohar Furman | Senior Cyber Security Researcher | Akamai 8:19 min The cloud changes
Everything about security Hybrid and multi-cloud environments demand consistent, portable security policies. Explore how organizations can maintain control while enabling agility. “Your policies need to travel with the workloads across hybrid environments — aligning your cloud and on-prem.” Ravid Glam | Technical Account Manager | AWS 7:50 min Define Zero Trust
at the application level Move beyond theory and into execution. Learn how to define and enforce Zero Trust policies at the application level to reduce risk and simplify operations. “Zero Trust only works when everything moves as one. AlgoSec is the glue…” Avishai Wool | CTO and Co-Founder |AlgoSec Get the complete guide The business benefits of Application-Centric Zero Trust Dive deeper into the strategy and business impact of Zero Trust An application-centric approach to Zero Trust Reduce risk, improve visibility, and drive measurable outcomes Real-world use cases and expert insights Actionable steps to strengthen security and agility Download e-book Schedule a demo Want to speak with an expert? Schedule a demo to discuss your application security challenges and see how AlgoSec can help you simplify Zero Trust. Schedule a demo

Streamline Network Security Policy Changes, Minimize Errors, and Improve Efficiency with Effective Change Management Processes Improve Cybersecurity with Better Security Policy Change Management 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. Network security policy changes Information systems are not static – and neither is information security Security policy changes must accommodate the organization’s unique IT security life cycle Changing security policies comes with steep challenges Process security policy changes in minutes not days With AlgoSec you can Get the latest insights from the experts Use these six best practices to simplify compliance and risk mitigation with the AlgoSec White paper Learn how AlgoSec can help you pass PCI-DSS Audits and ensure Solution overview See how this customer improved compliance readiness and risk Case study Schedule time with one of our experts Work email* First name* Last name* Company* country* Select country... Short answer* By submitting this form, I accept AlgoSec's privacy policy Continue

Join us for Cisco Live Melbourne 2025 Thank you for you interest! Schedule a meeting with our experts at Booth G5 Date 10-13 November 2025 Booth G5 Location Melbourne Convention and Exhibition Centre Visit our Content Corner | Tue, Nov 11 | 3:40 – 4:00 PM Simplifying Security, Accelerating Business — The AlgoSec Way What’s in It for You • Simplified Security with less complexity and continuous compliance • Accelerated Business through faster delivery and change management • Reduced Risk by preventing misconfigurations and downtime • The AlgoSec Way: turning security into a business enabler, not a blocker. Register now Email First name* Last name* Company* country* Select country... Select Date* Select Date Select Time* Select Time By submitting this form I agree to receive relevant marketing material from AlgoSec, subject to its privacy policy Book time now Thanks for registering

As you may have heard already, the National Security Agency (NSA) and the Federal Bureau of Investigation (FBI) released a joint... Cloud Security Drovorub’s Ability to Conceal C2 Traffic And Its Implications For Docker Containers Rony Moshkovich 2 min read Rony Moshkovich Short bio about author here Lorem ipsum dolor sit amet consectetur. Vitae donec tincidunt elementum quam laoreet duis sit enim. Duis mattis velit sit leo diam. Tags Share this article 8/15/20 Published As you may have heard already, the National Security Agency (NSA) and the Federal Bureau of Investigation (FBI) released a joint Cybersecurity Advisory about previously undisclosed Russian malware called Drovorub. According to the report, the malware is designed for Linux systems as part of its cyber espionage operations. Drovorub is a Linux malware toolset that consists of an implant coupled with a kernel module rootkit, a file transfer and port forwarding tool, and a Command and Control (C2) server. The name Drovorub originates from the Russian language. It is a complex word that consists of 2 roots (not the full words): “drov” and “rub” . The “o” in between is used to join both roots together. The root “drov” forms a noun “drova” , which translates to “firewood” , or “wood” . The root “rub” /ˈruːb/ forms a verb “rubit” , which translates to “to fell” , or “to chop” . Hence, the original meaning of this word is indeed a “woodcutter” . What the report omits, however, is that apart from the classic interpretation, there is also slang. In the Russian computer slang, the word “drova” is widely used to denote “drivers” . The word “rubit” also has other meanings in Russian. It may mean to kill, to disable, to switch off. In the Russian slang, “rubit” also means to understand something very well, to be professional in a specific field. It resonates with the English word “sharp” – to be able to cut through the problem. Hence, we have 3 possible interpretations of ‘ Drovorub ‘: someone who chops wood – “дроворуб” someone who disables other kernel-mode drivers – “тот, кто отрубает / рубит драйвера” someone who understands kernel-mode drivers very well – “тот, кто (хорошо) рубит в драйверах” Given that Drovorub does not disable other drivers, the last interpretation could be the intended one. In that case, “Drovorub” could be a code name of the project or even someone’s nickname. Let’s put aside the intricacies of the Russian translations and get a closer look into the report. DISCLAIMER Before we dive into some of the Drovorub analysis aspects, we need to make clear that neither FBI nor NSA has shared any hashes or any samples of Drovorub. Without the samples, it’s impossible to conduct a full reverse engineering analysis of the malware. Netfilter Hiding According to the report, the Drovorub-kernel module registers a Netfilter hook. A network packet filter with a Netfilter hook ( NF_INET_LOCAL_IN and NF_INET_LOCAL_OUT ) is a common malware technique. It allows a backdoor to watch passively for certain magic packets or series of packets, to extract C2 traffic. What is interesting though, is that the driver also hooks the kernel’s nf_register_hook() function. The hook handler will register the original Netfilter hook, then un-register it, then re-register the kernel’s own Netfilter hook. According to the nf_register_hook() function in the Netfilter’s source , if two hooks have the same protocol family (e.g., PF_INET ), and the same hook identifier (e.g., NF_IP_INPUT ), the hook execution sequence is determined by priority. The hook list enumerator breaks at the position of an existing hook with a priority number elem->priority higher than the new hook’s priority number reg->priority : int nf_register_hook ( struct nf_hook_ops * reg) { struct nf_hook_ops * elem; int err; err = mutex_lock_interruptible( & nf_hook_mutex); if (err < 0 ) return err; list_for_each_entry(elem, & nf_hooks[reg -> pf][reg -> hooknum], list) { if (reg -> priority < elem -> priority) break ; } list_add_rcu( & reg -> list, elem -> list.prev); mutex_unlock( & nf_hook_mutex); ... return 0 ; } In that case, the new hook is inserted into the list, so that the higher-priority hook’s PREVIOUS link would point into the newly inserted hook. What happens if the new hook’s priority is also the same, such as NF_IP_PRI_FIRST – the maximum hook priority? In that case, the break condition will not be met, the list iterator list_for_each_entry will slide past the existing hook, and the new hook will be inserted after it as if the new hook’s priority was higher. By re-inserting its Netfilter hook in the hook handler of the nf_register_hook() function, the driver makes sure the Drovorub’s Netfilter hook will beat any other registered hook at the same hook number and with the same (maximum) priority. If the intercepted TCP packet does not belong to the hidden TCP connection, or if it’s destined to or originates from another process, hidden by Drovorub’s kernel-mode driver, the hook will return 5 ( NF_STOP ). Doing so will prevent other hooks from being called to process the same packet. Security Implications For Docker Containers Given that Drovorub toolset targets Linux and contains a port forwarding tool to route network traffic to other hosts on the compromised network, it would not be entirely unreasonable to assume that this toolset was detected in a client’s cloud infrastructure. According to Gartner’s prediction , in just two years, more than 75% of global organizations will be running cloud-native containerized applications in production, up from less than 30% today. Would the Drovorub toolset survive, if the client’s cloud infrastructure was running containerized applications? Would that facilitate the attack or would it disrupt it? Would it make the breach stealthier? To answer these questions, we have tested a different malicious toolset, CloudSnooper, reported earlier this year by Sophos. Just like Drovorub, CloudSnooper’s kernel-mode driver also relies on a Netfilter hook ( NF_INET_LOCAL_IN and NF_INET_LOCAL_OUT ) to extract C2 traffic from the intercepted TCP packets. As seen in the FBI/NSA report, the Volatility framework was used to carve the Drovorub kernel module out of the host, running CentOS. In our little lab experiment, let’s also use CentOS host. To build a new Docker container image, let’s construct the following Dockerfile: FROM scratch ADD centos-7.4.1708-docker.tar.xz / ADD rootkit.ko / CMD [“/bin/bash”] The new image, built from scratch, will have the CentOS 7.4 installed. The kernel-mode rootkit will be added to its root directory. Let’s build an image from our Dockerfile, and call it ‘test’: [root@localhost 1]# docker build . -t test Sending build context to Docker daemon 43.6MB Step 1/4 : FROM scratch —> Step 2/4 : ADD centos-7.4.1708-docker.tar.xz / —> 0c3c322f2e28 Step 3/4 : ADD rootkit.ko / —> 5aaa26212769 Step 4/4 : CMD [“/bin/bash”] —> Running in 8e34940342a2 Removing intermediate container 8e34940342a2 —> 575e3875cdab Successfully built 575e3875cdab Successfully tagged test:latest Next, let’s execute our image interactively (with pseudo-TTY and STDIN ): docker run -it test The executed image will be waiting for our commands: [root@8921e4c7d45e /]# Next, let’s try to load the malicious kernel module: [root@8921e4c7d45e /]# insmod rootkit.ko The output of this command is: insmod: ERROR: could not insert module rootkit.ko: Operation not permitted The reason why it failed is that by default, Docker containers are ‘unprivileged’. Loading a kernel module from a docker container requires a special privilege that allows it doing so. Let’s repeat our experiment. This time, let’s execute our image either in a fully privileged mode or by enabling only one capability – a capability to load and unload kernel modules ( SYS_MODULE ). docker run -it –privileged test or docker run -it –cap-add SYS_MODULE test Let’s load our driver again: [root@547451b8bf87 /]# insmod rootkit.ko This time, the command is executed silently. Running lsmod command allows us to enlist the driver and to prove it was loaded just fine. A little magic here is to quit the docker container and then delete its image: docker rmi -f test Next, let’s execute lsmod again, only this time on the host. The output produced by lsmod will confirm the rootkit module is loaded on the host even after the container image is fully unloaded from memory and deleted! Let’s see what ports are open on the host: [root@localhost 1]# netstat -tulpn Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 1044/sshd With the SSH server running on port 22 , let’s send a C2 ‘ping’ command to the rootkit over port 22 : [root@localhost 1]# python client.py 127.0.0.1 22 8080 rrootkit-negotiation: hello The ‘hello’ response from the rootkit proves it’s fully operational. The Netfilter hook detects a command concealed in a TCP packet transferred over port 22 , even though the host runs SSH server on port 22 . How was it possible that a rootkit loaded from a docker container ended up loaded on the host? The answer is simple: a docker container is not a virtual machine. Despite the namespace and ‘control groups’ isolation, it still relies on the same kernel as the host. Therefore, a kernel-mode rootkit loaded from inside a Docker container instantly compromises the host, thus allowing the attackers to compromise other containers that reside on the same host. It is true that by default, a Docker container is ‘unprivileged’ and hence, may not load kernel-mode drivers. However, if a host is compromised, or if a trojanized container image detects the presence of the SYS_MODULE capability (as required by many legitimate Docker containers), loading a kernel-mode rootkit on a host from inside a container becomes a trivial task. Detecting the SYS_MODULE capability ( cap_sys_module ) from inside the container: [root@80402f9c2e4c /]# capsh –print Current: = cap_chown, … cap_sys_module, … Conclusion This post is drawing a parallel between the recently reported Drovorub rootkit and CloudSnooper, a rootkit reported earlier this year. Allegedly built by different teams, both of these Linux rootkits have one mechanism in common: a Netfilter hook ( NF_INET_LOCAL_IN and NF_INET_LOCAL_OUT ) and a toolset that enables tunneling of the traffic to other hosts within the same compromised cloud infrastructure. We are still hunting for the hashes and samples of Drovorub. Unfortunately, the YARA rules published by FBI/NSA cause False Positives. For example, the “Rule to detect Drovorub-server, Drovorub-agent, and Drovorub-client binaries based on unique strings and strings indicating statically linked libraries” enlists the following strings: “Poco” “Json” “OpenSSL” “clientid” “—–BEGIN” “—–END” “tunnel” The string “Poco” comes from the POCO C++ Libraries that are used for over 15 years. It is w-a-a-a-a-y too generic, even in combination with other generic strings. As a result, all these strings, along with the ELF header and a file size between 1MB and 10MB, produce a false hit on legitimate ARM libraries, such as a library used for GPS navigation on Android devices: f058ebb581f22882290b27725df94bb302b89504 56c36bfd4bbb1e3084e8e87657f02dbc4ba87755 Nevertheless, based on the information available today, our interest is naturally drawn to the security implications of these Linux rootkits for the Docker containers. Regardless of what security mechanisms may have been compromised, Docker containers contribute an additional attack surface, another opportunity for the attackers to compromise the hosts and other containers within the same organization. The scenario outlined in this post is purely hypothetical. There is no evidence that supports that Drovorub may have affected any containers. However, an increase in volume and sophistication of attacks against Linux-based cloud-native production environments, coupled with the increased proliferation of containers, suggests that such a scenario may, in fact, be plausible. Schedule a demo Related Articles Q1 at AlgoSec: What innovations and milestones defined our start to 2026? AlgoSec Reviews Mar 19, 2023 · 2 min read 2025 in review: What innovations and milestones defined AlgoSec’s transformative year in 2025? AlgoSec Reviews Mar 19, 2023 · 2 min read Navigating Compliance in the Cloud AlgoSec Cloud Mar 19, 2023 · 2 min read Speak to one of our experts Speak to one of our experts Work email* First name* Last name* Company* country* Select country... Short answer* By submitting this form, I accept AlgoSec's privacy policy Schedule a call

Your network is a maze, Create a path of awareness In today’s hybrid environments, scattered visibility and reactive policies create constant noise. This whitepaper introduces an application-centric mindful approach that anchors security in the real needs of your business applications. It reduces risk and creates space for calm, confident compliance. You’ll learn how to: See clearly: Visualize application connectivity and eliminate blind spots. Respond with purpose: Prioritize risks based on context, focusing on what matters most. Stay aligned: Automate compliance and streamline change management. Move with intention: Shift from chaos to clarity in managing your hybrid network. Get the report Work email* First name* Last name* Company* country* Select country... Short answer* By submitting this form, I accept AlgoSec's privacy policy Continue Highlights from the 2025 State
of Network Security Report: Visibility gaps as a driver for the shift in security management Managing risk in relation to manual processes Continued importance of firewalls in the cloud Adoption of Zero Trust strategy Changes in growth of SD-WAN and SASE The role of AI in security management