Search results

SaaS SLA Download PDF Download PDF Add a Title Add a Title Add a Title 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

Explore Algosec's customer success stories to see how organizations worldwide improve security, compliance, and efficiency with our solutions. NCR ACCELERATES TOWARDS ZERO-TRUST Organization NCR Global Industry Financial Services Headquarters Georgia, USA Download case study Share Customer
success stories “AlgoSec helps us be vendor-agnostic and understand our full security posture to lead us down this journey to achieve zero-trust.” Scott Theriault, Global Manager Network Perimeter Security NCR Corporation Background NCR Corporation is a leading global point-of-sale (POS) provider for restaurants, retailers, and banks and a provider of multi-vendor ATM software. Headquartered in Atlanta, Georgia, NCR has over 36,000 employees in 160 countries, and solutions are distributed in 141 countries. As NCR expands into public cloud platforms such as AWS, they require consistent visibility and security policy management across both on-premises and cloud environments. The challenge NCR needed to connect its DevOps pipeline with its network security. With over 4,500 policy changes made annually, it was difficult to securely manage their entire networking and security environment while being responsive to application owners but still achieve zero trust. Strategically, they were aiming to automate and orchestrate security policy changes across their entire hybrid network, so they could securely accelerate application delivery. As applications and services moved into AWS, NCR also needed unified governance across physical firewalls, Cisco ACI, and cloud-native controls such as AWS Security Groups and AWS Network Firewall. The solution They implemented the AlgoSec Security Policy Management Solution, made up of AlgoSec Horizon Security Analyzer , AlgoSec Horizon FireFlow , and AlgoSec Horizon AppViz and AppChange. This solution is now part of AlgoSec Horizon, which also includes AlgoSec Cloud Enterprise (ACE) for cloud-native visibility and policy management . AlgoSec Horizon Security Analyzer enables organizations to discover, identify, and map business applications across their entire hybrid network. It analyzes complex network security policies across the network. It automates and simplifies security operations, including troubleshooting, auditing, and risk analysis. AlgoSec Horizon FireFlow enables security staff to automate the entire security policy change process from design and submission to proactive risk analysis, implementation, validation, and auditing. Its intelligent, automated workflows save time and improve security by eliminating manual errors and reducing risk. AlgoSec Horizon AppViz , the application visibility add-on for AlgoSec Horizon Security Analyzer , provides visibility for your network applications, enabling secure application delivery. AlgoSec AppChange, the application automation add-on for AlgoSec Horizon FireFlow , allows for changes at the business application level, including during the application migrations, server deployment, and decommissioning projects. With ACE, NCR also gains visibility into AWS environments, including VPCs, Transit Gateways, Security Groups, and AWS Network Firewall, ensuring consistent zero-trust controls across their hybrid network. The results AlgoSec is a strategic component of NCR’s network security, managing its entire network security infrastructure. The AlgoSec platform enables the NCR Corporation to manage application connectivity end-to-end across their network — including public cloud, Cisco ACI, and physical firewalls. With AlgoSec Horizon and ACE, NCR now extends this visibility into AWS cloud environments, unifying security policy management across firewalls, Cisco ACI, and AWS-native controls such as Security Groups and AWS Network Firewall. “Most products don’t understand the end-to-end environment. AlgoSec does,” noted Scott Theriault, Global Manager, Network Perimeter Security. Some of the ways that NCR Corporation benefits from AlgoSec include: Launched migration of their on-premises data centers into the Cisco ACI fabric. Extended micro-segmentation to Cisco ACI environment. Extended segmentation and zero-trust policy enforcement into AWS cloud architectures. Achieved complete visibility of their global security posture from a single dashboard. Automated risk analysis, achieving visibility and insights into the risk that changes introduce. Streamlined auditing process with to automatic logging and audit-ready compliance reports. Cleaned up and reduced firewall policies with rule cleanup, object cleanup, and policy tuning. Unified governance across on-prem, ACI, and AWS environments to support consistent zero-trust policy controls. “As we aspire to achieve zero-trust, when moving into the cloud, micro-segmentation and container security come into play. Therefore, we need tools like AlgoSec to assist us in the journey because most application owners don’t know what access is needed. This tool helps them learn what needs to be implemented to reduce the attack surface,” stated Theriault. Schedule time with one of our experts

