Quantcast StorefrontBacktalk » Blog Archive » Avaya Learns An Expensive IT Lesson About Transitioning HR Systems
advertisement
advertisement

Avaya Learns An Expensive IT Lesson About Transitioning HR Systems

Written by Evan Schuman
October 29th, 2009
Like this story? Share it
To share this story with people in your social network, please click on the network icons below.

Back in the fall of 2002, $5.3 billion software firm Avaya purchased a brand new human resources database and payroll system. At the same time, it hired a new senior systems analyst. That analyst quickly reconsidered his decision and withdrew his acceptance of the position. Due to a problem with the database transition, the HR database removed him but the payroll system—with its new integrated direct deposit system—didn’t. Yep, payroll kept depositing checks into his account for years, giving the non-employee almost a half-million dollars.

New Jersey prosecutors have charged the almost-employee, Anthony Armatys, with theft, and he faces as many as six years in prison. Given that the checks kept getting deposited for more than four years (from October 2002 through February 2007) makes one wonder how long they would have continued had the systems analyst, according to the prosecutors, not chosen to push his luck. The Somerset County Prosecutor’s Office said that Armatys called Fidelity Investments, said he was an employee of Avaya and asked to transfer funds from his retirement savings account to his personal account. The irony is Avaya’s tagline: “Avaya delivers Intelligent Communications solutions that help companies transform their businesses to achieve marketplace advantage.” Wonder if that always includes payroll systems that don’t stop paying employees when HR deletes them or if that’s just a homegrown extra?


advertisement

One Comment | Read Avaya Learns An Expensive IT Lesson About Transitioning HR Systems

  1. Sreekumar J Says:

    This is a shocking incident. To be frank, unbelievable! but sometimes truth would be like that.

    One should be very careful when select a HR or Payroll software products. Also utmost care should be given for implementation and go live. IT team should perform periodic audits to find any discrepancies in system.

Leave a Reply

Newsletter

Quickly catch-up on the latest in E-Commerce and Retail Tech with our free weekly newsletter, with urgent bulletins as news merits.
advertisement

Most Recent Comments

Kill All The Passwords

This article does mention, but does not give enough attention to, the fact that the attacks discussed are only feasible when the encrypted password file can be copied and subjected to an offline attack. The trick is to have authentication performed on a separate, much more strongly secured host - such as an Active Directory Domain Controller, or a Kerberos server, or a NIS+ server, or even using something as banal as an LDAP-over-SSL authentication dialog. In these environments, the odds of the "password file" being stolen and subjected to an offline attack go to near zero, and only online attacks may be carried out by the attacker. With sensible exponential backoff between failed password attempts, lockout after a modest number of failed attempts on a single account, and pattern detection, that minimum 7 character password is quite secure enough. Passwords aren't dead yet for security purposes, and they will be with us for a very long while to come for practical purposes. The trick is to employ them correctly. Read more...
The possibilities you describe are years away from being implemented at best, so for the moment passwords are an ugly reality. Luckily, password managers can easily manage hundreds of passwords of any length. The only thing a user needs to remember is the master password. It seems like an easier task to educate users on how to use password managers rather than implement complex security technology on a global basis. Read more...