Can your Employer Wipe your Phone?

An Survey released today indicated that 70% of employees would not use their personal devices for work if they had knowledge that their employer could remotely wipe or lock that device.  70% !! It’s clear that employees are beginning to recognize that just downloading their work email onto their personal devices such as phones, tablets and laptops means the Enterprise will want to secure that information, and that this is often done in an overbearing, infringement of privacy fashion.  Not that Enterprises are trying to interfere with their employees privacy, they are simply trying to protect their data in any way possible, and in the past, most MDM (Mobile Device Management) solutions have been similar to a linebacker knocking over a toddler to get the ball.

Eweek.com reported that “more than 75 percent of enterprises in the survey were unable to meet eight out of 10 of their current top security requirements– this was combined with the fact that only 11 percent of employees are aware of the current level of enterprise control over their device.”  

So what happens as more and more employees gain awareness of the tight infringements on their personal devices? Lack of compliancy, which leads to vulnerability of sensitive data, which can of course lead to – disaster for the Enterprise.

The study of 1,000 IT  person; and 1,000 employees, conducted by research firm Harris Interactive, found that 83 percent of staff would stop using their own device or still use it with deep concern, if they knew their employer could see what they were doing at all times.

So what’s the Solution?  Enterprises SHOULD protect their data on devices that leave the office, but the level of intrusion on an employee’s personal device needs to be kept in check too, to make sure employees will not feel intruded upon and actually be compliant.  The first step is to use a product/service that uses the minimum security necessary; in many cases there is no need for an Enterprise to monitor which websites employees visit or what games they install.  Keep the Enterprise’s data separate (sandboxed) and manage it that way – it is really more the management of the DATA versus the management of the device.  The second step is discussing these policies with the employees, so that they have full knowledge of what these policies entail and how it affects their personal devices.  Engage your employees in the solution, versus thrusting it upon them.

 Yes, these email policies ARE necessary. But they don’t need to necessarily infringe on your rights – there are solutions out there (our own Cockpit, for one, and likely others, in the future) that are cost-effective, keep company data safe and maintain your privacy.  Win-Win!

 

Securing your Email with S/MIME

Today we start an awesome mini-series from one of our support gurus, DragonFly, about how S/MIME works in general, with following tutorials on how to implement S/MIME in TouchDown on iOS, Android and Mac platforms.  Check out today’s tutorial on iOS!

Hi,