AlgoSec application discovery Enhance the discovery of your network applications Download PDF Download PDF Add a Title Add a Title Add a Title 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

The AlgoSec technology partner ecosystem Download PDF Download PDF Add a Title Add a Title Add a Title 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

AlgoSec offers support programs to provide the right level of service for each customer’s needs AlgoSec support programs We aim to provide the most professional and highest level of technical support to our customers. Support is provided through centers located around the globe which serve customers and partners in their local time zone View detailed information Customer Type Access to Knowledgebase and Documentation Access to AlgoSec Technical Community New Upgrades Patches and Hotfixes Email Support Coverage During Local Business Hours (9:00-17:00) 24 x 7 Coverage Instant Online Chat Priority Access to Support and R&D 6-Hour Response Time for Severity 1 Issues* 2-Hour Response Time for Severity 1 Issues* Designated Support Engineer Staging Environment in AlgoSec QA Lab Annual On-Site Preventive Maintenance Visit Quarterly Service Review 10% Discount On Certification Training (Unlimited Number of People) Self service Self service SMB SMB Preferred Enterprise Premium Large enterprise 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

6 best practices to stay secure in the hybrid cloud  Download PDF Download PDF Add a Title Add a Title Add a Title 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 the most widely adapted open-source container software, Kubernetes provides businesses with efficient processes to schedule, deploy,... Cloud Security Understanding and Preventing Kubernetes Attacks and Threats Ava Chawla 2 min read Ava Chawla 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 10/20/21 Published As the most widely adapted open-source container software, Kubernetes provides businesses with efficient processes to schedule, deploy, and scale containers across different machines. The bad news is that cybercriminals have figured out how to exploit the platform’s vulnerabilities , resulting in catastrophic network intrusions across many company infrastructures. A recent report revealed that 94% of respondents reported security incidents in Kubernetes environments. The question is, what is behind this surge of Kubernetes attacks, and how can they be prevented? How Kubernetes is Vulnerable As a container-based platform, a new set of vulnerabilities, permission issues, and specific images set the stage for the increase in attacks. The threats have included fileless malware in containers, leveraging misconfigured Docker API ports, and using container images for attacks. Misconfigured Docker API Ports Exploitation Scanning for misconfigured Docker API ports and using them for deploying images containing malware is a relatively new type of attack. The malware, designed to evade static scanning, has become a popular method to hijack compute cycles for fraudulent cryptomining. This cryptojacking activity steals CPU power to mine currencies such as Ethereum and Monero. By first identifying vulnerable front-end websites and other systems, attackers send a command through the application layer simply by manipulating a domain’s text field or through an exposed API in the website’s URL. The code then enters the container, where it is executed with commands sent to a Docker container’s shell. A wget command is executed to download the malware. To protect against this attack, enterprises must ensure their container files are not writable, establish CPU consumption limits, and enable alerts to detect interactive shell launches. DDoS Attacks With Open Docker Daemons Cybercriminals use misconfigured open Docker daemons to launch DDoS attacks using a botnet of containers. UDP flood and Slowloris were recently identified as two such types of container-based botnet attacks. A recent blog describes an anatomy of these Kubernetes attacks. The attackers first identified open Docker daemons using a scanning tool such as Shodan to scan the internet for IP addresses and find a list of hosts, open ports, and services. By uploading their own dedicated images to the Docker hub, they succeeded in deploying and remotely running the images on the host. Analyzing how the UDP flood attack was orchestrated required an inspection of the binary with IDA. This revealed the start_flood and start_tick threads. The source code for the attack was found on Github. This code revealed a try_gb parameter, with the range of 0 to 1,024, used to configure how much data to input to flood the target. However, it was discovered that attackers are able to modify this open-source code to create a self-compiled binary that floods the host with even greater amounts of UDP packets. In the case of the Slowloris attack, cybercriminals launched DDoS with the slowhttptest utility. The attackers were able to create a self-compiling binary that is unidentifiable in malware scans. Protection from these Kubernetes attacks requires vigilant assurance policies and prevention of images other than compliant ones to run in the system. Non-compliant images will then be blocked when intrusion attempts are made. Man in the Middle Attacks With LoadBalancer or ExternalIPs An attack affecting all versions of Kubernetes involves multi-tenant clusters. The most vulnerable clusters have tenants that are able to create and update services and pods. In this breach, the attacker can intercept traffic from other pods or nodes in the cluster by creating a ClusterIP service and setting the spec.externalIP’s field. Additionally, a user who is able to patch the status of a LoadBalancer service can grab traffic. The only way to mitigate this threat is to restrict access to vulnerable features. This can be done with the admission webhook container, externalip-webhook , which prevents services from using random external IPs. An alternative method is to lock external IPs with OPA Gatekeeper with this sample Constraint Templatecan. Siloscape Malware Security researcher, Daniel Prizmant, describes a newer malware attack that he calls Siloscape. Its primary goal is to escape the container that is mainly implemented in Windows server silo. The malware targets Kubernetes through Windows containers to open a backdoor into poorly configured clusters to run the malicious containers. While other malware attacks focus on cryptojacking, the Siloscape user’s motive is to go undetected and open a backdoor to the cluster for a variety of malicious activities. This is possible since Siloscape is virtually undetectable due to a lack of readable strings in the binary. This type of attack can prove catastrophic. It compromises an entire cluster running multiple cloud applications. Cybercriminals can access critical information including sign-ins, confidential files, and complete databases hosted inside the cluster. Additionally, organizations using Kubernetes clusters for testing and development can face catastrophic damage should these environments be breached. To prevent a Siloscape attack, it is crucial that administrators ensure their Kubernetes clusters are securely configured. This will prevent the malware from creating new deployments and force Siloscape to exit. Microsoft also recommends using only Hyper-V containers as a security boundary for anything relying on containerization. The Threat Matrix The MITRE ATT&CK database details additional tactics and techniques attackers are using to infiltrate Kubernetes environments to access sensitive information, mine cryptocurrency, perform DDoS attacks, and other unscrupulous activities. The more commonly used methods are as follows: 1. Kubernetes file compromise Because this file holds sensitive data such as cluster credentials, an attacker could easily gain initial access to the entire cluster. Only accept kubeconfig files from trusted sources. Others should be thoroughly inspected before they are deployed. 2. Using similar pod names Attackers create similar pod names and use random suffixes to hide them in the cluster. The pods then run malicious code and obtain access to many other resources. 3. Kubernetes Secrets intrusion Attackers exploit any misconfigurations in the cluster with the goal of accessing the API server and retrieving information from the Secrets objects. 4. Internal network access Attackers able to access a single pod that communicates with other pods or applications can move freely within the cluster to achieve their goals. 5. Using the writeable hostPath mount Attackers with permissions to create new containers can create one with a writeable hostPath volume. Kubernetes Attacks: Key Takeaways Kubernetes brings many advantages to organizations but also presents a variety of security risks, as documented above. However, by ensuring their environments are adequately protected through proper configuration and appropriately assigned permissions, the threat of Kubernetes attacks is greatly minimized. Should a container be compromised, properly assigned privileges can severely limit a cluster-wide compromise. Prevasio assists companies in the management of their cloud security through built-in vulnerability and anti-malware scans for containers. Contact us for more information on our powerful CSPM solutions. Learn about how we can protect your company from Kubernetes attacks and other cyberattacks. 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

