Analytics
12/31/2009
11:28 AM
Connect Directly
RSS
E-Mail
50%
50%
Repost This

Tech Insight: After The Holidays, It's Time To Re-Examine Smartphone Policies

With new portable devices coming out of the wrapping paper, how can enterprise security keep up?

'Twas the season for stockings stuffed with smartphones -- phones that include more computing power and functionality than computers might have wished for a decade ago. For enterprises, however, these "gifts" could be costly.

New toys, like iPhones, BlackBerrys, and the new Motorola Droid, give us around-the-clock connectivity that comes at a price not only to employees' personal time, but also to enterprise information security; just look at the recent attacks against "jailbroken" iPhones to steal personal data.

President Barack Obama's addiction to his BlackBerry is a testament to the need of today's society to have within reach the means to check e-mail, send text messages, and browse the Web. Of course, those are the more ordinary tasks. Smartphones now give us the capability to play online games, use instant messaging services, stay in touch with social networking sites, and much more. But what should companies do to secure these mobile communications and the data stored on such portable devices?

That's a question many IT workers will be facing as they ring in the new year. Many users will be returning to work with new Droids, iPhones, and even iPod Touches in-hand that they "need" connected ASAP to check email, access corporate intranets, and update statuses on social networks.

These requests and activities give rise to tough questions. Who's responsible for managing the security of "personal" devices that connect to the corporate network? What happens if a device capable of connecting to enterprise systems is lost? Should encryption be mandatory on portable devices that are used for work?

If it's a C-level executive with a new Droid, sometimes policies go out the window. However, that's not always the case. The key to dealing with smartphones -- and, really, any new whiz-bang hardware or software -- is to have policies for introducing them into the current infrastructure.

Previous
1 of 2
Next
Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Flash Poll
Current Issue
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2011-3154
Published: 2014-04-17
DistUpgrade/DistUpgradeViewKDE.py in Update Manager before 1:0.87.31.1, 1:0.134.x before 1:0.134.11.1, 1:0.142.x before 1:0.142.23.1, 1:0.150.x before 1:0.150.5.1, and 1:0.152.x before 1:0.152.25.5 does not properly create temporary files, which allows local users to obtain the XAUTHORITY file conte...

CVE-2013-2143
Published: 2014-04-17
The users controller in Katello 1.5.0-14 and earlier, and Red Hat Satellite, does not check authorization for the update_roles action, which allows remote authenticated users to gain privileges by setting a user account to an administrator account.

CVE-2014-0036
Published: 2014-04-17
The rbovirt gem before 0.0.24 for Ruby uses the rest-client gem with SSL verification disabled, which allows remote attackers to conduct man-in-the-middle attacks via unspecified vectors.

CVE-2014-0054
Published: 2014-04-17
The Jaxb2RootElementHttpMessageConverter in Spring MVC in Spring Framework before 3.2.8 and 4.0.0 before 4.0.2 does not disable external entity resolution, which allows remote attackers to read arbitrary files, cause a denial of service, and conduct CSRF attacks via crafted XML, aka an XML External ...

CVE-2014-0071
Published: 2014-04-17
PackStack in Red Hat OpenStack 4.0 does not enforce the default security groups when deployed to Neutron, which allows remote attackers to bypass intended access restrictions and make unauthorized connections.

Best of the Web