The Register® — Biting the hand that feeds IT

Feeds

Lock up your Crackberries

Smartphones can be secure

  • print
  • alert

Magic Quadrant for Enterprise Backup/Recovery

Sysadmin blog Most of the articles about the security of Research In Motion’s Blackberries have focused on governments that want a peek behind RIM’s encryption, but other elements of the Blackberry make it well-designed for a business environment.

Administrators who work with Blackberries are familiar with the ways in which handhelds can be controlled from Blackberry Enterprise Server (BES). BES can push down policies which allow administrators to enable just about any feature of a handheld or handhelds. If the unit has been lost or stolen, they can locate it using the GPS, or remotely wipe it.

In addition, there are only two ways to move a Blackberry from one BES setup to another. The first is to deactivate the handheld against the old server and reactivate against the new one. Doing this completely wipes all personal information (e-mail, contacts) from the device immediately. The second method is to wipe the handheld and reactivate against the new server.

This means that it is difficult for individuals to use a Blackberry handheld for corporate data theft. You can prevent a user from tethering a Blackberry using Desktop Manager and synching data to a PC outside company control. It is not possible to disconnect the Blackberry from the server, join a new one, and push all the information up to the new server. 

An unscrupulous Blackberry user with sensitive information could, of course, turn the radio off on the device to prevent a remote wipe from the (most likely former) organisation’s BES, but they would be forced to copy the information off the handheld manually. While not infallible, Blackberry security is robust.

Despite Research In Motion’s failure in the consumer market, and encryption spats, look at the security model to understand why Research In Motion has earned its position as the enterprise mobile device.

It is odd to long-time Blackberry administrators that these features are news to anyone. The push by vendors and carriers to move Android and iPhone into the business world have focused on Exchange connectivity at the expense of discussing security. Non-Blackberry administrators may simply not have been exposed to these features.

The explosive growth of handhelds should be forcing a rethink of mobile data security. Powerful as Blackberry security is, alternatives are appearing. Microsoft offers System Center Mobile Device Manager to support Windows Mobile 6.1 and newer handhelds. This brings the security of Windows Mobile within range of the Blackberry.

Third party mobile device management applications are also appearing, each supporting mixtures of Symbian, WebOS, iOS, Android, Windows Mobile and Blackberry. Zenprise, Fromdistance, Soti, MobileIron, Excitor, Tangoe and Sybase’s Afaria are all contenders. Research In Motion has an excellent product with a well-established history in enterprise mobile device security, but it had best watch its back. ®

Agentless Backup is Not a Myth

Common sense invention

Why don't the Lock Screens for smart phones have a space where the owner could provide his contact information (alternate landline telephone number, e-mail). As it is, if you have a password on your smart phone, then when someone finds it there's no obvious way to contact the rightful owner. At best, they drop it off with the local authorities and, with luck, it eventually gets returned.

But if the Enter Passcode screen had a spot for an alternate telephone number or e-mail address, then it would make things very easy for the finder to contact the owner.

Perhaps the alternate telephone number could even be an active button that would allow the call to be made from the found phone.

This improvement would allow lost phones to be returned within hours. Directly.

4
0

Who Cares About the Phone?

The company I work for does not give a toss about a cheap bit of hardware - they want to know that they can zap it should I report it lost. And they do not want the finder to know that it belonged to Mr XXX of XXXX Ltd, either, as that just helps identify the data source.

They don't want it back if lost/stolen - they just want it, and its data, to die.

2
0

Obviously it must just be that easy

...because everybody's doing it. All you have to do is steal a device, hope nobody notices it's gone and wipes/deactivates it from BES, and then tunnel your ill deeds through the BES protocol through the RIM NOC and through an exploited BES server.

Simple, I think I'll do it tonight just to show how easy it is. Maybe I could film it and put it on Youtube.

/sarcasm

Seriously, not trying to offend here but you have no idea what you're talking about. The BES server is only open to the RIM NOC - an ISA (assuming you're running Exchange) or Traveler (if you're one of the rare Lotus types) server is open to everything.

Which is easier - the hack that requires you to have physical access to a trusted device and relies on some unknown method/ability to exploit a BES server, or the one that does not require a physical device (i.e. can be spoofed) and is open to the world (meaning: direct connection by the attacker)?

1
0

More from The Register

SCO vs. IBM battle resumes over ownership of Unix
Zombie lawsuit back and wants to suck the brains out of Linux
 breaking news
You don't need phone lines or cable for ANYTHING, says Dish
The satellite-dish man can sort you out with phone and broadband over the air too
 breaking news
What's HP got under wraps? Looks awfully flash and tape shaped
What happens in Vegas won't stay there - we've got the details
AMD lifts the veil on Opteron, ARM chip plans for 2014
Not much action going on in 2013, though
Microsoft borks botnet takedown in Citadel snafu
Stupid Redmond kicked over our honeypots, wail white hats
IBM's $1bn layoffs latest: Now axe swings in US, Canada - reports
Union claims 121 storage bods canned after dismal sales
NetApp musters muscular cluster bluster for ONTAP busters
Storage array OS overhauled to juggle more nodes, go down on you, er, less
HP adds 'Haswell' Xeon E3s to entry ProLiant servers
Gussies up MicroServer for SMBs, adds baby switches