DeveloperWeek Austin: A DevOps State of Mind: Continuous Security with Containers

With the rise of DevOps, containers are at the brink of becoming a pervasive technology in Enterprise IT to accelerate application delivery for the business. When it comes to adopting containers in the enterprise, Security is the highest adoption barrier. In this presentation, you'll learn about: - DevSecOps - embedding security best practices at scale without slowing down the CI/CD pipeline. - The top security risks with containers and how to manage theses risks at scale. - Images, Builds, Registry, CI/CD, Hosts, Network, Storage, APIs, Monitoring/Logging, and Federation. - Improving container images security with reproducible builds - Automating security vulnerability and security policy scans for containers - Managing security updates at scale with automated Rolling, Canary, Blue/Green deployment strategies and A/B testing - DevSecOps metrics to track success and failure

Transcript

1. A DEVOPS STATE OF MIND: Continuous Security with Containers Chris Van Tuin Chief Technologist, NA West / Silicon Valley cvantuin@redhat.com
2. THE DISRUPTORS
3. “Only the Paranoid Survive” - Andy Grove, 1998
4. Retail Finance Media Transportation ? ? SOFTWARE DISRUPTS BUSINESS
5. + ≠ TAXI TRANSPORTATION DISRUPTER https://goo.gl/MP7QQH Ack: Andrew Ng APP IT’S NOT JUST A… +
6. Culture of experimentation A B 20% vs. 25% Empowered organization Time Change Rapid Innovation THE DISRUPTORS = AI /
 ML Data-driven intelligence Data, Data, Data
7. WHAT CAN I.T. DO?
8. DEV QA OPS Walled off people, walled off processes, walled off technologies “THROW IT OVER THE WALL”
9. I.T. MUST EVOLVE TO ENABLE THE BUSINESS Development Model Application Architecture Deployment & Packaging Application Infrastructure Storage Waterfall Agile Monolithic N-tier Bare Metal Virtual Servers Data Center Hosted Scale Up Scale Out DevOps MicroServices Containers Hybrid Cloud Storage as a Service
12. 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
13. WHAT ABOUT SECURITY?
14. DEV QA OPS SECURITY IS AN AFTERTHOUGHT | SECURITY | “Patch? The servers are behind the firewall.” - Anonymous (far too many to name), 2005 - …
15. http://www.informationisbeautiful.net/visualizations/worlds-biggest-data-breaches-hacks/
16. DEVSECOPS End to End Security + + SECURITY DEV QA OPS Linux + Containers IaaS Orchestration CI/CD Source Control Management Collaboration Build and Artifact Management Testing Frameworks Open Source Culture Process Technology
17. CONTAINERS
18. WHAT ARE CONTAINERS? It depends who you ask…
19. APPLICATION DELIVERY VIA CONTAINERS
20. docker.io Registry Private Registry FROM fedora:1.0 CMD echo “Hello” Build file Physical, Virtual, Cloud Image Container Build Run Ship CONTAINERS: BUILD, SHIP, RUN
21. CONTAINER SECURITY AT SCALE
22. Scheduling Monitoring Persistence Discovery Lifecycle & health Scaling Aggregation Security MORE THAN CONTAINERS…
23. DEVSECOPS End to End Security + + DEV QA OPS SECURITY
24. 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 Are there known vulnerabilities 
 in each application layer? Are the runtime and OS layers 
 up to date? How frequently will the container be updated and how will I know when its updated? IS THE CONTAINER ENVIRONMENT SECURE? Is the image from a trusted source? Can I quickly deploy a security update at scale? Is my multi-tenant host secure?
25. Network isolation Storage API & Platform access Monitoring & Logging Federated clusters Registry Container host {} Builds CI/CD Images SECURING CONTAINERS
26. CONTAINER IMAGE SECURITY
27. 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
28. SECURITY IMPLICATIONS What’s inside matters…
29. A CONVERGED SOFTWARE SUPPLY CHAIN
30. code config data Kubernetes configmaps secrets Container image Traditional 
 data services, Kubernetes 
 persistent volumes TREAT CONTAINERS AS IMMUTABLE
31. NODE MASTER Container Distributed Store Container ! Secure mechanism for holding sensitive data e.g. ◦ Passwords and credentials ◦ SSH Keys ◦ Certificates ! Secrets are made available as ◦ Environment variables ◦ Volume mounts ◦ Interaction with external systems ! Encrypted in transit ! Never rest on the nodes SECRETS
32. IMAGE SIGNING Validate what images and version are running
33. CONTAINER REGISTRY SECURITY
34. 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
35. PRIVATE REGISTRY
36. CI WITH CONTAINERS
37. CI/CD PIPELINE Continuous Integration Continuous Build Continuous Deployment Developer -> Source -> Git Git -> RPMS -> Images-> Registry Images from 
 Registry -> Clusters
