Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Application Security

7/9/2019
03:40 PM
Connect Directly
Twitter
RSS
E-Mail
50%
50%

What the AppSec Penetration Test Found

New data drills down on the types of security misconfigurations and challenges dogging application developers.

It should come as no surprise that misconfigured security by far remains the most common flaw found in applications today with the wave of exposed Amazon Web Services S3 buckets, HTTPS pages, and other high-profile mistakes exposed publicly over the past year. But new data gathered from real-world appsec penetration tests exposes just what types of configuration mistakes organizations are making that expose their data.

Pen-test-as-a-service firm Cobalt found in nearly 1,000 pen tests using its platform in 2018 that 60% of all security misconfigurations are mistakes with security headers and application settings. Security misconfiguration basically is where an app or setting doesn't enforce security controls, according to Cobalt, which has seen misconfiguration as the No. 1 vulnerability for the past three years of its pen testing. Misconfiguration mistakes can include insecure default configurations, exposed S3 buckets, error messages that include sensitive information, and not keeping systems or software and development frameworks updated.

As obvious as properly setting security-headers sounds — ensuring the entire site is HTTPS and doesn't revert to HTTP, for example — it isn't always as easy for organizations to get it right. "These things are often an afterthought. Folks continue to be focused on getting their code completed, done, and released," says Caroline Wong, chief security strategist at Cobalt, which will release its appsec pen-testing report this week. "It's pretty easy to make mistakes."

Ensuring that all Web connections use HTTPS, for example, can be tricky. "There are security features in [platforms] that take these [potential] mistakes out of the hands of developers, but developers still have to use them and include them," she says.

Cobalt found that 30.1% of security misconfigurations were in security headers; 28.5% in application settings; 12.7% in encryption settings; 11.5% in server configuration; 9.6% in mobile settings; 4.9% in cloud settings; and 2.9% due to an improper security control. But the highest-risk mistakes, according to the pen-test report, are server configuration — such as unprotected file shares and unpatched operating systems — and application settings such as error messages that reveal sensitive information and software version disclosure.

Joe Sechman, vice president of Cobalt Core Labs, says security misconfiguration won't be solved overnight, especially with the arrival of Internet of Things devices. "The grim observation is we don't see misconfigurations magically turned around and fixed overnight," he says. "I'll bet it's going to be a little worse in ... IoT devices ... with the rush to market [new] features.

But the good news, he says, is that progress is actually being made on the application side in general. "Be informed before you do pen testing," he advises.

Cobalt also surveyed 150 security, DevOps, and other related professionals across various industries including cloud, retail, and finance, about their secure development practices and pen-testing strategies. Some 92% of those surveyed employ Agile/DevOps, and 20%, waterfall development methods. More than half write their own software, and 26% work with third parties to develop apps.

Cobalt's Wong says the main nugget from the survey, which is part of the overall pen-test report, is that while most of the organizations want to conduct more appsec pen testing, the cost is prohibitive. Half of the organizations say it's too expensive to perform pen tests more regularly than they currently do.

Some 80% say they pen test their apps because it improves their security; 60% because it's part of their development life cycle; 57% because customers request it; 56% to prove security issues were fixed; 54% for regulatory compliance for customers; and 36% for risk assessment for third-party vendors.

Nearly half of the organizations say they pen test some 67% to 100% of their applications; that was the case of just 24% of organizations in last year's survey by Cobalt.

Budget-wise, 60% say pen testing is a high priority and 2% say it's a low priority, according to the new report.

Related Content:

 

Black Hat USA returns to Las Vegas with hands-on technical Trainings, cutting-edge Briefings, Arsenal open-source tool demonstrations, top-tier security solutions, and service providers in the Business Hall. Click for information on the conference and to register.

Kelly Jackson Higgins is the Executive Editor of Dark Reading. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise ... View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 10/30/2020
'Act of War' Clause Could Nix Cyber Insurance Payouts
Robert Lemos, Contributing Writer,  10/29/2020
6 Ways Passwords Fail Basic Security Tests
Curtis Franklin Jr., Senior Editor at Dark Reading,  10/28/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
How to Measure and Reduce Cybersecurity Risk in Your Organization
In this Tech Digest, we examine the difficult practice of measuring cyber-risk that has long been an elusive target for enterprises. Download it today!
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-5425
PUBLISHED: 2020-10-31
Single Sign-On for Vmware Tanzu all versions prior to 1.11.3 ,1.12.x versions prior to 1.12.4 and 1.13.x prior to 1.13.1 are vulnerable to user impersonation attack.If two users are logged in to the SSO operator dashboard at the same time, with the same username, from two different identity provider...
CVE-2020-15703
PUBLISHED: 2020-10-31
There is no input validation on the Locale property in an apt transaction. An unprivileged user can supply a full path to a writable directory, which lets aptd read a file as root. Having a symlink in place results in an error message if the file exists, and no error otherwise. This way an unprivile...
CVE-2020-5991
PUBLISHED: 2020-10-30
NVIDIA CUDA Toolkit, all versions prior to 11.1.1, contains a vulnerability in the NVJPEG library in which an out-of-bounds read or write operation may lead to code execution, denial of service, or information disclosure.
CVE-2020-15273
PUBLISHED: 2020-10-30
baserCMS before version 4.4.1 is vulnerable to Cross-Site Scripting. The issue affects the following components: Edit feed settings, Edit widget area, Sub site new registration, New category registration. Arbitrary JavaScript may be executed by entering specific characters in the account that can ac...
CVE-2020-15276
PUBLISHED: 2020-10-30
baserCMS before version 4.4.1 is vulnerable to Cross-Site Scripting. Arbitrary JavaScript may be executed by entering a crafted nickname in blog comments. The issue affects the blog comment component. It is fixed in version 4.4.1.