Tigera: Implementing Tenant Isolation in Multi-tenant Microsoft AKS environments to prevent lateral movement of threats
Multi-tenant Kubernetes deployments are common. For example, a platform team may offer shared services such as security tools and databases to multiple internal “customers” and a SaaS vendor may also have multiple teams sharing a development cluster. However, due to the flat nature of Kubernetes network, multi-tenant Kubernetes environments are susceptible to the risk of lateral movement of threats from one tenant to another. Within the Shared Security Framework, while Microsoft AKS secures the infrastructure, enterprises are tasked with the security of workloads.
This webinar will demonstrate how Calico’s security policy recommendations can:
- Automatically achieve workload isolation in Microsoft AKS with namespace isolation
- Remove the manual overhead of identifying workload communication patterns for building isolation policies with policy recommendations
- Reduce the potential impact of threats by restricting communication between workloads with microsegmentation
- Streamline and expedite policy enforcement processes with preview and stage included