As a consequence of the recent FTC investigation, Facebook cut off friend data access for Microsoft and Sony and announced an overhaul of its API. Facebook’s privacy changes will impact dozens of partners that have been using the Facebook API to build experiences on third-party apps and devices. Here are three essential considerations for API providers, consumers, and end-users to avoid a scandal like Facebook’s and protect the privacy of user data.
There’s no doubt that today’s businesses are under increasing pressure to innovate faster. Looking to deliver innovative offerings at an accelerated pace to meet ever-evolving customer expectations, many are turning to modern development models underpinned by the cloud, microservices architectures, and containerization technologies.
At MuleSoft, we are committed to maintaining privacy and security on the data you share with us. Like many of our customers and partners, MuleSoft has been preparing for the GDPR regulations that are changing the global data privacy landscape. Our privacy and security teams have been working with customers and internal teams to prepare for the GDPR, which goes into effect on May 25, 2018.
One of the more challenging aspects of integration work is dealing with various security protocols. This holds true both as a consumer of a secured service and as a producer of a service that must enforce the security protocol.
Cybersecurity solution provider Trend Micro has issued a report that highlights how chat platform APIs can and are being used by cybercriminals to achieve their nefarious objectives.
Because of the degree to which Webhook APIs are involved (an API attack vector not previously discussed on ProgrammableWeb), the warnings and incidents should serve as a wake-up call to API providers and developers when it comes to the sorts of best practices and ongoing vigilance it takes to fully secure their customers and systems.Provided that the incentives are worth it,
2016 has finally come to an end, and that means an opportunity for your IT teams to start fresh and do great things for the business in 2017. But where’s the best place to start? Here are our top 7 r resolutions for your teams to consider in the upcoming year.
A convergence of digital forces – notably mobile, SaaS, cloud, big data, IoT and social – is creating massive disruption in the market and pushing businesses to move at much faster speeds. However, with a fixed set of resources and a constrained capacity to deliver on new projects, IT is often accused of holding the business back rather than enabling it.
The resulting IT delivery gap is exacerbated even further when IT resorts to shortcuts that get projects done on time and on budget.
This is part 3 of my API security blog series. I will be showing an example scenario of how Anypoint platform can be a vital component of a secure API-led architecture and the capabilities to securing the API.
This post will be part 1 of 3 for my ultimate guide to API security best practices series. In this post, I will be discussing the current concerns IT decision makers have in regards to their current digital assets.
In some organizations, the Chief Information Security Officer (CISO) has earned a reputation inside of IT as a blocker or a hindrance to innovation. Some CISOs have even be referred to as the ‘Queen (or King) of No.’ Why? Because despite the massive amounts of attention being paid to security in the media, with Target, Apple, Nissan, and Twitter all making the news recently for their security failures,
MuleSoft provides the most widely used integration platform for connecting any application, data source or API, whether in the cloud or on-premises. With Anypoint Platform®, MuleSoft delivers a complete integration experience built on proven open source technology, eliminating the pain and cost of point-to-point integration. Anypoint Platform includes CloudHub™ iPaaS, Mule ESB™, and a unified solution for API management™, design and publishing.