Search results

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

Application outages caused by human error can be a nightmare for businesses, leading to financial losses, customer dissatisfaction, and... Cyber Attacks & Incident Response Resolving human error in application outages: strategies for success Malynnda Littky-Porath 2 min read Malynnda Littky-Porath 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 Application outages caused by human error can be a nightmare for businesses, leading to financial losses, customer dissatisfaction, and reputational damage. While human error is inevitable, organizations can implement effective strategies to minimize its impact and resolve outages promptly. In this blog post, we will explore proven solutions for addressing human error in application outages, empowering businesses to enhance their operational resilience and deliver uninterrupted services to their customers. Organizations must emphasize training and education One of the most crucial steps in resolving human error in application outages is investing in comprehensive training and education for IT staff. By ensuring that employees have the necessary skills, knowledge, and understanding of the application environment, organizations can reduce the likelihood of errors occurring. Training should cover proper configuration management, system monitoring, troubleshooting techniques, and incident response protocols. Additionally, fostering a culture of continuous learning and improvement is essential. Encourage employees to stay up to date with the latest technologies, best practices, and industry trends through workshops, conferences, and online courses. Regular knowledge sharing sessions and cross-team collaborations can also help mitigate human errors by fostering a culture of accountability and knowledge transfer. It’s time to implement robust change management processes Implementing rigorous change management processes is vital for preventing human errors that lead to application outages. Establishing a standardized change management framework ensures that all modifications to the application environment go through a well-defined process, reducing the risk of inadvertent errors. The change management process should include proper documentation of proposed changes, a thorough impact analysis, and rigorous testing in non-production environments before deploying changes to the production environment. Additionally, maintaining a change log and conducting post-implementation reviews can provide valuable insights for identifying and rectifying any potential errors. Why automate and orchestrate operational tasks Human errors often occur due to repetitive, mundane tasks that are prone to oversight or mistakes. Automating and orchestrating operational tasks can significantly reduce human error in application outages. Organizations should leverage automation tools to streamline routine tasks such as provisioning, configuration management, and deployment processes. By removing the manual element, the risk of human error decreases, and the consistency and accuracy of these tasks improve. Furthermore, implementing orchestration tools allows for the coordination and synchronization of complex workflows involving multiple teams and systems. This reduces the likelihood of miscommunication and enhances collaboration, minimizing errors caused by lack of coordination. Establish effective monitoring and alerting mechanisms Proactive monitoring and timely alerts are crucial for identifying potential issues and resolving them before they escalate into outages. Implementing robust monitoring systems that capture key performance indicators, system metrics, and application logs enables IT teams to quickly identify anomalies and take corrective action. Additionally, setting up alerts and notifications for critical events ensures that the appropriate personnel are notified promptly, allowing for rapid response and resolution. Leveraging artificial intelligence and machine learning capabilities can enhance monitoring by detecting patterns and anomalies that human operators might miss. Human errors will always be a factor in application outages, but by implementing effective strategies, organizations can minimize their impact and resolve incidents promptly. Investing in comprehensive training, robust change management processes, automation and orchestration, and proactive monitoring can significantly reduce the likelihood of human error-related outages. By prioritizing these solutions and fostering a culture of continuous improvement, businesses can enhance their operational resilience, protect their reputation, and deliver uninterrupted services to their customers. Schedule a demo Related Articles Q1 at AlgoSec: What innovations and milestones defined our start to 2026? AlgoSec Reviews Mar 19, 2023 · 2 min read 2025 in review: What innovations and milestones defined AlgoSec’s transformative year in 2025? AlgoSec Reviews Mar 19, 2023 · 2 min read Navigating Compliance in the Cloud AlgoSec Cloud Mar 19, 2023 · 2 min read Speak to one of our experts Speak to one of our experts Work email* First name* Last name* Company* country* Select country... Short answer* By submitting this form, I accept AlgoSec's privacy policy Schedule a call

