Search results

AlgoSec and Cisco Catalyst SD-WAN Solution Brief 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

Anat Kleinmann, AlgoSec Sr. Product Manager and IaC expert, discusses how incorporating Infrastructure-as-Code into DevSecOps can allow... Risk Management and Vulnerabilities Bridging the DevSecOps Application Connectivity Disconnect via IaC Anat Kleinmann 2 min read Anat Kleinmann 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/7/22 Published Anat Kleinmann, AlgoSec Sr. Product Manager and IaC expert, discusses how incorporating Infrastructure-as-Code into DevSecOps can allow teams to take a preventive approach to secure application connectivity . With customer demands changing at breakneck speed, organizations need to be agile to win in their digital markets. This requires fast and frequent application deployments, forcing DevOps teams to streamline their software development processes. However, without the right security tools placed in the early phase of the CI/CD pipeline, these processes can be counterproductive leading to costly human errors and prolonged application deployment backups. This is why organizations need to find the right preventive security approach and explore achieving this through Infrastructure-as-Code. Understanding Infrastructure as Code – what does it actually mean? Infrastructure-as-Code (Iac) is a software development method that describes the complete environment in which the software runs. It contains information about the hardware, networks, and software that are needed to run the application. IAC is also referred to as declarative provisioning or automated provisioning. In other words, IAC enables security teams to create an automated and repeatable process to build out an entire environment. This is helpful for eliminating human errors that can be associated with manual configuration. The purpose of IaC is to enable developers or operations teams to automatically manage, monitor and provision resources, rather than manually configure discrete hardware devices and operating systems. What does IaC mean in the context of running applications in a cloud environment When using IaC, network configuration files can contain your applications connectivity infrastructure connectivity specifications changes, which mkes it easier to edit, review and distribute. It also ensures that you provision the same environment every time and minimizes the downtime that can occur due to security breaches. Using Infrastructure as code (IaC) helps you to avoid undocumented, ad-hoc configuration changes and allows you to enforce security policies in advance before making the changes in your network. Top 5 challenges when not embracing a preventive security approach Counterintuitive communication channel – When reviewing the code manually, DevOps needs to provide access to a security manager to review it and rely on the security manager for feedback. This can create a lot of unnecessary back and forth communication between the teams which can be a highly counterintuitive process. Mismanagement of DevOps resources – Developers need to work on multiple platforms due to the nature of their work. This may include developing the code in one platform, checking the code in another, testing the code in a third platform and reviewing requests in a fourth platform. When this happens, developers often will not be alerted of any network risk or non-compliance issue as defined by the organization. Mismanagement of SecOps resources – At the same time, network security managers are also bombarded with security review requests and tasks. Yet, they are expected to be agile, which is impossible in case of manual risk detection. Inefficient workflow – Sometimes risk analysis process is skipped and only reviewed at the end of the CI/CD pipeline, which prolongs the delivery of the application. Time consuming review process – The risk analysis review itself can sometimes take more than 30 minutes long which can create unnecessary and costly bottlenecking, leading to missed rollout deadlines of critical applications Why it’s important to place security early in the development cycle Infrastructure-as-code (IaC) is a crucial part of DevSecOps practices. The current trend is based on the principle of shift-left, which places security early in the development cycle. This allows organizations to take a proactive, preventive approach rather than a reactive one. This approach solves the problem of developers leaving security checks and testing for the later stages of a project often as it nears completion and deployment. It is critical to take a proactive approach since late-stage security checks lead to two critical problems. Security flaws can go undetected and make it into the released software, and security issues detected at the end of the software development lifecycle demand considerably more time, resources and money to remediate than those identified early on. The Power of IaC Connectivity Risk Analysis and Key Benefits IaC connectivity risk analysis provides automatic and proactive connectivity risk analysis, enabling a frictionless workflow for DevOps with continuous customized risk analysis and remediation managed and controlled by the security managers. IaC Connectivity Risk Analysis enables organizations to use a single source of truth for managing the lifecycle of their applications. Furthermore, security engineers can use IaC to automate the design, deployment, and management of virtual assets across a hybrid cloud environment. With automated security tests, engineers can also continuously test their infrastructure for security issues early in the development phase. Key benefits Deliver business applications into production faster and more securely Enable a frictionless workflow with continuous risk analysis and remediation Reduce connectivity risks earlier in the CI/CD process Customizable risk policy to surface only the most critical risks The Takeaway Don’t get bogged down by security and compliance. When taking a preventive approach using a connectivity risk analysis via IaC, you can increase the speed of deployment, reduce misconfiguration and compliance errors, improve DevOps – SecOps relationship and lower costs Next Steps Let AlgoSec’s IaC Connectivity Risk Analysis can help you take a proactive, preventive security approach to get DevOps’ workflow early in the game, automatically identifying connectivity risks and providing ways to remediate them. Watch this video or visit us at GitHub to learn how. 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

