February 10, 2020
Related Articles (594)
Despite the fact that the costs associated with hacking and data breaches have arguably never been higher, recent API-related security incidents involving large companies, T-Mobile and Accenture, highlight the fact that basic API security best practices are still often not being adhered to.
For a few days, Facebook was providing a user's phone number and address available, with the user's permission, via its Facebook Graph API. Likely fueled by distrust of Facebook's previous approaches to privacy, users and press reacted negatively to the concept. Based on this feedback, Facebook reversed its decision and neither phone or address is returned to applications at this time. Privacy is a big concern, especially for APIs, but Facebook took appropriate steps for gaining user permission. The reaction to Facebook's platform change was an overreaction, which points to a need for more granular privacy controls and a better method of granting access.
Are all CPaaSes (Communications Platform as a Service) created alike? Telesign's director of product management Vince Oh thinks not. In this interview with ProgrammableWeb.com editor-in-chief David Berlind, Oh explains how Telesign's parent company gives it a unique competitive advantage.