Bring Your Own Device: A Simple Policy for Employee iPhones, Androids, and iPads

From the archive: this article was written in 2011 and reflects the technology and threats of that time. For current advice, see our latest articles or ask us directly.

A few years ago, the company phone was a BlackBerry handed out by the office, and personal phones stayed in pockets. That world is fading fast. Walk through any office in Clearwater or New Port Richey today and you will see iPhones, Android phones, and a growing number of iPads, most of them bought by the employees themselves, and nearly all of them hooked up to company email.

The industry has started calling this "bring your own device," or BYOD. It is mostly a good thing: people are more responsive, work gets done from the road, and the business does not pay for the hardware. But it also means company email, contacts, and documents are sitting on devices the business does not own and does not control. A little planning goes a long way.

Why this matters more than it seems

Think about what is on a typical employee's phone: months of email, attachments with pricing or customer details, the entire company contact list, calendar entries, and often saved passwords for business websites. Now think about how often phones get left in restaurants, forgotten in cabs, or stolen from cars.

A lost laptop gets people's attention. A lost phone often gets shrugged off with "I will just get a new one." Yet the data exposure can be very similar. Without a passcode, anyone who picks up that phone has instant access to your company inbox.

The good news: you probably already have the tools

If your office uses Microsoft Exchange, whether on your own server, on Small Business Server, or through a hosted service like the new Office 365, you already have a powerful set of controls called Exchange ActiveSync policies. ActiveSync is the technology that syncs email, calendar, and contacts to most smartphones, including the iPhone, the iPad, and many Android phones.

When a phone connects to Exchange through ActiveSync, the server can require certain settings before it hands over any email. Common ones include:

  • Require a passcode to unlock the device.
  • Minimum passcode length and, optionally, complexity.
  • Automatic lock after a few minutes of inactivity.
  • Wipe after too many failed attempts, so someone cannot just keep guessing.
  • Require device encryption on devices that support it.
  • Remote wipe, which lets an administrator (or the user, through Outlook Web App) erase the device if it is lost or stolen.

One important caveat: not every device honors every policy. Support varies between phone makers and Android versions, and some older or cheaper devices ignore settings they do not understand. Exchange can be set to block devices that cannot comply, which is worth considering.

A four-digit passcode and the ability to wipe a lost phone solve most of the real-world risk. Start there.

The tricky part: it is their phone

Here is where BYOD gets delicate. A remote wipe through ActiveSync typically erases the whole device: not just company email, but the employee's personal photos, music, and apps too. That is a big deal, and employees deserve to know about it before they connect.

That is the main reason to write a policy down, even a short one. It turns an awkward surprise into an agreed-upon rule. It also encourages people to back up their own phones regularly, which is good advice anyway. On the iPhone, syncing with iTunes makes it easy to restore personal content after a wipe, and Apple's free Find My iPhone service can help locate a misplaced device before anyone has to wipe it.

What happens when someone leaves

This is the scenario most small offices never think about until it happens. An employee resigns or is let go. Their Windows account gets disabled. But their iPhone still has two years of company email on it, and maybe it is still syncing.

Your policy should cover this clearly:

  • Disable the account and block the device on the day of departure, as part of the normal exit checklist.
  • Remove the company email account from the device, ideally with the employee present.
  • Decide in advance whether the company reserves the right to wipe the device if it cannot confirm company data has been removed.
  • Change any shared passwords the person may have saved on their phone.

A simple BYOD policy checklist

You do not need a 30-page document. A one- or two-page policy that people actually read beats a thick binder nobody opens. Cover these points:

  1. Which devices are allowed to connect to company email and systems.
  2. Security requirements: passcode, auto-lock, and encryption where available.
  3. Remote wipe: when the company may use it, and a clear statement that it may erase personal data.
  4. Lost or stolen devices must be reported right away, day or night.
  5. No jailbroken or rooted devices, since they bypass built-in protections.
  6. Leaving the company: company data is removed and access is revoked on the last day.
  7. Support boundaries: what IT will help with, and what is the employee's own responsibility.
  8. Signed acknowledgment from each employee who connects a personal device.

Then turn on the matching ActiveSync policies in Exchange so the rules are enforced, not just written down.

The bottom line

BYOD is not a trend you can stop, and most businesses should not try. People are more productive with the devices they like. The goal is simply to make sure company information is protected when those devices get lost, stolen, or walk out the door with a departing employee. If you would like help setting up ActiveSync policies or drafting a sensible device policy for your team, we are glad to help. Get in touch at info@pinellasit.com or through our contact form, or read more about our managed IT services.

Need help with this?

Talk to a local IT team that has supported businesses across Pinellas & Pasco County since 2010.

Get a Free Consultation Free Security Assessment