whitehat security 2014 statistics report explained

34
WhiteHat Security 2014 Stats Report Explained Presented by: Jeremiah Grossman Twitter: @jeremiahg #2014WebStats

Upload: jeremiah-grossman

Post on 02-Nov-2014

195 views

Category:

Technology


3 download

DESCRIPTION

In this report, we put this area of application security understanding to the test by measuring how various web programming languages and development frameworks actually perform in the field. To which classes of attack are they most prone, how often and for how long; and, how do they fare against popular alternatives? Is it really true that the most popular modern languages and frameworks yield similar results in production websites? By analyzing the vulnerability assessment results of more than 30,000 websites under management with WhiteHat Sentinel, we begin to answer these questions. These answers may enable the application security community to ask better and deeper questions, which will eventually lead to more secure websites. Organizations deploying these technologies can have a closer look at particularly risk-prone areas. Software vendors may focus on areas that are found to be lacking. Developers can increase their familiarity with the strengths and weaknesses of their technology stack. All of this is vitally important because security must be baked into development frameworks and must be virtually transparent. Only then will application security progress be made.

TRANSCRIPT

Page 1: WhiteHat Security 2014 Statistics Report Explained

WhiteHat Security2014 Stats Report Explained

Presented by: Jeremiah GrossmanTwitter: @jeremiahg

#2014WebStats

Page 2: WhiteHat Security 2014 Statistics Report Explained

Founded in 2001

• 125+ web security experts: world’s largest security experts

• 30,000s of assessments: currently running at this moment

• Security leader:Gartner Magic Quadrant

Page 3: WhiteHat Security 2014 Statistics Report Explained

Title: iCEOInfo: 15 years in Info SecurityFun fact: Brazillian Jiu-Jitsu Black Belt

Jeremiah Grossman

Page 4: WhiteHat Security 2014 Statistics Report Explained

What I’ll discuss today…

• Overall key findings• Average vulnerabilities: security

posture• Median days open by vulnerability

class• Vulnerability class by language• Industry analysis• Recommendations/takeaways– How to use this report based on job role

Page 5: WhiteHat Security 2014 Statistics Report Explained

Déjà Vu

• Numerous report conclusions all point to the need for more secure software– Verizon Data Breach Report– FireHost “Superfecta” Attack Report

• Cyber insurance claims reaching as high as $20 million, with an average payout of just above $900,000

Page 6: WhiteHat Security 2014 Statistics Report Explained

Big Questions

• Are some programming languages more secure than others?

• What are the prevalent threats per programming language?

• What are the prevalent threats per industry?

Page 7: WhiteHat Security 2014 Statistics Report Explained

• 30,000 websites in all different verticals

• Purely from WHS assessing w/ Sentinel

• Because we focused on programming language

About the Data

Page 8: WhiteHat Security 2014 Statistics Report Explained

Overall Key Findings

Page 9: WhiteHat Security 2014 Statistics Report Explained

Percent of URLs by Language

.NET

JAVA

ASP

PHP

ColdFusion

Perl

5% 10% 15% 20% 25% 30% 40% 50%

Page 10: WhiteHat Security 2014 Statistics Report Explained

Mean Number Of Vulnerabilities in Each Language

11 11 11 10 7 6

.Net Java ASP PHP ColdFusion Perl

Page 11: WhiteHat Security 2014 Statistics Report Explained

• Risk exposure does not vary widely between languages, as language choice does not affect number of vulnerabilities.

• We will take a look at risk exposure and remediation rates further into the discussion.

Risk exposure

Page 12: WhiteHat Security 2014 Statistics Report Explained

Average vulnerabilities

Page 13: WhiteHat Security 2014 Statistics Report Explained

Vulnerabilities Found per LanguageWhat does this mean?

.NET

JAVA

ASP

PHP

ColdFusion

Perl

5% 10% 15% 20% 25% 30% 40% 50%

(*Larger consequently more vulnerable)

