Top Banner
CONTINUOUS SECURITY FOR CONTINUOUS DEVELOPMENT
18

FutureStack 2015 - Continuous security for continuous development

Feb 13, 2017

Download

Technology

IMMUNIO
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: FutureStack 2015 - Continuous security for continuous development

CONTINUOUS SECURITYFOR CONTINUOUS DEVELOPMENT

Page 2: FutureStack 2015 - Continuous security for continuous development

WE USED TO BUILD APPS LIKE THIS:

January - April: Write code

May: Test / Fix Bugs / Security!

June: Deploy

Page 3: FutureStack 2015 - Continuous security for continuous development

NOW WE BUILD APPS LIKE THIS:

9:00 AM - Noon: Write code

Noon: Test / Fix Bugs / Security!

2:00 PM: Deploy

Page 4: FutureStack 2015 - Continuous security for continuous development

COMPARING SECURITY TECHNIQUES

▸Code Reviews & Penetration Testing

▸Static Analysis

▸Web Application Firewalls (WAFs)

▸Run-time Application Self Protection

Page 5: FutureStack 2015 - Continuous security for continuous development

COMPARING SECURITY TECHNIQUES

CODE REVIEWS & PEN TESTING

▸ Requires significant expertise

▸ Manual process which takes time

▸ Prone to human error

▸ “Permanently” fixes underlying issue (when done well)

Page 6: FutureStack 2015 - Continuous security for continuous development
Page 7: FutureStack 2015 - Continuous security for continuous development

COMPARING SECURITY TECHNIQUES

▸Code Reviews & Penetration Testing

▸Static Analysis

▸Web Application Firewalls (WAFs)

▸Run-time Application Self Protection

Page 8: FutureStack 2015 - Continuous security for continuous development

BRAKEMANSCANNER

HTTPS://GITHUB.COM/PRESIDENTBEEF/BRAKEMAN

Page 9: FutureStack 2015 - Continuous security for continuous development

COMPARING SECURITY TECHNIQUES

STATIC CODE ANALYSIS

▸ “Warnings” != Vulnerabilities

▸ Requires manual review and manual correction

▸ Easy-to-implement

▸ Gives engineers code-level details to find and fix vulns

Page 10: FutureStack 2015 - Continuous security for continuous development

COMPARING SECURITY TECHNIQUES

▸Code Reviews & Penetration Testing

▸Static Analysis

▸Web Application Firewalls (WAFs)

▸Run-time Application Self Protection

Page 11: FutureStack 2015 - Continuous security for continuous development

COMPARING SECURITY TECHNIQUES

WEB APPLICATION FIREWALL (WAF)

▸ Needs to be manually trained and updated (rule writing)

▸ Has little context available (sits outside the application)

▸ Adds latency (extra network hop, usually)

▸ Protects the app in realtime, in production

▸ A lot of vendors to choose from

Page 12: FutureStack 2015 - Continuous security for continuous development

COMPARING SECURITY TECHNIQUES

▸Code Reviews & Penetration Testing

▸Static Analysis

▸Web Application Firewalls (WAFs)

▸Run-time Application Self Protection

Page 13: FutureStack 2015 - Continuous security for continuous development

LET’S TALK ABOUTRASP(Run-time Application Self-Protection)

Page 14: FutureStack 2015 - Continuous security for continuous development

COMPARING SECURITY TECHNIQUES

RUNTIME APPLICATION SELF-PROTECTION (RASP)

▸ Requires integration, or explicit framework/library support

▸ Protects the app in realtime, in production

▸ Visibility of session, user, behavior, and more

▸ Gives engineers code-level details to find and fix vulns

▸ Protects against many zero-day exploits

Page 15: FutureStack 2015 - Continuous security for continuous development

INSTALL

Page 16: FutureStack 2015 - Continuous security for continuous development

CONFIGURE

Page 17: FutureStack 2015 - Continuous security for continuous development

LIVE DEMO!

Page 18: FutureStack 2015 - Continuous security for continuous development

IMMUNIO

HTTPS://WWW.IMMUN.IO/