Search results

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

Securely accelerate application delivery by automating application connectivity and security policy across the hybrid network estate. 솔루션 환영합니다! 클라우드 보안 통제 및 사내 구축 방화벽에 대한 네트워크 보안 정책의 관리는 세심한 균형을 요하는 작업입니다. 한편으로 공격 범위(attack surface)라고 불리는 외부 위협에 대한 노출을 최소화하여 리스크를 줄여야 하며, 다른 한편으로는 중요한 비즈니스 애플리케이션에 대한 연결성을 제공함으로써 생산성을 향상시켜야 합니다. 하지만, 네트워크 보안 정책 관리 프로세스는 늘 복잡하고 오류가 많아 시간 소모적이었습니다. 이제는 더 이상 그럴 필요가 없습니다. AlgoSec은 사내 (On-premise) 및 클라우드 상의 네트워크 보안 정책 관리를 간소화하고 자동화하여 기업의 민첩성과 보안을 강화하고 언제나 규정을 준수하는 환경을 제공합니다. 보안 정책 관리에 대한 독자적인 라이프사이클 접근방식 AlgoSec은 보안 정책 라이프사이클을 전반적으로 관리하여 고객의 비즈니스 애플리케이션에 대한 지속적이며 안전한 연결성을 제공한다는 점에서 독보적입니다. 단일 창을 통해 애플리케이션 연결성 요구사항을 자동으로 검색할 수 있고, 리스크를 사전에 분석하며, 네트워크 보안 변경 계획을 신속하게 수립하여 실행할 수 있으며 방화벽 규칙을 안전하게 제거할 수 있습니다. 아울러, 고객의 이기종 환경 전반에 걸쳐 이 모든 작업이 완벽히 조화를 이루어 자동으로 원활하게 이루어집니다. AlgoSec 솔루션을 이용하면 클라우드, SDN, 사내망 (on-premise)에 걸쳐 네트워크 보안 정책관리를 통합 할수 있습니다 지속적으로 규제를 준수하고, 방화벽 감사 준비에 소요되는 시간과 비용을 현저히 줄일 수 있습니다 신속하고 안전하게 애플리케이션 연결성을 제공하고, 네트워크 관련 가동중단을 방지할 수 있습니다 보안, 네트워크 및 애플리케이션 팀 간의 연계와 DevSecOps를 발전시킵니다 방화벽 변경 관리를 자동화하고 구성 오류를 제거할 수 있습니다 정확한 보안 구성 및 효과적인 네트워크 분할 을 통해 리스크를 줄일 수 있습니다 솔루션 보안 정책 네트워크 분석 더 많은 정보 AlgoSec Firewall Analyzer 보안 정책 변경 자동화 더 많은 정보 AlgoSec FireFlow ROI 계산기 AlgoSec 솔루션 브로슈어 문의하기 Algosec Korea 탁정수 지사장 Phone: +82-10-8994-7121
Email: [email protected] Algosec Korea 정욱 이사 (Sales Engineer) Phone: +82-10-9953-5717
Email: [email protected] 관련 링크 AlgoSec 솔루션 브로슈어 Schedule time with one of our experts

CISCO ACI & ALGOSEC Holistic policy management for ACI and the hybrid network Download PDF Schedule time with one of our experts Schedule time with one of our experts Work email* First name* Last name* Company* country* Select country... Short answer* By submitting this form, I accept AlgoSec's privacy policy Continue

