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

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
Cartoon
Current Issue
Dark Reading Must Reads - September 25, 2014
Dark Reading's new Must Reads is a compendium of our best recent coverage of identity and access management. Learn about access control in the age of HTML5, how to improve authentication, why Active Directory is dead, and more.
Flash Poll
Threat Intel Today
Threat Intel Today
The 397 respondents to our new survey buy into using intel to stay ahead of attackers: 85% say threat intelligence plays some role in their IT security strategies, and many of them subscribe to two or more third-party feeds; 10% leverage five or more.
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2012-5485
Published: 2014-09-30
registerConfiglet.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to execute Python code via unspecified vectors, related to the admin interface.

CVE-2012-5486
Published: 2014-09-30
ZPublisher.HTTPRequest._scrubHeader in Zope 2 before 2.13.19, as used in Plone before 4.3 beta 1, allows remote attackers to inject arbitrary HTTP headers via a linefeed (LF) character.

CVE-2012-5487
Published: 2014-09-30
The sandbox whitelisting function (allowmodule.py) in Plone before 4.2.3 and 4.3 before beta 1 allows remote authenticated users with certain privileges to bypass the Python sandbox restriction and execute arbitrary Python code via vectors related to importing.

CVE-2012-5488
Published: 2014-09-30
python_scripts.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to execute Python code via a crafted URL, related to createObject.

CVE-2012-5489
Published: 2014-09-30
The App.Undo.UndoSupport.get_request_var_or_attr function in Zope before 2.12.21 and 3.13.x before 2.13.11, as used in Plone before 4.2.3 and 4.3 before beta 1, allows remote authenticated users to gain access to restricted attributes via unspecified vectors.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
In our next Dark Reading Radio broadcast, we’ll take a close look at some of the latest research and practices in application security.