This is an excerpt from a transcript of The Axway Blog Team’s podcast, “Key takeaways of the ‘Speed to Revenue and Improved Customer Service’ white paper.”
ANNOUNCER: Hello everyone. The Axway Blog Team recently had a chance to catch up with Peter Benesh, Axway’s director of solution marketing for the Financial Services industry, and ask him to share his thoughts on the key takeaways of the IDC Financial Insights white paper titled “Speed to Revenue and Improved Customer Service: How Data Agility Underpins Success for Financial Institutions in the New Digital Economy” by Alex Kwiatkowski. Key Takeaway 2: The regulatory landscape around using, managing, and governing data must be constantly kept in view. Compliance with mandatory policies is of course essential, but institutions must also strike the correct balance between data opacity on the one hand and “safely” innovating when it comes to the creative use of information to improve operational and financial performance.
PETER BENESH: You want to give the outside world access to certain parts of your applications. But not just free-for-all, open-the-kimono, you-can-get-anything-you-want-you-can-see-anything-you-want. So we can maintain appropriate levels of privacy by the types of security we have in the gateway, and the types of permissions that we allow, such that only specific types of data are allowed to be accessed by developers. If something is truly private, it could either be masked so that when the API accesses it, it’s just genericized so that the outside world really doesn’t know the specifics of it. Or they could just be completely locked down and inaccessible because it’s just not the types of data that we’re ever going to let third parties get access to. It really depends on the outside applications that are being used. Who’s using them? Is it an individual that’s using a mobile app to access their personal accounts over their smart phone? They mentioned an example of Dun & Bradstreet trying to get access to certain types of financial information through an API. It all depends on who the end user is, what types of information they specifically need, what kind of app they’re using, and what kinds of permissions and authorizations should they be given.
To download the white paper, click here.
To listen to the podcast on YouTube (audio only), click here.