Bibliographic Details
| Title: |
API security: whose job is it anyway?. |
| Authors: |
Macy, Jason1 |
| Source: |
Network Security. Sep2018, Vol. 2018 Issue 9, p6-9. 4p. |
| Subjects: |
Application program interfaces, Application software security measures, Computer crimes, Cyberterrorism, Computer hacking |
| Abstract: |
It's probably safe to assume that nearly everyone is out to get your data. Nowadays it's data, not gold or oil, that is the world's most valuable and sought-after asset and it seems as if every month some company or other is hacked, exposing thousands of their users' information to unauthorised third parties. APIs are the glue that holds the digital world together. But's that's also the fundamental challenge with APIs – that they are everywhere. You use them every day and most of the time you are not even aware of it. And the sheer scale at which APIs are used means the potential impact of an API-related attack is significant. But as with other cyberthreats, the effects of a breach depend on the specific scenario and the data that is being shared through the API. Jason Macy of Forum Systems looks at how APIs can be vulnerable – and how they can be employed responsibly. [ABSTRACT FROM AUTHOR] |
|
Copyright of Network Security is the property of Mark Allen Holdings Limited and its content may not be copied or emailed to multiple sites without the copyright holder's express written permission. Additionally, content may not be used with any artificial intelligence tools or machine learning technologies. However, users may print, download, or email articles for individual use. This abstract may be abridged. No warranty is given about the accuracy of the copy. Users should refer to the original published version of the material for the full abstract. (Copyright applies to all Abstracts.) |
| Database: |
Engineering Source |
