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.

Attacks/Breaches

3/23/2016
10:30 AM
Preston Hogue
Preston Hogue
Commentary
Connect Directly
Twitter
RSS
E-Mail vvv
100%
0%

Think Risk When You Talk About Application Security Today

Security from a risk-based perspective puts the focus on component failures and provides robust security for the ultimate target of most attacks -- company, customer and personal data.

The definition of application security has not evolved in parallel with the current state of applications. Let me explain. Twenty years ago, applications mainly operated independently of the Internet. During this time, the process for securing apps was simply adhering to best practices for secure coding throughout the software development lifecycle. But, it’s no longer the late 90’s. While secure coding is still an essential foundation to application security, it’s only one piece of a much larger puzzle.

Security professionals must now expand our definition of application security to include a risk-based perspective that accounts for the vast number of threats we must defend against. In doing so, we’ll improve the security posture across all facets of our apps and their deployment, thereby safeguarding our data and businesses. Looking at app security from a risk-based perspective puts focus on component failures, and provides robust security for the ultimate target of most attacks—company, customer, and personal data.

Today’s attackers have a convenient route to data through the application, but a risk-based approach accounts for vulnerabilities that secure coding can’t protect against. This approach includes analyzing the exposed elements of an application, and then developing a holistic security strategy for that app in its entirety. Attackers only need one component of an app left unaccounted for in order to compromise it -- whether it’s a code vulnerability, compromised identity, network availability, weak encryption, or DNS. And once attackers are inside, the entire application, as well as the data it houses, will be affected.

Application availability is a great example of a threat beyond the scope of secure coding. Since most apps today are Internet-based, a volumetric DDoS attack can cripple, or even take them down, rendering even the most securely-written code useless. Another threat vector to consider is confidentiality. What happens when a password is stolen? The application can be compromised and its data exposed.

This situation will not get any easier. There are approximately one billion Web apps in existence today. The rapid growth of the Internet of Things—and the applications that go along with it—will lead to apps numbering in the billions, and it’s naive to think that all of them will be securely coded.

We must immediately rethink our definition of application security so we’re in a better position to effectively secure all the components that make up our apps, safeguard our data, and protect our businesses.  

Related Content: 

 

Interop 2016 Las VegasFind out more about security threats at Interop 2016, May 2-6, at the Mandalay Bay Convention Center, Las Vegas. Click here to register. 

Preston Hogue is the Director of Security Marketing Architecture at F5 Networks and serves as a worldwide security evangelist for the company. Previously, he was a Security Product Manager at F5, specializing in network security Governance, Risk, and Compliance (GRC). He ... View Full Bio
Comment  | 
Print  | 
More Insights
Comments
Oldest First  |  Newest First  |  Threaded View
7 Tips for Infosec Pros Considering A Lateral Career Move
Kelly Sheridan, Staff Editor, Dark Reading,  1/21/2020
For Mismanaged SOCs, The Price Is Not Right
Kelly Sheridan, Staff Editor, Dark Reading,  1/22/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
IT 2020: A Look Ahead
Are you ready for the critical changes that will occur in 2020? We've compiled editor insights from the best of our network (Dark Reading, Data Center Knowledge, InformationWeek, ITPro Today and Network Computing) to deliver to you a look at the trends, technologies, and threats that are emerging in the coming year. Download it today!
Flash Poll
How Enterprises are Attacking the Cybersecurity Problem
How Enterprises are Attacking the Cybersecurity Problem
Organizations have invested in a sweeping array of security technologies to address challenges associated with the growing number of cybersecurity attacks. However, the complexity involved in managing these technologies is emerging as a major problem. Read this report to find out what your peers biggest security challenges are and the technologies they are using to address them.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2015-3154
PUBLISHED: 2020-01-27
CRLF injection vulnerability in Zend\Mail (Zend_Mail) in Zend Framework before 1.12.12, 2.x before 2.3.8, and 2.4.x before 2.4.1 allows remote attackers to inject arbitrary HTTP headers and conduct HTTP response splitting attacks via CRLF sequences in the header of an email.
CVE-2019-17190
PUBLISHED: 2020-01-27
A Local Privilege Escalation issue was discovered in Avast Secure Browser 76.0.1659.101. The vulnerability is due to an insecure ACL set by the AvastBrowserUpdate.exe (which is running as NT AUTHORITY\SYSTEM) when AvastSecureBrowser.exe checks for new updates. When the update check is triggered, the...
CVE-2014-8161
PUBLISHED: 2020-01-27
PostgreSQL before 9.0.19, 9.1.x before 9.1.15, 9.2.x before 9.2.10, 9.3.x before 9.3.6, and 9.4.x before 9.4.1 allows remote authenticated users to obtain sensitive column values by triggering constraint violation and then reading the error message.
CVE-2014-9481
PUBLISHED: 2020-01-27
The Scribunto extension for MediaWiki allows remote attackers to obtain the rollback token and possibly other sensitive information via a crafted module, related to unstripping special page HTML.
CVE-2015-0241
PUBLISHED: 2020-01-27
The to_char function in PostgreSQL before 9.0.19, 9.1.x before 9.1.15, 9.2.x before 9.2.10, 9.3.x before 9.3.6, and 9.4.x before 9.4.1 allows remote authenticated users to cause a denial of service (crash) or possibly execute arbitrary code via a (1) large number of digits when processing a numeric ...