As your organization adopts a hybrid IT infrastructure, there are more ways for hackers to steal your sensitive data. This is why cloud... Cloud Security Cloud Application Security: Threats, Benefits, & Solutions 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 6/29/23 Published As your organization adopts a hybrid IT infrastructure, there are more ways for hackers to steal your sensitive data. This is why cloud application security is a critical part of data protection. It allows you to secure your cloud-based applications from cyber threats while ensuring your data is safe. This post will walk you through cloud application security, including its importance. We will also discuss the main cloud application security threats and how to mitigate them. What is Cloud Application Security Cloud application security refers to the security measures taken to protect cloud-based assets throughout their development lifecycle. These security measures are a framework of policies, tools, and controls that protect your cloud against cyber threats. Here is a list of security measures that cloud application security may involve: Compliance with industry standards such as CIS benchmarks to prevent data breaches. Identity management and access controls to prevent unauthorized access to your cloud-based apps. Data encryption and tokenization to protect sensitive data. Vulnerability management through vulnerability scanning and penetration testing. Network perimeter security, such as firewalls, to prevent unwanted access. The following are some of the assets that cloud security affects: Third-party cloud providers like Amazon AWS, Microsoft Azure, and Google GCP. Collaborative applications like Slack and Microsoft Teams. Data Servers. Computer Networks. Why is Cloud Application Security Important Cloud application security is becoming more relevant as businesses migrated their data to the cloud in recent years. This is especially true for companies with a multi-cloud environment. These types of environments create a larger attack surface for hackers to exploit. According to IBM , the cost of a data breach in 2022 was $4.35 million. And this represents an increase of 2.6% from the previous year. The report also revealed that it took an average of 287 days to find and stop a data breach in a cloud environment. This time is enough for hackers to steal sensitive data and really damage your assets. Here are more things that can go wrong if organizations don’t pay attention to cloud security: Brand image damage: A security breach may cause a brand’s reputation to suffer and a decline in client confidence. During a breach, your company’s servers may be down for days or weeks. This means customers who paid for your services will not get access in that time. They may end up destroying your brand’s image through word of mouth. Lost consumer trust: Consumer confidence is tough to restore after being lost due to a security breach. Customers could migrate to rivals they believe to be more secure. Organizational disruption: A security breach may cause system failures preventing employees from working. This, in turn, could affect their productivity. You may also have to fire employees tasked with ensuring cloud security. Data loss: You may lose sensitive data, such as client information, resulting in legal penalties. Trade secrets theft may also affect the survival of your organization. Your competitors may steal your only leverage in the industry. Compliance violations: You may be fined for failing to comply with industry regulations such as GDPR. You may also face legal consequences for failing to protect consumer data. What are the Major Cloud Application Security Threats The following is a list of the major cloud application security threats: Misconfigurations: Misconfigurations are errors made when setting up cloud-based applications. They can occur due to human errors, lack of expertise, or mismanagement of cloud resources. Examples include weak passwords, unsecured storage baskets, and unsecured ports. Hackers may use these misconfigurations to access critical data in your public cloud. Insecure data sharing: This is the unauthorized or unintended sharing of sensitive data between users. Insecure data sharing can happen due to a misconfiguration or inappropriate access controls. It can lead to data loss, breaches, and non-compliance with regulatory standards. Limited visibility into network operations: This is the inability to monitor and control your cloud infrastructure and its apps. Limited network visibility prevents you from quickly identifying and responding to cyber threats. Many vulnerabilities may go undetected for a long time. Cybercriminals may exploit these weak points in your network security and gain access to sensitive data. Account hijacking: This is a situation where a hacker gains unauthorized access to a legitimate user’s cloud account. The attackers may use various social engineering tactics to steal login credentials. Examples include phishing attacks, password spraying, and brute-force attacks. Once they access the user’s cloud account, they can steal data or damage assets from within. Employee negligence and inadequately trained personnel: This threat occurs when employees are not adequately trained to recognize, report and prevent cyber risks. It can also happen when employees unintentionally or intentionally engage in risky behavior. For example, they could share login credentials with unauthorized users or set weak passwords. Weak passwords enable attackers to gain entry into your public cloud. Rogue employees can also intentionally give away your sensitive data. Compliance risks: Your organization faces cloud computing risks when non-compliant with industry regulations such as GDPR, PCI-DSS, and HIPAA. Some of these cloud computing risks include data breaches and exposure of sensitive information. This, in turn, may result in fines, legal repercussions, and reputational harm. Data loss: Data loss is a severe security risk for cloud applications. It may happen for several causes, including hardware malfunction, natural calamities, or cyber-attacks. Some of the consequences of data loss may be the loss of customer trust and legal penalties. Outdated security software: SaaS vendors always release updates to address new vulnerabilities and threats. Failing to update your security software on a regular basis may leave your system vulnerable to cyber-attacks. Hackers may exploit the flaws in your outdated SaaS apps to gain access to your cloud. Insecure APIs: APIs are a crucial part of cloud services but can pose a severe security risk if improperly secured. Insecure APIs and other endpoint infrastructure may cause many severe system breaches. They can lead to a complete system takeover by hackers and elevated privileged access. How to Mitigate Cloud Application Security Risks The following is a list of measures to mitigate cloud app security risks: Conduct a thorough risk analysis: This entails identifying possible security risks and assessing their potential effects. You then prioritize correcting the risks depending on their level of severity. By conducting risk analysis on a regular basis, you can keep your cloud environment secure. You’ll quickly understand your security posture and select the right security policies. Implement a firm access control policy: Access control policies ensure that only authorized users gain access to your data. They also outline the level of access to sensitive data based on your employees’ roles. A robust access control policy comprises features such as: Multi-factor authentication Role-based access control Least Privilege Access Strong password policies. Use encryption: Encryption is a crucial security measure that protects sensitive data in transit and at rest. This way, if an attacker intercepts data in transit, it will only be useful if they have a decryption key. Some of the cloud encryption solutions you can implement include: Advanced Encryption Standard (AES) Rivest -Shamir-Addleman (RSA) Transport Layer Security (TSL) Set up data backup and disaster recovery policies: A data backup policy ensures data is completely recovered in case of breaches. You can always recover the lost data from your data backup files. Data backup systems also help reduce the impact of cyberattacks as you will restore normal operations quickly. Disaster recovery policies focus on establishing protocols and procedures to restore critical systems during a major disaster. This way, your data security will stay intact even when disaster strikes. Keep a constant watch over cloud environments: Security issues in cloud settings can only be spotted through continuous monitoring. Cloud security posture management tools like Prevasio can help you monitor your cloud for such issues. With its layer analysis feature, you’ll know the exact area in your cloud and how to fix it. Test and audit cloud security controls regularly: Security controls help you detect and mitigate potential security threats in your cloud. Examples of security controls include firewalls, intrusion detection systems, and database encryption. Auditing these security controls helps to identify gaps they may have. And then you take corrective actions to restore their effectiveness. Regularly evaluating your security controls will reduce the risk of security incidents in your cloud. Implement a security awareness training program: Security awareness training helps educate employees on cloud best practices. When employees learn commonly overlooked security protocols, they reduce the risks of data breaches due to human error. Organize regular assessment tests with your employees to determine their weak points. This way, you’ll reduce chances of hackers gaining access to your cloud through tactics such as phishing and ransomware attacks. Use the security tools and services that cloud service providers offer: Cloud service providers like AWS, Azure, and Google Cloud Platform (GCP) offer security tools and services such as: Web application firewalls (WAF), Runtime application self-protection (RASP), Intrusion detection and prevention systems Identity and access management (IAM) controls You can strengthen the security of your cloud environments by utilizing these tools. However, you should not rely solely on these features to ensure a secure cloud. You also need to implement your own cloud security best practices. Implement an incident response strategy: A security incident response strategy describes the measures to take during a cyber attack. It provides the procedures and protocols to bring the system back to normal in case of a breach. Designing incident response plans helps to reduce downtime. It also minimizes the impact of the damages due to cyber attacks. Apply the Paved Road Security Approach in DevSecOps Processes: DevSecOps environments require security to be integrated into development workflows and tools. This way, cloud security becomes integral to an app development process. The paved road security approach provides a secure baseline that DevSecOps can use for continuous monitoring and automated remediation. Automate your cloud application security practices Using on-premise security practices such as manual compliance checks to mitigate cloud application security threats can be tiring. Your security team may also need help to keep up with the updates as your cloud needs grow. Cloud vendors that can automate all the necessary processes to maintain a secure cloud. They have cloud security tools to help you achieve and maintain compliance with industry standards. You can improve your visibility into your cloud infrastructures by utilizing these solutions. They also spot real-time security challenges and offer remediations. For example, Prevasio’s cloud security solutions monitor cloud environments continually from the cloud. They can spot possible security threats and vulnerabilities using AI and machine learning. What Are Cloud Application Security Solutions? Cloud application security solutions are designed to protect apps and other assets in the cloud. Unlike point devices, cloud application security solutions are deployed from the cloud. This ensures you get a comprehensive cybersecurity approach for your IT infrastructure. These solutions are designed to protect the entire system instead of a single point of vulnerability. This makes managing your cybersecurity strategy easier. Here are some examples of cloud security application solutions: 1. Cloud Security Posture Management (CSPM) : CSPM tools enable monitoring and analysis of cloud settings for security risks and vulnerabilities. They locate incorrect setups, resources that aren’t compliant, and other security concerns that might endanger cloud infrastructures. 2. The Cloud Workload Protection Platform (CWPP) : This cloud application security solution provides real-time protection for workloads in cloud environments . It does this by detecting and mitigating real-time threats regardless of where they are deployed. CWPP solutions offer various security features, such as: Network segmentation File integrity monitoring Vulnerability scanning. Using CWPP products will help you optimize your cloud application security strategy. 3. Cloud Access Security Broker (CASB) : CASB products give users visibility into and control over the data and apps they access in the cloud. These solutions help businesses enforce security guidelines and monitor user behavior in cloud settings. The danger of data loss, leakage, and unauthorized access is lowered in the process. CASB products also help with malware detection. 4. Runtime Application Self Protection (RASP): This solution addresses security issues that may arise while a program is working. It identifies potential threats and vulnerabilities during runtime and thwarts them immediately. Some of the RASP solutions include: Input validation Runtime hardening Dynamic Application Security testing 5. Web Application and API protection (WAAP) : These products are designed to protect your organization’s Web applications and APIs. They monitor outgoing and incoming web apps and API traffic to detect malicious activity. WAAP products can block any unauthorized access attempts. They can also protect against cyber threats like SQL injection and Cross-site scripting. 6. Data Loss Prevention (DLP): DLP products are intended to stop the loss or leaking of private information in cloud settings. These technologies keep track of sensitive data in use and at rest. They can also enforce rules to stop unauthorized people from losing or accessing it. 7. Security Information and Event Management (SIEM) systems : SIEM systems track and analyze real-time security incidents and events in cloud settings. The effect of security breaches is decreased thanks to these solutions. They help firms in detecting and responding to security issues rapidly. Cloud Native Application Protection Platform (CNAPP) The CNAPP, which Prevasio created, raises the bar for cloud security. It combines CSPM, CIEM, IAM, CWPP, and more in one tool. A CNAPP delivers a complete security solution with sophisticated threat detection and mitigation capabilities for packaged workloads, microservices, and cloud-native applications. The CNAPP can find and eliminate security issues in your cloud systems before hackers can exploit them. With its layer analysis feature, you can quickly fix any potential vulnerabilities in your cloud . It pinpoints the exact layer of code where there are errors, saving you time and effort. CNAPP also offers a visual dynamic analysis of your cloud environment . This lets you grasp the state of your cloud security at a glance. In the process, saving you time as you know exactly where to go. CNAPP is also a scalable cloud security solution. The cloud-native design of Prevasio’s CNAPP enables it to expand dynamically and offer real-time protection against new threats. Let Prevasio Solve Your Cloud Application Security Needs Cloud security is paramount to protecting sensitive data and upholding a company’s reputation in the modern digital age. To be agile to the constantly changing security issues in cloud settings, Prevasio’s Cloud Native Application Protection Platform (CNAPP) offers an all-inclusive solution. From layer analysis to visual dynamic analysis, CNAPP gives you the tools you need to keep your cloud secure. You can rely on Prevasio to properly manage your cloud application security needs. Try Prevasio today! Schedule a demo Related Articles Q1 at AlgoSec: What innovations and milestones defined our start to 2026? AlgoSec Reviews Mar 19, 2023 · 2 min read 2025 in review: What innovations and milestones defined AlgoSec’s transformative year in 2025? AlgoSec Reviews Mar 19, 2023 · 2 min read Navigating Compliance in the Cloud AlgoSec Cloud Mar 19, 2023 · 2 min read Speak to one of our experts Speak to one of our experts Work email* First name* Last name* Company* country* Select country... Short answer* By submitting this form, I accept AlgoSec's privacy policy Schedule a call