38. CI/CD with Security
39. Security CONTINUOUS INTEGRATION WITH SECURITY SCAN
40. CUSTOM SUPPLY CHAIN
41. FROM fedora:latest CMD echo “Hello” Build file Build 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 BUILDS
42. Compliance and Vulnerability Audits with OpenSCAP
43. AUTOMATED SECURITY SCANNING with OpenSCAP Reports Scan SCAP Security Guide for RHEL CCE-27002-5 Set Password Minimum Length Content Scan physical servers, virtual machines, docker images and containers
 for Security Policy Compliance (CCEs) and known Security Vulnerabilities (CVEs)
44. Standard Docker Host Security Profile Java Runtime Environment (JRE) Upstream Firefox STIG RHEL OSP STIG Red Hat Corporate Profile for Certified Cloud Providers (RH CCP) STIG for Red Hat Enterprise Linux 6, 7 Server STIG for Red Hat Virtualization Hypervisor Common Profile for General-Purpose Debian Systems Common Profile for General-Purpose Fedora Systems Common Profile for General-Purpose Ubuntu Systems Payment Card Industry – Data Security Standard (PCI-DSS) v3 U.S. Government Commercial Cloud Services (C2S) CNSSI 1253 Low/Low/Low Control Baseline for Red Hat Enterprise Linux 7 Criminal Justice Information Services (CJIS) Security Policy Unclassified Information in Non-federal Information Systems and Organizations (NIST 800-171) U.S. Government Configuration Baseline (NIAP OSPP v4.0, USGCB, STIG) Security Policies in SCAP Security Guide (partial)
45. SECURITY POLICY REPORT
46. SECURITY POLICY REMEDIATION
47. SECURITY VULNERABILITY REPORT
48. RAPID INNOVATION & EXPERIMENTATION
49. ”only about 1/3 of ideas improve the metrics 
 they were designed to improve.”
 Ronny Kohavi, Microsoft (Amazon) MICROSERVICES RAPID INNNOVATION & EXPERIMENTATION
50. CONTINUOUS FEEDBACK LOOP
51. A/B TESTING USING CANARY DEPLOYMENTS
52. 50% 50% Version 1.2 Version 1 Route Version 1.2 25% Conversion Rate 30% Conversion Rate CANARY DEPLOYMENTS
53. CD WITH CONTAINERS
54. CONTINUOUS DEPLOYMENT WITH CONTAINERS
55. CD with Security
56. CONTINUOUS DELIVERY DEPLOYMENT STRATEGIES DEPLOYMENT STRATEGIES • Blue / Green deployment • Rolling updates • Canary deployments • A / B testing
57. Version 1 BLUE / GREEN DEPLOYMENT Route
58. Version 1 BLUE / GREEN DEPLOYMENT Version 1.2
59. Version 1 Tests / CI BLUE / GREEN DEPLOYMENT Version 1.2
60. Version 1 Version 1.2 BLUE / GREEN DEPLOYMENT Route Version 1.2
61. Version 1 BLUE / GREEN DEPLOYMENT Rollback Route Version 1.2
62. Version 1 Version 1 Version 1 Version 1.2 ` Tests / CI ROLLING UPDATES with ZERO DOWNTIME
63. 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
64. Each container/pod is updated one by one Version 1.2 50% Version 1 V1 V1.2
65. Each container/pod is updated one by one Version 1.2 Version 1.2 Version 1.2 100%
66. CONTAINER HOST SECURITY
67. 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
68. CGROUPS - RESOURCE ISOLATION
69. NAMESPACES - PROCESS ISOLATION
70. 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
71. SECCOMP - DROPPING PRIVILEGES
72. READ ONLY MOUNTS
73. 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
74. Network isolation Storage API & Platform access Monitoring & Logging Federated clusters Registry Container host {} Builds CI/CD Images SECURING CONTAINERS
75. NETWORK ISOLATION
76. Network Namespace 
 provides resource isolation NETWORK ISOLATION Multi-Environment Multi-Tenant
77. NETWORK POLICY example: 
 all pods in namespace ‘project-a’ allow traffic 
 from any other pods in the same namespace.”
78. STORAGE SECURITY
79. Local Storage Quota Security Context Constraints STORAGE SECURITY
80. API & PLATFORM ACCESS
81. Authentication via OAuth tokens and SSL certificate Authorization via Policy Engine checks User/Group Defined Roles API & PLATFORM ACCESS
82. MONITORING & LOGGING
83. Aggregate platform and application log access via Kibana + Elasticsearch LOGGING
84. Historical CPU and Memory usage provided by Heapster, Hawkular, Cassandra MONITORING
85. FEDERATION
86. Amazon East OpenStack FEDERATED CLUSTERS Roles & access management (in-dev)
87. Deployment Frequency Lead Time Deployment
 Failure Rate Mean Time to Recover 99.999 Service Availability DEVSECOPS METRICS Compliance Score
88. THANK YOU linkedin: Chris Van Tuin email: cvantuin@redhat.com twitter: @chrisvantuin