security as code owasp

30
SECURITY AS CODE A NEW FRONTIER Christian Price Cloud Security Architect, Intuit Shannon Lietz Sr. Mgr & DevSecOps Leader, Intuit

Upload: shannon-lietz

Post on 07-Jan-2017

589 views

Category:

Technology


0 download

TRANSCRIPT

Page 1: Security as  Code owasp

SECURITY AS CODE

A NEW FRONTIER

Christian PriceCloud Security Architect, Intuit

Shannon LietzSr. Mgr & DevSecOps Leader, Intuit

Page 2: Security as  Code owasp

IN THE BEGINNING

COMPLIANCE • 375 PAGE DOCUMENT• MINIMUM BASELINE: 87 RATIONALIZED

CONTROLS• RISK BASED ON IMPACT & LIKELIHOOD

SOFTWARE DEVELOPER• OK – HOW DOES THAT APPLY TO WHAT I

DO?

Page 3 of 375

Security Configuration ProceduresV 3.6.0.1.1,January 2011

UBERSECRET

Page 3: Security as  Code owasp

CHOICE

Page 4: Security as  Code owasp

WHO WE ARE

• CLOUD SECURITY ENGINEERING @ INTUIT• 20+ YEARS OF SECURITY EXPERIENCE • DIVERSIFIED GROUP OF DEVELOPERS,

OPERATIONS & SECURITY• FOUNDERS OF DEVSECOPS.ORG• RUGGED BUNCH OF RESEARCHERS &

EMERGING TECHNOLOGISTS-- FOUNDER --

Page 5: Security as  Code owasp

QUICK OVERVIEW• PROBLEM STATEMENT• DEVOPS REQUIRES CONTINUOUS DEPLOYMENTS• FAST DECISION MAKING IS CRITICAL TO DEVOPS SUCCESS• TRADITIONAL SECURITY JUST DOESN’T SCALE OR MOVE

FAST ENOUGH

• WELCOME DEVSECOPS!• CUSTOMER FOCUSED MINDSET• SCALE, SCALE, SCALE• OBJECTIVE CRITERIA• PROACTIVE HUNTING• CONTINUOUS DETECTION & RESPONSE

BangHead Here

Page 6: Security as  Code owasp

RUGGED SECURITY

Com

plia

nce

Oper

atio

ns

Secu

rity

Ope

ratio

ns Security Sc

ience

Security

Engineering

OPSSECDEVAppSec

NEW

NEW

NEW

• Security as Code• Self-Service Testing• Red Team/Blue Team• Inline Enforcement• Analytics & Insights• Detect & Contain• Incident Response• Investigations• Forensics

Page 7: Security as  Code owasp

THE ART OF DEVSECOPS -> SECURITY AS CODE

DevSecOps

Security Engineering

Experiment, Automate, Test

Security Operations

Hunt, Detect, Contain

Compliance Operations

Respond, Manage, Train

Security Science

Learn, Measure, Forecast

Page 8: Security as  Code owasp

EVOLUTION

Page 9: Security as  Code owasp

FULL STACK VULNERABILITIES

• API KEY EXPOSURE -> 8

HRS• DEFAULT

CONFIGS -> 24 HRS

• SECURITY GROUPS -> 24

HRS • ESCALATION OF

PRIVS -> 5 DAYS

• KNOWN VULN -> 8 HRS

Page 10: Security as  Code owasp

SECURITY AS CODE

• INFRASTRUCTURE -> TEMPLATES & RECIPES• FIREWALLS -> SECURITY GROUPS• ACCESS CONTROLS -> IAM USERS AND POLICIES• IDS -> HOST AGENTS & RESOURCE TESTING• LOGGING -> API & INSTANCE LOGGING• FORENSICS -> SNAPSHOTS & API PROFILE• VULNERABILITY SCORES -> GRADES

Page 11: Security as  Code owasp

SOFTWARE DEFINED UPS & DOWNS

PLUS• FAR MORE DATA THAT SIMPLY NEEDS TO BE HARNESSED• FASTER DETECTION, CONTAINMENT & REMEDIATION• ABILITY TO REFRESH STACKS TO AVOID CRITICAL ISSUES

MINUS• MUCH EASIER TO MAKE CRITICAL MISTAKES• MOST EVENTS COME FROM DEFAULT IMPLEMENTATIONS• HUGE DATA MAKES EVERYTHING HARDER

+/-

Page 12: Security as  Code owasp

LOW FRICTION TRANSPARENT GOVERNANCE

Central Account(Trusted)

Admin

IAM IAMIAM IAM IAM IAM

SecRole SecRole SecRole SecRole SecRole SecRole

IAM

How did we decide which roles would be deployed?• Human

• IAM Admin• Incident Response• Read Only

• Services• IAM Grantor• Instance Roles required to support

security services• Read Only

Page 13: Security as  Code owasp

TOOLS

Page 14: Security as  Code owasp

ENVIRONMENT

• SOFTWARE-DEFINED ENVIRONMENT

• BLAST RADIUS CONTAINMENT• NATIVE MULTI-FACTOR AUTH• GRANULAR ACCESS CONTROLS• EXTENSIVE LOGGING

AWSRUBY, PYTHON,

GOAPI/MICRO-SERVICES

LOG EVENTS

Page 15: Security as  Code owasp

GITHUB

• BASELINE TEMPLATES (CLOUDFORMATION, SCRIPTS, ETC.)

