Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

Containers

How to Secure the network of your GKE Cluster

By default, pods are non-isolated; they accept traffic from any source. The Google GKE solution to this security concern is Network Security Policy that lets developers control network access to their services. Google GKE comes configured with Network Security Policy using Project Calico which can be used to secure your clusters. This class will describe a few use cases for network security policy and a live demo implementing each use case.

Sysdig 2020 Container Security Snapshot: Key image scanning and configuration insights

Today, we are excited to share our Sysdig 2020 Container Security Snapshot, which provides a sneak peak into our upcoming 2020 Container Usage Report As containers and Kubernetes adoption continue to increase, cloud teams are realizing they need to adopt a new workflow that embeds security into their DevOps processes. Secure DevOps, a variation of DevSecOps, embeds security and monitoring throughout the application lifecycle, from development through production.

How to Implement Network Policy in Amazon EKS to Secure Your Cluster

By default, pods are non-isolated; they accept traffic from any source. The Amazon EKS solution to this security concern is Network Policy that lets developers control network access to their services. Amazon EKS comes configured with Network Policy using Project Calico which can be used to secure your clusters. This class will describe a few use cases for network policy and a live demo implementing each use case.

Enforcing Enterprise Security Controls in Kubernetes using Calico Enterprise

Hybrid cloud infrastructures run critical business resources and are subject to some of the strictest network security controls. Irrespective of the industry and resource types, these controls broadly fall into three categories. Workloads (pods) running on Kubernetes are ephemeral in nature, and IP-based controls are no longer effective. The challenge is to enforce the organizational security controls on the workloads and Kubernetes nodes themselves.

Calico Enterprise Multi Cluster Management - Federated Identity and Services

Learn how to simplify deployment and ongoing operations for more than one cluster running Calico Enterprise. What is Calico Enterprise Multi-Cluster Management How is Calico Enterprise Multi-Cluster architected How to set up Calico Enterprise Multi-Cluster Management How to enable Federated Endpoint Identity and Services for Multi-Cluster use cases A Calico Enterprise trial is available after this session and you will be able to practice these use cases on your own within a hosted lab.

Authentication vs. Authorization: Why we need authorization standards

I witnessed the transition from bespoke authentication to standards-based authentication. It’s time to do the same for authorization. Twenty years ago, almost everything in the IT world was on-premises: hardware and software, including the tools you used to verify who your users were and what they could do in your systems.

LXC vs Docker: Why Docker is Better

LXC (LinuX Containers) is a OS-level virtualization technology that allows creation and running of multiple isolated Linux virtual environments (VE) on a single control host. These isolation levels or containers can be used to either sandbox specific applications, or to emulate an entirely new host. LXC uses Linux’s cgroups functionality, which was introduced in version 2.6.24 to allow the host CPU to better partition memory allocation into isolation levels called namespaces .

Enterprise Security Controls for Kubernetes

In this talk, we will explore how to meet common enterprise security control needs when running Kubernetes. Specifically, we will look at a range of common enterprise security needs and how you can meet these with standard Kubernetes primitives and open source projects such as Calico, or take it a step further with the additional features of Calico Enterprise.

Unified cloud-native authorization: Policy everywhere and for everyone

When we started Styra, we set out to rethink authorization and policy for the cloud-native environment. We knew that new risks and challenges would emerge as companies embraced the cloud and began using a whole new host of technologies and architectures for building applications. The constant changes and dynamic runtime of the cloud-native environment complicated matters even more.