Oren Amiram, Director of Product at AlgoSec, explains why misconfigurations continue to plague public cloud network services and how... Firewall Change Management Why misconfigurations continue to plague public cloud network services and how to avoid them? Oren Amiram 2 min read Oren Amiram Short bio about author here Lorem ipsum dolor sit amet consectetur. Vitae donec tincidunt elementum quam laoreet duis sit enim. Duis mattis velit sit leo diam. Tags Share this article 3/18/24 Published Oren Amiram, Director of Product at AlgoSec, explains why misconfigurations continue to plague public cloud network services and how organizations can address these shortfalls with AlgoSec Cloud. Cloud security as a strategy is constantly evolving to meet the needs of organizations for scale, agility, and security. If your organization is weighing the merits of the use of public cloud versus private cloud, here are a few facts to keep in mind. Data shows that the public cloud is the preferred choice. Here’s what’s driving it. Public cloud security has become more ubiquitous thanks to IaaS platforms such as Amazon Web Services (AWS), Google Cloud Platform (GCP) and Microsoft Azure. According to Gartner, worldwide end-user spending on public cloud services is expected to grow by 20.4% in 2022 to a total of $494.7 billion, up from $410.9 billion in 2021 It is easy to see why public clouds are so appealing. Unlike private clouds, public cloud platform solutions allow organizations to provide business applications fast and reduce the costs associated with purchasing, managing, and maintaining on-premise hardware and application infrastructure. Furthermore, public clouds enable businesses to set up the required infrastructure much faster than on-premise and provide unmatched scalability, as well as extra security capabilities. Public cloud benefits are abundantly clear, but there’s more to this than meets the eye. As robust as a public cloud platform, there are also challenges that organizations need to overcome. According to a recent global survey on public cloud security risks, just under a third of organizations (31%) were not confident or only slightly confident about their ability to protect sensitive data in a cloud environment and another 44 percent reported they were only moderately confident. Another survey focused on top threats to cloud computing showed that misconfiguration of the cloud platform was one of the top three concerns among respondents. This challenge is even more amplified as evidenced in a separate survey, with nearly 76% of respondents stating their organization uses two or more different public cloud providers. The findings suggest that security teams often have to manage multiple native security and management consoles to enforce security and compliance across different environments. How profound is the impact of misconfigurations on your network? All it takes is a single hole It is no surprise that enterprise IT teams find it difficult to keep their applications secure. Migration of applications to public cloud platforms involves many potential pitfalls. Misconfiguration errors can occur at many different points on the network as part of the migration process, especially when moving from traditional firewalls to cloud security controls. Ongoing management of applications and workflows within the public cloud presents a unique challenge. Many organizations have multiple teams using different methods to manage the applications and the security controls that should protect them, such as Ansible, Chef and Terraform, in addition to manual changes. Even if you are using a single public cloud platform, you still need to manage multiple security controls protecting a multitude of applications. Organizations may have hundreds of separate public cloud accounts, each with multiple VPCs, spread across different regions. These VPCs are protected by multi-layered security controls, from Cloud Infrastructure, such as security groups and network ACLs, cloud-native advanced network firewalls, to Security Products offered by ISVs, such as NG Firewalls. It is easy to see why misconfiguration occurs if IT teams attempt to take on this complex, tedious and labor-intensive process themselves. A single mistake can cause outages, compliance violations and create holes in your security perimeter. Digital Shadows detected over 2.3 billion files that had been Misconfigured storage services have exposed more than 30 billion records and contributed to more than 200 breaches over the past two years. It is safe to assume that as organizations seek to optimize their public cloud deployment, cloud breaches will increase in velocity and scale. According to a recent Accurics report, misconfigured cloud storage services were commonplace in 93% of hundreds of public cloud deployments analyzed. Avoiding misconfiguration risks is easier said than done, but there’s a solution Given that organizations are so concerned about misconfiguration risks, what steps can they take to avoid making them? There are two basic principles that should be followed: Ensuring that only authorized, qualified personnel can make network or security control changes Following a clearly defined change process, with mandatory review and approval for each stage. It’s also important to keep in mind that errors are still likely to occur even while you’re still carrying out your processes manually. Luckily, there is an easy solution – hybrid network-aware automation. This solution enables you to employ network change automation, eliminates guesswork and error-prone manual input, while also simplifying large-scale, complex application migration projects and security change management. Is there a much more holistic solution? Yes, meet AlgoSec AlgoSec’s cloud offering seamlessly integrates with all leading brands of cloud security controls, firewalls (including NGFWs deployed in the cloud), routers, and load balancers, to deliver unified security policy management. With the AlgoSec Security Management Solution, users benefit from holistic management and automation spanning on-premise, SDN and public cloud. AlgoSec cloud offering, including CloudFlow, allows organizations to seamlessly manage security control layers across the hybrid network in three key areas: Visibility across your hybrid network With our cloud offering, you can obtain a full network map of your entire hybrid network security estate, as well as identify risks and correlate them to the assets they impact. You can also achieve instant visibility of cloud assets and security controls, pinpointing and troubleshooting application and network connectivity issues resulting from security policies. Change management Organizations can leverage a uniformed network model and change-management framework that covers the hybrid and multi-cloud environment, with an automated policy push for “zero-touch” automation. You can securely migrate workloads from on-prem to the public cloud and discover the power of CloudFlow’s central policy management, allowing you to orchestrate multiple similar security controls in a single policy. Cloud-centric risk analysis and remediation You can proactively detect misconfigurations to protect cloud assets, including cloud instances, databases and serverless functions. Also, you can easily identify risky security policy rules, the assets they expose and whether they are in use. You can also remediate risk, including cleaning up bloated and risky policies and enjoy audit-ready compliance reporting, including vast support for diverse regulations. Find out more about AlgoSec cloud offering or start your journey through AlgoSec’s hybrid cloud 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

Cloud-native organizations need an efficient and automated way to identify the security risks across their cloud infrastructure. Sergei... Cloud Security CSPM essentials – what you need to know? 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 11/24/22 Published Cloud-native organizations need an efficient and automated way to identify the security risks across their cloud infrastructure. Sergei Shevchenko, Prevasio’s Co-Founder & CTO breaks down the essence of a CSPM and explains how CSPM platforms enable organizations to improve their cloud security posture and prevent future attacks on their cloud workloads and applications. In 2019, Gartner recommended that enterprise security and risk management leaders should invest in CSPM tools to “proactively and reactively identify and remediate these risks”. By “these”, Gartner meant the risks of successful cyberattacks and data breaches due to “misconfiguration, mismanagement, and mistakes” in the cloud. So how can you detect these intruders now and prevent them from entering your cloud environment in future? Cloud Security Posture Management is one highly effective way but is often misunderstood. Cloud Security: A real-world analogy There are many solid reasons for organizations to move to the cloud. Migrating from a legacy, on-premises infrastructure to a cloud-native infrastructure can lower IT costs and help make teams more agile. Moreover, cloud environments are more flexible and scalable than on-prem environments, which helps to enhance business resilience and prepares the organization for long-term opportunities and challenges. That said, if your production environment is in the cloud, it is also prone to misconfiguration errors, which opens the firm to all kinds of security threats and risks. Think of this environment as a building whose physical security is your chief concern. If there are gaps in this security, for example, a window that doesn’t close all the way or a lock that doesn’t work properly, you will try to fix them on priority in order to prevent unauthorized or malicious actors from accessing the building. But since this building is in the cloud, many older security mechanisms will not work for you. Thus, simply covering a hypothetical window or installing an additional hypothetical lock cannot guarantee that an intruder won’t ever enter your cloud environment. This intruder, who may be a competitor, enemy spy agency, hacktivist, or anyone with nefarious intentions, may try to access your business-critical services or sensitive data. They may also try to persist inside your environment for weeks or months in order to maintain access to your cloud systems or applications. Old-fashioned security measures cannot keep these bad guys out. They also cannot prevent malicious outsiders or worse, insiders from cryptojacking your cloud resources and causing performance problems in your production environment. What a CSPM is The main purpose of a CSPM is to help organizations minimize risk by providing cloud security automation, ensuring multi-cloud environments remain secure as they grow in scale and complexity. But, as organizations reach scale and add more complexity to their multi- cloud cloud environment, how can CSPMs help companies minimize such risks and better protect their cloud environments? Think of a CSPM as a building inspector who visits the building regularly (say, every day, or several times a day) to inspect its doors, windows, and locks. He may also identify weaknesses in these elements and produce a report detailing the gaps. The best, most experienced inspectors will also provide recommendations on how you can resolve these security issues in the fastest possible time. Similar to the role of a building inspector, CSPM provides organizations with the tools they need to secure your multi-cloud environment efficiently in a way that scales more readily than manual processes as your cloud deployments grow. Here are some CSPM key benefits: Efficient early detection: A CSPM tool allows you to automatically and continuously monitor your cloud environment. It will scan your cloud production environment to detect misconfiguration errors, raise alerts, and even predict where these errors may appear next. Responsive risk remediation: With a CSPM in your cloud security stack, you can also automatically remediate security risks and hidden threats, thus shortening remediation timelines and protecting your cloud environment from threat actors. Consistent compliance monitoring: CSPMs also support automated compliance monitoring, meaning they continuously review your environment for adherence to compliance policies. If they detect drift (non-compliance), appropriate corrective actions will be initiated automatically. What a CSPM is not Using the inspector analogy, it’s important to keep in mind that a CSPM can only act as an observer, not a doer. Thus, it will only assess the building’s security environment and call out its weakness. It won’t actually make any changes himself, say, by doing intrusive testing. Even so, a CSPM can help you prevent 80% of misconfiguration-related intrusions into your cloud environment. What about the remaining 20%? For this, you need a CSPM that offers something container scanning. Why you need an agentless CSPM across your multi-cloud environment If your network is spread over a multi-cloud environment, an agentless CSPM solution should be your optimal solution. Here are three main reasons in support of this claim: 1. Closing misconfiguration gaps: It is especially applicable if you’re looking to eliminate misconfigurations across all your cloud accounts, services, and assets. 2. Ensuring continuous compliance: It also detects compliance problems related to three important standards: HIPAA, PCI DSS, and CIS. All three are strict standards with very specific requirements for security and data privacy. In addition, it can detect compliance drift from the perspectives of all three standards, thus giving you the peace of mind that your multi-cloud environment remains consistently compliant. 3. Comprehensive container scanning: An agentless CSPM can scan container environments to uncover hidden backdoors. Through dynamic behavior analyses, it can detect new threats and supply chain attack risks in cloud containers. It also performs container security static analyses to detect vulnerabilities and malware, thus providing a deep cloud scan – that too in just a few minutes. Why Prevasio is your ultimate agentless CSPM solution Multipurpose: Prevasio combines the power of a traditional CSPM with regular vulnerability assessments and anti-malware scans for your cloud environment and containers. It also provides a prioritized risk list according to CIS benchmarks, so you can focus on the most critical risks and act quickly to adequately protect your most valuable cloud assets. User friendly: Prevasio’s CSPM is easy to use and easier still to set up. You can connect your AWS account to Prevasio in just 7 mouse clicks and 30 seconds. Then start scanning your cloud environment immediately to uncover misconfigurations, vulnerabilities, or malware. Built for scale: Prevasio’s CSPM is the only solution that can scan cloud containers and provide more comprehensive cloud security configuration management with vulnerability and malware scans. 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