So we’ve made it to the last part of our blog series on PCI 3.0 Requirement 1. The first two posts covered Requirement 1.1... Auditing and Compliance Avoid the Traps: What You Need to Know About PCI Requirement 1 (Part 3) Matthew Pascucci 2 min read Matthew Pascucci Short bio about author here Lorem ipsum dolor sit amet consectetur. Vitae donec tincidunt elementum quam laoreet duis sit enim. Duis mattis velit sit leo diam. Tags Share this article 9/9/14 Published So we’ve made it to the last part of our blog series on PCI 3.0 Requirement 1. The first two posts covered Requirement 1.1 (appropriate firewall and router configurations) and 1.2 (restrict connections between untrusted networks and any system components in the cardholder data environment) and in this final post we’ll discuss key requirements of Requirements 1.3 -1.5 and I’ll again give you my insight to help you understand the implications of these requirements and how to comply with them. Implement a DMZ to limit inbound traffic to only system components that provide authorized publicly accessible services, protocols, and ports (1.3.1.): The DMZ is used to publish services such as HTTP and HTTPS to the internet and allow external entities to access these services. But the key point here is that you don’t need to open every port on the DMZ. This requirement verifies that a company has a DMZ implemented and that inbound activity is limited to only the required protocols and ports. Limit inbound Internet traffic to IP addresses within the DMZ (1.3.2): This is a similar requirement to 1.3.1, however instead of looking for protocols, the requirement focuses on the IPs that the protocol is able to access. In this case, just because you might need HTTP open to a web server, doesn’t mean that all systems should have external port 80 open to inbound traffic. Do not allow any direct connections inbound or outbound for traffic between the Internet and the cardholder data environment (1.3.3): This requirement verifies that there isn’t unfiltered access, either going into the CDE or leaving it, which means that all traffic that traverses this network must pass through a firewall. All unwanted traffic should be blocked and all allowed traffic should be permitted based on an explicit source/destination/protocol. There should never be a time that someone can enter or leave the CDE without first being inspected by a firewall of some type. Implement anti-spoofing measures to detect and block forged source IP addresses from entering the network (1.3.4): In an attempt to bypass your firewall, cyber attackers will try and spoof packets using the internal IP range of your network to make it look like the request originated internally. Enabling the IP spoofing feature on your firewall will help prevent these types of attacks. Do not allow unauthorized outbound traffic from the cardholder data environment to the Internet (1.3.5): Similar to 1.3.3, this requirement assumes that you don’t have direct outbound access to the internet without a firewall. However in the event that a system has filtered egress access to the internet the QSA will want to understand why this access is needed, and whether there are controls in place to ensure that sensitive data cannot be transmitted outbound. Implement stateful inspection, also known as dynamic packet filtering (1.3.6): If you’re running a modern firewall this feature is most likely already configured by default. With stateful inspection, the firewall maintains a state table which includes all the connections that traverse the firewall, and it knows if there’s a valid response from the current connection. It is used to stop attackers from trying to trick a firewall into initiating a request that didn’t previously exist. Place system components that store cardholder data (such as a database) in an internal network zone, segregated from the DMZ and other untrusted networks (1.3.7): Attackers are looking for your card holder database. Therefore, it shouldn’t be stored within the DMZ. The DMZ should be considered an untrusted network and segregated from the rest of the network. By having the database on the internal network provides another layer of protection against unwanted access. [Also see my suggestions for designing and securing you DMZ in my previous blog series: The Ideal Network Security Perimeter Design: Examining the DMZ Do not disclose private IP addresses and routing information to unauthorized parties (1.3.8): There should be methods in place to prevent your internal IP address scheme from being leaked outside your company. Attackers are looking for any information on how to breach your network, and giving them your internal address scheme is just one less thing they need to learn. You can stop this by using NAT, proxy servers, etc. to limit what can be seen from the outside. Install personal firewall software on any mobile and/or employee-owned devices that connect to the Internet when outside the network (for example, laptops used by employees), and which are also used to access the network (1.4): Mobile devices, such as laptops, that can connect to both the internal network and externally, should have a personal firewall configured with rules that prevent malicious software or attackers from communicating with the device. These firewalls need to be configured so that their rulebase can never be stopped or changed by anyone other than an administrator. Ensure that security policies and operational procedures for managing firewalls are documented, in use, and known to all affected parties (1.5): There needs to be a unified policy regarding firewall maintenance including how maintenance procedures are performed, who has access to the firewall and when maintenance is scheduled. Well, that’s it! Hopefully, my posts have given you a better insight into what is actually required in Requirement 1 and what you need to do to comply with it. Schedule a demo Related Articles Q1 at AlgoSec: What innovations and milestones defined our start to 2026? AlgoSec Reviews Mar 19, 2023 · 2 min read 2025 in review: What innovations and milestones defined AlgoSec’s transformative year in 2025? AlgoSec Reviews Mar 19, 2023 · 2 min read Navigating Compliance in the Cloud AlgoSec Cloud Mar 19, 2023 · 2 min read Speak to one of our experts Speak to one of our experts Work email* First name* Last name* Company* country* Select country... Short answer* By submitting this form, I accept AlgoSec's privacy policy Schedule a call

Nick Ellsmore is an Australian cybersecurity professional whose thoughts on the future of cybersecurity are always insightful. Having a... Cloud Security Errare humanum est 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/25/21 Published Nick Ellsmore is an Australian cybersecurity professional whose thoughts on the future of cybersecurity are always insightful. Having a deep respect for Nick, I really enjoyed listening to his latest podcast “Episode 79 Making the cyber sector redundant with Nick Ellsmore” . As Nick opened the door to debate on “all the mildly controversial views” he has put forward in the podcast, I decided to take a stab at a couple of points made by Nick. For some mysterious reason, these points have touched my nerve. So, here we go. Nick: The cybersecurity industry, we spent so long trying to get people to listen to us and take the issue seriously, you know, we’re now getting that, you know. Are the businesses really responding because we were trying to get people to listen to us? Let me rephrase this question. Are the businesses really spending more on cybersecurity because we were trying to get people to listen to us? The “cynical me” tells me No. Businesses are spending more on cybersecurity because they are losing more due to cyber incidents. It’s not the number of incidents; it’s their impact that is increasingly becoming devastating. Over the last ten years, there were plenty of front-page headliners that shattered even seemingly unshakable businesses and government bodies. Think of Target attack in 2013, the Bank of Bangladesh heist in 2016, Equifax breach in 2017, SolarWinds hack in 2020 .. the list goes on. We all know how Uber tried to bribe attackers to sweep the stolen customer data under the rug. But how many companies have succeeded in doing so without being caught? How many cyber incidents have never been disclosed? These headliners don’t stop. Each of them is another reputational blow, impacted stock options, rolled heads, stressed-out PR teams trying to play down the issue, knee-jerk reaction to acquire snake-oil-selling startups, etc. We’re not even talking about skewed election results (a topic for another discussion). Each one of them comes at a considerable cost. So no wonder many geniuses now realise that spending on cybersecurity can actually mitigate those risks. It’s not our perseverance that finally started paying off. It’s their pockets that started hurting. Nick: I think it’s important that we don’t lose sight of the fact that this is actually a bad thing to have to spend money on. Like, the reason that we’re doing this is not healthy. .. no one gets up in the morning and says, wow, I can’t wait to, you know, put better locks on my doors. It’s not the locks we sell. We sell gym membership. We want people to do something now to stop bad things from happening in the future. It’s a concept of hygiene, insurance, prevention, health checks. People are free not to pursue these steps, and run their business the way they used to .. until they get hacked, get into the front page, wondering first “Why me?” and then appointing a scapegoat. Nick: And so I think we need to remember that, in a sense, our job is to create the entire redundancy of this sector. Like, if we actually do our job, well, then we all have to go and do something else, because security is no longer an issue. It won’t happen due to 2 main reasons. Émile Durkheim believed in a “society of saints”. Unfortunately, it is a utopia. Greed, hunger, jealousy, poverty are the never-ending satellites of the human race that will constantly fuel crime. Some of them are induced by wars, some — by corrupt regimes, some — by sanctions, some — by imperfect laws. But in the end — there will always be Haves and Have Nots, and therefore, fundamental inequality. And that will feed crime. “Errare humanum est” , Seneca. To err is human. Because of human errors, there will always be vulnerabilities in code. Because of human nature (and as its derivative, geopolitical or religious tension, domination, competition, nationalism, fight for resources), there will always be people willing to and capable of exploiting those vulnerabilities. Mix those two ingredients — and you get a perfect recipe for cybercrime. Multiply that with never-ending computerisation, automation, digital transformation, and you get a constantly growing attack surface. No matter how well we do our job, we can only control cybercrime and keep the lid on it, but we can’t eradicate it. Thinking we could would be utopic. Another important consideration here is budget constraints. Building proper security is never fun — it’s a tedious process that burns cash but produces no tangible outcome. Imagine a project with an allocated budget B to build a product P with a feature set F, in a timeframe T. Quite often, such a project will be underfinanced, potentially leading to a poor choice of coders, overcommitted promises, unrealistic expectations. Eventually leading to this (oldie, but goldie): Add cybersecurity to this picture, and you’ll get an extra step that seemingly complicates everything even further: The project investors will undoubtedly question why that extra step was needed. Is there a new feature that no one else has? Is there a unique solution to an old problem? None of that? Then what’s the justification for such over-complication? Planning for proper cybersecurity built-in is often perceived as FUD. If it’s not tangible, why do we need it? Customers won’t see it. No one will see it. Scary stories in the press? Nah, that’ll never happen to us. In some way, extra budgeting for cybersecurity is anti-capitalistic in nature. It increases the product cost and, therefore, its price, making it less competitive. It defeats the purpose of outsourcing product development, often making outsourcing impossible. From the business point of view, putting “Sec” into “DevOps” does not make sense. That’s Ok. No need. .. until it all gloriously hits the fan, and then we go back to STEP 1. Then, maybe, just maybe, the customer will say, “If we have budgeted for that extra step, then maybe we would have been better off”. Schedule a demo Related Articles Q1 at AlgoSec: What innovations and milestones defined our start to 2026? AlgoSec Reviews Mar 19, 2023 · 2 min read 2025 in review: What innovations and milestones defined AlgoSec’s transformative year in 2025? AlgoSec Reviews Mar 19, 2023 · 2 min read Navigating Compliance in the Cloud AlgoSec Cloud Mar 19, 2023 · 2 min read Speak to one of our experts Speak to one of our experts Work email* First name* Last name* Company* country* Select country... Short answer* By submitting this form, I accept AlgoSec's privacy policy Schedule a call

Elevate Kubernetes container security with AlgoSec s Prevasio Shield your deployments effortlessly Explore more now Kubernetes and container security Agentless zero-trust container analysis system Schedule a demo Watch a video Watch a video AI powered container applications discovery Never misplace a containerized focused application on your estate with new AI powered cloud application discovery. Identify your containerized business applications and their connection to other cloud resources. Comprehensive risk assessment Proactively secure your containers with in-depth vulnerability scanning and malware detection. Take control of your cloud security with clear, actionable remediation recommendations. Compliance Ensure compliance with industry benchmarks such as CIS benchmarks . Achieve and maintain cloud compliance effortlessly. Our platform verifies your Kubernetes , EKS, ECS, and ECR configurations against industry benchmarks, then prioritizes fixes based on the impact to your critical applications. for Kubernetes, EKS, ECS and ECR. Dynamic threat analysis Gain unprecedented visibility into your containerized environments . Prevasio's dynamic threat analysis exposes concealed entry points, detects potential supply chain threats, and empowers you with actionable insights to strengthen your security posture. Get the latest insights from the experts A Guide to Upskilling Your Cloud Architects & Security Teams in 2023 Learn more Securing Cloud-Native Environments: Containerized Applications, Serverless Architectures, and Microservices Learn more Understanding and Preventing Kubernetes Attacks and Threats Read more Schedule time and secure your cloud Schedule time and secure your cloud 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

Protecting an organization against every conceivable threat is rarely possible. There is a practically unlimited number of potential threats in the world, and security leaders don’t have unlimited resources available to address them. Prioritizing risks associated with more severe potential impact allows leaders to optimize cybersecurity decision-making and improve the organization’s security posture. Cybersecurity risk management is important because many security measures come with large... Uncategorized Risk Management in Network Security: 7 Best Practices for 2024 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 1/26/24 Published Protecting an organization against every conceivable threat is rarely possible. There is a practically unlimited number of potential threats in the world, and security leaders don’t have unlimited resources available to address them. Prioritizing risks associated with more severe potential impact allows leaders to optimize cybersecurity decision-making and improve the organization’s security posture. Cybersecurity risk management is important because many security measures come with large costs. Before you can implement security controls designed to protect against cyberattacks and other potential risks, you must convince key stakeholders to support the project. Having a structured approach to cyber risk management lets you demonstrate exactly how your proposed changes impact the organization’s security risk profile. This makes it much easier to calculate the return on cybersecurity investment – making it a valuable tool when communicating with board members and executives. Here are seven tips every security leader should keep in mind when creating a risk management strategy: Cultivate a security-conscious risk management culture Use risk registers to describe potential risks in detail Prioritize proactive, low-cost risk remediation when possible Treat risk management as an ongoing process Invest in penetration testing to discover new vulnerabilities Demonstrate risk tolerance by implementing the NIST Cybersecurity Framework Don’t forget to consider false positives in your risk assessment What is a Risk Management Strategy? The first step to creating a comprehensive risk management plan is defining risk. According to the International Organization for Standardization (ISO) risk is “the effect of uncertainty on objectives”. This definition is accurate, but its scope is too wide. Uncertainty is everywhere, including things like market conditions, natural disasters, or even traffic jams. As a cybersecurity leader, your risk management process is more narrowly focused on managing risks to information systems, protecting sensitive data, and preventing unauthorized access. Your risk management program should focus on identifying these risks, assessing their potential impact, and creating detailed plans for addressing them. This might include deploying tools for detecting cyberattacks, implementing policies to prevent them, or investing in incident response and remediation tools to help you recover from them after they occur. In many cases, you’ll be doing all of these things at once. Crucially, the information you uncover in your cybersecurity risk assessment will help you prioritize these initiatives and decide how much to spend on them. Your risk management framework will provide you with the insight you need to address high-risk, high-impact cybersecurity threats first and manage low-risk, low-impact threats later on. 7 Tips for Creating a Comprehensive Risk Management Strategy 1. Cultivate a security-conscious risk management culture No CISO can mitigate security risks on their own. Every employee counts on their colleagues, partners, and supervisors to keep sensitive data secure and prevent data breaches. Creating a risk management strategy is just one part of the process of developing a security-conscious culture that informs risk-based decision-making. This is important because many employees have to make decisions that impact security on a daily basis. Not all of these decisions are critical-severity security scenarios, but even small choices can influence the way the entire organization handles risk. For example, most organizations list their employees on LinkedIn. This is not a security threat on its own, but it can contribute to security risks associated with phishing attacks and social engineering . Cybercriminals may create spoof emails inviting employees to fake webinars hosted by well-known employees, and use the malicious link to infect employee devices with malware. Cultivating a risk management culture won’t stop these threats from happening, but it might motivate employees to reach out when they suspect something is wrong. This gives security teams much greater visibility into potential risks as they occur, and increases the chance you’ll detect and mitigate threats before they launch active cyberattacks. 2. Use risk registers to describe potential risks in detail A risk register is a project management tool that describes risks that could disrupt a project during execution. Project managers typically create the register during the project planning phase and then refer to it throughout execution. A risk register typically uses the following characteristics to describe individual risks: Description : A brief overview of the risk itself. Category: The formal classification of the risk and what it affects. Likelihood: How likely this risk is to take place. Analysis: What would happen if this risk occurred. Mitigation: What would the team need to do to respond in this scenario. Priority: How critical is this risk compared to others. The same logic applies to business initiatives both large and small. Using a risk register can help you identify and control unexpected occurrences that may derail the organization’s ongoing projects. If these projects are actively supervised by a project manager, risk registers should already exist for them. However, there may be many initiatives, tasks, and projects that do not have risk registers. In these cases, you may need to create them yourself. Part of the overall risk assessment process should include finding and consolidating these risk registers to get an idea of the kinds of disruptions that can take place at every level of the organization. You may find patterns in the types of security risks that you find described in multiple risk registers. This information should help you evaluate the business impact of common risks and find ways to mitigate those risks effectively. 3. Prioritize proactive, low-cost risk remediation when possible Your organization can’t afford to prevent every single risk there is. That would require an unlimited budget and on-demand access to technical specialist expertise. However, you can prevent certain high-impact risks using proactive, low-cost policies that can make a significant difference in your overall security posture. You should take these opportunities when they present themselves. Password policies are a common example. Many organizations do not have sufficiently robust password policies in place. Cybercriminals know this –that’s why dictionary-based credential attacks still occur. If employees are reusing passwords across accounts or saving them onto their devices in plaintext, it’s only a matter of time before hackers notice. At the same time, upgrading a password policy is not an especially expensive task. Even deploying an enterprise-wide password manager and investing in additional training may be several orders of magnitude cheaper than implementing a new SIEM or similarly complex security platform. Your cybersecurity risk assessment will likely uncover many opportunities like this one. Take a close look at things like password policies, change management , and security patch update procedures and look for easy, low-cost projects that can provide immediate security benefits without breaking your budget. Once you address these issues, you will be in a much better position to pursue larger, more elaborate security implementations. 4. Treat risk management as an ongoing process Every year, cybercriminals leverage new tactics and techniques against their victims. Your organization’s security team must be ready to address the risks of emerging malware, AI-enhanced phishing messages, elaborate supply chain attacks, and more. As hackers improve their attack methodologies, your organization’s risk profile shifts. As the level of risk changes, your approach to information security must change as well. This means developing standards and controls that adjust according to your organization’s actual information security risk environment. Risk analysis should not be a one-time event, but a continuous one that delivers timely results about where your organization is today – and where it may be in the future. For example, many security teams treat firewall configuration and management as a one-time process. This leaves them vulnerable to emerging threats that they may not have known about during the initial deployment. Part of your risk management strategy should include verifying existing security solutions and protecting them from new and emerging risks. 5. Invest in penetration testing to discover new vulnerabilities There is more to discovering new risks than mapping your organization’s assets to known vulnerabilities and historical data breaches. You may be vulnerable to zero-day exploits and other weaknesses that won’t be immediately apparent. Penetration testing will help you discover and assess risks that you can’t find out about otherwise. Penetration testing mitigates risk by pinpointing vulnerabilities in your environment and showing how hackers could exploit them. Your penetration testing team will provide a comprehensive report showing you what assets were compromised and how. You can then use this information to close those security gaps and build a stronger security posture as a result. There are multiple kinds of penetration testing. Depending on your specific scenario and environment, you may invest in: External network penetration testing focuses on the defenses your organization deploys on internet-facing assets and equipment. The security of any business application exposed to the public may be assessed through this kind of test. Internal network penetration testing determines how cybercriminals may impact the organization after they gain access to your system and begin moving laterally through it. This also applies to malicious insiders and compromised credential attacks. Social engineering testing looks specifically at how employees respond to attackers impersonating customers, third-party vendors, and internal authority figures. This will help you identify risks associated with employee security training . Web application testing focuses on your organization’s web-hosted applications. This can provide deep insight into how secure your web applications are, and whether they can be leveraged to leak sensitive information. 6. Demonstrate risk tolerance by implementing the NIST Cybersecurity Framework The National Institute of Standards and Technology publishes one of the industry’s most important compliance frameworks for cybersecurity risk mitigation. Unlike similar frameworks like PCI DSS and GDPR, the NIST Cybersecurity Framework is voluntary – you are free to choose when and how you implement its controls in your organization. This set of security controls includes a comprehensive, flexible approach to risk management. It integrates risk management techniques across multiple disciplines and combines them into an effective set of standards any organization can follow. As of 2023, the NIST Risk Management Framework focuses on seven steps: Prepare the organization to change the way it secures its information technology solutions. Categorize each system and the type of information it processes according to a risk and impact analysis/ Select which NIST SP 800-53 controls offer the best data protection for the environment. Implement controls and document their deployment. Assess whether the correct controls are in place and operating as intended. Authorize the implementation in partnership with executives, stakeholders, and IT decision-makers. Monitor control implementations and IT systems to assess their effectiveness and discover emerging risks. 7. Don’t forget to consider false positives in your risk assessment False positives refer to vulnerabilities and activity alerts that have been incorrectly flagged. They can take many forms during the cybersecurity risk assessment process – from vulnerabilities that don’t apply to your organization’s actual tech stack to legitimate traffic getting blocked by firewalls. False positives can impact risk assessments in many ways. The most obvious problem they present is skewing your assessment results. This may lead to you prioritizing security controls against threats that aren’t there. If these controls are expensive or time-consuming to deploy, you may end up having an uncomfortable conversation with key stakeholders and decision-makers later on. However, false positives are also a source of security risks. This is especially true with automated systems like next-generation firewalls , extended detection and response (XDR) solutions, and Security Orchestration, Automation, and Response (SOAR) platforms. Imagine one of these systems detects an outgoing video call from your organization. It flags the connection as suspicious and begins investigating it. It discovers the call is being made from an unusual location and contains confidential data, so it blocks the call and terminates the connection. This could be a case of data exfiltration, or it could be the company CEO presenting a report to stockholders while traveling. Most risk assessments don’t explore the potential risk of blocking high-level executive communications or other legitimate communications due to false positives. Use AlgoSec to Identify and Assess Network Security Risks More Accurately Building a comprehensive risk management strategy is not an easy task. It involves carefully observing the way your organization does business and predicting how cybercriminals may exploit those processes. It demands familiarity with almost every task, process, and technology the organization uses, and the ability to simulate attack scenarios from multiple different angles. There is no need to accomplish these steps manually. Risk management platforms like AlgoSec’s Horizon Security Analyzer can help you map business applications throughout your network and explore attack simulations with detailed “what-if” scenarios. Use Horizon Security Analyzer to gain deep insight into how your organization would actually respond to security incidents and unpredictable events, then use those insights to generate a more complete risk management approach. Schedule a demo Related Articles Q1 at AlgoSec: What innovations and milestones defined our start to 2026? AlgoSec Reviews Mar 19, 2023 · 2 min read 2025 in review: What innovations and milestones defined AlgoSec’s transformative year in 2025? AlgoSec Reviews Mar 19, 2023 · 2 min read Navigating Compliance in the Cloud AlgoSec Cloud Mar 19, 2023 · 2 min read Speak to one of our experts Speak to one of our experts Work email* First name* Last name* Company* country* Select country... Short answer* By submitting this form, I accept AlgoSec's privacy policy Schedule a call

Yitzy Tannenbaum, Product Marketing Manager at AlgoSec, discusses how AWS customers can leverage AlgoSec for AWS to easily migrate... Uncategorized Migrating to AWS in six simple steps Yitzy Tannenbaum 2 min read Yitzy Tannenbaum 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/1/20 Published Yitzy Tannenbaum, Product Marketing Manager at AlgoSec, discusses how AWS customers can leverage AlgoSec for AWS to easily migrate applications Public cloud platforms bring a host of benefits to organizations but managing security and compliance can prove complex. These challenges are exacerbated when organizations are required to manage and maintain security across all controls that make up the security network including on-premise, SDN and in the public cloud. According to a Gartner study , 81% of organizations are concerned about security, and 57% about maintaining regulatory compliance in the public cloud. AlgoSec’s partnership with AWS helps organizations overcome these challenges by making the most of AWS’ capabilities and providing solutions that complement the AWS offering, particularly in terms of security and operational excellence. And to make things even easier, AlgoSec is now available in AWS Marketplace. Accelerating complex application migration with AlgoSec Many organizations choose to migrate workloads to AWS because it provides unparalleled opportunities for scalability, flexibility, and the ability to spin-up new servers within a few minutes. However, moving to AWS while still maintaining high-level security and avoiding application outages can be challenging, especially if you are trying to do the migration manually, which can create opportunities for human error. We help simplify the migration to AWS with a six-step automated process, which takes away manual processes and reduces the risk of error: Step 1 – AlgoSec automatically discovers and maps network flows to the relevant business applications. Step 2- AlgoSec assesses the changes in the application connectivity required to migrate it to AWS. Step 3- AlgoSec analyzes, simulates and computes the necessary changes, across the entire hybrid network (over firewalls, routers, security groups etc.), including providing a what-if risk analysis and compliance report. Step 4- AlgoSec automatically migrates the connectivity flows to the new AWS environment. Step 5 – AlgoSec securely decommissions old connectivity. Step 6- The AlgoSec platform provides ongoing monitoring and visibility of the cloud estate to maintain security and operation of policy configurations or successful continuous operation of the application. Gain control of hybrid estates with AlgoSec Security automation is essential if organizations are to maintain security and compliance across their hybrid environments, as well as get the full benefit of AWS agility and scalability. AlgoSec allows organizations to seamlessly manage security control layers across the entire network from on-premise to cloud services by providing Zero-Touch automation in three key areas. First, visibility is important, since understanding the network we have in the cloud helps us to understand how to deploy and manage the policies across the security controls that make up the hybrid cloud estate. We provide instant visibility, risk assessment and compliance, as well as rule clean-up, under one unified umbrella. Organizations can gain instant network visibility and maintain a risk-free optimized rule set across the entire hybrid network – across all AWS accounts, regions and VPC combinations, as well as 3rd party firewalls deployed in the cloud and across the connection to the on-prem network. Secondly, changes to network security policies in all these diverse security controls can be managed from a single system, security policies can be applied consistently, efficiently, and with a full audit trail of every change. Finally, security automation dramatically accelerates change processes and enables better enforcement and auditing for regulatory compliance. It also helps organizations overcome skill gaps and staffing limitations. Why Purchase Through AWS Marketplace? AWS Marketplace is a digital catalog with thousands of software listings from independent software vendors (ISVs). It makes it easy for organizations to find, test, buy, and deploy software that runs on Amazon Web Services (AWS), giving them a further option to benefit from AlgoSec. The new listing also gives organizations the ability to apply their use of AlgoSec to their AWS Enterprise Discount Program (EDP) spend commitment. With the addition of AlgoSec in AWS Marketplace, customers can benefit from simplified sourcing and contracting as well as consolidated billing, ultimately resulting in cost savings. It offers organizations instant visibility and in-depth risk analysis and remediation, providing multiple unique capabilities such as cloud security group clean-ups, as well as central policy management. This strengthens enterprises’ cloud security postures and ensures continuous audit-readiness. Ready to Get Started? The addition of AlgoSec in AWS Marketplace is the latest development in the relationship between AlgoSec and AWS and is available for businesses with 500 or more users. Visit the AlgoSec AWS Marketplace listing for more information or contact us to discuss it further. Schedule a demo Related Articles Q1 at AlgoSec: What innovations and milestones defined our start to 2026? AlgoSec Reviews Mar 19, 2023 · 2 min read 2025 in review: What innovations and milestones defined AlgoSec’s transformative year in 2025? AlgoSec Reviews Mar 19, 2023 · 2 min read Navigating Compliance in the Cloud AlgoSec Cloud Mar 19, 2023 · 2 min read Speak to one of our experts Speak to one of our experts Work email* First name* Last name* Company* country* Select country... Short answer* By submitting this form, I accept AlgoSec's privacy policy Schedule a call

The move from traditional data centers to a hybrid cloud network environment has revolutionized the way enterprises construct their... Hybrid Cloud Security Management Deconstructing the Complexity of Managing Hybrid Cloud Security 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 4/4/22 Published The move from traditional data centers to a hybrid cloud network environment has revolutionized the way enterprises construct their networks, allowing them to reduce hardware and operational costs, scale per business needs and be more agile. When enterprises choose to implement a hybrid cloud model, security is often one of the primary concerns. The additional complexity associated with a hybrid cloud environment can, in turn, make securing resources to a single standard extremely challenging. This is especially true when it comes to managing the behavioral and policy nuances of business applications . Moreover, hybrid cloud security presents an even greater challenge when organizations are unable to fully control the lifecycle of the public cloud services they are using. For instance, when an organization is only responsible for hosting a portion of its business-critical workloads on the public cloud and has little to no control over the hosting provider, it is unlikely to be able to enforce consistent security standards across both environments. Managing hybrid cloud security Hybrid cloud security requires an extended period of planning and investment for enterprises to become secure. This is because hybrid cloud environments are inherently complex and typically involve multiple providers. To effectively manage these complex environments, organizations will require a comprehensive approach to security that addresses each of the following challenges: Strategic planning and oversight : Policy design and enforcement across hybrid clouds Managing multiple vendor relationships and third-party security controls : Cloud infrastructure security controls, security products provided by cloud and third-party providers and third-party on-premise security vendor products. Managing security-enabling technologies in multiple environments : on-premise, public cloud and private cloud. Managing multiple stakeholders : CISO, IT/Network Security, SecOps, DevOps and Cloud teams. Workflow automation : Auto responding to changing business demands requiring provisioning of policy changes automatically and securely across the hybrid cloud estate. Optimizing security and agility : Aligning risk tolerance with the DevOps teams to manage business application security and connectivity. With these challenges in mind, here are 5 steps you can take to effectively address hybrid cloud security challenges. Step 1. Define the security objectives A holistic approach to high availability is focused on the two critical elements of any hybrid cloud environment: technology and processes. Defining a holistic strategy in a hybrid cloud environment has these advantages: Improved operational availability : Ensure continuous application connectivity, data, and system availability across the hybrid estate. Reduced risk : Understand threats to business continuity from natural disasters or facility disruptions. Better recovery : Maintain data consistency by mirroring critical data between primary locations in case of failure at one site through multiple backup sites. Step 2. Visualize the entire network topology The biggest potential point of failure for hybrid cloud deployment is where the public cloud and private environment offerings meet. This can result in a visual gap often due to disparities between in-house security protocols and third-party security standards, precluding SecOps teams from securing the connectivity of business applications. The solution lies in gaining complete visibility across the entire hybrid cloud estate. This requires having the right solution in place that can help SecOps teams discover, track and migrate application connectivity without regard for the underlying infrastructure. Step 3. Use automation for adaptability and scalability The ability to adapt and scale on demand is one of the most significant advantages of a hybrid cloud environment. Invariably, when considering the range of benefits of a hybrid cloud, it is difficult to conceptualize the power of scaling on demand. Still, enterprises can enjoy tremendous benefits when they correctly implement automation that can respond on-demand to necessary changes. With the right change automation solution, change requests can be easily defined and pushed through the workflow without disrupting the existing network security policy rules or introducing new potential risks. Step 4. Minimize the learning curb According to a 2021 Global Knowledge and IT Skills report , 76% of IT decision-makers experience critical skills gaps in their teams. Hybrid cloud deployment is a complicated process, with the largest potential point of failure being where in-house security protocols and third-party standards interact. If this gap is not closed, malicious actors or malware could slip through it. Meeting this challenge requires a unification of all provisions made to policy changes so that SecOps teams can become familiar with them, regardless of any new device additions to the network security infrastructure. This would be applicable to provisions associated with policy changes across all firewalls, segments, zones, micro‐segments, security groups and zones, and within each business application. Step 5. Get compliant Compliance cannot be guaranteed when the enterprise cannot monitor all vendors and platforms or enforce their policies in a standard manner. This can be especially challenging when attempting to apply compliance standardizations across an infrastructure that consists of a multi-vendor hybrid network environment. To address this issue, enterprises must get their SecOps teams to shift their focus away from pure technology management and toward a larger scale view that ensures that their network security policies consistently comply with regulatory requirements across the entire hybrid cloud estate. Summary Hybrid cloud security presents a significant—and often overlooked—challenge for enterprises. This is because hybrid cloud environments are inherently complex, involving multiple providers, and impact how enterprises manage their business applications and overall IT assets. To learn how to reach your optimal hybrid cloud security solution, read more and find out how you can simplify your journey. Schedule a demo Related Articles Q1 at AlgoSec: What innovations and milestones defined our start to 2026? AlgoSec Reviews Mar 19, 2023 · 2 min read 2025 in review: What innovations and milestones defined AlgoSec’s transformative year in 2025? AlgoSec Reviews Mar 19, 2023 · 2 min read Navigating Compliance in the Cloud AlgoSec Cloud Mar 19, 2023 · 2 min read Speak to one of our experts Speak to one of our experts Work email* First name* Last name* Company* country* Select country... Short answer* By submitting this form, I accept AlgoSec's privacy policy Schedule a call

I spend my days talking with customers and prospects around their security solutions, primarily regarding securing application... Hybrid Cloud Security Management Navigating the currents of cybersecurity trends Eric Jeffery 2 min read Eric Jeffery 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. cloudsecurity, hybridcloud, hybridcloudsecurity Tags Share this article 7/13/23 Published I spend my days talking with customers and prospects around their security solutions, primarily regarding securing application connectivity. Every conversation takes its own direction. Nevertheless, I hear similar challenges and goals across industries. I heard from a manufacturing firm that cost constraints require they centralize on Microsoft. An oil and gas company mentioned their needs to align their Operating Technology (OT) environment with their corporate technology solutions (IT). A healthcare organization let me know they were asked to use more Cisco technology and decommission competitive solutions. A financial services firm stated that they were looking to consolidate with zScaler thus eliminating numerous other security solutions. A second financial services firm inquired about AlgoSec Cloud offerings , so they ensure proper monitoring and security for their Cloud deployments. These themes appear and reappear daily, highlighting key trends throughout information security. The older I get, the more I understand how “the more things change, the more they stay the same.” Trends fall perfectly into this colloquialism, as we see organizations routinely move towards newer, hotter, and hopefully more powerful technologies. Working directly with customers of cybersecurity technology, I see similarities with direction and desire for future technical goals. Some of these I’ve seen before, such as centralization and consolidation. Cloud technologies have been around for a decade or more, but I consider this a current trend due to Cloud’s nature and diversity within the technology space. While specific trends come and go, the idea of trends remains the same. Cybersecurity professionals should understand current trends around the industry and see how these movements can improve their security maturity. In the fast-paced realm of cybersecurity, trends constantly emerge and evolve, shaping the landscape in which organizations operate. As I engage with customers and prospects, I uncover recurring patterns and goals that drive the industry forward. Understanding these trends is essential for cybersecurity professionals to strengthen their defenses and adapt to emerging threats. In this blog post, we will dive into the prevailing trends in cybersecurity today, providing insights to help organizations navigate the ever-changing currents. Centralization and consolidation: Empowering organizational control One significant trend is the movement towards centralization and consolidation. Centralization involves bringing technology resources into a unified location or under a cohesive solution. Consolidation focuses on streamlining vendors or technical suites to improve efficiency and reduce costs. For instance, organizations are exploring enterprise licensing options, such as those offered by Microsoft, which provide bundled services like MS Teams, O365, and MS Defender. This consolidation empowers businesses to replace multiple tools with integrated Microsoft technologies, resulting in cost savings and streamlined operations. Enterprise licensing grows in popularity (and could very well be a trend in and of itself) providing organizations an easy way to save money while using a consolidated solution. The most common enterprise license that I run into comes from Microsoft. Businesses that have certain license levels receive additional services such as MS Teams, O365, MS Defender, or other Microsoft technologies at either no or reduced cost. This capability empowers businesses to replace Zoom and WebEx with MS Teams. On the security front companies replace Crowdstrike, McAfee, Norton, and other endpoint protection solutions with MS Defender. For endpoint vulnerability management, Nexpose and Nessus see displacement by MS Defender Vulnerability Management. QRadar, Splunk, Exabeam and other SIEM lose out to Microsoft Sentinel. With a Cisco relationship, companies can potentially save money substituting Illumio or Guardicore in lieu of Cisco Secure Workload (formerly Tetration). With cost management sitting atop the list of priorities for CFO’s , consolidation is a consummate method for technology executives to align with this consideration. Consolidation trends reoccur regularly, especially during financial turmoil. Organizations looking to align technology with financial and business concerns should look to this trend and determine if/where benefits align. After consolidation, I hear a lot about centralization. While customers don’t use this word, at the core, this is what they are looking for. The main technical consideration around this consolidation falls under secure access services edge, known as SASE . SASE inherently centralizes security inside a robust environment that passes customer traffic. COVID-19 introduced a severe need to create secure solutions for remote workers. While SASE began pre-2020, the virus really launched this business (as it did with teleconferencing, a trend back in 2020 and 2021). Entities using SASE pass end user traffic through a central location which provides numerous security services. These offerings include virtual private networks (VPN), proxy, web-filtering, virus protection, spam protection, and many others. Each of these technologies also lends themselves to the consolidation trend tying both movements together. Organizations looking to cut costs procure SASE, align this with numerous information technology teams (networks, Cloud, security, etc.) and double up on trends. Embracing the power of the Cloud The Cloud has revolutionized the information technology landscape, and cyber security is no exception. Organizations are increasingly leveraging Cloud technology as part of their digital transformation journeys. From compliance to network security, application security, and identity management, the Cloud offers a multitude of benefits. It enables organizations to offload hardware maintenance, software upgrades, and data center costs while providing scalability and flexibility. My customers look to not only expand in single clouds, primarily AWS, MS Azure, and Google Cloud, they are going across Clouds creating hybrid deployments. Hybrid solutions enhance the need for security as cross deployments require extensive monitoring and review ensuring zero gaps. Cloud attacks happen more often than ever and with this trend continuing, industry must understand and secure these environments. The importance of staying informed To thrive in the ever-changing world of cyber security, professionals must stay informed about the latest trends. Whether it’s for cost optimization, enhanced security, or delivering innovative services, organizations need to be aware of opportunities to improve their information technology landscapes. Complacency can be detrimental, and understanding the current trends allows businesses to align their goals, enhance operational capacity, and safeguard their digital assets effectively. Centralization, consolidation, and Cloud technologies are at the forefront of today’s trends, offering organizations the means to grow, add value, and protect their data. In the dynamic realm of cyber security, staying ahead of the curve is crucial for organizations seeking to fortify their defenses. Centralization, consolidation, and Cloud technologies are driving the industry forward. By understanding and embracing these trends, businesses can align their strategies, enhance security postures, and capitalize on growth opportunities. As the currents of cyber security trends continue to shift, it’s essential to navigate these waters with agility and adaptability. By doing so, organizations can confidently steer towards success in the ever-evolving world of cyber security. For more information on hybrid cloud security, please check out the latest Managing Cybersecurity podcast. #cloudsecurity #hybridcloud #HybridCloudSecurity Schedule a demo Related Articles Q1 at AlgoSec: What innovations and milestones defined our start to 2026? AlgoSec Reviews Mar 19, 2023 · 2 min read 2025 in review: What innovations and milestones defined AlgoSec’s transformative year in 2025? AlgoSec Reviews Mar 19, 2023 · 2 min read Navigating Compliance in the Cloud AlgoSec Cloud Mar 19, 2023 · 2 min read Speak to one of our experts Speak to one of our experts Work email* First name* Last name* Company* country* Select country... Short answer* By submitting this form, I accept AlgoSec's privacy policy Schedule a call

Jeremiah Cornelius, Technical Lead for Alliances and Partners at AlgoSec, discusses how Cisco Nexus Dashboard Orchestrator (NDO) users can achieve policy-driven application-centric security management with AlgoSec. Leading Edge of the Data Center with AlgoSec and Cisco NDO AlgoSec ASMS A32.6 is our latest release to feature a major technology integration, built upon our well-established collaboration with Cisco — bringing this partnership to the front of the Cisco innovation cycle with... Application Connectivity Management Achieving policy-driven application-centric security management for Cisco Nexus Dashboard Orchestrat Jeremiah Cornelius 2 min read Jeremiah Cornelius Short bio about author here Lorem ipsum dolor sit amet consectetur. Vitae donec tincidunt elementum quam laoreet duis sit enim. Duis mattis velit sit leo diam. Tags Share this article 1/2/24 Published Jeremiah Cornelius, Technical Lead for Alliances and Partners at AlgoSec, discusses how Cisco Nexus Dashboard Orchestrator (NDO) users can achieve policy-driven application-centric security management with AlgoSec. Leading Edge of the Data Center with AlgoSec and Cisco NDO AlgoSec ASMS A32.6 is our latest release to feature a major technology integration, built upon our well-established collaboration with Cisco — bringing this partnership to the front of the Cisco innovation cycle with support for Nexus Dashboard Orchestrator (NDO) . NDO allows Cisco ACI – and legacy-style Data Center Network Management – to operate at scale in a global context, across data center and cloud regions. The AlgoSec solution with NDO brings the power of our intelligent automation and software-defined security features for ACI, including planning, change management, and microsegmentation, to this global scope. I urge you to see what AlgoSec delivers for ACI with multiple use cases, enabling application-mode operation and microsegmentation, and delivering integrated security operations workflows. AlgoSec now brings support for Shadow EPG and Inter-Site Contracts with NDO, to our existing ACI strength. Let’s Change the World by Intent I had my first encounter with Cisco Application Centric Infrastructure in 2014 at a Symantec Vision conference. The original Senior Product Manager and Technical Marketing lead were hosting a discussion about the new results from their recent Insieme acquisition and were eager to onboard new partners with security cases and added operations value. At the time I was promoting the security ecosystem of a different platform vendor, and I have to admit that I didn’t fully understand the tremendous changes that ACI was bringing to security for enterprise connectivity. It’s hard to believe that it’s now seven years since then and that Cisco ACI has mainstreamed software-defined networking — changing the way that network teams had grown used to running their networks and devices since at least the mid-’90s. Since that 2014 introduction, Cisco’s ACI changed the landscape of data center networking by introducing an intent-based approach, over earlier configuration-centric architecture models. This opened the way for accelerated movement by enterprise data centers to meet their requirements for internal cloud deployments, new DevOps and serverless application models, and the extension of these to public clouds for hybrid operation – all within a single networking technology that uses familiar switching elements. Two new, software-defined artifacts make this possible in ACI: End-Point Groups (EPG) and Contracts – individual rules that define characteristics and behavior for an allowed network connection. ACI Is Great, NDO Is Global That’s really where NDO comes into the picture. By now, we have an ACI-driven data center networking infrastructure, with management redundancy for the availability of applications and preserving their intent characteristics. Through the use of an infrastructure built on EPGs and contracts, we can reach from the mobile and desktop to the datacenter and the cloud. This means our next barrier is the sharing of intent-based objects and management operations, beyond the confines of a single data center. We want to do this without clustering types, that depend on the availability risk of individual controllers, and hit other limits for availability and oversight. Instead of labor-intensive and error-prone duplication of data center networks and security in different regions, and for different zones of cloud operation, NDO introduces “stretched” shadow EPGs, and inter-site contracts, for application-centric and intent-based, secure traffic which is agnostic to global topologies – wherever your users and applications need to be. NDO Deployment Topology – Image: Cisco Getting NDO Together with AlgoSec: Policy-Driven, App-Centric Security Management  Having added NDO capability to the formidable shared platform of AlgoSec and Cisco ACI, regional-wide and global policy operations can be executed in confidence with intelligent automation. AlgoSec makes it possible to plan for operations of the Cisco NDO scope of connected fabrics in application-centric mode, unlocking the ACI super-powers for micro-segmentation. This enables a shared model between networking and security teams for zero-trust and defense-in-depth, with accelerated, global-scope, secure application changes at the speed of business demand — within minutes, rather than days or weeks. Change management : For security policy change management this means that workloads may be securely re-located from on-premises to public cloud, under a single and uniform network model and change-management framework — ensuring consistency across multiple clouds and hybrid environments. Visibility : With an NDO-enabled ACI networking infrastructure and AlgoSec’s ASMS, all connectivity can be visualized at multiple levels of detail, across an entire multi-vendor, multi-cloud network. This means that individual security risks can be directly correlated to the assets that are impacted, and a full understanding of the impact by security controls on an application’s availability. Risk and Compliance : It’s possible across all the NDO connected fabrics to identify risk on-premises and through the connected ACI cloud networks, including additional cloud-provider security controls. The AlgoSec solution makes this a self-documenting system for NDO, with detailed reporting and an audit trail of network security changes, related to original business and application requests. This means that you can generate automated compliance reports, supporting a wide range of global regulations, and your own, self-tailored policies. The Road Ahead Cisco NDO is a major technology and AlgoSec is in the early days with our feature introduction, nonetheless, we are delighted and enthusiastic about our early adoption customers. Based on early reports with our Cisco partners, needs will arise for more automation, which would include the “zero-touch” push for policy changes – committing Shadow EPG and Inter-site Contract changes to the orchestrator, as we currently do for ACI APIC. Feedback will also shape a need for automation playbooks and workflows that are most useful in the NDO context, and that we can realize with a full committable policy by the ASMS Horizon Security Analyzer. Contact Us! I encourage anyone interested in NDO and enhancing their operational maturity in aligned network and security operation, to talk to us about our joint solution. We work together with Cisco teams and resellers and will be glad to share more. Schedule a demo Related Articles Q1 at AlgoSec: What innovations and milestones defined our start to 2026? AlgoSec Reviews Mar 19, 2023 · 2 min read 2025 in review: What innovations and milestones defined AlgoSec’s transformative year in 2025? AlgoSec Reviews Mar 19, 2023 · 2 min read Navigating Compliance in the Cloud AlgoSec Cloud Mar 19, 2023 · 2 min read Speak to one of our experts Speak to one of our experts Work email* First name* Last name* Company* country* Select country... Short answer* By submitting this form, I accept AlgoSec's privacy policy Schedule a call

Before I became a Sale Engineer I started my career working in operations and I don’t remember the first time I heard the term zero trust... Zero Trust AlgoSec and Zero-Trust for Healthcare Adolfo Lopez 2 min read Adolfo Lopez 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 2/26/24 Published Before I became a Sale Engineer I started my career working in operations and I don’t remember the first time I heard the term zero trust but I all I knew is that it was very important and everyone was striving to get to that level of security. Today I’ll get into how AlgoSec can help achieve those goals, but first let’s have a quick recap on what zero trust is in the first place. There are countless whitepapers and frameworks that define zero trust much better than I can, but they are also multiple pages long, so I’ll do a quick recap. Traditionally when designing a network you may have different zones and each zone might have different levels of access. In many of these types of designs there is a lot of trust that is given once they are in a certain zone. For example, once someone gets to their workplace at the hospital, the nursing home, the dental center or any other medical office and does all the necessary authentication steps (proper company laptop, credentials, etc…) they potentially have free reign to everything. This is a very simple example and in a real-world scenario there would hopefully be many more safeguards in place. But what does happen in real world scenarios is that devices still manage to get trusted more than they should. And from my own experience and from working with customers this happens way too often. Especially in the healthcare industry this is becoming more and more important. These days there are many different types of medical devices, some that hold sensitive information, some scanning instruments, and some that might even be critical to patient support. More importantly many are connected to some type of network. Because of this level of connectivity, we do need to start shifting toward this idea of zero trust. In healthcare cybersecurity isn’t just a matter of maintaining the network, it’s about maintaining the critical operations of the hospitals running smoothly and patient data safe and secure. Maintaining security policies is critical to achieving zero trust. Below you can see some of the key features that AlgoSec has that can help achieve that goal. Feature Description Security Policy Analysis Analyze existing security policy sets across all parts of the network (on-premises and cloud) with various vendors. Policy Cleanup Identify and remove redundant rules, duplicate rules, and more from the first report. Specific Recommendations Over time, recommendations become more specific, such as identifying unnecessary rules (e.g., a printer talking to a medical device without actual use). Application Perspective Tie firewall rules to actual applications to understand the business function they support, leading to more targeted security policies. Granularity & Visibility Higher level of visibility and granularity in security policies, focusing on specific application flows rather than broad network access. Security Posture by Application View and assess security risks and vulnerabilities at the application level, improving overall security posture. One of my favorite aspects of the AlgoSec platform is that we not only help optimize your security policies, but we also start to look at security from an application perspective. Traditionally, firewall change requests come in and it’s just asking for very specific things, “Source A to Destination B using Protocol C.” But using AlgoSec we tie those rules to actual applications to see what business function this is supporting. By knowing the specific flows and tying them to a specific application this allows us to keep a closer eye on the actual security policies we need to create. This helps with that zero trust journey because having that higher level of visibility and granularity helps to keep the rules more specific. Instead of a change request coming in that is allowing wide open access between two subnets the application can be designed for only the access that is required. It also allows for an overall better view of the security posture. Zero trust, like many other ideas and frameworks in our industry might seem farfetched at first. We ask ourselves, how do we get there or how do we implement without it becoming so cumbersome that we give up on it. I think it’s normal to be a bit pessimistic about achieving the goal and it’s completely fine to look at some projects as moving targets that we might not have a hard deadline on. There usually isn’t a magic bullet that accomplish our goals, especially something like achieving zero trust. Multiple initiatives and projects are necessary. With AlgoSec’s expertise in application connectivity and policy management, we can be a key partner in that journey. Schedule a demo Related Articles Q1 at AlgoSec: What innovations and milestones defined our start to 2026? AlgoSec Reviews Mar 19, 2023 · 2 min read 2025 in review: What innovations and milestones defined AlgoSec’s transformative year in 2025? AlgoSec Reviews Mar 19, 2023 · 2 min read Navigating Compliance in the Cloud AlgoSec Cloud Mar 19, 2023 · 2 min read Speak to one of our experts Speak to one of our experts Work email* First name* Last name* Company* country* Select country... Short answer* By submitting this form, I accept AlgoSec's privacy policy Schedule a call