Empower your cloud security posture with AlgoSec s Prevasio CSPM Achieve compliance and peace of mind Dive deeper now Cloud security posture management (CSPM) Real-time monitoring for comprehensive cloud security Schedule a demo Watch a video Watch a video Remove blind spots and take control of your multi-cloud Uncover all services and resources within your multi-cloud environment. Supporting Amazon AWS , Microsoft Azure and Google GCP, Prevasio scans a comprehensive range of asset classes such as Lambda functions, S3 buckets, Azure VMs and 60 other cloud service assets. Prioritize risks and misconfigurations to focus on what's critical Thousands of alerts are generated by over 600 CSPM alert types at the asset, service and aggregated levels. Build a prioritized risk list according to CIS Benchmarks to make sense of the deluge of alerts and misconfigurations. Confidently meet compliance requirements With Prevasio , compliance posture is constantly being assessed through continuous monitoring of cloud assets. Organizations can prioritize data security and adhere to regulatory frameworks such as PCI-DSS and HIPAA . Close the loop on your risk mitigation through Jira integration Turn Prevasio CSPM alerts into Jira tasks to ensure a streamlined approach to risk mitigation. Empower collaborative efforts between teams to address and resolve security posture issues. Get the latest insights from the experts What is a Cloud Security Assessment? Read blog Shaping tomorrow: Leading the way in cloud security Read blog CSPM importance for CISOs. What security issues can be prevented\defended with CSPM? Read blog Schedule time and secure your cloud Schedule time and secure your cloud Work email* First name* Last name* Company* country* Select country... Short answer* By submitting this form, I accept AlgoSec's privacy policy Schedule a call

