Containerisation technologies come with different approach to isolation than virtual machines. This brings forwards serious security concerns and puts enormous pressure on management of secure configuration as well as policy enforcement techniques. A Security Context defines privilege and access control settings for a Pod or Container in Kubernetes. This is usually done by DevOps staff and is optional. Therefore there is need for independent Security Context setting enforcement in whole Kubernetes cluster. Security policy can define a set of conditions that a pod must run with in order to be accepted into the system. There are several implementations available for policy enforcement on Kubernetes. For example security profiles are control plane mechanisms to enforce specific settings in the Security Context, as well as other related parameters outside the Security Context. Student is expected to provide analysis of relevant security related settings for containers and pods in Kubernetes focused primarily on security risk and real world use-cases. Then compare available implementations for Pod Security Standards profiles enforcement (Pod Security Admission Controller, OPA Gatekeeper, Kubewarden, Kyverno, etc.) from all aspects but mainly as a solution for enterprise scale Kubernetes deployment on managed Kubernetes cloud offering.