Application Security

2/2/2018
10:40 AM
Connect Directly
Twitter
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
Newest First  |  Oldest First  |  Threaded View
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 )
Election Websites, Back-End Systems Most at Risk of Cyberattack in Midterms
Kelly Jackson Higgins, Executive Editor at Dark Reading,  8/14/2018
Intel Reveals New Spectre-Like Vulnerability
Curtis Franklin Jr., Senior Editor at Dark Reading,  8/15/2018
Australian Teen Hacked Apple Network
Dark Reading Staff 8/17/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-15504
PUBLISHED: 2018-08-18
An issue was discovered in Embedthis GoAhead before 4.0.1 and Appweb before 7.0.2. The server mishandles some HTTP request fields associated with time, which results in a NULL pointer dereference, as demonstrated by If-Modified-Since or If-Unmodified-Since with a month greater than 11.
CVE-2018-15505
PUBLISHED: 2018-08-18
An issue was discovered in Embedthis GoAhead before 4.0.1 and Appweb before 7.0.2. An HTTP POST request with a specially crafted "Host" header field may cause a NULL pointer dereference and thus cause a denial of service, as demonstrated by the lack of a trailing ']' character in an IPv6 a...
CVE-2018-15492
PUBLISHED: 2018-08-18
A vulnerability in the lservnt.exe component of Sentinel License Manager version 8.5.3.35 (fixed in 8.5.3.2403) causes UDP amplification.
CVE-2018-15494
PUBLISHED: 2018-08-18
In Dojo Toolkit before 1.14, there is unescaped string injection in dojox/Grid/DataGrid.
CVE-2018-15495
PUBLISHED: 2018-08-18
/filemanager/upload.php in Responsive FileManager before 9.13.3 allows Directory Traversal and SSRF because the url parameter is used directly in a curl_exec call, as demonstrated by a file:///etc/passwd value.