Knowing how to select and position security capabilities in different cloud deployment models is critical to comprehensive security... Cloud Security Understanding Security Considerations in IaaS/PaaS/SaaS Deployments Rony Moshkovich 2 min read Rony Moshkovich Short bio about author here Lorem ipsum dolor sit amet consectetur. Vitae donec tincidunt elementum quam laoreet duis sit enim. Duis mattis velit sit leo diam. Tags Share this article 11/24/22 Published Knowing how to select and position security capabilities in different cloud deployment models is critical to comprehensive security across your organization. Implementing the right pattern allows you to protect the confidentiality, integrity, and availability of cloud data assets. It can also improve incident response to security threats. Additionally, security teams and cloud security architects no longer have to rely on pre-set security templates or approaches built for on-premises environments. Instead, they must adapt to the specific security demands of the cloud and integrate them with the overall cloud strategy. This can be accomplished by re-evaluating defense mechanisms and combining cloud-native security and vendor tools. Here, we’ll break down the security requirements and best practices for cloud service models like IaaS, PaaS, and SaaS. Do you have cloud security architects on board? We’ll also cover their roles and the importance of leveraging native security tools specific to each model. Managing Separation of Responsibilities with the Cloud Service Provider Secure cloud deployments start with understanding responsibilities. Where do you stand, and what is expected of you? There are certain security responsibilities the cloud security provider takes care of and those that the customer handles. This division of responsibilities means adjusting focus and using different measures to ensure security is necessary. Therefore, organizations must consider implementing compensating controls and alternative security measures to make up for any limitations in the cloud service provider’s security offerings. Security Considerations for SaaS (Software-as-a-Service) Deployments The specific security requirements in SaaS deployments may vary between services. However, it’s important to consider the following areas: Data protection During cloud deployments, protecting data assets is a tough nut to crack for many organizations. As a SaaS provider, ensuring data protection is crucial because you handle and store sensitive customer data. Encryption must be implemented for data in transit and at rest. Protecting data at rest is the cloud provider’s responsibility, whereas you are responsible for data in transit. The cloud provider implements security measures like encryption, access controls, and physical security to protect the data stored in their infrastructure. On the other hand, it’s your responsibility to implement secure communication protocols like encryption, ensuring data remains protected when it moves between your SaaS application. Additionally, best practice solutions may offer you the option of managing your encryption keys so that cloud operations staff cannot decrypt customer data. Interfacing with the Cloud Service There are a number of security considerations to keep in mind when interacting with a SaaS deployment. These include validating data inputs, implementing secure APIs, and securing communication channels. It’s crucial to use secure protocols like HTTPS and to ensure that the necessary authentication and authorization mechanisms are in place. You may also want to review and monitor access logs frequently to spot and address any suspicious activity. Application Security in SaaS During SaaS deployments, it’s essential to ensure application security. For instance, secure coding practices, continuous vulnerability assessments, and comprehensive application testing all contribute to effective SaaS application security. Cross-site scripting (XSS) and SQL injection are some of the common web application cyber-attacks today. You can improve the application’s security posture by implementing the right input validation, regular security patches from the SaaS provider, and web application firewalls (WAFs). Cloud Identity and Access Controls Here, you must define how cloud services will integrate and federate with existing enterprise identity and access management (IAM) systems. This ensures a consistent and secure access control framework. Implementing strong authentication mechanisms like multifactor authentication (MFA) and enforcing proper access controls based on roles and responsibilities are necessary security requirements. You should also consider using Cloud Access Security Broker (CASB) tools to provide adaptive and risk-based access controls. Regulatory Compliance Using a cloud service doesn’t exempt one from regulatory compliance, and cloud architects must design the SaaS architecture to align with these requirements. But why are these stringent requirements there in the first place? The purpose of these regulations is to protect consumer privacy by enforcing confidentiality, integrity, availability, and accountability. So, achieving compliance means you meet these regulations. It demonstrates that your applications and tech stack maintain secure privacy levels. Failure to comply could cost money in the form of fines, legal action, and a damaged reputation. You don’t want that. Security Considerations for PaaS (Platform-as-a-Service) Deployments PaaS security considerations during deployments will address all the SaaS areas. But as a PaaS customer, there are slight differences you should know. For example, more options exist to configure how data is protected and who can do what with it. As such, the responsibility of user permissions may be given to you. On the other hand, some PaaS providers may have built-in tools and mechanisms for managing user permissions. So, what are the other key areas you want to address to ensure a secure environment for PaaS deployments? We’ll start with the application security. Application Security The customer is responsible for securing the applications they build and deploy on the PaaS platform. Securing application platforms is necessary, and cloud architects must ensure this from the design and development stage. So, what do you do to ensure application security? It all starts from the onset. From secure coding practices, addressing application vulnerabilities, and conducting regular security testing. You’ll often find that most security vulnerabilities are introduced from the early stages of software development. If you can identify and fix potential flaws using penetration testing and threat modeling practices, you’re on your way to successful deployment. Data Security PaaS cloud security deployments offer more flexibility and allow customers control over their data and user entitlements. What this means is you can build and deploy your own applications on the platform. You can configure security measures and controls within your applications by defining who has access to applications, what they can do, and how data is protected. Here, cloud security architects and security teams can ensure data classification and access controls, determining appropriate encryption keys management practices, secure data integration and APIs, and data governance. Ultimately, configuring data protection mechanisms and user permissions provides customers with greater customization and control. Platform Security The platform itself, including the operating system, underlying infrastructure, data centers, and middleware, need to be protected. This is the responsibility of the PaaS provider. They must ensure that the components that keep the platform up are functional at all times. Network Security In PaaS environments, identity and roles are primarily used for network security to determine access to resources and data in the PaaS platform. As such, the most important factor to consider in this case is verifying the user identity and managing access based on their roles and permissions. Rather than relying on traditional network security measures like perimeter controls, IDS/IPS, and traffic monitoring, there is a shift to user-centric access controls. Security Considerations for IaaS (Infrastructure-as-a-Service) Cloud Deployments When it comes to application and software security, IaaS security during cloud deployment is similar. If you’re an IaaS customer, there are slight differences in how IaaS cloud deployment is handled. For example, while the cloud provider handles the hypervisor or virtualized layer, everything else is the customers’ responsibility. So, you must secure the cloud deployment by implementing appropriate security measures to safeguard their applications and data. Due to different deployment patterns, some security tools that work well for SaaS may not be suitable for IaaS. For example, we discussed how CASB could be excellent for cloud identity, data, and access controls in SaaS applications. However, this may not be effective in IaaS environments. Your cloud architects and security teams must understand these differences when deploying IaaS. They should consider alternative or additional security measures in certain areas to ensure more robust security during cloud deployments. These areas are: Access Management IaaS deployment requires you to consider several identity and access management (IAM) dimensions. For example, cloud architects must consider access to the operating system, including applications and middleware installed on them. Additionally, they must also consider privileged access, such as root or administrative access at the OS level. Keep in mind that IaaS has additional access layers. These consist of access to the IaaS console and other cloud provider features that may offer insights about or impact the operation of cloud resources. For example, key management and auditing and resource configuration and hardening. It’s important to clarify who has access to these areas and what they can do. Regular Patching There are more responsibilities for you. The IaaS customer is responsible for keeping workloads updated and maintained. This typically includes the OS itself and any additional software installed on the virtual machines. Therefore, cloud architects must apply the same vigilance to cloud workloads as they would to on-premises servers regarding patching and maintenance. This ensures proactive, consistent, and timely updates that ensure the security and stability of cloud workloads. Network Security IaaS customers must configure and manage security mechanisms within their virtual networks. This includes setting firewalls, using intrusion detection and intrusion prevention systems (IDS/IPS), establishing secure connections (VPN), and network monitoring. On the other hand, the cloud provider ensures network security for the underlying network infrastructure, like routers and switches. They also ensure physical security by protecting network infrastructure from unauthorized access. Data Protection While IaaS providers ensure the physical security of data centers, IaaS customers must secure their own data in the IaaS environment. They need to protect data stored in databases, virtual machines (VMs), and any other storage system provisioned by the IaaS provider. Some IaaS providers, especially large ones, offer encryption capabilities for the VMs created on their platform. This feature is typically free or low-priced. It’s up to you to decide whether managing your own encryption keys is more effective or to choose the provider’s offerings. If you decide to go for this feature, it’s important to clarify how encrypting data at rest may affect other services from the IaaS provider, such as backup and recovery. Leveraging Native Cloud Security Tools Just like the encryption feature, some cloud service providers offer a range of native tools to help customers enforce effective security. These tools are available for IaaS, PaaS, and SaaS cloud services. While customers may decide not to use them, the low financial and operational impact of native cloud security tools on businesses makes them a smart decision. It allows you to address several security requirements quickly and easily due to seamless control integration. However, it’s still important to decide which controls are useful and where they are needed. Conclusion Cloud security architecture is always evolving. And this continuous change makes cloud environments more complex and dynamic. From misconfigurations to data loss, many challenges can make secure cloud deployments for IaaS, PaaS, and SaaS services more challenging. Prevasio, an AlgoSec company, is your trusted cloud security partner that helps your organization streamline cloud deployments. Our cloud-native application provides increased risk visibility and control over security and compliance requirements. Contact us now to learn more about how you can expedite your cloud security operations. Schedule a demo Related Articles 2025 in review: What innovations and milestones defined AlgoSec’s transformative year in 2025? AlgoSec Reviews Mar 19, 2023 · 2 min read Navigating Compliance in the Cloud AlgoSec Cloud Mar 19, 2023 · 2 min read 5 Multi-Cloud Environments Cloud Security Mar 19, 2023 · 2 min read Speak to one of our experts Speak to one of our experts Work email* First name* Last name* Company* country* Select country... Short answer* By submitting this form, I accept AlgoSec's privacy policy Schedule a call