A quarter-by-quarter review of AlgoSec’s 2025 covering key product launches like Horizon, our latest research on zero trust and convergence, customer milestones, and the industry recognition that defined our year. AlgoSec Reviews 2025 in review: What innovations and milestones defined AlgoSec’s transformative year in 2025? Adel Osta Dadan 2 min read Adel Osta Dadan Short bio about author here Lorem ipsum dolor sit amet consectetur. Vitae donec tincidunt elementum quam laoreet duis sit enim. Duis mattis velit sit leo diam. Tags Share this article 12/18/25 Published As we close out 2025, I find myself reflecting on what has been an extraordinary journey for AlgoSec. This year was marked by breakthrough innovations, significant industry recognition, and an unwavering commitment to our vision of secure application connectivity. From launching game-changing solutions to earning accolades on the global stage, 2025 challenged us to push boundaries – and we rose to the occasion with confidence and purpose. Every challenge met, every milestone achieved, has reinforced our resolve to lead in network security policy management across hybrid cloud environments. The story of AlgoSec in 2025 is one of innovation validated by the industry and, most importantly, by the trust of our customers. In this featured year-end review, I’ll walk through AlgoSec’s 2025 journey quarter by quarter. It’s a personal narrative from my vantage point as someone fortunate enough to help shape our story. The tone is proud and forward-looking because the accomplishments of this year have set the stage for an even more ambitious 2026. So let’s dive in, quarter by quarter, into how 2025 unfolded for AlgoSec – a year of solidifying leadership, fostering innovation, and securing connectivity for enterprises worldwide. Q1 – Launching a new horizon in hybrid cloud security The first quarter of 2025 was all about bold beginnings. We started the year by challenging the status quo in hybrid network security and laying the groundwork for everything to follow. Launch of the AlgoSec Horizon platform: In February, we unveiled AlgoSec Horizon , our most advanced application-centric security management platform for converging cloud and on-premise environments. This wasn’t just a product launch – it was a statement of direction. AlgoSec Horizon is the industry’s first platform to unify security policy automation across hybrid networks, giving teams a single pane of glass for both cloud and data center connectivity. By applying AI-driven visibility and risk mitigation, Horizon allows security teams to consistently manage application connectivity and policies across any environment. “Today’s networks are 100x more complex... requiring organizations to unify security operations, automate policies and enhance visibility across infrastructures,” as our VP of Product Eran Shiff noted at launch. With Horizon, our customers gained full visibility into their hybrid-cloud network and the power to remediate risks without slowing down the business. We even showcased Horizon live at Cisco Live 2025 in Amsterdam, letting attendees see firsthand how it simplifies hybrid cloud security. This Q1 milestone set the tone for the year – proving that we don’t just adapt to industry shifts, we lead them. Continuing analyst recognition and thought leadership: Building on momentum from the previous year, we carried forward strong validation from industry analysts. AlgoSec entered 2025 still highlighted as a Market Outperformer in GigaOm’s recent Radar Report for Cloud Network Security. In that report, analyst Andrew Green praised our core strength: “AlgoSec automates application connectivity and security policy across the hybrid network estate including public cloud, private cloud, containers, and on-premises networks.” Such independent insight validated our unique, application-centric approach. Internally, these early recognitions energized our teams. We doubled down on R&D and prepared to share our expertise more broadly – including wrapping up work on our annual research report. Q1’s focus on innovation and expert validation paved the way for the accomplishments that followed in subsequent quarters. Q2 – Thought leadership and industry accolades on the global stage If Q1 was about innovation, Q2 was about validation. In the second quarter, AlgoSec stepped onto the global stage at RSAC 2025 and emerged with both influential research and prestigious awards. It was a period where our thought leadership in secure connectivity met with resounding industry recognition. State of network security report 2025: In April, we released our annual State of Network Security Report , a comprehensive vendor-agnostic study of emerging trends and challenges in network security. This report quickly became a cornerstone of our thought leadership. It revealed how businesses are prioritizing multi-cloud strategies and zero-trust architecture in unprecedented ways. For instance, zero-trust adoption reached an all-time high – 56% of organizations reported they had fully or partially implemented zero-trust by 2025. We also highlighted that multi-cloud environments are now the norm, with Azure rising to become the most widely used cloud platform among respondents. Perhaps most telling was the finding that automating application connectivity ranked as the top priority for minimizing risk and downtime [9] . These insights underscored a message we’ve championed for years – that security can and should be an enabler of business agility. By shining a light on gaps in visibility and the need for policy automation, our Q2 research reinforced AlgoSec’s role as a thought leader in secure application connectivity. The report’s influence was evident in conversations at industry events and in how customers approached their network security strategy. Awards at RSAC 2025 – best security company and more: The highlight of Q2 came during the RSA Conference in late April, when AlgoSec earned two major industry accolades in one week. SC Media honored AlgoSec with the 2025 SC Award for Best Security Company, a recognition of our impact and innovation in cybersecurity. At the same time, Cyber Defense Magazine announced us as a winner of a 2025 Global InfoSec Award for Best Service – Cybersecurity Company [11] . Securing these prestigious awards simultaneously was a proud and humbling moment. It marked a significant milestone for our team as we continue to gain momentum across the global enterprise market. These accomplishments also validated our mission to deliver secure, seamless application connectivity across hybrid environments. “We’re honored to be recognized for empowering our customers to move faster and stay secure,” an AlgoSec spokesperson said, when discussing what the SC Award means to us. Indeed, being named Best Security Company came on the heels of some impressive company growth metrics – over 2,200 organizations now trust AlgoSec for their security policy management needs, and we saw 14% customer growth over the past year. The SC Award judges also noted that we command roughly 32% of the security policy management market share , highlighting AlgoSec’s leadership in this space. For me personally, seeing our work celebrated at RSAC 2025 was exhilarating. It wasn’t just about trophies; it was about validation from the community that the path we chose – focusing on application-centric, hybrid-cloud security – is the right one. Q2 ended with our trophy cabinet a bit fuller and our resolve stronger than ever to keep raising the bar. Q3 – Accelerating growth and fostering community The third quarter saw our innovations bear fruit in the market and our community initiatives take center stage. Coming out of the big wins of Q2, we maintained that momentum through the summer by executing on our strategies and engaging deeply with customers and partners. Q3 was about scaling up – both in terms of business impact and thought leadership outreach. Surging adoption and business growth: By mid-year, the impact of our new platform and solutions was clear in the numbers . In fact, we recorded a 36% year-over-year increase in new annual recurring revenue (ARR) in the first half of 2025 , driven largely by strong adoption of the AlgoSec Horizon platform. Our existing customers stayed with us as well – we maintained a gross dollar retention rate above 90%, a metric that speaks to the tangible value organizations are getting from our products. One anecdote that sticks with me is a story from a major U.S. financial institution: after deploying Horizon, they discovered 1,800 previously unknown applications and their connectivity requirements within the first two weeks . That kind of visibility – uncovering what was once shadow IT – is a game-changer for risk reduction. It proved that our focus on hybrid cloud security and intelligent automation is solving real problems. Equally rewarding was the feedback from customers. By Q3, AlgoSec was sustaining an average rating of 4.5 stars on Gartner Peer Insights , with users praising our platform’s depth and ease of use. We’ve also consistently ranked at the top of our category on peer review sites like G2 and PeerSpot, reflecting the positive outcomes our users are achieving . This convergence of market growth and customer satisfaction in Q3 affirmed that our application-centric approach is resonating strongly. Extending thought leadership through strategic research: Our growth in Q3 wasn’t just reflected in numbers—it also showed in how we’re shaping the security conversation. One standout was the publication of the Security Convergence eBook , developed in partnership with ESG. This research-backed guide addressed the operational and strategic challenges of aligning application, network, and cloud security. It offered actionable insights for enterprises navigating the intersection of security domains, a challenge we consistently hear about from our customers. The eBook resonated with CISOs and security leaders tasked with unifying fragmented processes under growing compliance and performance pressures. It reaffirmed AlgoSec’s unique position—not just as a solution provider, but as a partner helping drive clarity and convergence in the face of growing complexity. Community engagement and knowledge sharing : Even as we grew, we never lost sight of the importance of community and education. In September, we launched the AlgoSec Horizon Tour , a roadshow of interactive sessions across EMEA and the U.S. aimed at sharing best practices in secure application connectivity. These workshops gave enterprise security teams a hands-on look at Horizon’s capabilities and provided a forum for us to hear feedback directly from users. The tour culminated in our annual AlgoSummit 2025 – a virtual conference we hosted on September 30th that brought together customers, partners, and industry experts. If I had to choose a proud moment from Q3, AlgoSummit 2025 would be high on the list. We facilitated deep-dive discussions on zero trust architecture , cloud security, and the future of network policy automation. It was inspiring to see our community openly exchange ideas and solutions. This summit wasn’t just a company event; it felt like an industry think-tank. It reinforced AlgoSec’s role as a trusted advisor in the field of network security, not just a product vendor. By the end of Q3, we had strengthened the bonds with our user community and showcased that as networks evolve, we’re evolving right alongside our customers – providing guidance, platform innovations, and an open ear to their needs. Recognition of customer success: On a more personal note, Q3 also brought moments that reminded us why we do what we do. I recall one customer review that particularly struck me, where a network security manager described how AlgoSec became indispensable as their organization embraced zero trust. “As we aspire to achieve zero-trust… we need tools like AlgoSec to assist us in the journey because most application owners do not know what access is needed. This tool helps them learn what needs to be implemented to reduce the attack surface,” he noted. Hearing directly from customers about how we’re helping them reduce risk and implement zero trust principles is incredibly motivating. It underscores that behind the growth statistics are real organizations becoming safer and more agile, powered by our solutions. This customer-centric ethos carried us through Q3 and into the final stretch of the year. Q4 – Culminating achievements and setting the stage for what’s next As the year drew to a close, AlgoSec showed no signs of slowing down. In fact, Q4 was about finishing strong and preparing for the future. We used the final quarter to expand our solution capabilities, help customers navigate new security paradigms, and celebrate the capstone of several achievements. It’s been a period of tying up 2025’s narrative threads and pointing our compass toward 2026. Expanding zero-trust and cloud security initiatives: In Q4, we doubled down on helping customers realize Zero Trust Architecture across their increasingly complex environments. Building on the micro-segmentation and application dependency mapping capabilities of our platform, we introduced new workflows to streamline zero-trust policy adoption. Our approach has been to make zero trust practical – ensuring that as enterprises segment their networks, they maintain clear visibility into application flows and can automate rule changes without fear of breaking things. We also expanded integrations with cloud platforms, recognizing that hybrid cloud deployments require consistent enforcement of zero-trust principles. The goal is simple: only allow what’s necessary. As one of our customers at NCR put it, “we need tools like AlgoSec… because most application owners do not know what access is needed. This tool helps them learn what needs to be implemented to reduce the attack surface.” That insight from the field echoes in our Q4 product enhancements – we focused on features that help identify and tighten overly permissive access, be it on-prem or in the cloud. Additionally, we kept an eye on emerging regulations and frameworks. With new security compliance requirements on the horizon, we ensured our solutions can automate audits and segmentation policies to keep our customers one step ahead. In short, Q4 was about reinforcing our commitment to hybrid cloud security and zero trust, so that our users can enter 2026 with confidence in their security posture. Even as 2025 ends, the wave of recognition we’ve ridden continues into Q4. I’m thrilled to share that in November, AlgoSec was named a “Trailblazing” company in Network Security and Management as part of the 2025 Top InfoSec Innovator Awards . This honor, bestowed by Cyber Defense Magazine’s panel of judges, places us among a select group of cybersecurity companies driving innovation and shaping the future of the industry. It’s a testament to our team’s hard work and our forward-thinking roadmap. Looking ahead to 2026 Reflecting on 2025, it’s clear that this year has been t ransformationa l for AlgoSec. We innovated boldly, earned trust widely, and solidified our position as the go-to partner for enterprises seeking secure, agile connectivity. The awards and recognitions were wonderful highlights – they energize us – but what truly drives our pride is knowing we helped organizations around the world accelerate their business securely . The foundations we laid this year in areas like zero trust architecture, hybrid cloud security, and intelligent policy automation have set us up for an even more impactful 2026. As we turn toward 2026, our vision is sharper than ever. We will continue to advance our platform – expect even more AI-driven insights, broader cloud integrations, and features that make managing network security policies in complex environments simpler than ever. We’ll also keep championing thought leadership through research and community engagement, because educating the market is part of our DNA. The threat landscape will undoubtedly evolve in 2026, but we plan to stay ahead of the curve , helping our customers navigate whatever comes next with confidence and clarity. On a personal note, I am incredibly grateful for the dedication of our team and the unwavering support of our AlgoSec community. It’s your feedback and your challenges that inspire our innovations. This year we’ve seen what we can achieve together – from launching Horizon to embracing zero trust, from winning awards to solving tough problems on the ground. 2025 has been a chapter of leadership and growth in AlgoSec’s story. Now we set our sights on writing the next chapter. With the momentum at our backs and our mission guiding us, we step into 2026 ready to continue redefining what’s possible in secure application connectivity. Here’s to another year of innovation, collaboration, and success on the horizon! Thank you for being part of our 2025 journey. We’re excited for what’s to come – and we’ll be sure to keep you posted every step of the way. 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

