Deployment Overview

VSP deployment includes the below steps:

1. VSP CMS Deployment - CMS can be deployed in two configurations:
   1. SaaS: CMS can be deployed on AWS infrastructure as a SaaS instance
   2. On-Prem: CMS can be deployed on both VM and Container environments:
      1. VM: All CMS services running as docker containers on a hardened RHEL 8 VM. This VM is delivered is various formats so that it can be deployed on common Hypervisors and Public Cloud IaaS platforms. Check the latest compatibility matrix, as Virsec continues add supports for more platforms
      2. Container: Various CMS services running as Kubernetes Pods in a single Kubernetes cluster. The number of Pods varies depending on the choice of deployment. Virsec provides scripts that can deploy the entire CMS using kubectl (For Native Kubernetes, AWS EKS, HPE Ezmeral) and Helmcharts. Check the latest compatibility matrix, as Virsec continues add supports for more orchestration platforms.
2. Probe Deployment- Probe can be deployed on both VM and Container. VSP Probe also comprises of multiple services, with distinct functions. VSP Probe can be deployed on the Workload itself for both VMs and containers. For containers, it can also be deployed with Sidecar configuration.
   1. VSP vRuleEngine can be deployed on:

      VM		Container
      Deployed on Workload	Remote	Deployed on Workload	Remote	Sidecar
      Yes	Yes	Yes	Yes	Yes

3. Configuration - VSP must be configured to enable the below protection
   1. Host Protection
   2. Web Protection
   3. Memory Protection