OpenStack Summit Vancouver: A DevOps State of Mind: Continuous Security with Kubernetes

Slide 1

Slide 1 text

A DevOps State of Mind: Continuous Security with Kubernetes Chris Van Tuin Chief Technologist, NA West / Silicon Valley [email protected]

Slide 2

Slide 2 text

“Only the paranoid survive” - Andy Grove, 1996

Slide 3

Slide 3 text

Retail Finance Media Transportation ? ? SOFTWARE DISRUPTS BUSINESS

Slide 4

Slide 4 text

HOW DOES I.T. ACCELERATE   BUSINESS INNOVATION? 6 to 9 months Innovation Hours to Weeks

Slide 5

Slide 5 text

DEV QA OPS “THROW IT OVER THE WALL” Challenges 1. Limited resources 2. Security bottlenecks 3. Large change set =   more bugs, more testing 4. Extended feedback loop 5. Environment drift Walled off people, walled off processes, walled off technologies

Slide 6

Slide 6 text

DEVOPS Speeding Up Time to Market Leverage tooling & automation Reduce organizational silos Accept failure  as normal Implement gradual change Measure everything

Slide 7

Slide 7 text

DEV QA OPS SECURITY IS AN AFTERTHOUGHT | SECURITY | “Patch? The servers are behind the firewall.” - Anonymous (far too many to name), 2005 - …

Slide 8

Slide 8 text

http://www.informationisbeautiful.net/visualizations/worlds-biggest-data-breaches-hacks/ SECURITY BREACH: BILLION DATA RECORDS

Slide 9

Slide 9 text

36% - Employees not taking proper security measures 32% - Outside breach 14% - Unpatched or unpatchable 11% - Internal attack by an employee 4% - Shadow IT 3% - Bring your own device/mobile Source: Techvalidate/Red Hat % of Respondants WHAT IS THE GREATEST SECURITY RISK?

Slide 10

Slide 10 text

SECURITY MUST EVOLVE & KEEP UP

Slide 11

Slide 11 text

ANY COMBINATION, WHETHER TRADITIONAL OR CONTAINERIZED LEGACY APPS (1,000+) BARE METAL PRIVATE CLOUD PUBLIC CLOUD VIRTUAL PRODUCTION DEV/TEST HYBRID CLOUD ENVIRONMENTS

Slide 12

Slide 12 text

BARE METAL VIRTUAL PRIVATE CLOUD OFF-PREMISE ON-PREMISE PUBLIC CLOUD DATA DATA DISTRIBUTED APPLICATIONS

Slide 13

Slide 13 text

DEV QA OPS Open organization +   cross-functional teams Software factory automation Linux + Containers IaaS Orchestration CI/CD Source Control Management Collaboration Build and Artifact Management Testing Frameworks Open Source CI/CD pipelines with feedback Culture Process Technology + + BREAKING DOWN THE WALLS WITH DEVOPS

Slide 14

Slide 14 text

DEVSECOPS + + End to End Security DEV QA OPS Culture Automated Process Technology Linux + Containers IaaS Orchestration CI/CD Source Control Management Collaboration Build and Artifact Management Testing Frameworks Open Source

Slide 15

Slide 15 text

No content

Slide 16

Slide 16 text

No content

Slide 17

Slide 17 text

DEVSECOPS Continuous Security Improvement Process Optimization Security Automation Dev QA Prod Reduce Risks, Lower Costs, Speed Delivery, Speed Reaction

Slide 18

Slide 18 text

CONTAINERS

Slide 19

Slide 19 text

CONTAINERS

Slide 20

Slide 20 text

4 ● Are there known vulnerabilities in the application layer? ● Are the runtime and OS layers up to date? ● How frequently will the container be updated and how will I know when it’s updated? CONTENT: EACH LAYER MATTERS CONTAINER OS RUNTIME APPLICATION CONTENT: EACH LAYER MATTERS AYER MATTERS CONTAINER OS RUNTIME APPLICATION JAR CONTAINER

Slide 21

Slide 21 text

LAPTOP Container Application OS dependencies Guest VM LINUX BARE METAL Container Application OS dependencies LINUX VIRTUALIZATION Container Application OS dependencies Virtual Machine LINUX PRIVATE CLOUD Container Application OS dependencies Virtual Machine LINUX PUBLIC CLOUD Container Application OS dependencies Virtual Machine LINUX APPLICATION PORTABILITY WITH CONTAINERS