Compared to on-premises data storage, cloud computing comes with a lot of benefits. On-demand access to company data, flexibility, and... Cloud Security What is a Cloud Security Assessment? (and How to Perform One) Rony Moshkovich 2 min read Rony Moshkovich Short bio about author here Lorem ipsum dolor sit amet consectetur. Vitae donec tincidunt elementum quam laoreet duis sit enim. Duis mattis velit sit leo diam. Tags Share this article 7/12/23 Published Compared to on-premises data storage, cloud computing comes with a lot of benefits. On-demand access to company data, flexibility, and fast collaboration are just a few. But along with these advantages come increased security risks. To manage them, companies should invest in regular cloud security assessments. What Is a Cloud Security Risk Assessment? A cloud security assessment evaluates the potential vulnerabilities of an organization’s cloud environment. These assessments are essential to mitigate risks and ensure the continued security of cloud-based systems. By looking at cloud applications, services, and data, companies can better understand the biggest threats to their cloud environment. By managing these threats, businesses can avoid costly workflow interruptions. A security assessment can be done by an organization’s internal security team or by an outside security expert. This can happen one time only, or it can be done regularly as part of an organization’s overall cybersecurity plan. How Do Cloud Security Risk Assessments Protect Your Business? Cloud-based systems and services are an essential part of most businesses nowadays. Unfortunately, what makes them convenient is also what makes them vulnerable to security threats. A cloud security risk assessment helps organizations find out what might go wrong and prevent it from happening. It also helps with prioritizing and managing the most serious issues before they become full-on data breaches. One way assessments do this is by identifying misconfigurations. Cloud misconfigurations are behind many security breaches. They result from errors introduced by network engineers working on early cloud systems. A cloud security assessment earmarks these and other outmoded security features for repair. What’s more, cloud security assessments identify third-party risks from APIs or plugins. When your company identifies risks and manages permissions, you keep your cloud environment safe. By mitigating third-party risks, you can still benefit from outside vendors. Of course, none of this information is valuable without employee education. Employees need to know about risks and how to stop them; this is the best way to reduce the number of security incidents caused by human error or carelessness. To put it simply, a cloud security assessment helps your business run smoothly. When you know the risks your company faces and can manage them, you reduce the impact of security-related incidents. That means you can recover faster and get back to work sooner. 7 Benefits of Cloud Security Risk Assessments Cloud security risk assessments provide lots of benefits. They can help you: Improve cloud security posture . Understanding the ins and outs of a cloud-based system helps organizations plan better. For example, they can modify their security budget or improve their risk management strategy based on the results. Uncover security vulnerabilities . Cloud security assessments pinpoint weak spots. This includes misconfigurations , access control issues, and missing multi-factor authentications (MFAs). Once identified, organizations can fix the issues and avoid security breaches. Develop a more secure multi-cloud environment . Most organizations use multiple cloud platforms. Usually, this involves private or public clouds or a combination of both. This is ideal from a financial and agility perspective. But every extra layer in a cloud environment introduces potential risks. A cloud security assessment is essential in identifying these cross-cloud threats. Achieve compliance with industry standards and regulatory bodies . Ensuring compliance with GDPR, PCI-DSS, and HIPAA helps protect organizations from millions of dollars of potential fines . Manage your reputation. A sensitive data leak or other cloud security incident damages a company’s reputation. Think of companies like Target, Facebook, and LinkedIn. All have faced backlash after security breaches . Conducting cloud security assessments shows that organizations value customer and stakeholder privacy. Detect past threats . A cloud security assessment looks for things that might be wrong with the way your cloud system is set up. It can also help you find out if there have been any past security problems. By doing this, you can see if someone has tried to tamper with the security of your cloud system in the past, which could signal a bigger problem. Increase efficiency . Cloud security assessments show you which security measures are working and which aren’t. By getting rid of security tools that aren’t needed, employees have more time to work on other tasks. Cost savings . The most compelling reason to run a cloud security assessment is that it helps save money. Cost savings come from eliminating unnecessary security measures and from missed work time due to breaches. What Risks Do Cloud Security Assessments Look For? Cloud security assessments focus on six areas to identify security vulnerabilities in your cloud infrastructure: overall security posture, access control and management, incident management, data protection, network security, and risk management and compliance. Some specific risks cloud security assessments look for include: Cloud Misconfigurations Misconfigurations are one of the most common threats to overall security posture. In fact, McAfee’s enterprise security study found that enterprises experience 3,500 security incidents per month because of misconfigurations. From improperly stored passwords to insecure automated backups, misconfiguration issues are everywhere. Because they’re so common, fixing this issue alone can reduce the risk of a security breach by up to 80%, according to Gartner . Access Control and Management Problems This assessment also highlights ineffective access control and management. One way it does this is by identifying excessive network permissions. Without the proper guardrails (like data segmentation) in place, an organization’s attack surface is greater. Plus, its data is at risk from internal and external threats. If an employee has too much access to a company’s network, they might accidentally delete or change important information. This could cause unintended system problems. Additionally, if hackers get access to the company’s network, they could easily steal important data. Cloud security assessments also look at credentials as part of user account management. A system that uses only static credentials for users or cloud workloads is a system at risk. Without multifactor authentication (MFA) in place, hackers can gain access to your system and expose your data. Improper Incident Management and Logging When it comes to incident management, a cloud security assessment can reveal insufficient or improper logging — problems that make detecting malicious activities more difficult. Left unchecked, the damage is more severe, making recovery more time-consuming and expensive. Insufficient Data and Network Security Data protection and network security go hand in hand. Without proper network controls in place (for example firewalls and intrusion detection), data in the cloud is vulnerable to attack. A cloud security assessment can identify gaps in both areas. Based on the results of a cloud security assessment, a company can make a risk management plan to help them react as quickly and effectively as possible in the event of an attack. The last aspect of cloud security the assessment looks at is compliance with industry standards. 7 Steps To Perform a Cloud Security Assessment The main components of cloud security assessments include: Identifying your cloud-based assets, discovering vulnerabilities through testing, generating recommendations, and retesting once the issues have been addressed. The steps to performing a cloud security assessment are as follows: Step One: Define the project Get a picture of your cloud environment. Look at your cloud service providers (CSPs), third-party apps, and current security tools. First, decide which parts of your system will be evaluated. Next, look at the type of data you’re handling or storing. Then consider the regulations your business must follow. Step Two: Identify potential threats Look at both internal and external threats to your cloud-based system. This could include endpoint security, misconfigurations, access control issues, data breaches, and more. Then figure out how likely each type of attack is. Finally, determine what impact each attack would have on your business operations. Step Three: Examine your current security system Look for vulnerabilities in your existing cloud security. In particular, pay attention to access controls, encryption, and network security. Step Four: Test Penetration testing, port scanners, and vulnerability scanners are used to find weaknesses in your cloud environment that were missed during the original risk assessment. Step Five: Analyze Look at the results and determine which weaknesses need immediate attention. Deal with the issues that will have the biggest impact on your business first. Then, focus on the issues most likely to occur. Finish by handling lower-priority threats. Step Six: Develop an action plan Come up with a time-bound remediation plan. This plan should spell out how your organization will deal with each security vulnerability. Assign roles and responsibilities as part of your incident response program. Depending on the results, this could include updating firewalls, monitoring traffic logs, and limiting access control. Step Seven: Maintain Cloud security assessments can be done as a one-off, but it’s much better to monitor your systems regularly. Frequent monitoring improves your organization’s threat intelligence. It also helps you identify and respond to new threats in real time. Getting Help With Your Cloud Security Assessment Cloud security assessment tools are used to identify vulnerabilities in a cloud infrastructure which could lead to data loss or compromise by attackers. As an agentless cloud security posture management (CSPM) tool , Prevasio helps identify and fix security threats across all your cloud assets in minutes. Our deep cloud scan checks for security weaknesses, malware, and compliance. This helps ensure that your company’s cloud environment is protected against potential risks. But any CSPM can do that . Prevasio is the only solution that provides container security dynamic behavior analysis. Our technology spots hidden backdoors in your container environments. It also identifies supply chain attack risks. Paired with our container security static analysis for vulnerabilities and malware, your containers will never be safer. Our CSPM works across multi-cloud, multi-accounts, cloud-native services , and cloud assets. Whether you’re using Microsoft Azure, S3 buckets in AWS, or Cosmos DB in GCP, Prevasio is the security system your company has been looking for. But we do more than identify security threats. We increase your team’s efficiency. How? By providing a prioritized list of cloud risks ranked according to CIS benchmarks. That means no more uncertainty about what needs to get done. Our easy-to-understand results help your team concentrate on the most important things. This saves time and money by reducing the need for extra administrative work. A Final Word on Cloud Security Assessments Performing regular cloud security assessments helps your business spot security issues before they become major problems. When you reinforce your security controls and define your incident response plan, you make your organization more efficient. Plus, you keep things going even when issues arise. Put together, these proactive measures can save you money. Sign up today and see how Prevasio can help your team ! FAQs About Cloud Security Assessments What are the four areas of cloud security? The four pillars of cloud security are data availability, data confidentiality, data integrity, and regulatory compliance. What is included in a security assessment? Cloud security assessments include: Identifying your cloud-based assets, discovering vulnerabilities through testing, generating recommendations, and retesting once the issues have been addressed. Schedule a demo Related Articles 2025 in review: What innovations and milestones defined AlgoSec’s transformative year in 2025? AlgoSec Reviews Mar 19, 2023 · 2 min read Navigating Compliance in the Cloud AlgoSec Cloud Mar 19, 2023 · 2 min read 5 Multi-Cloud Environments Cloud Security Mar 19, 2023 · 2 min read Speak to one of our experts Speak to one of our experts Work email* First name* Last name* Company* country* Select country... Short answer* By submitting this form, I accept AlgoSec's privacy policy Schedule a call

