Salmat coder blamed for St.George data leak

 

42,000 account details compromised.

A "statement production issue" has caused the account information of 42,000 St.George Bank account holders to be sent to other customers.

The error was blamed on an interruption in the data processing function at ASX-listed business process outsourcing firm Salmat on 26 February.

According to Salmat COO Peter Anson, the error occurred when a programmer "went against protocol" and intervened after a file was found to be corrupted.

"Normally, data comes in and it runs on an automated process," Anson explained. "In this particular run, the file was corrupted. Corruption took place during our processing; I believe it was a software glitch."

"When it went to print, we knew there was an error. The programmer went against protocol and manually intervened."

Anson said that disciplinary action would be taken. The company was "deeply embarrassed", and had publicly apologised to St.George Bank and its customers, he said.

According to a St.George spokesperson, only personal savings accounts were affected.

Some of the statements would erroneously display no transactions or account balance for the month ending 26 February. Others displayed the transaction history of other customers.

Approximately 1,300 statements also featured the account number of other customers, presenting privacy issues and an opportunity for fraud.

The St.George spokesperson told iTnews that those 1,300 accounts would be closely monitored by fraud detection teams so any irregularities would be identified.

St.George also established a dedicated, 24/7 telephone line, 1300 668 460, with additional staff to assist customers affected by erroneous statements.

"We can guarantee that customers will not suffer any financial losses resulting from this issue," he said.

He added that it was a serious issue, but would not comment on how it would affect St.George's relationship with Salmat.

"The error is unacceptable to us; we're looking at the process and investigating the issue further," he said.

In December 2003, Salmat beat 17 of St.George's Group Procurement key suppliers to win the bank's inaugural "Supplier Of The Year" award for printing and distributing customer statements and shareholder communications.

The banking sector was a core market for the company, Anson said, although its other banking clients could not be named.

Salmat also provided customer relationship management services to the Australian Taxation Office (ATO), Coles Myer and Woolworths. Neither reported having had any issues with its services.

Copyright © iTnews.com.au . All rights reserved.


Salmat coder blamed for St.George data leak
"The protocol probably wasn't known or happenned to be an instruction sent along with the other hundreds of messages sent down by managers. Anyway, the fact that programmers need access to ..."
By Spock
 
 
 
Comments: 5
DavidJordan
Mar 4, 2010 2:41 PM
This is serious as it could have caused a run on the bank and is an issue of reputational risk under Basel II, the international banking regulation. Financial Institutions are taking risks for profits by low cost outsourcing which being cheap comes at a sacrifice, that sacrifice is usually quality and integrity. APRA needs to be taking a long hard look at the banks outsourcing to India and other low cost organisations as the potential risk of something more serious occuring is quite high.
myoung
Mar 5, 2010 8:01 AM
Salmat is not an Indian Outsourcer. It's an Australian company founded in 1979 by Philip SALter and Peter MATtick. St George Bank outsourced the work to some Aussie workers.
M_Princz
Mar 5, 2010 2:02 PM
Personally I have a huge problem with this. How can you blame a developer? they write the code ok but surely that code needs to be tested, or even before testing reviewed by a peer. Even once it is tested, the final approval for the change to a major client like St. George needs to come from a manager or client executive.

This is yet another incident of poor Application Lifecycle Management from a supposedly top tier Australian company. "The developer" is a quaint scapegoat for poor process and policy.

Salmat you are not alone in these practices, however, by not understanding risk, impact and traceability your mistakes have becoming public knowledge.
Yertle
Mar 5, 2010 3:41 PM
it sounds like he messed with an input file which is probably outside the change control process. i don't think he is being blamed for the glitch that caused the corruption but for going against their protocols.

I would imagine finance company's would take breaking the procedures and protocols pretty seriously (i've never worked in finance)
Spock
Mar 5, 2010 7:17 PM
The protocol probably wasn't known or happenned to be an instruction sent along with the other hundreds of messages sent down by managers. Anyway, the fact that programmers need access to production systems shows that the protocols are not mature enough.
Comments have been disabled for this article.
 
 
 
Top Stories
Telstra shifts BigPond email to Windows Live
All data to be migrated to Microsoft cloud.
 
Windows 8: Under the hood
Part One of iTnews' enterprise guide to Windows 8.
 
iTnews on tour: The Executive Summit Series
Join us in Sydney and Melbourne to meet Australia's tech leaders.
 
Sign up to receive iTnews email bulletins
   FOLLOW US...

Latest VideosSee all videos »

Latest Comments
Polls
Would you be concerned about your business' email data being hosted offshore?

   |   View results
Yes
  93%
 
No
  7%
TOTAL VOTES: 30

Vote