Cloud computing has become a cornerstone of business operations, with cloud security at the forefront of strategic concerns. In a recent... Cloud Network Security Shaping tomorrow: Leading the way in cloud security 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. cnapp Tags Share this article 12/28/23 Published Cloud computing has become a cornerstone of business operations, with cloud security at the forefront of strategic concerns. In a recent SANS webinar , our CTO Prof. Avishai Wool discussed why more companies are becoming more concerned protecting their containerized environments, given the fact that they are being targeted in cloud-based breaches more than ever. Watch the SANS webinar now! Embracing CNAPP (Cloud-Native Application Protection Platform) is crucial, particularly for its role in securing these versatile yet vulnerable container environments. Containers, encapsulating code and dependencies, are pivotal in modern application development, offering portability and efficiency. Yet, they introduce unique security challenges. With 45% of breaches occurring in cloud-based settings, the emphasis on securing containers is more critical than ever. CNAPP provides a comprehensive shield, addressing specific vulnerabilities inherent to containers, such as configuration errors or compromised container images. The urgent need for skilled container security experts The deployment of CNAPP solutions, while technologically advanced, also hinges on human expertise. The shortage of skills in cloud security management, particularly around container technologies, poses a significant challenge. As many as 35% of IT decision-makers report difficulties in navigating data privacy and security management, underscoring the urgent need for skilled professional’s adept in CNAPP and container security. The economic stakes of failing to secure cloud environments, especially containers, are high. Data breaches, on average, cost companies a staggering $4.35 million . This figure highlights not just the financial repercussions but also the potential damage to reputation and customer trust. CNAPP’s role extends beyond security, serving as a strategic investment against these multifaceted risks. As we navigate the complexitis of cloud security, CNAPP’s integration for container protection represents just one facet of a broader strategy. Continuous monitoring, regular security assessments, and a proactive approach to threat detection and response are also vital. These practices ensure comprehensive protection and operational resilience in a landscape where cloud dependency is rapidly increasing. The journey towards securing cloud environments, with a focus on containers, is an ongoing endeavour. The strategic implementation of CNAPP, coupled with a commitment to cultivating skilled cybersecurity expertise, is pivotal. By balancing advanced technology with professional acumen, organizations can confidently navigate the intricacies of cloud security, ensuring both digital and economic resilience in our cloud-dependent world. #CNAPP 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