Slide 22

Slide 22 text

CONTAINERS AT SCALE

Slide 23

Slide 23 text

Scheduling Monitoring Persistence Discovery Lifecycle & health Scaling Aggregation Security MORE THAN CONTAINERS…

Slide 24

Slide 24 text

BARE METAL VIRTUAL PRIVATE CLOUD PUBLIC CLOUD

Slide 25

Slide 25 text

DEVSECOPS End to End Security + + DEV QA OPS SECURITY

Slide 26

Slide 26 text

Web Database replicas=1,   role=db replicas=2,   role=web ORCHESTRATION Deployment, Declarative Nodes Controller Manager & Data Store (etcd)

Slide 27

Slide 27 text

role=web role=web ORCHESTRATION Schedule + Provision Pods (Compute/Storage/Network) Image Registry Pods Nodes Web replicas=2,   role=web ReplicaSet

Slide 28

Slide 28 text

role=web role=db role=web Pods Nodes Image Registry ORCHESTRATION Schedule + Provision Pods (Compute/Storage/Network) Web replicas=2,   role=web ReplicaSet Database replicas=1,   role=db StatefulSet

Slide 29

Slide 29 text

Web Database role=web role=db role=web replicas=1,   role=db replicas=2,   role=web ORCHESTRATION Service (Load Balancer) Pods Nodes Services Controller Manager & Data Store (etcd)

Slide 30

Slide 30 text

HEALTH CHECK Monitoring & Logging Pods Nodes Services Web Database role=web role=db role=web replicas=1,   role=db replicas=2,   role=web

Slide 31

Slide 31 text

HEALTH CHECK Pods Nodes Services Web Database role=web role=db role=web replicas=1,   role=db replicas=2,   role=web role=web Controller Manager & Data Store (etcd)

Slide 32

Slide 32 text

Web Database replicas=1,   role=db replicas=2,   role=web HEALTH CHECK Pods Nodes Services role=web role=db role=web Controller Manager & Data Store (etcd)

Slide 33

Slide 33 text

Web Database replicas=1,   role=db replicas=2,   role=web AUTO-SCALE Monitoring & Logging 80% CPU Pods Nodes Services role=web role=db role=web

Slide 34

Slide 34 text

Web Database replicas=1,   role=db replicas=3   role=web AUTO-SCALE 80% CPU Pods Nodes Services role=web role=db role=web role=web Controller Manager & Data Store (etcd)

Slide 35

Slide 35 text

Pods Nodes Services Web Database replicas=1,   role=db replicas=3   role=web AUTO-SCALE 50% CPU role=web role=db role=web role=web Controller Manager & Data Store (etcd)

Slide 36

Slide 36 text

CONTAINER SECURITY

Slide 37

Slide 37 text

Network isolation Storage API & Platform access Monitoring & Logging Federated clusters Registry Container host {} CI/CD Images SECURING CONTAINERS Builds

Slide 38

Slide 38 text

CONTAINER BUILDS

Slide 39

Slide 39 text

docker.io Registry Private Registry FROM fedora:1.0 CMD echo “Hello” Build file Physical, Virtual, Cloud Image Container Build Run Ship CONTAINER BUILDS

Slide 40

Slide 40 text

Best Practices • Treat as a Blueprint • Don’t login to build/configure • Version control build file • Be explicit with versions, not latest • Each Run creates a new layer CONTAINER BUILDS FROM fedora:1.0 CMD echo “Hello” Build file Build

Slide 41

Slide 41 text

A CONVERGED SOFTWARE   SUPPLY CHAIN

Slide 42

Slide 42 text

CONTAINER IMAGE SECURITY

Slide 43

Slide 43 text

