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.
The following is a list of ProgrammableWeb articles that matched your search term. On an nearly 24/7 basis, ProgrammableWeb publishes new articles ranging from news to opinion to tutorials for both developers and API providers. All of our articles are categorized in such a way that you can find your way to related articles, APIs, SDKs, Libraries, Frameworks, Tutorials and Sample Source Code. If you have an interest in contributing any of the aforementioned content to ProgrammableWeb, be sure to read our guidelines for such contributions.
Google, IBM, along with a number of other technology companies have introduced the Grafeas API, an open source artifact metadata API. Using the Grafeas API, organizations can combine data with other metadata to build a comprehensive model for security and governance at scale.
Cloud-based apps rely on an increasingly diverse set of underlying services, tied together through APIs - and hackers have taken notice. To resolve attacks and outages affecting APIs it is critical to understand and test the performance of the service delivery of application components.
In order for APIs to deliver on a myriad of benefits and objectives, organizations must design them with scale in mind. However, the need to build high-performing APIs that scale with the business ecosystem is pressuring many development teams to build APIs that may be restricting business growth.
Flashpoint announced the fourth version of its business risk intelligence API. The latest feature added to the API is Risk Intelligence Observables (RIOs), which the company contends move beyond traditional security indicators. A number of Flashpoint partners have already utilized v4.
At this point in your API journey, you have made a number of business decisions and a couple of technical ones. Now, several crucial decisions need to be made around security. Securing an API is an often neglected task, yet doing so is at the heart of an effective API strategy.
A recent white paper reported an Autofill API vulnerability within Android's 8.0 Oreo release. The vulnerability comes via the ability for widgets to hide themselves from users and request information that users are unaware they are providing to the hidden widget. No public fixes have been issued.
After it was revealed that over 143 million Americans may have been impacted when their personally identifiable information may have been breached through the credit reporting agency Equifax, there were further revelations that the so-called secret PINs issued by Equifax were actually timestamps.
From Slack integrations to coffee buttons, if Starbucks were to open up their API to the public, there are a ton of integrations that third-party developers could create. Tendigi CTO Nick Lee over at the Tendigi blog couldn’t wait so he reverse-engineered the Starbucks mobile app.
Although most of the technical details regarding the breach of Equifax are not known, the scope of the damage and the questions it raises should be enough to stimulate some organizational introspection regarding all that you have done to safeguard your Web services, sites, and APIs.