Enterprises are embracing cloud platforms to drive innovation, enhance operational efficiency, and gain a competitive edge. Cloud... Hybrid Cloud Security Management Securing Cloud-Native Environments: Containerized Applications, Serverless Architectures, and Microservices Malcom Sargla 2 min read Malcom Sargla Short bio about author here Lorem ipsum dolor sit amet consectetur. Vitae donec tincidunt elementum quam laoreet duis sit enim. Duis mattis velit sit leo diam. Tags Share this article 9/6/23 Published Enterprises are embracing cloud platforms to drive innovation, enhance operational efficiency, and gain a competitive edge. Cloud services provided by industry giants like Google Cloud Platform (GCP), Azure, AWS, IBM, and Oracle offer scalability, flexibility, and cost-effectiveness that make them an attractive choice for businesses. One of the significant trends in cloud-native application development is the adoption of containerized applications, serverless architectures, and microservices. While these innovations bring numerous benefits, they also introduce unique security risks and vulnerabilities that organizations must address to ensure the safety of their cloud-native environments. The Evolution of Cloud-Native Applications Traditionally, organizations relied on on-premises data centers and a set of established security measures to protect their critical applications and data. However, the shift to cloud-native applications necessitates a reevaluation of security practices and a deeper understanding of the challenges involved. Containers: A New Paradigm Containers have emerged as a game-changer in the world of cloud-native development. They offer a way to package applications and their dependencies, ensuring consistency and portability across different environments. Developers appreciate containers for their ease of use and rapid deployment capabilities, but this transition comes with security implications that must not be overlooked. One of the primary concerns with containers is the need for continuous scanning and vulnerability assessment. Developers may inadvertently include libraries with known vulnerabilities, putting the entire application at risk. To address this, organizations should leverage container scanning tools that assess images for vulnerabilities before they enter production. Tools like Prevasio’s patented network sandbox provide real-time scanning for malware and known Common Vulnerabilities and Exposures (CVEs), ensuring that container images are free from threats. Continuous Container Monitoring The dynamic nature of containerized applications requires continuous monitoring to ensure their health and security. In multi-cloud environments, it’s crucial to have a unified monitoring solution that covers all services consistently. Blind spots must be eliminated to gain full control over the cloud deployment. Tools like Prevasio offer comprehensive scanning of asset classes in popular cloud providers such as Amazon AWS, Microsoft Azure, and Google GCP. This includes Lambda functions, S3 buckets, Azure VMs, and more. Continuous monitoring helps organizations detect anomalies and potential security breaches early, allowing for swift remediation. Intelligent and Automated Policy Management As organizations scale their cloud-native environments and embrace the agility that developers demand, policy management becomes a critical aspect of security. It’s not enough to have static policies; they must be intelligent and adaptable to evolving threats and requirements. Intelligent policy management solutions enable organizations to enforce corporate security policies both in the cloud and on-premises. These solutions have the capability to identify and guard against risks introduced through development processes or traditional change management procedures. When a developer’s request deviates from corporate security practices, an intelligent policy management system can automatically trigger actions, such as notifying network analysts or initiating policy work orders. Moreover, these solutions facilitate a “shift-left” approach, where security considerations are integrated into the earliest stages of development. This proactive approach ensures that security is not an afterthought but an integral part of the development lifecycle. Mitigating Risks in Cloud-Native Environments Securing containerized applications, serverless architectures, and microservices in cloud-native environments requires a holistic strategy. Here are some key steps that organizations can take to mitigate risks effectively: 1. Start with a Comprehensive Security Assessment Before diving into cloud-native development, conduct a thorough assessment of your organization’s security posture. Identify potential vulnerabilities and compliance requirements specific to your industry. Understanding your security needs will help you tailor your cloud-native security strategy effectively. 2. Implement Continuous Security Scanning Integrate container scanning tools into your development pipeline to identify vulnerabilities early in the process. Automate scanning to ensure that every container image is thoroughly examined before deployment. Regularly update scanning tools and libraries to stay protected against emerging threats. 3. Embrace Continuous Monitoring Utilize continuous monitoring solutions that cover all aspects of your multi-cloud deployment. This includes not only containers but also serverless functions, storage services, and virtual machines. A unified monitoring approach reduces blind spots and provides real-time visibility into potential security breaches. 4. Invest in Intelligent Policy Management Choose an intelligent policy management solution that aligns with your organization’s security and compliance requirements. Ensure that it offers automation capabilities to enforce policies seamlessly across cloud providers. Regularly review and update policies to adapt to changing security landscapes. 5. Foster a Culture of Security Security is not solely the responsibility of the IT department. Promote a culture of security awareness across your organization. Train developers, operations teams, and other stakeholders on best practices for cloud-native security. Encourage collaboration between security and development teams to address security concerns early in the development lifecycle. Conclusion The adoption of containerized applications, serverless architectures, and microservices in cloud-native environments offers unprecedented flexibility and scalability to enterprises. However, these advancements also introduce new security challenges that organizations must address diligently. By implementing a comprehensive security strategy that includes continuous scanning, monitoring, and intelligent policy management, businesses can harness the power of the cloud while safeguarding their applications and data. As the cloud-native landscape continues to evolve, staying proactive and adaptive in security practices will be crucial to maintaining a secure and resilient cloud environment. 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

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

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