• PATTERNS & DECISIONS• RULES, SIGNATURES, SEARCH

QUERIES, ALERT DEFINITIONS• WHITELISTING & SHARING TO

EXTEND FOR SCALE

Page 16: Security as  Code owasp

COMPONENTS

MACHINE IMAGESDOCKER

CONTAINERSBASELINE SCRIPTS

LIBRARIES & TOOLKITS

• BUILD SECURE COMPONENTS FOR INCLUSION

• MAKE RESOURCE LEVEL CHANGES AND DISSEMINATE TO TEAMS

• APPLY LESSONS FROM SECURITY OPERATIONS & INCIDENT RESPONSE TO BASELINE COMPONENTS

• MANAGE FOR DRIFT BY BUILDING OUT DIFF TOOLS

Page 17: Security as  Code owasp

RESOURCE TESTING & VALIDATION

• RESOURCE AND COMPONENT TESTING IMPROVES RUGGEDNESS OF SOFTWARE DURING INTEGRATION

• TOOLS CAN BE CALLED FROM CONTINUOUS INTEGRATION & CONTINUOUS DEPLOYMENT PIPELINE

• RESPONDERS CAN TRIGGER INLINE TESTING TO IDENTIFY VULNERABILITIES UNDER ATTACK

• ATTACKS ARE DEFINED IN GHERKIN• API TO REQUEST TESTING BY TYPE

ZAP PROXYGAUNTLTNESSUS

NEXPOSEMETASPLOITBURP SUITE

LIFECYCLE/AUDITOR

Page 18: Security as  Code owasp

SCHEDULER & QUEUES

• SCHEDULING FOR BASELINE CHECKS• AD-HOC OPERATIONS REQUIRE QUEUES• COORDINATION AMONG MICRO-

SERVICES• MULTI-USE DATA SUPPORTS VARYING

SECURITY VIEWS

RESQUESNS SQSKINESISKAFKA

Page 19: Security as  Code owasp

RECONNAISSANCE: DATA IS CRITICAL

insightssecuritysciencesecurity

tools & data

AWS accounts

S3

Glacier

EC2

CloudTrail

ingestion

threat intel

Page 20: Security as  Code owasp

SELF-SERVICE

Page 21: Security as  Code owasp

RESPONDER, SELFIE & GRAVE ROBBER

• TOOLKIT FOR INCIDENT RESPONDERS TO TRIAGE & QUERY ACCOUNT & INSTANCES AT SAME TIME

• SNAPSHOT INSTANCES FOR REAL-TIME ANALYSIS

• LOTS OF STORAGE, FASTER WHEN BIG DATA IS APPLIED

RUBYAWS API

DR ACCOUNTENCASE

Page 22: Security as  Code owasp

LESSONS

Page 23: Security as  Code owasp

TABLE STAKES

• GO NATIVE, WHEN POSSIBLE• MFA -> TABLE-STAKES, USE IT.• PRIVILEGED ACCESS -> USE LEAST PRIVILEGE, ASSUMEROLE WHEN

NEEDED• SECURITY GROUPS -> LIMIT ACCESS AND SCOPE TO SPECIFIC NEEDS• DEPLOYMENT AUTOMATION -> OVER-PRIVILEGED, UNDER-SECURED• RE-STACK OFTEN -> CRITICAL VULNERABILITIES OCCUR ON AVERAGE EVERY 10

DAYS.• USE ENCRYPTION OPTIONS

Page 24: Security as  Code owasp

DON’T BE AN ALL-*

Page 25: Security as  Code owasp

DON’T EMBED SECRETS…

…DON’T PUT ANY API KEYS, SSH PRIVATE KEYS, OR SSL PRIVATE KEYS IN :• CLOUDFORMATION, • USER-DATA, • GIT, • OR ANYWHERE ELSE THAT CAN’T KEEP A SECRET,

SECRET

Page 26: Security as  Code owasp

DON’T OVER-SHARE…

WE DON’T WANT TO KNOW YOUR SECRETS…

…AND YOU DON’T WANT YOUR SECRETS GETTING OUT.

Page 27: Security as  Code owasp

DON’T BE A ZERO

Page 28: Security as  Code owasp

CHOICE?

Page 29: Security as  Code owasp

EMERGING SECURITY TRENDS

• SHORTAGE OF SECURITY PROFESSIONALS• BIG COMPANIES ARE ATTEMPTING TO SCALE SECURITY

TO MOVE FASTER: FACEBOOK, NETFLIX, LINKEDIN, AWS, INTUIT

• INDUSTRY LEADERS TALKING ABOUT THE INTEGRATION OF DEVOPS & SECURITY: JOE SULLIVAN, JASON CHAN, GENE KIM, JOSH CORMAN

• INTRODUCTION OF DEVSECOPS AT MIRCON IN 2014• SECDEVOPS AT RSA 2015 WAS FULL DAY OF

DEDICATED CONTENT• LINKEDIN PEOPLE SEARCH: 36 DEVSECOPS, 13

SECDEVOPS, 11 DEVOPSSEC, 33K+ CLOUD SECURITY

Page 30: Security as  Code owasp

GET INVOLVED

• DEVSECOPS.ORG• @DEVSECOPS ON TWITTER• DEVSECOPS ON LINKEDIN• RUGGEDSOFTWARE.ORG• JOIN US !!!