Imagine you’ve lost your Blackberry, which contained the last 17 customer loan applications you were working on and internal e-mails regarding a proposed merger of your bank. Making matters worse, it was your own personal Blackberry, not one provided to you by the IT department.
The explosion of mobile computing devices such as laptops, smart phones and hand-held personal digital assistants in today’s banking industry has created a risky security environment. Banks face the issue of lost or stolen MCDs that contain private and sensitive financial, personnel, business and customer information. Additionally, bank staff routinely use personal MCDs for bank business, plugging them into the bank’s systems without explicit permission. The need to manage and secure MCD use is paramount today.
MCDs are productivity enhancers. They allow bank staff to be mobile and to get the job done on the go. They allow for more off-site visits to clients and vendors, improved customer response times, real time team and distance communications, and faster decision making.
But MCDs can be misplaced, stolen or their contents “sniffed out” via wireless communications hack attacks from hundreds of feet away. Devices can become infected with viruses that threaten the bank’s entire IT network. Attackers can install spyware programs that capture the keystrokes of passwords and sensitive emails. And because customers often send banks confidential personal information, the risks are high for costly Gramm-Leach-Bliley Act information security violations.
What can banks do to manage the growing risk? The first step is to conduct a full IT risk assessment that methodically determines what devices (authorized and unauthorized) currently exist in the environment, which staff use them and for what purposes. Consider this a snapshot of current MCD usage.
Banks should then develop a mobile computing device policy that defines standards, procedures and best practices. Since different products have different security feature sets, and too many diverse products become unmanageable, most banks start by standardizing on products. Then it’s important to develop an authorized use and user policy that spells out who can use the devices, for what legitimate purposes, and makes MCD users aware of their professional and regulatory responsibilities.
Per GLBA information security guidelines, banks should develop a lost device policy/ incident response plan that includes:
Digging deeper into technological security solutions, banks should consider implementing these recommended industry best practices:
Although wireless technology security has improved over the years, it is still vulnerable to remote hacking attacks. Wireless communications should be sent via tried-and-tested end-to-end encryption protocols such as SSL (secure sockets layer), SSH (secure shell), IPSec (IP security) and virtual private networks.
Bluetooth is widely used as a wireless communications technology. Because of inherent risks with any wireless technology, banks should enable Bluetooth only if really needed. Additionally, banks should regularly check the list of paired devices to ensure there are no unknown devices on the list, require long and hard-to-guess PINs (not 9999) for devices, keep devices in hidden mode and reject all mysterious unrequested pairing requests.
By following these basic guidelines, banks can minimize and manage the risks associated with the use of productivity-enhancing MCDs. Remember that Blackberry you lost in the opening paragraph? Well, you should now have a backup copy of all your data, and you can remotely delete all the information contained on the device.
Len Filppu is executive vice president/director of operations for AuditOne LLC in San Jose, Calif., an independent internal audit firm specializing in banks and their service providers throughout the western United States. He can be reached at 408-980-8099 or www.audit-one.com. Marv Chen, CISSP, is senior vice president/technical practices leader for AuditOne LLC. He can be reached at marv.chen(at)audit-one.com.
Copyright August-September 2007 Western Banking (BankNews Publications)