Monitoring Application Attack Surface and Integrating Security into DevOps Pipelines
3 likes1,458 views
The document discusses the importance of monitoring attack surfaces in the context of integrating security into DevOps pipelines, emphasizing the need for both dynamic and static application security testing. It covers the Hybrid Analysis Mapping (HAM) technology developed to combine results from these security tests and improve vulnerability management. The presentation also highlights tools and practices to effectively assess and mitigate risks associated with web applications, including various plugins and community resources from the Denim Group.
![Dynamic
Application
Security
Testing
(DAST)
• Spider
to
enumerate
attack
surface
– Crawl
the
site
like
Google
would
– But
with
authentication
/
session
detection
• Fuzz
to
identify
vulnerabilities
based
on
analysis
of
request/response
patterns
– If
you
send
a
SQL
control
character
and
get
a
JDBC
error
message
back,
that
could
indicate
a
SQL
injection
vulnerability
• A
finding
looks
like
(CWE,
relative
URL,
[entry
point])](https://image.slidesharecdn.com/monitoringattacksurfacetosecuredevopspipelinescontentv5owasp-170530160944/85/Monitoring-Application-Attack-Surface-and-Integrating-Security-into-DevOps-Pipelines-19-320.jpg)
![Unified
Endpoint
Database
• EndpointQuery
– dynamicPath
– staticPath
– Parameter
– httpMethod
– codePoints [List<CodePoint>]
– informationSourceType
• EndpointDatabase
– findBestMatch(EndpointQuery query):
Endpoint
– findAllMatches(EndpointQuery query):
Set<Endpoint>
– getFrameworkType():
FrameworkType](https://image.slidesharecdn.com/monitoringattacksurfacetosecuredevopspipelinescontentv5owasp-170530160944/85/Monitoring-Application-Attack-Surface-and-Integrating-Security-into-DevOps-Pipelines-23-320.jpg)
![Endpoints
CLI
Notes
• Syntax:
java
–jar
[jar-‐name].jar
/path/to/source
• JAR
name
will
change
based
on
build
ID
• After
Maven
build,
can
also
be
found
in:
$GIT/threadfix/threadfix-‐cli-‐
endpoints/target/
• You
want
the
”-‐jar-‐with-‐dependencies”
JAR
• Will
output
list
of
HTTP
methods,
URLs
and
parameters
based
on
analysis
of
the
source
code
• Attack
surface!
• Add
“-‐json”
to
the
end
of
the
command
to
get
output
in
JSON
format
– Easier
to
manipulate](https://image.slidesharecdn.com/monitoringattacksurfacetosecuredevopspipelinescontentv5owasp-170530160944/85/Monitoring-Application-Attack-Surface-and-Integrating-Security-into-DevOps-Pipelines-32-320.jpg)
![Scripting
Attack
Surface
Interactions
• [Anywhere]
– Script
using
endpoints-‐cli.jar JSON
outputs
• That’s
most
of
what
we’ve
seen
here
– Script
using
JSON
output
from
ThreadFix API
• Can
be
useful
in
environments
with
limited
access
to
source
code
• Java:
Use
endpoints-‐cli.jar as
a
library
– We
need
to
do
a
better
job
of
documenting
the
APIs
• Jython:
Use
endpoints-‐cli.jar as
a
library](https://image.slidesharecdn.com/monitoringattacksurfacetosecuredevopspipelinescontentv5owasp-170530160944/85/Monitoring-Application-Attack-Surface-and-Integrating-Security-into-DevOps-Pipelines-48-320.jpg)
Monitoring Application Attack Surface and Integrating Security into DevOps Pipelines
- 1. 8-‐12 May, 2017 Monitoring Attack Surface and Integrating Security into DevOps Pipelines Dan Cornell, CTO Denim Group
- 2. Agenda • Background • Importance of Attack Surface • What Does Attack Surface Have to Do with DevOps? • Hybrid Analysis Mapping (HAM) Background • Installation Instructions • Use Cases • Questions
- 3. My Background • Dan Cornell, founder and CTO of Denim Group • Software developer by background (Java, .NET, etc) • OWASP San Antonio 3
- 4. Denim Group Background • Secure software services and products company – Builds secure software – Helps organizations assess and mitigate risk of in-‐house developed and third party software – Provides classroom training and e-‐Learning so clients can build software securely • Software-‐centric view of application security – Application security experts are practicing developers – Development pedigree translates to rapport with development managers – Business impact: shorter time-‐to-‐fix application vulnerabilities • Culture of application security innovation and contribution – Develops open source tools to help clients mature their software security programs • Remediation Resource Center, ThreadFix – OWASP national leaders & regular speakers at RSA, SANS, OWASP, ISSA, CSI – World class alliance partners accelerate innovation to solve client problems 4
- 5. OWASP ZAP • Open source web proxy and dynamic application security testing tool • https://www.owasp.org/index.php/OWASP_Zed_Attack_Proxy_Project
- 6. Example Codebases • BodgeIt Store – Example vulnerable web application – https://github.com/psiinon/bodgeit • Java Spring Petstore – Example Spring application – https://github.com/spring-‐projects/spring-‐petclinic • Railsgoat – Example vulnerable web application – https://github.com/OWASP/railsgoat
- 7. ThreadFix Community Edition • Application vulnerability management – And some other stuff • https://github.com/denimgroup/threadfix
- 8. Downloads • https://dl.dropboxusercontent.com/u/737351/endpoints-‐json.jar • https://dl.dropboxusercontent.com/u/737351/threadfix-‐release-‐2.zap • https://github.com/denimgroup/threadfix-‐examples/tree/master/web_app_attack_surface
- 9. Importance of Attack Surface
- 10. Importance of Attack Surface • This is where an attacker can “reach out and touch” your application – Web: Mostly in the HTTP request: URL, parameters, headers (cookies) – Mobile, IoT: More complicated – We will focus on web today • Target for dynamic testing – Automated DAST – Manual assessment/penetration testing
- 11. What Does Attack Surface Have to Do With DevOps? • If you want your talk to be accepted, it has to have DevOps in the title • Let’s look at what we want from security in the DevOps pipeline
- 12. Security in the DevOps Pipeline Organizations like Etsy and Netflix are doing amazing things to secure apps via their DevOps pipelines
- 13. Security in the DevOps Pipeline • Testing – Synchronous – Asynchronous • Decision • Reporting Blog Post: Effective Application Security Testing in DevOps Pipelines http://www.denimgroup.com/blog/2016/12/effective-‐application-‐security-‐testing-‐in-‐devops-‐pipelines/ https://www.denimgroup.com/resources/effective-‐application-‐security-‐for-‐devops/
- 14. Focus on Testing in DevOps Pipeline • Many security tools run too long to include in many pipeline builds – Full SAST, DAST • Security testing also includes manual testing – Which is way too slow for most pipeline builds • Tracking attack surface changes over time can help us: – Focus testing activities – Trigger testing activities
- 15. Hybrid Analysis Mapping • Goal: Merge the results of SAST and DAST testing • Funded via DHS S&T SBIR contracts • Facilitated the creation of our attack surface modeling engine
- 16. Department of Homeland Security Support • Currently in Phase 2 of a DHS S&T CSD SBIR • Acronyms! – DHS = Department of Homeland Security – S&T = Directorate of Science and Technology – CSD = CyberSecurity Division – SBIR = Small Business Innovation Research • Geared toward developing new technologies for Federal customers • Hybrid Analysis Mapping (HAM) • Technology has been included with ThreadFix • Has also resulted in some other released components we will talk about today • Please do not assume this talk is endorsed by DHS – This is just me talking about what we have done
- 17. Hybrid Analysis Mapping (HAM) • Initial goal: Correlate and merge results from SAST and DAST • After we made that work, we found other stuff we could do with the technology
- 18. Hybrid Analysis Mapping (HAM) • Determine the feasibility of developing a system that can reliably and efficiently correlate and merge the results of automated static and dynamic security scans of web applications. HP Fortify SCA IBM AppScan Standard
- 19. Dynamic Application Security Testing (DAST) • Spider to enumerate attack surface – Crawl the site like Google would – But with authentication / session detection • Fuzz to identify vulnerabilities based on analysis of request/response patterns – If you send a SQL control character and get a JDBC error message back, that could indicate a SQL injection vulnerability • A finding looks like (CWE, relative URL, [entry point])
- 20. Static Application Security Testing (SAST) • Use source or binary to create a model of the application – Kind of like a compiler or VM • Perform analysis to identify vulnerabilities and weaknesses – Data flow, control flow, semantic, etc • A finding looks like (CWE, code/data flow)
- 21. Hybrid Analysis Mapping Sub-‐Goals • Standardize vulnerability types – Settled on MITRE Common Weakness Enumeration (CWE) • Match dynamic and static locations – Use knowledge of language/web framework to build attack surface database • Improve static parameter parsing – Parse out of source code to match with DAST result
- 22. Information Used • Source Code – Git, Subversion, Local Copy • Framework Type – Java: JSP, Spring, Struts – C#: .NET WebForms, .NET MVC – Ruby: Rails – PHP: in progress • Extra information from SAST results (if available)
- 23. Unified Endpoint Database • EndpointQuery – dynamicPath – staticPath – Parameter – httpMethod – codePoints [List<CodePoint>] – informationSourceType • EndpointDatabase – findBestMatch(EndpointQuery query): Endpoint – findAllMatches(EndpointQuery query): Set<Endpoint> – getFrameworkType(): FrameworkType
- 24. Merging SAST and DAST Results • I have a DAST result: – (“Reflected XSS”, /login.jsp, “username” parameter) • Query the Endpoint Database: – Entry point is com.something.something.LoginController.java, line 62 • Search the other findings for SAST results like: – (“Reflected XSS”, source at com.something.something.LoginController.java, line 62) • If you find a match – correlate those two findings • Magic!
- 25. That’s Great But I Want More • So our research produced a successful/valuable outcome – Hooray • But – given these data structures, what else can we do? • From an EndpointDatabase we can: – Get all of the application’s attack surface – Map DAST results to a specific line of code • Given those capabilities we can: – Pre-‐seed scanners with attack surface – Map DAST results to lines of code in a developer IDE – Map DAST results to lines of code in SonarQube
- 26. Final Thoughts on SBIR Work with DHS S&T • Great use of the SBIR program – In my humble and totally unbiased opinion • Proved to be the tipping point to developing HAM – HAM was interesting, but required material investment • Research produced a successful outcome (we think) • We found other things we could do with the technology • Released much of it open source to increase adoption
- 27. Scanner Seeding • What if we could give the DAST spidering process a head start? • Pre-‐seed with all of the attack surface – Landing pages that link in to the application – Hidden directories – Backdoor or “unused” parameters • Currently have plugins for OWASP ZAP and BurpSuite – Plugin for IBM Rational AppScan Standard is in progress https://github.com/denimgroup/threadfix/wiki/Scanner-‐Plugins
- 28. Getting the Plugins • Main ThreadFix site – https://github.com/denimgroup/threadfix/ • ThreadFix build instructions – https://github.com/denimgroup/threadfix/wiki/Development-‐Environment-‐Setup – “Running ThreadFix Without an IDE” • Download plugins from ThreadFix
- 29. Plugin Installation • OWASP ZAP plugin installation instructions – https://github.com/denimgroup/threadfix/wiki/Zap-‐Plugin • Plugins also available for: – Portswigger BurpSuite Professional – IBM Rational AppScan (soon)
- 30. Attack Surface Enumeration • Find all of the attack surface – URLs – Parameters that will change application behavior – Future: Cookies, other HTTP headers • Why is this a problem? – Hidden landing pages – Multi-‐step processes that automated crawls don’t traverse – Unknown parameters – Debug/backdoor parameters (will discuss this further) • Great for REST APIs support single-‐page web applications and mobile applications
- 31. Attack Surface Enumeration Benefits • Reduce false negatives from scanners – Better coverage for standard fuzzing • Pen test all of the application
- 32. Endpoints CLI Notes • Syntax: java –jar [jar-‐name].jar /path/to/source • JAR name will change based on build ID • After Maven build, can also be found in: $GIT/threadfix/threadfix-‐cli-‐ endpoints/target/ • You want the ”-‐jar-‐with-‐dependencies” JAR • Will output list of HTTP methods, URLs and parameters based on analysis of the source code • Attack surface! • Add “-‐json” to the end of the command to get output in JSON format – Easier to manipulate
- 34. Scanner Attack Surface Seeding Demo
- 35. attack_surface_lib.py • Warning! • What’s the opposite of ”Pythonic?” • Race conditions, sloppy file handling, etc • Possibly even some command injection – That you can currently exploit from … the command line – Some mitigations in place, but… • Please be careful what you attach this to
- 36. attack_surface_lib.py • What does it do? – Takes JSON output of cli-‐endpoints • Creates attack surface tree data structure • Calculates differences between trees – Some git utility tasks • Used as the basis for upcoming examples • https://github.com/denimgroup/threadfix-‐examples/blob/master/web_app_attack_surface/attack_surface_lib.py
- 37. Attack Surface Visualization Demo Code: https://github.com/denimgroup/threadfix-‐examples/blob/master/web_app_attack_surface/make_d3_tree_json.py HTML framework: https://github.com/denimgroup/threadfix-‐examples/tree/master/web_app_attack_surface/html
- 38. Attack Surface Comparison Visualization Demo Code: https://github.com/denimgroup/threadfix-‐examples/blob/master/web_app_attack_surface/make_d3_tree_json.py HTML framework: https://github.com/denimgroup/threadfix-‐examples/tree/master/web_app_attack_surface/html
- 39. Diffing Attack Surface Demo Code: https://github.com/denimgroup/threadfix-‐examples/blob/master/web_app_attack_surface/diff_attack_surface_git_commits.py
- 40. What About Behavior Changes? • Identify files that have changed that are associated with attack surface • Mark that attack surface as possibly having changed behavior • Is this perfect? No. • Does it provide additional information with potential value? Yes.
- 41. Potential Behavior Modified Demo
- 42. Applications for DevOps Pipelines • Target DAST testing to focus on new attack surface in latest build – “Run an authenticated ZAP scan against the three new URLs added in the last commit” • Set thresholds for when manual assessment/penetration testing is triggered – “Schedule a manual penetration test when the attack surface has increased by 10 URLs” – “Schedule a manual penetration test when the attack surface has increased by 5%” – Focus those efforts on new attack surface • ChatOps: Attack surface delta notifications on commit – “Commit beb78c835706efe5d619148b9a8dc9e35ee9572b added attack surface: /advanced.jsp, /preferenes.jsp”
- 43. attacksurface_notifier.py • Watch a git repository for new commits • When there are commits, check for attack surface changes • On attack surface changes – do stuff • In production: would be done via CI/CD server • BUT for demo purposes… • https://github.com/denimgroup/threadfix-‐examples/blob/master/web_app_attack_surface/attacksurface_notifier.py
- 44. Attack Surface ChatOps Demo Code: https://github.com/denimgroup/threadfix-‐examples/blob/master/web_app_attack_surface/attacksurface_notifier.py
- 45. Manual Test JIRA Ticket Demo Code: https://github.com/denimgroup/threadfix-‐examples/blob/master/web_app_attack_surface/attacksurface_notifier.py
- 46. Differential ZAP Scan Demo Code: https://github.com/denimgroup/threadfix-‐examples/blob/master/web_app_attack_surface/attacksurface_notifier.py
- 48. Scripting Attack Surface Interactions • [Anywhere] – Script using endpoints-‐cli.jar JSON outputs • That’s most of what we’ve seen here – Script using JSON output from ThreadFix API • Can be useful in environments with limited access to source code • Java: Use endpoints-‐cli.jar as a library – We need to do a better job of documenting the APIs • Jython: Use endpoints-‐cli.jar as a library
- 49. Jython Use of HAM Library Demo Code: https://github.com/denimgroup/threadfix-‐examples/blob/master/web_app_attack_surface/jython_endpoints_cli.py
- 50. Next Steps • Expand the model of application attack surface – Currently: Parameters, HTTP verbs – Working on: HTTP headers (cookies) – Future: Other application types: Mobile, IoT • Better visualization – More details – Better granularity – Track changes over time • Native integrations: Jenkins, Slack, HipChat, JIRA, etc – This is very “scripty” right now
- 51. Questions / Contact Information Dan Cornell Principal and CTO dan@denimgroup.com Twitter @danielcornell (844) 572-‐4400 www.threadfix.it 51