Malware Protection and Data Breach Prevention for Containerized Applications

MetaDefender Core and MetaDefender for Secure Storage High Availability Solutions Now Available for Kubernetes Clusters

Your organization has created containerized applications for faster file uploads, transfers, and delivery. To go along with your microservices architecture, you want an anti-malware and threat prevention solution that is not only effective and efficient, but also scalable for your team to keep up with continuous cybersecurity efforts.

Many of our customers often face modern challenges as their architecture expands and evolves:

  • The need for scalability of MetaDefender engines
  • The need for integrating the MetaDefender platform into their organization’s existing Kubernetes infrastructure to analyze and sanitize files
  • The need for threat prevention — to prevent potential malicious traffic allowed in their deployment environment

In response to these growing demands, OPSWAT has expanded its deployment options for MetaDefender Core and MetaDefender for Secure Storage via Kubernetes (K8S). This will help simplify the deployment and installation process, reduce overhead on scalability, and provide high availability and self-healing mechanisms that can back up and restore in the case of disaster recovery.

IT infrastructure architects, administrators and DevOps professionals can now install MetaDefender Core in a Kubernetes cluster in whatever environment they have it deployed. Whether in one of the principal cloud providers like Amazon Web Services (AWS), your in-house Kubernetes cluster, or Microsoft Azure and GCP (coming in the next releases). Organizations interested in protecting their applications deployed in existing Kubernetes infrastructure can leverage this upgrade to prevent potential malicious traffic allowed in their environments.

How it Works

opswat-metadefender-kubernetes-deployment

MetaDefender Kubernetes is a flexible and customizable solution. Depending on your organization’s current infrastructure, there are multiple configuration and deployment options available to choose from:

  • Your own existing Kubernetes cluster
  • AWS Elastic Kubernetes Service (EKS) cluster
  • Single AWS Elastic Compute Cloud (EC2) instance
  • Autoscaling AWS EC2
  • AWS Fargate
  • Customizable architecture – with external database or PostgreSQL service

MetaDefender can be deployed in Kubernetes clusters in two ways: using a deployment script and via customized deployment. MetaDefender Kubernetes Bash provision script will allow customers to provision the infrastructure or install MetaDefender Core services. The script automatically takes care of all dependencies and lets you define the provisioning of your instances as well as deploying MetaDefender Core in your existing clusters. It can set up credentials, connects you to EC2 or Fargate, set up your ingress, create a new database if desired and set it up inside the cluster.

For customized deployments, a GitHub project is made publicly available with code and MetaDefender Kubernetes scripts. Users looking to customize the solution can directly use this repository without using the MetaDefender Kubernetes script.

Highlight Features

Two Deployment Combination Options

There will be different deployment services depending on how the cluster is accessed and what type of database will be used to work with MetaDefender Core. Learn more

There are two possible combinations:

  • MetaDefender Core Service + Ingress + PostgreSQL service
    • md-core components
    • postgres-core component
    • core-ingress component (in case cloud-hosted Load Balancer is not in use)
  • MetaDefender Core Service + Ingress + External Database
    • md-core components
    • core-ingress component (in case cloud-hosted Load Balancer is not in use)

Load Balancers in AWS

This solution enables the provisioning of the recommended architecture in AWS for MetaDefender Core in Kubernetes. To access the md-core service, you can set up a load balancer in AWS that will need to install an ingress controller for AWS and create a TargetGroupBinding as a Custom Resource (CR), which allows the cluster to manage the target groups of the load balancer. Learn more

Bring Your Own Cluster to Install MetaDefender Core

You can use the provisioning script to generate all the Kubernetes components needed to run MetaDefender Core in your existing Kubernetes cluster. Depending on the configuration options, the script will dynamically adapt the helm chart values accordingly. Learn more

Why MetaDefender Kubernetes Solutions

Ease of Use: MetaDefender Kubernetes enables simple, quick, and flexible deployment. Deployment and installation can be automated through scripts or customized through available GitHub repositories. You do not need to worry about license activations as they automatically get reused as the pods are restarted and reprovisioned.

Native Threat Prevention Technologies: MetaDefender scans files for malware and checks for known vulnerabilities. Files are sanitized and harmful content disarmed before they are made accessible to the end-users to ensure that no malicious content is allowed or distributed through the web application. Vulnerabilities from unpatched OSs are identified across all running services and applications.

Horizontal Scalability: Kubernetes can help optimize costs and minimize overhead by auto-scaling MetaDefender Core nodes across multiple environments. You only use what you need and the capacity scales as your needs grow.

High Availablity and Self-Healing: MetaDefender Kubernetes makes sure that the systems are always up and running. In cases of a disaster such as when a containerized application or component goes down, or in case of data loss; you can automatically restore and back up data and return the application to its optimal state.

For more details about deploying MetaDefender in containerized environments, read our documentation or talk to an OPSWAT cybersecurity expert.

Sign up for Blog updates!
Get information and insight from the leader in advanced threat prevention.