Kube Security Shifting left, with Armo Security

Table of Contents

As kubernetes matures into the standard de facto Operating System of the Cloud, in addition to a shift in deployment methods such as GitOps and Continuous delivery paradigms - automation of security is one of our main concerns

The security policy alignment starts from the CI/CD pipelines, and continues to runtime security solutions. In this talk, we will introduce a few solutions built around kubernetes from the early stages of the CI/CD pipelines through runtime application security models which we are seeing from many companies on the security vertical.

Scanning tools [ static ] Runtime [ pro-active, permissive ]

Video

Presntation slides

Kube Security Shifting left | Scanners & OPA from Haggai Philip Zagury

Tags :

comments powered by Disqus

Getting Up & Running with Kubernetes

Organized Chaos with Kubernetes for a startup/new companies Kubernetes is easy, for companies moving from Legacy / Bare metal & Multi-cloud is a whole different story, from setting up the k8s cluster to managing microservices and bridging on the gaps between new-gen and legacy infrastructure with cloud-native solutions given at Tikal

Managing your dotfiles or ~/.config ...

This is a common approach I adopted to manage my dotfiles

Pre-commit hooks using python library pre-commit

Pre-commit examples used in just-do-it repository

I really need a strict pre-commit considering the number of branches and tools i’m using. Because the heart of the projects is tasks I want at the bare least .pre-commit-config.yaml to include the task --list-all command considering it compiles all the includes which may change name / location between branches.