Attacks/Breaches
10/25/2011
11:00 AM
Connect Directly
RSS
E-Mail
50%
50%

UBS Finds Risk Management Stress Test Costly

UBS failed to stop a single rogue trader from racking up $2 billion in losses. Yet, some experts argue that banks overall may be better than others at managing risk.

What's the harm in having a risk management system in place, but ignoring the alarm bells when they seem inconvenient? No harm at all, if you don't mind seeing your quarterly net profit decline by 39%, and revenue slide by 4%.

Swiss banking giant UBS announced those results Tuesday, saying they reflected not only "market conditions," but also the recent "unauthorized trading incident" that resulted in its losing 1.8 billion Swiss francs ($2 billion). One piece of good news is that the actual losses were $300 million less than the bank had originally estimated.

UBS had discovered the unauthorized Delta One trades last month in its Global Synthetic Equity business and alerted London police. That same day, they arrested and later charged a 31-year-old trader, Kweku Adoboli, on suspicion of fraud and abuse of his position.

Delta One trades are a form of complex derivatives trading, and by all accounts, incredibly opaque. Interestingly, rogue trader Jerome Kerviel at Societe General in 2008 hid Delta One trades, ultimately resulting in losses of $7 billion. Accordingly, while Delta One trades might offer significant revenue potential, their potential for insider abuse--not least when traders get in over their heads and double down, seeking a quick fix for losses--should cause banks to carefully monitor such trades.

"Risk and operational systems did detect unauthorized or unexplained activity but this was not sufficiently investigated nor was appropriate action taken to ensure existing controls were enforced," UBS interim chief executive Sergio Ermotti told employees in a memo earlier this month. "We have accepted the resignations of the co-heads of Global Equities. Firm disciplinary action will be taken against further individuals in Equities and across other responsible functions. We have also taken specific steps to address the failures identified."

How did one of the world's biggest banks fail to heed the alarm bells, despite its former chief executive, Oswald Grubel--ousted over the unauthorized trading--having recently boasted that UBS had "one of the best" risk management programs in the business? "Having controls in place is one thing. Acting upon them is a different one," Martin Kuppinger, principal analyst at market researcher KuppingerCole, tells me. "That's why I strongly believe in automated controls which just can't be ignored that easily. But even that's about knowing risks, having controls in places, and the right processes and people."

Kuppinger, however, also cautions that until the full details of the UBS incident emerge--the bank has said it will release more details after the current investigation wraps--no one should jump to conclusions. "Without having proven details on what really happened and the reasons behind it, I won't blame UBS," he said.

Still, might UBS have been slow to rein in its massively profitable investment banking group's practices, especially given the firm's history of poor risk management oversight? "This story absolutely does suggest a deeper culture challenge," says Alexei Miller, executive VP at DataArt, a custom application development shop that builds risk management systems for financial services firms.

But, he says, no system, check, or balance--including governance, risk, and compliance (GRC) controls--is 100% foolproof. "The whole incident is not, in the end, about systems or controls or risk officer's power," says Miller. "No system will ever guarantee absolute protection. It is human behavior, first and foremost. A clever and well-connected bad apple will always find a way around risk controls. How many instances of unauthorized trading will we never learn about, because they go the trader's way?"

In the case of Societe Generale, Kerviel avoided detection for some time by using other people's passwords to subvert the access management system. He also bypassed the risk management system, based on his understanding of how it worked.

"Banks are still learning--not only from SocGen. But it's a process which takes its time. SocGen has alerted banks, and UBS added to this," says Kuppinger. Overall, banks are getting better at addressing risk management. "And honestly, they overall are much better than other industries," he says.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Bprince
50%
50%
Bprince,
User Rank: Ninja
10/27/2011 | 10:10:42 PM
re: UBS Finds Risk Management Stress Test Costly
"Having controls in place is one thing. Acting upon them is a different one." -- Good quote. An alarm is useless if it is ignored.
Brian Prince, InformationWeek contributor
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading, September 16, 2014
Malicious software is morphing to be more targeted, stealthy, and destructive. Are you prepared to stop it?
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2006-1318
Published: 2014-09-19
Microsoft Office 2003 SP1 and SP2, Office XP SP3, Office 2000 SP3, Office 2004 for Mac, and Office X for Mac do not properly parse record lengths, which allows remote attackers to execute arbitrary code via a malformed control in an Office document, aka "Microsoft Office Control Vulnerability."

CVE-2014-1391
Published: 2014-09-19
QT Media Foundation in Apple OS X before 10.9.5 allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption and application crash) via a crafted movie file with RLE encoding.

CVE-2014-4350
Published: 2014-09-19
Buffer overflow in QT Media Foundation in Apple OS X before 10.9.5 allows remote attackers to execute arbitrary code or cause a denial of service (application crash) via a crafted MIDI file.

CVE-2014-4376
Published: 2014-09-19
IOKit in IOAcceleratorFamily in Apple OS X before 10.9.5 allows attackers to execute arbitrary code in a privileged context or cause a denial of service (NULL pointer dereference) via an application that provides crafted API arguments.

CVE-2014-4390
Published: 2014-09-19
Bluetooth in Apple OS X before 10.9.5 does not properly validate API calls, which allows attackers to execute arbitrary code in a privileged context via a crafted application.

Best of the Web
Dark Reading Radio