64% of official images in Docker Hub   contain high priority security vulnerabilities examples: ShellShock (bash) Heartbleed (OpenSSL) Poodle (OpenSSL) Source: Over 30% of Official Images in Docker Hub Contain High Priority Security Vulnerabilities, Jayanth Gummaraju, Tarun Desikan, and Yoshio Turner, BanyanOps, May 2015 (http://www.banyanops.com/pdf/BanyanOps-AnalyzingDockerHub-WhitePaper.pdf) WHAT’S INSIDE THE CONTAINER MATTERS

Slide 44

Slide 44 text

SECURITY IMPLICATIONS What’s inside matters…

Slide 45

Slide 45 text

code config data Kubernetes configmaps secrets Container image Traditional   data services, Kubernetes   persistent volumes TREAT CONTAINERS AS IMMUTABLE

Slide 46

Slide 46 text

CONTAINER REGISTRY SECURITY

Slide 47

Slide 47 text

PRIVATE REGISTRY

Slide 48

Slide 48 text

IMAGE SIGNING Validate what images and version are running

Slide 49

Slide 49 text

CONTINUOUS INTEGRATION WITH CONTAINERS

Slide 50

Slide 50 text

CONTINUOUS INTEGRATION + SECURITY

Slide 51

Slide 51 text

Security CONTINUOUS INTEGRATION WITH SECURITY SCAN

Slide 52

Slide 52 text

CONTINUOUS DELIVERY WITH CONTAINERS

Slide 53

Slide 53 text

CONTINUOUS DELIVERY WITH CONTAINERS

Slide 54

Slide 54 text

CONTINUOUS DELIVERY + SECURITY

Slide 55

Slide 55 text

CONTINUOUS DELIVERY: DEPLOYMENT STRATEGIES

Slide 56

Slide 56 text

CONTINUOUS DELIVERY DEPLOYMENT STRATEGIES DEPLOYMENT STRATEGIES • Recreate • Rolling updates • Blue / Green deployment

Slide 57

Slide 57 text

Recreate

Slide 58

Slide 58 text

Version 1 Version 1 Version 1 Version 1.2 ` Tests / CI RECREATE WITH DOWNTIME

Slide 59

Slide 59 text

Version 1 Version 1 Version 1 Version 1.2 ` Tests / CI RECREATE WITH DOWNTIME

Slide 60

Slide 60 text

Version 1.2 Version 1.2 Version 1.2 RECREATE WITH DOWNTIME Use Case • Non-mission critical services Cons • Downtime Pros • Simple, clean • No Schema incompatibilities • No API versioning

Slide 61

Slide 61 text

Rolling Updates

Slide 62

Slide 62 text

Version 1 Version 1 Version 1 Version 1.2 ` Tests / CI ROLLING UPDATES with ZERO DOWNTIME

Slide 63

Slide 63 text

Deploy new version and wait until it’s ready… Version 1 Version 1 V1.2 Health Check: readiness probe e.g. tcp, http, script V1

Slide 64

Slide 64 text

Each container/pod is updated one by one Version 1.2 50% Version 1 V1 V1.2

Slide 65

Slide 65 text

Each container/pod is updated one by one Version 1.2 Version 1.2 Version 1.2 100% Use Case • Horizontally scaled • Backward compatible API/data • Microservices Cons • Require backward compatible APIs/data • Resource overhead Pros • Zero downtime • Reduced risk, gradual rollout w/health checks • Ready for rollback

Slide 66

Slide 66 text

Blue / Green Deployment

Slide 67

Slide 67 text

Version 1 BLUE / GREEN DEPLOYMENT Route BLUE

Slide 68

Slide 68 text

Version 1 BLUE / GREEN DEPLOYMENT Version 1.2 BLUE GREEN

Slide 69

Slide 69 text

Version 1 Tests / CI BLUE / GREEN DEPLOYMENT Version 1.2 BLUE GREEN

Slide 70

Slide 70 text

Version 1 Version 1.2 BLUE / GREEN DEPLOYMENT Route Version 1.2 BLUE GREEN

Slide 71

Slide 71 text

Version 1 BLUE / GREEN DEPLOYMENT Rollback Route Version 1.2 BLUE GREEN Use Case • Self-contained micro services (data) Cons • Resource overhead • Data synchronization Pros • Low risk, never change production • No downtime • Production like testing • Rollback

Slide 72

Slide 72 text

RAPID INNOVATION & EXPERIMENTATION

Slide 73

Slide 73 text

”only about 1/3 of ideas improve the metrics   they were designed to improve.”  Ronny Kohavi, Microsoft (Amazon) MICROSERVICES RAPID INNNOVATION & EXPERIMENTATION

Slide 74

Slide 74 text

CONTINUOUS FEEDBACK LOOP

Slide 75

Slide 75 text

A/B TESTING USING CANARY DEPLOYMENTS

Slide 76

Slide 76 text

Version 1.2 Version 1 100% Tests / CI Version 1.2 Route 25% Conversion Rate ?! Conversion Rate CANARY DEPLOYMENTS

Slide 77

Slide 77 text

50% 50% Version 1.2 Version 1 Route Version 1.2 25% Conversion Rate 30% Conversion Rate CANARY DEPLOYMENTS

Slide 78

Slide 78 text

25% Conversion Rate 100% Version 1 Version 1.2 Route Version 1.2 30% Conversion Rate CANARY DEPLOYMENTS

Slide 79

Slide 79 text

Version 1.2 Version 1 100% Route Rollback 25% Conversion Rate 20% Conversion Rate CANARY DEPLOYMENTS

Slide 80

Slide 80 text

CONTAINER HOST SECURITY

Slide 81

Slide 81 text

Kernel Hardware (Intel, AMD) or Virtual Machine Containers Containers Containers Unit File Docker Image Container CLI SYSTEMD Cgroups Namespaces SELinux Drivers CONTAINERS ARE LINUX seccomp Read Only mounts

Slide 82

Slide 82 text

CGROUPS - RESOURCE ISOLATION

Slide 83

Slide 83 text

NAMESPACES - PROCESS ISOLATION

Slide 84

Slide 84 text

SELINUX - MANDATORY ACCESS CONTROLS Password Files Web Server Attacker Discretionary Access Controls   (file permissions) Mandatory Access Controls   (selinux) Internal Network Firewall Rules Password Files Firewall Rules Internal Network Web Server selinux policy

Slide 85

Slide 85 text

SECCOMP - DROPPING PRIVILEGES

Slide 86

Slide 86 text

READ ONLY MOUNTS

Slide 87

Slide 87 text

Best Practices • Don’t run as root • Limit SSH Access • Use namespaces • Define resource quotas • Enable logging • Apply Security Errata • Apply Security Context and seccomp filters http://blog.kubernetes.io/2016/08/security-best-practices-kubernetes-deployment.html CONTAINER HOST SECURITY Kernel Hardware (Intel, AMD) or Virtual Machine Containers Containers Containers Unit File Docker Image Container SYSTEM Cgroup Namespace SELinu Driver seccom Read Only

Slide 88

Slide 88 text

Network isolation Storage API & Platform access Monitoring & Logging Federated clusters Registry Container host {} CI/CD Images Builds SECURING CONTAINERS

Slide 89

Slide 89 text

NETWORK ISOLATION

Slide 90

Slide 90 text

Network Namespace   provides resource isolation NETWORK ISOLATION Multi-Environment Multi-Tenant

Slide 91

Slide 91 text

NETWORK POLICY example:   all pods in namespace ‘project-a’ allow traffic   from any other pods in the same namespace.”

Slide 92

Slide 92 text

STORAGE SECURITY

Slide 93

Slide 93 text

Local Storage Quota Security Context Constraints STORAGE SECURITY

Slide 94

Slide 94 text

API & PLATFORM ACCESS

Slide 95

Slide 95 text

Authentication via OAuth tokens and SSL certificate Authorization via Policy Engine checks User/Group Defined Roles API & PLATFORM ACCESS

Slide 96

Slide 96 text

MONITORING & LOGGING

Slide 97

Slide 97 text

Aggregate platform and application log access via Kibana + Elasticsearch LOGGING

Slide 98

Slide 98 text

Historical CPU and Memory usage MONITORING

Slide 99

Slide 99 text

FEDERATION

Slide 100

Slide 100 text

Amazon East OpenStack FEDERATED CLUSTERS Roles & access management (in-dev)

Slide 101

Slide 101 text

Deployment Frequency Lead Time Deployment  Failure Rate Mean Time to Recover 99.999 Service Availability DEVSECOPS METRICS Compliance Score

Slide 102

Slide 102 text

THANK YOU linkedin: Chris Van Tuin email: [email protected] twitter: @chrisvantuin