410 likes | 619 Views
Jeff Williams, CEO Aspect Security, Inc. Application Security at DevOps Speed and Portfolio Scale. About Me. Application Security Is Healthcare. Sensors Are Revolutionizing Healthcare. Your phone will know you’re sick before you do!.
E N D
Jeff Williams, CEO Aspect Security, Inc. Application Security atDevOps Speed and Portfolio Scale
Sensors Are Revolutionizing Healthcare Your phone will know you’re sick before you do! Instrumenting the body means continuousrealtime monitoring… Not periodic checkups
Traditional Tools and Techniques Are Failing… DevOps Agile Aspect Oriented Programming CloudMobile RawSocket Libraries and Frameworks Serialized Objects Inversion of Control SOAP/REST Javascript Ajax
AppSec Progress Continuous AppSec Software Security
Defining “Portfolio Scale” The rightdefenses for everyapplication are… • Present • Correct • Used Properly
Defining “DevOpsSpeed” Application security happens continuouslyand in real time
One Thing at a Time… Is my portfolio protected against clickjacking?
Gathering Intelligence Controller Business Functions Data Layer Presentation Third Party Libraries Framework Application Server Platform Runtime Operating System
Security Intelligence Sources Data Flow Backend Connections HTTP Traffic Vulnerability Trace Control Flow Libraries and Frameworks Configuration Data
Designing a Clickjacking Sensor • Experiment Style • Environment • Analysis Technique • Data Sources • Positive • Dev • Manual • Code • Negative • CI • SAST • HTTP • Sampling • Test • DAST • Configuration • Intelligence • QA • IAST • Data Flow • Staging • Passive • Control Flow • Security • Libraries • JUnit • Choose based on: • Speed • Accuracy • Feedback • Scalability • Ease of Use • Cost • Prod • Connections
Continuous ClickJacking Defense Verification A new HTTP sensor to verify that the X-Frame-Options header is set to DENY orSameOrigin on every webpage Data Warehouse: Application Security Intelligence DEV CI TEST QA STAG SEC OPS Manual Static Dynamic JUnit Interactive
Run Against Entire Portfolio TB RPC F IR XX CM JJ RH QP X DD TY CO AS RA & @ S
Check Your Headers https://cyh.herokuapp.com/cyh
One Small Step Towards Continuous AppSec • We transformed clickjackingverification todevops speed and portfolio scale! Okay, clickjacking. Big deal.
Access Control Intelligence Sensor • Control Flow • SAST • Intelligence • CI
Known Vulnerable Libraries Sensor Run DependencyCheckduring every build (and do a build once a month even if nothing changed) • Libraries • SAST • Negative • CI
CSRF Defense Sensor • Run tests through ZAP • ZEST to check CSRF Token • Get results via ZAP REST API • HTTP • Passive • Positive • QA
Canonicalization Correctness Sensor • Code • JUnit • Positive • Staging
Injection Sensors Use IAST tools for DFA vulnerabilities • Data Flow • IAST • Negative • Dev
Architecture, Inventory, and More… • What would you like to gather from all your applications? • Inventory? Architecture? Outbound connections? Lines of code? Security components? • All possible…. and all at devops speed and portfolio scale
Building Continuous AppSec Data Warehouse: Application Security Intelligence DEV CI TEST QA STAG SEC OPS Manual Static Dynamic JUnit Interactive
Sensors? How do you know what sensors you need? • The OWASP Top Ten? • What your tools are good at? • What your pentester thinks is important? • Actually figure out what matters?
What’s In Your Expected Model? Expected Requirements Threat Model Abuse Cases Policy Standards… • There is no security without a model
What Are You Actually Testing? Actual Pentest Code Review Tools Arch Review …
Unfortunately… Expected Actual Not being tested (aka RISK) Doesn’t need testing (aka WASTE)
Are You Secure? Secure?
Aligning Sensors with Business Concerns • Fraud • Availability
Continuous Application Security! Expected Actual Translate “expected” into sensors Application Portfolio A A A New Threats, Business Priorities A A A A A A A A A A A A A A A Application security dashboards
Transforming AppSec • We will never improve if our only metric is whether we are doing what everyone else is doing
Thank You! Please stop by the Contrast Security booth! @planetlevel
Expected:Tracking Coverage • Minimal data collection • … • Strong encryption in storage and transit • All external connections use SSL • All internal connections use SSL • SSL hardened according to OWASP • All highly sensitive data encrypted • Encryption uses standard control • Encryption uses AES, no CBC or ECB • Universal authentication • … • Pervasive access control • … • Injection defenses • Strict positive validation of all input • Use of parameterized interfaces • All parsers hardened • XML parsers set to not use DOCTYPE • Browser set no content sniffing header • Etc… • Use Hibernate and secure coding • Use JQuery and secure coding • Etc… InfrastructureSecurity Logging andAccountability DataProtection SecureDevelopment SecurityVerification Incident Response