How To Reduce Attack Surface: 6 Proven Tactics Security-oriented organizations continuously identify, monitor, and manage... Cyber Attacks & Incident Response How To Reduce Attack Surface: 6 Proven Tactics Tsippi Dach 2 min read Tsippi Dach Short bio about author here Lorem ipsum dolor sit amet consectetur. Vitae donec tincidunt elementum quam laoreet duis sit enim. Duis mattis velit sit leo diam. Tags Share this article 12/20/23 Published How To Reduce Attack Surface: 6 Proven Tactics Security-oriented organizations continuously identify, monitor, and manage internet-connected assets to protect them from emerging attack vectors and potential vulnerabilities. Security teams go through every element of the organization’s security posture – from firewalls and cloud-hosted assets to endpoint devices and entry points – looking for opportunities to reduce security risks. This process is called attack surface management. It provides a comprehensive view into the organization’s cybersecurity posture, with a neatly organized list of entry points, vulnerabilities, and weaknesses that hackers could exploit in a cyberattack scenario. Attack surface reduction is an important element of any organization’s overall cybersecurity strategy. Security leaders who understand the organization’s weaknesses can invest resources into filling the most critical gaps first and worrying about low-priority threats later. What assets make up your organization’s attack surface? Your organization’s attack surface is a detailed list of every entry point and vulnerability that an attacker could exploit to gain unauthorized access. The more entry points your network has, the larger its attack surface will be. Most security leaders divide their attention between two broad types of attack surfaces: The digital attack surface This includes all network equipment and business assets used to transfer, store, and communicate information. It is susceptible to phishing attempts , malware risks, ransomware attacks, and data breaches. Cybercriminals may infiltrate these kinds of assets by bypassing technical security controls, compromising unsecured apps or APIs, or guessing weak passwords. The physical attack surface This includes business assets that employees, partners, and customers interact with physically. These might include hardware equipment located inside data centers and USB access points. Even access control systems for office buildings and other non-cyber threats may be included. These assets can play a role in attacks that involve social engineering, insider threats, and other malicious actors who work in-person. Even though both of these attack surfaces are distinct, many of their security vulnerabilities and potential entry points overlap in real-life threat scenarios. For example, thieves might steal laptops from an unsecured retail location and leverage sensitive data on those devices to launch further attacks against the organization’s digital assets. Organizations that take steps to minimize their attack surface area can reduce the risks associated with this kind of threat. Known Assets, Unknown Assets, and Rogue Assets All physical and digital business assets fall into one of three categories: Known assets are apps, devices, and systems that the security team has authorized to connect to the organization’s network. These assets are included in risk assessments and they are protected by robust security measures, like network segmentation and strict permissions. Unknown assets include systems and web applications that the security team is not aware of. These are not authorized to access the network and may represent a serious security threat. Shadow IT applications may be part of this category, as well as employee-owned mobile devices storing sensitive data and unsecured IoT devices. Rogue assets connect to the network without authorization, but they are known to security teams. These may include unauthorized user accounts, misconfigured assets, and unpatched software. A major part of properly managing your organization’s attack surface involves the identification and remediation of these risks. Attack Vectors Explained: Minimize Risk by Following Potential Attack Paths When conducting attack surface analysis, security teams have to carefully assess the way threat actors might discover and compromise the organization’s assets while carrying out their attack. This requires the team to combine elements of vulnerability management with risk management , working through the cyberattack kill chain the way a hacker might. Some cybercriminals leverage technical vulnerabilities in operating systems and app integrations. Others prefer to exploit poor identity access management policies, or trick privileged employees into giving up their authentication credentials. Many cyberattacks involve multiple steps carried out by different teams of threat actors. For example, one hacker may specialize in gaining initial access to secured networks while another focuses on using different tools to escalate privileges. To successfully reduce your organization’s attack surface, you must follow potential attacks through these steps and discover what their business impact might be. This will provide you with the insight you need to manage newly discovered vulnerabilities and protect business assets from cyberattack. Some examples of common attack vectors include: API vulnerabilities. APIs allow organizations to automate the transfer of data, including scripts and code, between different systems. Many APIs run on third-party servers managed by vendors who host and manage the software for customers. These interfaces can introduce vulnerabilities that internal security teams aren’t aware of, reducing visibility into the organization’s attack surface. Unsecured software plugins. Plugins are optional add-ons that enhance existing apps by providing new features or functionalities. They are usually made by third-party developers who may require customers to send them data from internal systems. If this transfer is not secured, hackers may intercept it and use that information to attack the system. Unpatched software. Software developers continuously release security patches that address emerging threats and vulnerabilities. However, not all users implement these patches the moment they are released. This delay gives attackers a key opportunity to learn about the vulnerability (which is as easy as reading the patch changelog) and exploit it before the patch is installed. Misconfigured security tools. Authentication systems, firewalls, and other security tools must be properly configured in order to produce optimal security benefits. Attackers who discover misconfigurations can exploit those weaknesses to gain entry to the network. Insider threats. This is one of the most common attack vectors, yet it can be the hardest to detect. Any employee entrusted with sensitive data could accidentally send it to the wrong person, resulting in a data breach. Malicious insiders may take steps to cover their tracks, using their privileged permissions and knowledge of the organization to go unnoticed. 6 Tactics for Reducing Your Attack Surface 1. Implement Zero Trust The Zero Trust security model assumes that data breaches are inevitable and may even have already occurred. This adds new layers to the problems that attack surface management resolves, but it can dramatically improve overall resilience and preparedness. When you develop your security policies using the Zero Trust framework, you impose strong limits on what hackers can and cannot do after gaining initial access to your network. Zero Trust architecture blocks attackers from conducting lateral movement, escalating their privileges, and breaching critical data. For example, IoT devices are a common entry point into many networks because they don’t typically benefit from the same level of security that on-premises workstations receive. At the same time, many apps and systems are configured to automatically trust connections from internet-enabled sensors and peripheral devices. Under a Zero Trust framework, these connections would require additional authentication. The systems they connect to would also need to authenticate themselves before receiving data. Multi-factor authentication is another part of the Zero Trust framework that can dramatically improve operational security. Without this kind of authentication in place, most systems have to accept that anyone with the right username and password combination must be a legitimate user. In a compromised credential scenario, this is obviously not the case. Organizations that develop network infrastructure with Zero Trust principles in place are able to reduce the number of entry points their organization exposes to attackers and reduce the value of those entry points. If hackers do compromise parts of the network, they will be unable to quickly move between different segments of the network, and may be unable to stay unnoticed for long. 2. Remove Unnecessary Complexity Unknown assets are one of the main barriers to operational security excellence. Security teams can’t effectively protect systems, apps, and users they don’t have detailed information on. Any rogue or unknown assets the organization is responsible for are almost certainly attractive entry points for hackers. Arbitrarily complex systems can be very difficult to document and inventory properly . This is a particularly challenging problem for security leaders working for large enterprises that grow through acquisitions. Managing a large portfolio of acquired companies can be incredibly complex, especially when every individual company has its own security systems, tools, and policies to take into account. Security leaders generally don’t have the authority to consolidate complex systems on their own. However, you can reduce complexity and simplify security controls throughout the environment in several key ways: Reduce the organization’s dependence on legacy systems. End-of-life systems that no longer receive maintenance and support should be replaced with modern equivalents quickly. Group assets, users, and systems together. Security groups should be assigned on the basis of least privileged access, so that every user only has the minimum permissions necessary to achieve their tasks. Centralize access control management. Ad-hoc access control management quickly leads to unknown vulnerabilities and weaknesses popping up unannounced. Implement a robust identity access management system so you can create identity-based policies for managing user access. 3. Perform Continuous Vulnerability Monitoring Your organization’s attack surface is constantly changing. New threats are emerging, old ones are getting patched, and your IT environment is supporting new users and assets on a daily basis. Being able to continuously monitor these changes is one of the most important aspects of Zero Trust architecture . The tools you use to support attack surface management should also generate alerts when assets get exposed to known risks. They should allow you to confirm the remediation of detected risks, and provide ample information about the risks they uncover. Some of the things you can do to make this happen include: Investing in a continuous vulnerability monitoring solution. Vulnerability scans are useful for finding out where your organization stands at any given moment. Scheduling these scans to occur at regular intervals allows you to build a standardized process for vulnerability monitoring and remediation. Building a transparent network designed for visibility. Your network should not obscure important security details from you. Unfortunately, this is what many third-party security tools and services achieve. Make sure both you and your third-party security partners are invested in building observability into every aspect of your network. Prioritize security expenditure based on risk. Once you can observe the way users, data, and assets interact on the network, you can begin prioritizing security initiatives based on their business impact. This allows you to focus on high-risk tasks first. 4. Use Network Segmentation to Your Advantage Network segmentation is critical to the Zero Trust framework. When your organization’s different subnetworks are separated from one another with strictly protected boundaries, it’s much harder for attackers to travel laterally through the network. Limiting access between parts of the network helps streamline security processes while reducing risk. There are several ways you can segment your network. Most organizations already perform some degree of segmentation by encrypting highly classified data. Others enforce network segmentation principles when differentiating between production and live development environments. But in order for organizations to truly benefit from network segmentation, security leaders must carefully define boundaries between every segment and enforce authentication policies designed for each boundary. This requires in-depth knowledge of the business roles and functions of the users who access those segments, and the ability to configure security tools to inspect and enforce access control rules. For example, any firewall can block traffic between two network segments. A next-generation firewall can conduct identity-based inspection that allows traffic from authorized users through – even if they are using mobile devices the firewall has never seen before. 5. Implement a Strong Encryption Policy Encryption policies are an important element of many different compliance frameworks . HIPAA, PCI-DSS, and many other regulatory frameworks specify particular encryption policies that organizations must follow to be compliant. These standards are based on the latest research in cryptographic security and threat intelligence reports that outline hackers’ capabilities. Even if your organization is not actively seeking regulatory compliance, you should use these frameworks as a starting point for building your own encryption policy. Your organization’s risk profile is largely the same whether you seek regulatory certification or not – and accidentally deploying outdated encryption policies can introduce preventable vulnerabilities into an otherwise strong security posture. Your organization’s encryption policy should detail every type of data that should be encrypted and the cipher suite you’ll use to encrypt that data. This will necessarily include critical assets like customer financial data and employee payroll records, but it also includes relatively low-impact assets like public Wi-Fi connections at retail stores. In each case, you must implement a modern cipher suite that meets your organization’s security needs and replace legacy devices that do not support the latest encryption algorithms. This is particularly important in retail and office settings, where hardware routers, printers, and other devices may no longer support secure encryption. 6. Invest in Employee Training To truly build security resilience into any company culture, it’s critical to explain why these policies must be followed, and what kinds of threats they address. One of the best ways to administer standardized security compliance training is by leveraging a corporate learning platform across the organization, so that employees can actually internalize these security policies through scenario based training courses. It’s especially valuable in organizations suffering from consistent shadow IT usage. When employees understand the security vulnerabilities that shadow IT introduces into the environment, they’re far less likely to ignore security policies for the sake of convenience. Security simulations and awareness campaigns can have a significant impact on training initiatives. When employees know how to identify threat actors at work, they are much less likely to fall victim to them. However, actually achieving meaningful improvement may require devoting a great deal of time and energy into phishing simulation exercises over time – not everyone is going to get it right in the first month or two. These initiatives can also provide clear insight and data on how prepared your employees are overall. This data can make a valuable contribution to your attack surface reduction campaign. You may be able to pinpoint departments – or even individual users – who need additional resources and support to improve their resilience against phishing and social engineering attacks. Successfully managing this aspect of your risk assessment strategy will make it much harder for hackers to gain control of privileged administrative accounts. 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