As 2022 comes to a close, Professor Avishai Wool, AlgoSec Co-Founder and CTO, provides his top 5 issues organizations will need to be... IaC 2023 Cybersecurity Predictions and Best Practices 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 12/6/22 Published As 2022 comes to a close, Professor Avishai Wool, AlgoSec Co-Founder and CTO, provides his top 5 issues organizations will need to be aware in 2023 that will also dominate the cyber community conversation. 1) Application centric approach to network security will supersede basic NSPM I think the market has matured to the point where the NSPM approach has reached a tipping point and I see the shift to an application perspective becoming the de facto approach in network security policy management as there are better and more robust technologies in the market that can help organizations get there faster. I see this shift becoming even more viable in 2023 based on recent market trends in which organizations are opting for downsizing and trying to do more with the smaller staff at the expense of losing tribal knowledge. As a result, I see organizations shifting more towards adopting a holistic approach to network security that are more application centric in which they can retain critical knowledge, such as application traffic intent and application policy rules, so that the new generations can step in and pick up where the previous predecessors left off. 2) Containerization will enhance layered security I expect container security to be increasingly popular in the future, as companies understand that their existing network security mechanisms are not enough for the communication networks of today. Containers are seen as a cost-effective light-weight solution for deployment – and deploying them introduces another inner layer where security policies can be applied: behind the perimeter filters, the internal zoning, and the micro-segmentation, organizations can now also consider nano-segmentation at the container level. Vulnerability testing is another dimension of the container platform especially within cloud applications and SaaS products. The common Kubernetes platform offers both opportunities and challenges for vulnerability scanners. Beyond 2023 , businesses will need to enhance both their visibility and management capabilities of security within their containerized applications 3) Security driven IaaS ecosystems to improve network security I expect the popularity of Infrastructure as a service (IaaS) to continue to soar, making it difficult for security teams to keep up with the associated risks and vulnerabilities. Pre-set security settings may not meet the needs of the organization and customizing these settings can prove to be difficult. The customizability of IaaS offers great potential for productivity, but it also makes it complicated to secure. The bottom line is that companies can no longer depend on their network perimeter to guard sensitive data. In response, I anticipate organizations that begin utilizing an “Always-on Security” approach such as Infrastructure as Code (IaC) which would permit them to construct personalized policies to control the development environments during each phase of the software development life cycle (SDLC) and recognize potential risks, security flaws, and compliance issues on a what-if basis, before deploying flawed settings into production. 4) Cloud-native security tools will reign supreme I expect that cloud-based security systems will become more commonplace: these security solutions offer a wide range of abilities, such as secure access, identity and access management, data loss prevention, application security, automation of security, detection and prevention of intrusions, security information and event management, and encryption. With companies transitioning more workloads to the cloud, they will want to make use of many of these features. These tools make it possible for remote teams to manage a greater public cloud presence: comfortably configuring services and automating processes, to identify and preemptively tackle any kind of threats. To bridge the gap in cloud data security, I anticipate the emergence of data safeguarding systems that are designed specifically for cloud usage and are able to link up with public cloud systems in an advanced, agentless manner. This has been classified in the market as Cloud Native Application Protection Platform (CNAPP) . These platforms must be able to detect where the data is stored and what sorts of data are stored in the cloud, so that corporations can prioritize on what is most important – defending their most sensitive data and cloud-based applications without interfering with their normal operations. 5) Expect ransomware not to go away and get even more sophisticated Organizations in 2022 saw no let-up from ransomware threats, some of whom were attacked multiple times and I do not see any reason why this trend will change in 2023. Cyber criminals are getting more resourceful and savvier in their attempts to stay ahead of law enforcement, and I anticipate these attacks will only become more frequent as their perpetrators are proving more capable of infiltrating many organizations’ cyber defenses. In response, organizations will have to seek more technology solutions to protect data at the source. But that would not suffice. I think organizations will need to look beyond technological solutions and apply better preparedness strategies. Whether it be Zero Trust or something less overarching but more practical for an organization’s business needs, such as Micro-segmentation , it would ensure that threat-actors would not be able to access the data residing inside the security perimeter. 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

