Unify DevOps and SecOps: Security Without Friction

Transcription

1 SANS Secure DevOps Summit Unify DevOps and SecOps: Security Without Friction Matt Alderman, CISSP Chief Strategy & Marketing Officer Layered

2 Technology Trend #1: Infrastructure Migrates to the Cloud

3 Technology Trend #2: IoT Accelerates Edge Computing

4 Technology Trend #3: Applications are the Future

5 The People Challenge DevOps Benefits Agility Velocity (Production, Market, Improvement, and Innovation) Optimization (Productivity, Costs, and Competitiveness) DevOps Challenges Not Understanding Security Automating to Enhance Agility Starting with Technology Solutions

6 The People Challenge SecOps Wants Inventory Of Authorized and Unauthorized Software Compliance with Policies and Regulations Security Assessment, Monitoring, and Remediation SecOps Challenges Adjusting to Speed Security s Changing Role Legacy Solutions Limit Visibility and Control

7 The People Challenge DevOps SecOps SPEED? AGILITY? PORTABILITY? INVENTORY? COMPLIANCE? SECURITY?

8 The People Solution: Unify DevOps and SecOps DevOps ized Applications SecOps SPEED? AGILITY? PORTABILITY? INVENTORY? COMPLIANCE? SECURITY? Unify DevOps and SecOps to provide complete visibility and control

9 The Technology Challenge 2016 Challenges 1. Shrinking infrastructure, as organizations continue migration to the cloud 2. s deployed within Virtual Machines 3. But organizations still have the overhead and costs of the hypervisor and virtual machines Application Engine Application Engine Application Engine Guest OS Guest OS Guest OS Hypervisor Host Operating System Kernel Infrastructure Infrastructure

10 The Technology Challenge 2017 Challenges 1. The orchestration battle ends with Kubernetes winning 80% of the market 2. But organizations struggle to scale their own Kubernetes clusters 3. Also, where do you put security without creating dependencies? Engine Engine Engine Guest OS Guest OS Guest OS Hypervisor Engine Host Operating System Kernel Infrastructure

11 The Technology Challenge 2018 Challenges 1. -as-a-service and Orchestration-as-a-Service adoption accelerate container adoption 2. Now where do you put security? as a Service Engine Host Operating System Kernel Infrastructure

12 The Three Approaches Approach #1: Kernel Plugin with Root Access Approach #2: Privileged with Root Access Approach #3: Native with User Access

13 The Three Approaches #1: Kernel Plugin Engine Operating System Kernel Infrastructure Challenges Has Root Privileges Lacks App Visibility Limits Portability

14 The Three Approaches #1: Kernel Plugin #2: Privileged Privilege Engine Engine Operating System Operating System Kernel Kernel Infrastructure Infrastructure Challenges Challenges Has Root Privileges Lacks App Visibility Limits Portability Requires Root Access Lacks Scalability Limits Portability

15 The Three Approaches #1: Kernel Plugin #2: Privileged #3: Native Privilege Secured Secured Secured Engine Engine Engine Kernel Operating System Kernel Operating System Zero-Touch Kernel Operating System Infrastructure Infrastructure Infrastructure Challenges Challenges Advantages Has Root Privileges Lacks App Visibility Limits Portability Requires Root Access Lacks Scalability Limits Portability No Root Privileges Scales Elastically Infinite Portability

16 The Technology Solution: Native Solution 1. Native injects sensors within the container image to monitor application, system, network, and file activity 2. Native protects the s independently of the underlying infrastructure as a Service Orchestration as a Service

17 The Process Challenge Insecure posted to registry Insecure container sent to Sec New container build with basic unit test New Post to registry Insecure Registry Insecure git commit git push Dev Sec sends Insecure to Dev for re-imaging Sec B u i l d S h i p R u n

18 The Process Solution: Security Without Friction Insecure posted to registry Instrumented inserted into registry Instrumented runs in observation mode on premise or in cloud Automated enforcement of Secured on premise or in cloud New container build with basic unit test New Post to registry Insecure Registry Copy of Original Instrumented Instrumented Secured Security Policy Enforcement git commit git push Pull container image from registry S t a t i c A n a l y s i s R u n t i m e A n a l y s i s R u n t i m e P r o t e c t i o n Software Inventory Security Assessment Compliance Enforcement Pass/Fail Inject Security Sensors for App, Sys, Network, and Storage Behavior Profiles Dev Any failed containers are returned to DevOps Scan Validate Instrument Security Policies Machine Learning Alerts Notifications Insight << FAIL PASS >> Failed Native Solution Sec DevOps SecOps A s s e s s m e n t / I n s t r u m e n t a t i o n T e s t / S t a g i n g P r o d u c t i o n B u i l d S h i p R u n

19 Conclusion & Call To Action People: Unify DevOps and SecOps 1. Do you have a formal DevOps team? 2. Are they developing with containers? 3. Are they deploying or preparing to deploy containers?

20 Conclusion & Call To Action Technology: Native Application Protection 1. Are you deploying on-premises or in the cloud? 2. Are you looking at CaaS/serverless infrastructure? 3. Do you want to future-proof security?

21 Conclusion & Call To Action Process: Security Without Friction 1. What is the current CI/CD process? 2. How do you embed security within the process? 3. How do you integrate with your exiting SecOps/SOC process?

22 Thank You Copyright 2018 Layered Insight. All rights reserved.