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
Newest First  |  Oldest First  |  Threaded View
Cybersecurity Team Holiday Guide: 2019 Gag Gift Edition
Ericka Chickowski, Contributing Writer,  12/2/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Navigating the Deluge of Security Data
In this Tech Digest, Dark Reading shares the experiences of some top security practitioners as they navigate volumes of security data. We examine some examples of how enterprises can cull this data to find the clues they need.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-19647
PUBLISHED: 2019-12-09
radare2 through 4.0.0 lacks validation of the content variable in the function r_asm_pseudo_incbin at libr/asm/asm.c, ultimately leading to an arbitrary write. This allows remote attackers to cause a denial of service (application crash) or possibly have unspecified other impact via crafted input.
CVE-2019-19648
PUBLISHED: 2019-12-09
In the macho_parse_file functionality in macho/macho.c of YARA 3.11.0, command_size may be inconsistent with the real size. A specially crafted MachO file can cause an out-of-bounds memory access, resulting in Denial of Service (application crash) or potential code execution.
CVE-2019-19642
PUBLISHED: 2019-12-08
On SuperMicro X8STi-F motherboards with IPMI firmware 2.06 and BIOS 02.68, the Virtual Media feature allows OS Command Injection by authenticated attackers who can send HTTP requests to the IPMI IP address. This requires a POST to /rpc/setvmdrive.asp with shell metacharacters in ShareHost or ShareNa...
CVE-2019-19637
PUBLISHED: 2019-12-08
An issue was discovered in libsixel 1.8.2. There is an integer overflow in the function sixel_decode_raw_impl at fromsixel.c.
CVE-2019-19638
PUBLISHED: 2019-12-08
An issue was discovered in libsixel 1.8.2. There is a heap-based buffer overflow in the function load_pnm at frompnm.c, due to an integer overflow.