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
Cartoon
Current Issue
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2012-3946
Published: 2014-04-24
Cisco IOS before 15.3(2)S allows remote attackers to bypass interface ACL restrictions in opportunistic circumstances by sending IPv6 packets in an unspecified scenario in which expected packet drops do not occur for "a small percentage" of the packets, aka Bug ID CSCty73682.

CVE-2012-5723
Published: 2014-04-24
Cisco ASR 1000 devices with software before 3.8S, when BDI routing is enabled, allow remote attackers to cause a denial of service (device reload) via crafted (1) broadcast or (2) multicast ICMP packets with fragmentation, aka Bug ID CSCub55948.

CVE-2013-6738
Published: 2014-04-24
Cross-site scripting (XSS) vulnerability in IBM SmartCloud Analytics Log Analysis 1.1 and 1.2 before 1.2.0.0-CSI-SCALA-IF0003 allows remote attackers to inject arbitrary web script or HTML via an invalid query parameter in a response from an OAuth authorization endpoint.

CVE-2014-0188
Published: 2014-04-24
The openshift-origin-broker in Red Hat OpenShift Enterprise 2.0.5, 1.2.7, and earlier does not properly handle authentication requests from the remote-user auth plugin, which allows remote attackers to bypass authentication and impersonate arbitrary users via the X-Remote-User header in a request to...

CVE-2014-2391
Published: 2014-04-24
The password recovery service in Open-Xchange AppSuite before 7.2.2-rev20, 7.4.1 before 7.4.1-rev11, and 7.4.2 before 7.4.2-rev13 makes an improper decision about the sensitivity of a string representing a previously used but currently invalid password, which allows remote attackers to obtain potent...

Best of the Web