Partner solution brief AlgoSec & Zscaler Download PDF Download PDF Add a Title Add a Title Add a Title 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

Containers aren’t VMs. They’re a great lightweight deployment solution, but they’re only as secure as you make them. You need to keep... Cloud Security Best Practices for Docker Containers’ Security 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/27/20 Published Containers aren’t VMs. They’re a great lightweight deployment solution, but they’re only as secure as you make them. You need to keep them in processes with limited capabilities, granting them only what they need. A process that has unlimited power, or one that can escalate its way there, can do unlimited damage if it’s compromised. Sound security practices will reduce the consequences of security incidents. Don’t grant absolute power It may seem too obvious to say, but never run a container as root. If your application must have quasi-root privileges, you can place the account within a user namespace , making it the root for the container but not the host machine. Also, don’t use the –privileged flag unless there’s a compelling reason. It’s one thing if the container does direct I/O on an embedded system, but normal application software should never need it. Containers should run under an owner that has access to its own resources but not to other accounts. If a third-party image requires the –privileged flag without an obvious reason, there’s a good chance it’s badly designed if not malicious. Avoid running a Docker socket in a container. It gives the process access to the Docker daemon, which is a useful but dangerous power. It includes the ability to control other containers, images, and volumes. If this kind of capability is necessary, it’s better to go through a proper API. Grant privileges as needed Applying the principle of least privilege minimizes container risks. A good approach is to drop all capabilities using –cap-drop=all and then enabling the ones that are needed with –cap-add . Each capability expands the attack surface between the container and its environment. Many workloads don’t need any added capabilities at all. The no-new-privileges flag under security-opt is another way to protect against privilege escalation. Dropping all capabilities does the same thing, so you don’t need both. Limiting the system resources which a container guards not only against runaway processes but against container-based DoS attacks. Beware of dubious images When possible, use official Docker images. They’re well documented and tested for security issues, and images are available for many common situations. Be wary of backdoored images . Someone put 17 malicious container images on Docker Hub, and they were downloaded over 5 million times before being removed. Some of them engaged in cryptomining on their hosts, wasting many processor cycles while generating $90,000 in Monero for the images’ creator. Other images may leak confidential data to an outside server. Many containerized environments are undoubtedly still running them. You should treat Docker images with the same caution you’d treat code libraries, CMS plugins, and other supporting software, Use only code that comes from a trustworthy source and is delivered through a reputable channel. Other considerations It should go without saying, but you need to rebuild your images regularly. The libraries and dependencies that they use get security patches from time to time, and you need to make sure your containers have them applied. On Linux, you can gain additional protection from security profiles such as secomp and AppArmor . These modules, used with the security-opt settings, let you set policies that will be automatically enforced. Container security presents its distinctive challenges. Experience with traditional application security helps in many ways, but Docker requires an additional set of practices. Still, the basics apply as much as ever. Start with trusted code. Don’t give it the power to do more than it needs to do. Use the available OS and Docker features for enhancing security. Monitor your systems for anomalous behavior. If you take all these steps, you’ll ward off the large majority of threats to your Docker environment. 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 cloud visibility imperative WhitePaper Download PDF Download PDF Add a Title Add a Title Add a Title 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