Regulations and compliance for the data center – A Day in the Life Download PDF Schedule time with one of our experts Schedule time with one of our experts Work email* First name* Last name* Company* country* Select country... Short answer* By submitting this form, I accept AlgoSec's privacy policy Continue

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

Discover AlgoSec's transformative 2024 journey: innovation in secure connectivity, industry leadership, and a bold vision for an empowered, Network Security 2024 in review: A transformative year for AlgoSec in secure application connectivity Adel Osta Dadan 2 min read Adel Osta Dadan Short bio about author here Lorem ipsum dolor sit amet consectetur. Vitae donec tincidunt elementum quam laoreet duis sit enim. Duis mattis velit sit leo diam. Tags Share this article 12/16/24 Published As we close out 2024, I find myself reflecting on what has truly been a transformative journey for AlgoSec . This year has been filled with ground-breaking innovation, meaningful industry recognition, and a deep commitment to our vision of secure application connectivity. It has been a year where every challenge was met with determination, every milestone became a stepping-stone toward a greater future, and every success strengthened our resolve to lead in secure connectivity. Q1: Redefining secure application connectivity. We started the year by challenging traditional approaches to secure application connectivity, setting the tone for everything that followed. State of Network Security Report : The release of our State of Network Security Report was the first major milestone, quickly becoming a cornerstone of our thought leadership. This report highlighted major trends such as the enduring importance of hybrid networks and the growing shift toward multi-cloud strategies. We emphasized that security could—and should—be a driver of digital transformation. The findings made it clear that advanced tools like SD-WAN and SASE are no longer optional but essential for navigating today’s increasingly complex connectivity landscape. Launch of AlgoSec A33: In March, we launched AlgoSec A33, an application-first approach to security management. This was not just another product release; it was a clear statement of our belief that security should be an enabler of business growth. With A33, we offered seamless integration into business processes, aligning security with broader organizational goals. This launch symbolized our commitment to making secure application connectivity the foundation for organizational success. Q2: Advancing security automation and building connections. Building on the momentum from Q1, the second quarter was about advancing our automation capabilities and strengthening connections within our community. Recognition from GigaOm and Gartner : During Q2, we received meaningful recognition from GigaOm and Gartner, being named an Established Vendor in Gartner Peer Insights Voice of the Customer for Secure Connectivity Automation Platforms. This recognition validated our dedication to combining intelligent automation with human expertise, simplifying network security across increasingly complex multi-cloud environments. It was a proud moment that affirmed our efforts and pushed us to do even more. Industry Conversations on Secure Connectivity: We also took the lead in important industry conversations during this period. From enhancing visibility to tackling the challenges of multi-cloud security, AlgoSec was at the forefront—delivering solutions that drove operational efficiency while addressing the real-world challenges faced by our customers. These conversations reinforced our position as a proactive leader committed to shaping the future of secure connectivity. Q3: Setting new standards in secure connectivity. Moving into Q3, our goal was to push the boundaries further and set new industry standards for secure connectivity. Introduction of Security Application Connectivity. Anywhere (SACA): One of the major highlights of the third quarter was the introduction of our Security Application Connectivity Anyware (SACA) framework. SACA embodied our vision that secure connectivity is fundamental to digital transformation. By providing our customers with confidence in their application flows—without sacrificing performance or agility—we enabled them to innovate with assurance. AlgoSummit 2024: In September, we hosted AlgoSummit 2024—our flagship event that brought together customers, partners, and industry experts. AlgoSummit was not just an event but a collaborative platform for shared learning and innovation. Together, we explored the evolving landscape of secure connectivity in hybrid and multi-cloud environments. This summit further solidified AlgoSec's role as a visionary leader in the industry, committed to both solving today’s challenges and anticipating those of tomorrow. Q4: Expanding Zero Trust and navigating regulatory changes. As we entered the final quarter, our focus shifted to expanding our Zero Trust offerings and helping customers prepare for upcoming regulatory changes. Zero Trust Architecture Expansion: We made significant strides in advancing our Zero Trust network architecture initiatives in Q4. As hybrid environments grow more complex, we understood the need to simplify Zero Trust adoption for our customers. By leveraging both micro and macro-segmentation strategies, we offered a streamlined, application-centric approach that provided greater visibility and control—ensuring that connectivity remained secure, segmented, and compliant. Navigating DORA Compliance : Another key focus for Q4 was helping our customers navigate the requirements of the Digital Operational Resilience Act (DORA). With the compliance deadline fast approaching, we used our intelligent automation tools to make the transition as smooth as possible. Our solutions offered comprehensive visibility, automated risk assessments, and policy recertification, allowing financial institutions to meet DORA’s stringent standards confidently and strengthen their resilience. Recognition for innovation and ethical leadership Throughout the year, our commitment to responsible innovation and ethical leadership did not go unnoticed. SC Awards Finalist in Application Security: Being named a finalist in the SC Awards for Application Security was a significant milestone, reaffirming our dedication to protecting the applications that drive business growth and innovation. Top InfoSec Innovator Award from CyberDefense Magazine: In November, we were recognized as a Top InfoSec Innovator by CyberDefense Magazine. This accolade underscored our focus on ethical innovation—delivering security solutions that are trustworthy, responsible, and aligned with global standards. Accolades in Network and Application Security : Additionally, we were named a Hot Company in Secure Application Connectivity and recognized as the Most Innovative in Application Security. These awards were not just acknowledgments of our technology but a testament to our ongoing commitment to setting new standards of transparency, accountability, and secure connectivity. Cisco Meraki Marketplace Tech Partner of the Month : In October 2024, we were honored as the Cisco Meraki Marketplace Tech Partner of the Month based on our continued innovation and dedication to application security . This recognition highlights our ability to deliver holistic visibility, automate security policy changes, reduce risks, and ensure continuous compliance through seamless integration with Cisco Meraki solutions. Looking to the future: building on the foundations of 2024 Reflecting on 2024, it’s clear that this has been a year of significant growth, innovation, and resilience. The lessons we’ve learned and the progress we’ve made have laid a strong foundation for the future. As we look ahead to 2025, our mission remains clear: to continue providing application-centric security solutions that not only protect but also empower our customers to achieve their strategic objectives. I am incredibly grateful for the dedication of our team, the trust our customers have placed in us, and the opportunity to continue shaping the future of secure connectivity. Here’s to another year of impactful innovation, collaboration, and leadership as we step confidently into 2025. Schedule a demo Related Articles 2025 in review: What innovations and milestones defined AlgoSec’s transformative year in 2025? AlgoSec Reviews Mar 19, 2023 · 2 min read Navigating Compliance in the Cloud AlgoSec Cloud Mar 19, 2023 · 2 min read 5 Multi-Cloud Environments Cloud Security Mar 19, 2023 · 2 min read Speak to one of our experts Speak to one of our experts Work email* First name* Last name* Company* country* Select country... Short answer* By submitting this form, I accept AlgoSec's privacy policy Schedule a call