14 Step Checklist for a Flawless Network Security Audit If security policies aren’t periodically updated to meet modern threat demands,... Cyber Attacks & Incident Response 14 Step Checklist for a Flawless Network Security Audit Tsippi Dach 2 min read Tsippi Dach Short bio about author here Lorem ipsum dolor sit amet consectetur. Vitae donec tincidunt elementum quam laoreet duis sit enim. Duis mattis velit sit leo diam. Tags Share this article 12/20/23 Published 14 Step Checklist for a Flawless Network Security Audit If security policies aren’t periodically updated to meet modern threat demands, organizations risk introducing vulnerabilities into their IT security posture. Comprehensive audit reports help security leaders gain in-depth visibility into their organization’s cybersecurity strategy and assess the resilience of its network infrastructure . Network Security Audit Checklist: What Does Your IT Security Audit Need to Cover? Cybersecurity audits demand an extensive overview of the organization’s security posture and risk profile. It requires gathering and analyzing network data to identify security vulnerabilities, monitor access controls, and assess potential threats. It also includes an overview of operational security practices, penetration testing results, and incident response playbooks . Ultimately, comprehensive risk assessment data should guide the organization towards improving its security measures and preventing hackers from breaching critical data and assets. A complete network security audit should include provide in-depth visibility into the following: Security controls and their implementation. The availability of network devices and access points. High-impact security risks and their potential consequences. The effectiveness of information security management processes. Performance data on security systems and network assets like firewalls. What Do Network Security Audits Help You Achieve? Conducting in-depth security audits helps security leaders identify data breach risks and develop plans for managing those risks. Audit results play an incredibly important role in preventative risk management and in the remediation of cyberattacks. Organizations that regularly conduct these kinds of assessments are better equipped to address the security weaknesses that might arise when onboarding new users, adding new endpoints to the network, or installing new apps. Network audits and security assessments can also help you achieve other important goals as well, such as: Identifying network performance issues and addressing them to improve overall performance. Unlocking opportunities to leverage network assets and mobile devices more efficiently. Demonstrating compliance with regulatory frameworks like the NIST Cybersecurity Framework 1.1 , ISO 27001 and 27002 , and SOC 2 Type 2 . Present security performance information to core stakeholders to demonstrate the value of security policies and controls. Update system security processes to address new vulnerabilities and potential threats. Recommended Read: 20 Best Network Security Solutions + FAQs How to Perform a Network Security Audit The network audit process involves collecting data, analyzing it to identify potential threats, and using it to compile a formal audit report. Depending on the size and complexity of the organization, this audit may be performed by an individual network analyst, a third-party IT security audit specialist, or an entire team of internal security professionals. These are the steps that make up a typical network audit: 1. Plan for the audit and inform everyone involved The audit process will involve many different types of technical tasks. The specific steps you take will change depending on the complexity of your network and the specialist talent required to assess data security in different IT contexts. You will need to verify authentication protocols, operating system security, password policies, and more. It’s rare for an individual security auditor to have all the technical skills necessary to do this on every app, device, and platform an organization uses. In most cases, you’ll need to work with other employees, third-party service providers, and other stakeholders to obtain the data you need. 2. Document all procedures and processes associated with the audit Recording every process that takes place during the audit is crucial. When preparing your final report, you may want to go back and verify some of the processes that took place to ensure the fidelity and accuracy of your data. If methodological errors creep into your data, they can skew your final report’s findings and end up damaging your ability to secure sensitive data correctly. Documentation is especially important in network security audits because you are looking for systematic flaws in the way user accounts, network assets, and security systems interact with one another. These flaws may not reveal themselves without clear documentation. 3. Review standard operating procedures and how they are managed Protecting sensitive information and critical network assets from security threats takes more than sophisticated technology. It also requires strict adherence to security policies and best practices from human users. Security audits should verify that employees and third-party providers are observing security policies in their operating procedures, and provide evidence attesting to that fact. Reviewing the organization’s procedure management system should provide key insight into whether users are following procedures or not. If they are not, there is a high risk of shadow IT processes leading to phishing attacks and security breaches. This should be reported so that the security team can find ways to remediate these threats. 4. Assess the training logs and operations Human error is behind eight out of ten cyberattacks . All customer-facing employees should be trained to detect phishing and social engineering attacks, and internal staff should know how to prevent malware from infecting the network. Every employee should understand how their role contributes to the security profile of the organization as a whole. Verifying authentication processes, permissions, and password policy is also part of employee training. Every user account should be protected by a consistent policy that follows the latest guidelines for beating brute force and dictionary-based credential attacks. Data encryption policies should keep sensitive login credentials secure even if hackers successfully compromise network assets. 5. Confirm the security patches for network software are up-to-date Start by creating a list of every software application used on the network. This can be a long, time-consuming manual process, but there are automated vulnerability scanning solutions that can help you automate this step. You will have to investigate each item on the list and determine whether new security patches are installed in a reasonably tight time frame. Keep in mind that cybercriminals often exploit security patch releases by scanning for organizations that delay installing new patches. Patch release changelogs essentially broadcast known vulnerabilities directly to hackers, so exploiting late patch installations is a trivial task. 6. Confirm the penetration testing policy and process is sufficient Penetration testing is one of the best ways to identify vulnerabilities on a network. If your organization has invested in pentesting initiatives, you will need to review and confirm its policies as part of the network security audit process. If you haven’t yet invested in pentesting, you may wish to outline a potential path for incorporating it into your security processes here. You may wish to verify the size and scope of your pentesting processes at this point. Assess some of the vulnerabilities you have uncovered and determine whether the organization is investing the appropriate resources into pentesting, or whether other security initiatives should take precedence. 7. Identify gaps and misconfigurations in your firewall policies Your organization’s firewalls play an important role managing traffic between network assets. Firewall rules should not be static. They must be continuously updated to meet the needs of the organization as it changes and grows. These devices can enforce bring your own device (BYOD) mobile policies, prevent distributed denial of service (DDoS) attacks, and contribute to proper network segmentation. Manually configuring firewall policies can be costly and time-consuming. Consider using an automated change management platform like AlgoSec Firewall Analyzer to rapidly identify potential vulnerabilities in your firewall rules. Document any changes you make and include those updates in your report. 8. Ensure all sensitive and confidential data is stored securely Every organization has to store some form of sensitive or confidential data. A major goal of network security audits is making sure this data is kept separate from non-sensitive data and protected by a higher standard of security. This data includes individuals’ names, addresses, phone numbers, financial information, and government ID data. Access to sensitive data should be only allowed when critical for business purposes, and every action involving sensitive data should generate comprehensive logs. The data itself should be encrypted so that even if attackers successfully breach the database, they won’t be able to use the data itself. It may also be worth considering an enterprise data backup solution to provide a failsafe in the event of a disaster. 9. Encrypt the hard disks on any company laptops Portable devices like laptops should not generally hold sensitive data. However, many employees can’t work without processing some amount of sensitive data and storing it on the local hard drive. This is usually less than critical data, but it can still contribute to a cyberattack if it falls into the wrong hands. Encrypting laptop hard disks can help prevent that from happening. If all the data on the device is encrypted, then the organization can avoid triggering a crisis-level security incident every time an employee misplaces or loses a company device. 10. Check the security of your wireless networks Wireless network security is vital for preventing hackers from conducting phishing attacks against employees and on-premises customers. If your organization’s Wi-Fi network is not secured, hackers can spoof the network and trick users into giving up vital information without their knowledge. All modern Wi-Fi equipment supports multiple security protocols. Avoid WEP and WPA – these are old protocols with well-known security vulnerabilities – and make sure your networks are using WPA2. If the organization has equipment that does not support WPA2, you must upgrade the equipment. 11. Scan for and identify any unauthorized access points Your network may have access points that were never set up or approved by the organization. Cybercriminals can use these unauthorized access points to steal data without triggering exfiltration alerts. Additional Wi-Fi frequencies are a common culprit here – your private Wi-Fi network may be configured to use the 2.4 GHz band even though you have equipment that supports 5 GHz frequencies. If someone sets up an access point on the 5 GHz frequency, you can easily overlook it. Data breaches can occur over a wide variety of similar media. USB and Bluetooth-enabled devices have introduced malware into corporate networks in the past. Your security audit should cover as many of these communication channels as possible. 12. Review the event log monitoring process The best way to verify security events is by analyzing the logs generated by network assets as they respond to user interactions. These logs can tell you who accessed sensitive data and report where and when that access took place. Security analysts can connect log data across applications to contextualize security incidents and understand how they took place. The problem is that even a small organization with a simple network can generate an enormous volume of log data every day. Your security audit should investigate the event log monitoring process and look for opportunities to streamline it. You may consider implementing a security information and event management (SIEM) platform or improving your existing one. 13. Compile a comprehensive report Once you’ve gathered all the relevant data and included your insight into the organization’s security posture, you are ready to create your audit report. This report should compile all of your findings into a single well-organized document, with evidence supporting the claims you make and clear recommendations for improving operational security moving forward. Consider creating customized data visualizations to showcase how key performance metrics change over time. The way you choose to communicate data can have a major impact on the way it is received, potentially convincing key stakeholders to implement the changes you suggest. 14. Send the final report to appropriate stakeholders and other key parties. Once you’ve finished your network security audit, you are ready to send it to your organization’s leaders and any other stakeholders who have an interest in your findings. Be prepared to explain your recommendations and justify the methods you used to collect and analyze the organization’s security data. The more confident you are in the accuracy of your findings, the better-equipped you’ll be to present them if called upon. 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 Horizon Platform Solution brief 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