Домой United States USA — software What to Consider Before Developing an API Security Strategy

What to Consider Before Developing an API Security Strategy

376
0
ПОДЕЛИТЬСЯ

eWEEK DATA POINTS: Enterprises first must understand the very nature of their API infrastructures. Most are not even aware of how many APIs they have to begin with.
Recent incidents at Salesforce, Facebook, Google+ —not to mention the Equifax breach and the Cambridge Analytica scandal that plagued Facebook—point directly to the unsettling reality that API security is often an afterthought for enterprises. Such incidents serve as a major wake-up call for enterprise security teams everywhere.
Enterprises first must understand the very nature of their API infrastructures. Most are not even aware of how many APIs they have to begin with.
In this eWEEK Data Point article, using new research from Ping Identity based on a survey of 100 security and IT professionals, we offer five API security issues of which to be aware as you consider your holistic API security strategy.
Data Point 1: API sprawl is a growing issue.
Twenty-five percent of respondents say their company has more than 1,000 APIs, while 35 percent report having between 400 to 1,000 APIs. This suggests that APIs are continuing to expand at an accelerated rate.

Continue reading...