Application Security Workflow Automation Using Docker and Kubernetes Abhisek Datta Head of Technology, Appsecco 

Rootconf Pune 2019 

About Me – Abhisek Datta • Head of Technology (appsecco.com) • A boutique security consulting company • TechWing @ null0x00 (null.co.in) • An Open Security Community • Security Researcher • Discovered vulnerabilities in MS Office, Internet Explorer, HP SiteScope etc. • Open Source Contributor • Wireplay, RbWinDBG etc. github.com/abhisek 

1. How does an Application Security Workflow look like (Our opinion) 2. How to get started in automating Application Security Workflow using KubeSecO 3. Our approach of security automation using Kubernetes native technologies Key Take Away 

What is Docker and Kubernetes? 

What is Docker and Kubernetes? • https://www.katacoda.com/courses/docker • https://www.katacoda.com/courses/kubernetes 

Let's do HANDS ON docker run –it jess/hollywood 

Setup Kubernetes Deploy apps and services Run Workflow Getting Started with KubeSecO https://github.com/appsecco/kubeseco 

$ git clone https://github.com/appsecco/kubeseco $ cd kubeseco $ ./cluster_create_gcp.sh # Optional $ ./setup.sh # Need kubectl & helm KubeSecO: Setup and Get Started 

Application Security Workflow 

Domain / URL / ... OSINT Application Discovery Security Testing Exploitation Analysis AppSec Workflow 

An Example AppSec Workflow Domain Hosts Subdomain Enumeration CIDR ASN Search DNS SPF, MX etc. Port and Service Scanning URLs Technologies Cloud Infrastructure Emails Public Breach DB Query Password Spraying Application Security Scan 

Data Collection Analysis Inference Further Actions How does it look like from Automation Perspective? Security Tools Human + Learning Systems Human + Learning Systems Feedback Loop 

Security Tool Workflow Rules Security Automation Automating AppSec Workflow 

KubeSecO Live in Action 

What's under the hood? 

How does the system look like? 

Driving the System – Events FTW! API Service HTTP POST NATS Write to NATS Message Queue Scanners (Client) Minio Object Storage Persist Output Output Analysis and Feedback Alerting and Notification Tool Output Event 

• 3rd Party Tools are not in our control • We need to be able to • Receive input from NATS • Run tool with tool specific command line • Receive output or check for error • Persist output to Minio The Tool Adapter (Pattern) 

1. Package 3rd party tools as Docker containers 2. Add Tool Adapter binary and set as entrypoint 3. Write Kubernetes deployment spec (YAML) 4. Deploy to Kubernetes 5. Write YAML rules for Feedback Processing Adding a Security Tool (3rd Party) 

Security Tool Dockerfile 

Security Tool Kubernetes Spec (YAML) 

Match Transform Take Action Feedback Processor (Driving the System) 

Feedback Processor - Example 

• State management is difficult due to asynchronous nature of the system • NATS connection issue with preemptible nodes on GKE • Capacity planning and analysis • Cost analysis Challenges, Constraints and Things to do 

How to Contribute 1. Clone the repository from Github 2. Try out and report bugs 3. Add new security tools 4. Add feedback processor rules 5. Submit PR 

Questions? [email protected] That’s all for now.. https://appsecco.com @abh1sek github.com/abhisek github.com/appsecco/kubeseco