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

2/2/2018
10:40 AM
Connect Directly
Twitter
RSS
E-Mail
100%
0%

APIs Pose 'Mushrooming' Security Risk

As APIs grow in prominence, top security concerns include bots and authentication.

The application economy has now become the API economy. And as the importance of application programming interfaces (APIs) grows within the enterprise, organizations must keep their security top-of-mind, lest they put the entire software stack at risk.

Software is powering digital disruption today and the secret sauce to this success is not just the features of the software itself, but how well it integrates with other software. Integrations between internal applications across business groups, with external platforms and applications held by partners, and with other consumer-based applications on customer devices is what fuels business success today. APIs are the glue that holds all these integrations together.

But APIs deployed without security measures expose organizations to yet another class of attack vectors.

"APIs represent a mushrooming security risk because they expose multiple avenues for hackers to try to access a company's data," explains Terry Ray, CTO of Imperva. "To close the door on security risks and protect their customers, companies need to treat APIs with the same level of protection that they provide for their business-critical web applications.”

Nevertheless, APIs remain greatly important for business and IT strategy.

"The greatest revenue potential (APIs) provide is removing barriers to growing revenue by integrating platforms and apps so organizations can quickly launch new business models and scale fast," explains Louis Columbus, an enterprise software strategist and principal at IQMS, a manufacturing ERP vendor, in a Forbes piece last year.

What's more, APIs are also fueling new methods of developing and deploying software. As organizations seek means to deliver and tweak software faster, they're increasingly breaking up large monolithic code bases into smaller chunks of independent code called microservices. Advanced organizations develop applications using segmented microservices that fit together like bricks into a larger software structure, making it easier to execute quick changes to parts of the software without accidentally breaking something else in the code base. But these microservices must interface with one another, and it takes APIs to accomplish that.

According to a study out this week from Imperva, these trends in software strategy have translated to the kind of proliferation where the typical organization is managing an average of 363 APIs within their application ecosystem. So, the obvious question for cybersecurity is where do the risks lie? 

According to the survey, more than two-thirds of organizations expose APIs to the public in order to enable partners and external developers to hook into the power of their software. This kind of exposure may open up a world of business opportunity, but it also brings risk to the table. Among the 250 IT and security practitioners questioned, the biggest proportion - 39% - were most concerned about the risks that bots and DDoS attacks posed to APIs.

Nearly a quarter of respondents also expressed concerns about authentication enforcement, a tricky topic when it comes to allowing access to only some data within an application without exposing other sensitive data. A bank, for example, might want its application to easily interface with other consumer applications, but wouldn't want its credentials shared with those applications on sign-on. And that's just the start of the threat exposure.

Some 76% of organizations report that they currently treat API security differently than Web security. Only about 63% of organizations use a Web application firewall to secure their APIs. Approximately 63% also report using an API gateway, though that number does bump up to 80% for public-facing APIs. Meanwhile, fewer than half of organizations use runtime application self-protection (RASP) to prevent attackers from tampering with or reversing API code for future attacks.

"In their approach to API security, organizations exposing Web APIs must balance ease of access - to ensure adoption of APIs - with control - to prevent abuse or attacks," Gartner analysts Mark O'Neill, Dionisio Zumerle, and Jeremy D'Hoinne said in a recent report on API security strategy. "Like the bank robber attacking banks because 'that's where the money is,' the use of APIs to provide access to applications and to business-critical data has naturally led to API security incidents."

Related Content:

 

Ericka Chickowski specializes in coverage of information technology and business innovation. She has focused on information security for the better part of a decade and regularly writes about the security industry as a contributor to Dark Reading.  View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Threaded  |  Newest First  |  Oldest First
aumickmanuela
50%
50%
aumickmanuela,
User Rank: Strategist
2/7/2018 | 10:00:10 AM
Interesting post
Post is really interesting) I have never heard such interesting terms, thanks a lot )
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
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-19317
PUBLISHED: 2019-12-05
lookupName in resolve.c in SQLite 3.30.1 omits bits from the colUsed bitmask in the case of a generated column, which allows attackers to cause a denial of service or possibly have unspecified other impact.
CVE-2019-19602
PUBLISHED: 2019-12-05
fpregs_state_valid in arch/x86/include/asm/fpu/internal.h in the Linux kernel before 5.4.2, when GCC 9 is used, allows context-dependent attackers to cause a denial of service (memory corruption) or possibly have unspecified other impact because of incorrect fpu_fpregs_owner_ctx caching, as demonstr...
CVE-2019-19601
PUBLISHED: 2019-12-05
OpenDetex 2.8.5 has a Buffer Overflow in TexOpen in detex.l because of an incorrect sprintf.
CVE-2019-19589
PUBLISHED: 2019-12-05
The Lever PDF Embedder plugin 4.4 for WordPress does not block the distribution of polyglot PDF documents that are valid JAR archives.
CVE-2019-19597
PUBLISHED: 2019-12-05
D-Link DAP-1860 devices before v1.04b03 Beta allow arbitrary remote code execution as root without authentication via shell metacharacters within an HNAP_AUTH HTTP header.