Dragonfly from NitroDesk support here. In the following, today I’ll be describing how to import and use S/MIME in Touchdown for iOS. Using this functionality you can sign messages, proving that you are the person sending that particular message, and optionally encrypt them, meaning the email will only be readable by people who you have included in the message. Signing provides you with non-repudiation and potentially detect tampering on the fly and encryption prevents unauthorized viewing of the message. This type of functionality is great for keeping your emails safe and ensuring that information’s coming from the right source. (For more information on how S/MIME works, here’s a good tutorial: http://technet.microsoft.com/en-us/library/aa995740%28v=exchg.65%29.aspx) Just know that to send an encrypted email, you need to have the recipient’s public key and vice versa- these can be verified from within Touchdown when that person sends you a signed message. Here’s what you’ll need before you get started:

First, you’ll need a certificate for S/MIME signing and the latest version of Touchdown. To get a certificate for S/MIME, you’ll want to contact your IT team. Also, keep in mind the only two certificate types Touchdown supports is .pfx and .p12. The certificate would need to include the complete chain to the root certificate authority.

If you have your certificate already in IE, but need to export it to your desktop,Here’s how (in IE):

1. Go into the Settings>Internet Options, and clicking on the Content tab.

2. Click on Certificates, and find the one you want to export

3. Click Export. Make sure you choose the option to export the private key and also to include all certificates in the certification path.

4. Choose a file path, and save it.

5. Don’t forget to  remember the password you use to perform the export. This password prevents anyone else from being able to access the certificate. If you’re having difficulty with this process, contact your IT team and see if there’s another way you should be doing it. As with any operations like this, make sure you are staying within your IT team’s best practices so you stay in alignment with any security policies.

6. Once you have your certificate backed up to a file, send that file to your email as an attachment, and you’re ready to go.

Let’s start with the iOS version.

S/MIME for iOS

In this demo, I show how to send an encrypted email to the ‘welovenitrodesk’ account.

First, I want to ensure that I have my certificate for S/MIME, so I find the email with the attached certificate, and view it in the attachment list.

IMG_0007
The attached certificate, note the file type is .pfx. 

After downloading, I click the ‘I’ icon and choose to ‘Import for both.’

IMG_0008
Choose Import for Both.

A password prompt appears.

IMG_0009
Enter your certificate password here that was created when you generated the certificate. 

After entering the correct password (This is set up during certificate exporting from your browser, for help with this  please contact your IT team) it will tell you your certificate has been saved.

IMG_0010
Saved certificate message. 

Now that I have a certificate, I’m ready to send the account  welovenitrodesk an encrypted message:

I click on the tools/options icon and enable Encryption and signing.

IMG_0011
Tools icon to enable encryption signing.

IMG_0012
Enable signing and encryption for the email.

I send the email. If you suddenly see this message (see below), it means you didn’t validate the recipient’s public certificate key from a signed message. (This can also be done over the GAL if your company supports it.) Remember how I said earlier that to send an encrypted email, you need the recipient’s public key? Now I just need to fetch it. Thankfully, a while back welovenitrodesk sent me a signed message, which contains the key.

IMG_0016
Oops!

I find the email where welovenitrodesk sent me the key, and click on the lock icon.

IMG_0017
Welovenitrodesk sent me a signed message.

I click ‘verify signature’ and it verifies.

IMG_0018

Now I can send that encrypted message!

The second time, I attempt to send the encrypted message again. This time it comes through.

Back in welovenitrodesk, after having imported the public certificate and the welovenitrodesk certificate, I check the encrypted message, and am able to successfully decrypt it.

IMG_0020

The signed and encrypted email.

Clicking on the lock icon, I can confirm that it is indeed signed and encrypted.

Hope this helps you get a better understanding on how to use S/MIME functionality with Touchdown for  iOS. If you have any questions, please feel free to contact us at  iossupport@nitrodesk.com for any iOS queries. Be sure to check in on Monday for Part II, SMIME for Android. Thanks for reading!

KNOX Vulnerabilities

There is a lot of buzz going around the discovery that Samsung’s KNOX container has been found to have some vulnerabilities, as reported by the Wall Street Journal Tuesday and  PC World yesterday.  While it is very poor timing for Samsung, considering CES, the huge technology show in Vegas, starts next week, we are confident that Samsung is dedicated to security and will find a fix quickly.

What exactly is the concern? The vulnerabilities found by Israel’s Ben-Gurion University of the Negev indicate that Knox software (when used on a  Samsung Galaxy S4 or Note 3) could allow malicious apps to eavesdrop on data transferred within the secure environment.  The WSJ reports :“Samsung officials told the Journal that the vulnerability was found in developer phones that weren’t “fully loaded with the extra software that a corporate client would use in conjunction with Knox,” the paper reported. So far, the Knox vulnerability has only been discovered on the Galaxy S4.”

The PC World article compared KNOX to our TouchDown, since both are designed to keep data secure – so what does all this mean and how does it work?  TouchDown was specifically designed to keep data secure against this type of data breach.  It keeps corporate data secure through encryption and by keeping it ‘sandboxed’ away from a users personal data on their device (smartphone, laptop, tablet).  It works directly with ActiveSync Exchange and keeps email, contacts, calendar and notes data secure when kept within TouchDown.  Meanwhile Samsung’s KNOX creates a container around several third party apps, with the purpose of keeping data within those apps separate from app data not inside the KNOX container.  The security breach discussed  in the article regards the potential security breach of the KNOX container itself, meaning malware could have access to apps inside the container.  If there are apps inside the container that are not secure, they could potentially be breached. Luckily, TouchDown users can breathe easy, since even if a malware attack did get past the KNOX container it would not be able to breach TouchDown data. So whether you are using  TouchDown in or out of the KNOX container on a Samsung device, your data will remain secure and separate from other data on your device.  If you’re not using TouchDown…what are you waiting for??