Commentary

Ed Hansberry
 

IT Versus User Devices

Corporate IT managers often find themselves at odds with employees over allowing access to company data with personal devices. There are ways though to benefit both parties.

Employees for years have been bringing in personal devices to give them easier access to the data they need to get their jobs done. This is exactly what gives IT managers some of the worst cases of heartburn though.

When personal digital assistants like the original Palm Pilot hit the scene in the mid-1990s it was aimed at the corporate executive or mobile employee. Corporations weren't exactly falling over themselves to provide PDAs to employees, yet there were few major companies that didn't have a PDA synchronization tool installed, surreptitiously or not, somewhere on their network that let an employee have a portable copy of their contacts, appointments, tasks, emails and even office documents.


More Security Insights

Webcasts

More >>

White Papers

More >>

Reports

More >>

Those were truly the days of the wild west for mobile devices. Devices then didn't know what a policy was so there was no way to control what happened. Today though, things are a bit different. Employees still bring in devices and try to plug them in, but today's devices are more IT friendly. With the exception of RIM's Blackberry, all of the major smartphone players have Microsoft's Exchange ActiveSync client built in. With that, IT managers are at least able to push down policies that require the device to lock with a security code and ensure that it can be wiped clean in the event the device is reported lost or stolen.

Blackberry devices, of course, are the veritable Swiss army knife when it comes to policies IT can enforce when paired with the Blackberry Enterprise Server. The problem is fewer and fewer employees are bringing in a Blackberry to hook up. As I wrote yesterday, the real battle in this area is between Apple's iOS and Google's Android.

Regardless of the device though, some sticky questions remain. How much control can a company exercise over a device it doesn't own? What happens when the employee leaves? The Wall Street Journal tries to answer these and other questions in a recent story.

When evaluating these issues, it is important to remember that an employee that wants to do this is trying to be more productive. They don't mind when work encroaches a bit on personal time, so the IT department that comes down hard with draconian measures to prevent this will foster resentment and cut overall productivity.

The key is to find a balance between adequate security to protect company information and enough flexibility to benefit users and their departments. How device friendly is your company?


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
Subscribe to RSS

Resource Links