Getting a Secure Grip on Handheld Devices

Companies today do not have a firm grasp ofstolen or lost resulting in sensitive information
the security vulnerabilities associated with theirbeing disclosed to unauthorized individuals.
handheld devices. Personal Electronic DevicesThe first and best step to getting a grip on hand
(PEDs), Personal Digital Assistants (PDAs), emailheld devices, is to ensure that your company
and paging devices (such as the Blackberry), andincludes them in their written security policies.
other hybrid handheld communication devices areCompanies must issue clear and concise guideline
found in the hands of most every businesson what devices may and MAY NOT be used and
manager these days but their inherentfor what specific purposes.
vulnerabilities are largely overlooked.How the devices are used and the type of
Perhaps this is because of their size, mobility orinformation that is allowed to be stored on the
relatively inexpensive costs. Either way, thesedevices will directly impact the overall risk to the
devices do not register on the radar of mostorganization. Good policies will specify the
systems administrators and are wronglyapproved configuration of the devices and modes
perceived as not as vulnerable as end userof operation including whether wireless radio
terminals connecting via hardwire to a LAN, WANfrequency and/or infrared transmission is
or the Internet. The popularity, proliferation andpermitted and whether the user is allowed
rapidly evolving technology associated with theSystem Administrator rights to the base PC with
devices make them extremely susceptible towhich the device synchronizes. Clearly define the
security vulnerabilities.purpose and acceptable use conditions of the
There are several general classes of hand helddevices. Corporate provided devices should be
device operating systems: the Palm Operatingused only for work related activities. Users should
System (OS) (Palm Pilots, Handspring Visor, etc.);sign an agreement to abide by the acceptable use
Apple IPhone OS; Symbian; and those runningpolicy. Devices should not be used to enter or
Windows CE and Pocket PC (Compaq, HPstore passwords, safe/door combinations,
Jornada, Casio, etc.). Hand held devices arepersonal identification numbers, or classified,
equipped with a wide variety of accessories fromsensitive or proprietary information.
cameras, modems and synchronization cables toEffective policies should delineate approved
Bluetooth and wireless connections and flashconnectivity requirements, prohibiting up and
memory storage. All of the operating systemsdownloads via wireless or infrared while connected
have software libraries with applications, widgetsto desktop PCs and stating approved methods
and plugins developed and distributed throughoutfor infrared data transfers. Users should be given
both the commercial and freeware sharewareprecise instructions regarding requirements to
channels and as with any software developed bysync their devices to receive patches, fixes and
non-trusted sources, freeware programs mayupdates. It's imperative that your policies spell out
possibly contain hidden code - be it adware ordevice-specific build and configuration requirements
malware.to include: firewall, VPN, encryption, biometric,
Given their size and portability, the primaryauthentication and anti-virus software needs.
security concern associated with hand heldPhysical security requirements should be simple
devices is their ability to store large amounts ofand achievable but at a minimum should state that
information. Add to this the breadth ofdevices shall not be left unattended when
communication options available and you have aattached to a computer, secured with password
device that introduces formidable risks. Since theprotection when not in use and reported
devices are relatively inexpensive, users buy theirimmediately if lost or stolen and insured against
own or receive them as gifts and they tend totheft, loss or breakage.
come into use in an organization regardless ofYour organization should have a mechanism to
whether they are approved or not. As such,manage the policies for hand held devices from a
companies have little or no control over datacentral location and establish a registry of all
leaving the organization.devices in use. This registry should include: serial
A wide variety of vulnerabilities exist when thesenumber, configuration, make and model and to
devices are attached to PCs or otherwhom the device has been issued. Each device
network-connected automated informationowned by the organization should be marked as
systems (AIS): Trojan horse and malwaresuch with an asset tag or other permanent
programs can easily be installed thus creating amarking.
backdoor on host networks to permit exploitationWhile handheld devices may currently be a lesser
since antivirus products for hand held devices aretarget than networks, end user terminals or
not as evolved as PC antivirus software andlaptops for virus and hacker attacks, that won't
operating systems currently do not limit maliciousalways be the case. The applications and
codes from modifying system files. Wirelessfunctionality we see on PDAs today is what we
device connections can be intercepted and datasaw on a laptops five years ago. What we'll find
captured without the knowledge or permission ofon PDAs five years from now is what we find on
the user as recently demonstrated inlaptops today. The increased power and flexibility
well-publicised incidents of drive-by hacking, bluein the operating systems will bring greater
snarfing and blue jacking. Hand held devices usingsecurity risk. The sooner you get a grip on this
infrared data transport technology might also berisk the better.
intercepted as well. Finally, hand held devices byLast but not least: don't forget that handheld
their very nature are small and therefore easilydevices are subject to PCI requirements too!