How did Shellshock actually happen and how did we succumb to such a vulnerability? In our webinar, we explained how Shellshock came about, and how to develop the right security monitoring and automation system protections to prevent the next one from devastating the cloud.

1. Preparing for the Next
Shellshock

2. Jen Andre
Threat Stack
Co-Founder & Chief Scientist
@fun_cuddles

3. 0
2000
4000
6000
8000
1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014
0-1 1-2 2-3 3-4 4-5 5-6 6-7 7-8 8-9 9-10
Vulnerabilities by Score
1999 - 2014
7439
source: http://www.cvedetails.com/

4. How and What
Shellshock

5. The details

6. At a Glance
• 6 CVEs
• Initial report (CVE-2014-6271), CVE-2014-627,
CVE-2014-6278, CVE-2014-7169,
CVE-2014-7186, CVE-2014-7187
• ??? Vendors/Tools Affected

7. Lessons Learned
Question What We Know
Prevention Is a Myth
Monitor Everything in Real Time

8. The myth of the “many
eyes” trope?
?

9. "To put these exponential numbers into perspective, we’re
about to transition from an Internet the size of a golf ball to
an Internet the size of the sun." Marc Goodman, Global Security Futurist

10. Continuous Delivery
& You

11. How To Prepare
Understand Your Responsibility
Uncover New Threats
Protect Customer Data w/ Continuous Monitoring

12. Day Zero
A walk through day zero, with the proper safeguards in place

13. • The Setup
• 1 VM running vulnerable version of bash shell with real-
life Nagios cgi-bin exploit.
• Threat Stack installed.
• The Investigation
• See how the exploit works, and attack is detected
without signatures
• The Response
• How to track down impact.

14. Get Started Today!
Request a Demo
threatstack.com/demo.html
Start a trial
threatstack.com/signup.html