Page 14: WhiteHat Security 2014 Statistics Report Explained

Median Days Open by Vulnerability Class

Page 15: WhiteHat Security 2014 Statistics Report Explained

Median Days Open - XSS• XSS vulnerabilities appear to take a

relative amount of effort to fix regardless of the language.

• Median days open by language– Perl open for median 184 days– ASP 135– .Net 126– PHP 49

Page 16: WhiteHat Security 2014 Statistics Report Explained

Median Days Open - SQLi• PHP stood out from the pack with the

lowest median days 6.8• Median days open by language– ColdFusion open for median 107.4 days– ASP 97.5– Java 64.8– .Net 51.4– Perl 19.4

Page 17: WhiteHat Security 2014 Statistics Report Explained

• ASP vulnerabilities remain open the longest at 139 days

• ColdFusion has the largest days open for SQLi at 107

• Languages with the most security controls are taking the longest to remediate. Why?

Rounding Out the Top 5

Page 18: WhiteHat Security 2014 Statistics Report Explained

Vulnerability Classes

Page 19: WhiteHat Security 2014 Statistics Report Explained

Vulnerabilities Percent Class by Language

Page 20: WhiteHat Security 2014 Statistics Report Explained

Remediation Rates

Page 21: WhiteHat Security 2014 Statistics Report Explained

Remediation Rates by Vulnerability Class

Page 22: WhiteHat Security 2014 Statistics Report Explained

Industrial Analysis

Page 23: WhiteHat Security 2014 Statistics Report Explained

Industry Analysis - Banking

ASP

ColdFusion

.NET

Java

Perl

PHP

5% 10% 20% 30% 40% 50% 60% 70%

57% XSS

44% Info. Leakage

49% XSS

Page 24: WhiteHat Security 2014 Statistics Report Explained

Industry Analysis – IT

ASP

ColdFusion

.NET

Java

Perl

PHP

5% 10% 20% 30% 40% 50% 60% 70%

57% XSS

44% Info. Leakage

49% XSS

Page 25: WhiteHat Security 2014 Statistics Report Explained

Industry Analysis – retail

ASP

ColdFusion

.NET

Java

Perl

PHP

5% 10% 20% 30% 40% 50% 60% 70%

44% Info. Leakage

57% XSS

49% XSS

Page 26: WhiteHat Security 2014 Statistics Report Explained

Industry analysis – Financial service

ASP

ColdFusion

.NET

Java

Perl

PHP

5% 10% 20% 30% 40% 50% 60% 70%

49% XSS

44% Info. Leakage

57% XSS

Page 27: WhiteHat Security 2014 Statistics Report Explained

Industry Analysis – Health Care

ASP

ColdFusion

.NET

Java

Perl

PHP

5% 10% 20% 30% 40% 50% 60% 70%

49% XSS

44% Info. Leakage

57% XSS

Page 28: WhiteHat Security 2014 Statistics Report Explained

Recommendations

Page 29: WhiteHat Security 2014 Statistics Report Explained

Language Choice

• Does not matter– Test– Test– Test– All through SDLC

• Developer training is also extremely important

Page 30: WhiteHat Security 2014 Statistics Report Explained

Governance

• Security program– Know all assets &

Inventory of Assets– Policy Enforcement

Page 31: WhiteHat Security 2014 Statistics Report Explained

• What is it?• Why is it important?• How do you measure risk?

Risk BasedApproach

Page 32: WhiteHat Security 2014 Statistics Report Explained

How to Use This Report• If you are a– Developer– Security Staff– Security and/or Development Manager

Page 33: WhiteHat Security 2014 Statistics Report Explained

• Are some programming languages more secure than others?

• What are the prevalent threats per programming language?

• What are the prevalent threats per industry?

Big Questions…Answered

Page 34: WhiteHat Security 2014 Statistics Report Explained

Questions

Twitter: @whitehatsecEmail: [email protected] the conversation: #2014WebStatsPhone: 1-408-703-2750