Since 2005 we offer the industry’s only money back guarantee If we do not meet your expectations you have the right to cancel the purchase Money-Back Guarantee At AlgoSec we are passionate about customer satisfaction. Therefore, since 2005 we have offered the industry’s only money-back-guarantee. If we do not meet your expectations you have the right to cancel your software purchase and get your money back. More importantly, you decide whether to invoke the money-back guarantee. You are the sole judge. The only condition is that you do it within a reasonable timeline. As outlined below. This way you can ensure that the AlgoSec solution works across your entire estate, not just in your lab – without assuming any financial risk. Money-Back Guarantee Terms The terms of the money-back guarantee are outlined in the table. They depend on the deal size and whether or not the product was evaluated in the customer’s lab. Note: Make sure the terms of the Money Back Guarantee are included in your project proposal. Product Deal Size Less than $300K $300K-$1M More than $1M Product Purchased
WITHOUT an Evaluation 60 Days 90 Days 120 Days Product Purchased
AFTER an Evaluation 30 Days 45 Days 60 Days Contact sales At AlgoSec, Customer Satisfaction Starts at the Top Yuval Baron Chairman and CEO “When AlgoSec was only 2 years old we initiated the industry’s only money back guarantee. Nowadays, we have over 1,800 customers and the AlgoSec team still shares the same desire and passion to make sure they are all happy.” Contact sales Work email* First name* Last name* Company* country* Select country... Short answer* By submitting this form, I accept AlgoSec's privacy policy Continue

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

