Google can help banks fix their risk data problems

Despite banks’ ongoing struggle to improve the agility and transparency of their information systems, David Rowe argues they are still ignoring the need for a fundamental change in architecture

David Rowe

This past January, the Basel Committee on Banking Supervision issued its second report1 on progress towards the January 1, 2016 deadline for compliance with BCBS 239 – its principles on risk data aggregation. Once again, it makes depressing reading. Some self-estimates of progress have actually fallen since the previous report, issued in October 2013, although the committee reasonably infers this may be partly attributable to improved understanding of the full scope of the requirements.


Only users who have a paid subscription or are part of a corporate subscription are able to print or copy content.

To access these options, along with all other subscription benefits, please contact or view our subscription options here:

You are currently unable to copy this content. Please contact to find out more.

Sorry, our subscription options are not loading right now

Please try again later. Get in touch with our customer services team if this issue persists.

New to View our subscription options


Want to know what’s included in our free membership? Click here

This address will be used to create your account

You need to sign in to use this feature. If you don’t have a account, please register for a trial.

Sign in
You are currently on corporate access.

To use this feature you will need an individual account. If you have one already please sign in.

Sign in.

Alternatively you can request an individual account here