The transition to cloud-based environments has ushered in unparalleled efficiency, scalability, and innovation. However, it has also... Hybrid Cloud Security Management Unveiling best practices for a resilient cloud security strategy Malcom Sargla 2 min read Malcom Sargla Short bio about author here Lorem ipsum dolor sit amet consectetur. Vitae donec tincidunt elementum quam laoreet duis sit enim. Duis mattis velit sit leo diam. Tags Share this article 8/30/23 Published The transition to cloud-based environments has ushered in unparalleled efficiency, scalability, and innovation. However, it has also magnified the importance of fortifying our digital fortresses against an array of potential risks. Considering the increasing reliance on cloud computing, it’s important to find the best practices and strategies that organizations can adopt to enhance their cloud security posture and mitigate the risks associated with cloud-based environments. Navigating the Cloud Security Landscape As organizations race to seize the transformative potential of the cloud, they are faced with a series of profound decisions. Each step forward, though laden with promise, demands a profound understanding of the evolving cloud security landscape. Choosing your guardian: Cloud providers’ security Selecting a cloud provider marks a pivotal choice. The giants of the cloud – AWS, GCP, Azure, Oracle, and IBM – have honed their commitment to delivering secure platforms. These titans weave intricate layers of cutting-edge security technologies and artificial intelligence into their infrastructures, assuring an ironclad foundation for their clients. Here, diversity shines as a beacon of strength. Many organizations, mindful of fault domains and corporate governance, choose a multi-cloud approach. This approach is further empowered by solutions like AlgoSec, streamlining security management across diverse cloud estates. The hybrid conundrum: Security beyond the divide The debate over a cloud-only versus hybrid deployment churns with vigor. It’s not merely a technical decision; it’s an embodiment of an organization’s security philosophy. Retaining an on-premises presence offers a sense of comfort, an insurance policy for vital intellectual property. To navigate the hybrid landscape successfully, a unified security approach is imperative. A single-pane view that seamlessly spans visibility, risk assessment, compliance, and intelligent policy automation is the rudder that guides this ship. Blueprint for secure migration In the digital world, where data and applications surge like currents, migrating to the cloud demands meticulous planning and a steadfast commitment to security. Application Dependency: The heartbeat of cloud migration As applications metamorphose, they weave intricate relationships with their ecosystem. Moving them recklessly can disrupt the very heartbeat of your organization. Consider AlgoSec’s partnerships with Cisco Secure Workload, Illumio, and Guardicore. Through this synergy, applications are mapped, relationships dissected, and policies laid bare. These insights power intelligent remediation, ensuring that policies serve the application, not risk its integrity. The goldilocks move: Finding the right application components When migrating applications, precision is paramount. Moving the right components in tandem is akin to choreographing a symphony. Avoiding ‘hair-pinning’ between cloud and on-premises domains is key to preserving user experience and mitigating egress traffic costs. The mantra: migrate high-dependent application tiers in harmonious unison. Purifying the legacy: Pruning unneeded policies Before the embacing the cloud, make sure to clean your digital canvas. Rid it of unneeded policies, unburden the legacy baggage, and craft a secure foundation. AlgoSec advocates a risk-mitigation approach. Tune, optimize, and refine policies. This digital spring-cleaning ensures that your cloud journey is unmarred by relics of the past. The promise of a secure sky As the digital horizon stretches ever farther, cloud security ascends as both a challenge and an opportunity. With each step we take towards a cloud-powered future, we must arm ourselves with knowledge, tools, and practices that will safeguard our data, applications, and innovations. So, the question of how to mitigate risk becomes not just a query, but a clarion call. A call to weave security into the very fabric of our cloud endeavors. A call to adopt the best practices, to forge ahead with a robust strategy, and to ensure that the cloud’s promise of a brighter future is matched only by its commitment to security. Schedule a demo Related Articles 2025 in review: What innovations and milestones defined AlgoSec’s transformative year in 2025? AlgoSec Reviews Mar 19, 2023 · 2 min read Navigating Compliance in the Cloud AlgoSec Cloud Mar 19, 2023 · 2 min read 5 Multi-Cloud Environments Cloud Security Mar 19, 2023 · 2 min read Speak to one of our experts Speak to one of our experts Work email* First name* Last name* Company* country* Select country... Short answer* By submitting this form, I accept AlgoSec's privacy policy Schedule a call

Executive brochure – The business benefits of AlgoSec Horizon platform Brochure Download PDF Schedule time with one of our experts Schedule time with one of our experts Work email* First name* Last name* Company* country* Select country... Short answer* By submitting this form, I accept AlgoSec's privacy policy Continue