When Mobile Device meets Home Network

In his recent Forbes article, Adam Levin made a good argument for the danger of BYOD, and what steps enterprises should employ if they do allow BYOD.  He points out that employees do utilize devices and computer at home, often on insecure networks and weak routers.  Levin emphasizes that enterprises should require and verify that  home networks use secure routers with up-to-date firmware, that home equipment should be just as secure as the network at work.  In general, a lot of solutions forget that its not only tablets and smartphones that enterprises need to worry about.  Laptops are mobile devices too, and if employees are using home computers and home networks, those should be secured as well.

I think the best overall approach to data security is education, containment, verification and respect.  I do agree that it is imperative that enterprises secure their data, the expense of not doing so far outweighs  the costs of security implementation.  While I do believe this should reach even into the employees home network, I think that educating the employees on how important this is and what the disastrous results could be if this is not followed is as critical as the implementation itself.  Furthermore, I think respecting the employees privacy is the number one way to ensure their commitment to protect this data.  Employees will be a lot more likely to follow through with the invasion of their own devices if the corporate data is in a separate container, and the personal part of the device is left alone.  With all the device and data management options out there, there is no excuse to have to wipe all the data off of an employees device; only the corporate data should be wiped.

So, to add to Levin’s points:

1. Have a corporate Data Policy which includes all technology used to access corporate data, whether this is a smartphone or an employees home network used to access corporate data.

2. Discuss above policy with employees to help them understand the importance of keeping corporate data safe, and outline how you will keep the employees data private.

3. Make it easy for employees to implement security software.

 

There are so many data management options out there – choose one that allows comprehensive control and allows employees the privacy and integrity of their own data if the device would need to be wiped.

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!

 

How S/MIME Encryption works, Part II

As promised, here is part two of our S/MIME encryption series (how to encrypt your email on TouchDown for Android) by our awesome support master, Dragonfly:

First off, I open the email with the certificate attached. Entering the attachment list, I download and long press it to bring up a menu, and choose ‘import certificate.’

Long press on the attached certificate.

Choose import certificate.

I enter the password.

Enter the password.

This menu pops up, make any changes you want, and hit Ok. Contact your IT team if you’re not sure if you need to choose any of these settings.

Now I have the certificate imported, and can send out signed or encrypted emails. As I want to send an encrypted email to welovenitrodesk, I’ll grab their public key in an email they sent to me.

The signed email from welovenitrodesk. I apparently can’t spell sign.

I click on the key icon in the top right, and am prompted to validate the certificate, which I do. Now I have their public key in my store.

Click Validate.

The certificate is valid.

Now I compose an email to them and click the menu button, and choose ‘options’.

The device I used for this doesn’t have a menu button, so Touchdown generates a soft one. Different devices will look different, but it usually isn’t too hard to find the menu key on the compose screen. (If you don’t see a soft menu button, and are on a device running Android 3.x or above, you want to be using Touchdown HD instead of Touchdown for Smartphones.). Optionally you can also press the Options button on the blue toolbar.

Choose to sign and encrypt it.

And just like that, I’ve sent welovenitrodesk a signed and encrypted message.

Meanwhile, in welovenitrodesk, the signed/encrypted message decrypts perfectly.

Hope this helps users get a better understanding on how to use S/MIME functionality with Touchdown for Android. If you have any questions, please feel free to contact us at support@nitrodesk.com for any iOS queries. Thanks for reading!

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.

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

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

Choose Import for Both.

A password prompt appears.

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.

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.

Tools icon to enable encryption signing.

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.

Oops!

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

Welovenitrodesk sent me a signed message.

I click ‘verify signature’ and it verifies.

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.

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!

Make BYOD a Win-Win

More and more the BYOD (Bring your Own Device) movement is taking over the small, medium and even huge enterprise world.  At first it seemed like a win- win for smaller firms – employees would get to use their own devices that they prefer and are comfortable, and business wouldn’t have to shell out a ton of money purchasing new devices for each new employee.  Employees could sneak in a a Facebook post or check their personal email during working hours, and no one would be the wiser. While Heads of IT departments freaked out everywhere,(with good reason) CEO’s and employees everywhere were happy – until the realization hit that now that enterprises sensitive data was  being carried out of the office onto trains, planes and automobiles.  Not to mention cafe’s movie theaters, bars…  A logistical nightmare or IT departments trying to make sure no data leaks pout anywhere.

MDM’s to the rescue!  Smart developers responded to this growing need by  developing all-encompassing, control-every-move of the user’s device – and charging a lot for this security.   IT heads breathed a sigh of relief, and CEO’s shortly followed, if nothing but relieved that their IT department heads were no longer complaining. However, now employees were unhappy, rightfully feeling that their privacy rights were being infringed upon.  If Joe brings his cell phone to the workplace and back home to do work, should the enterprise be able to control what he downloads? Where he surfs?  What he takes pictures of?  So, the pendulum tipped the other way, and while controls are secure, employees feel violated and therefore, end up being less compliant.  Less employees are using all the necessary passwords, PIN’s and other security measures.

What’s the answer?  The middle, of course!

BYOD doesn’t have to be a win-lose proposition where only the employee or the enterprise wins.  There are many options that allow employees to use their own devices that preserved the users privacy.  Enterprise data SHOULD be protected on a users device – in it’s own, safe sandboxed compartment on the device.  Enterprises SHOULD be able to control that compartment, whether  to access it, wipe it remotely, or check on it’s current state.  That’s all that is really necessary. There is absolutely no need to ” manage” the rest of the device – only the enterprise compartmentalized data.  It’s the Data,  (and only the Enterprise’s data) not the device, that needs to be managed.  It IS possible to make BYOD be a win-win.

 

 

What happened with Target and what you can learn from it

So it turns out Target was allowing one of their maintenance companies (an HVAC/refrigeration company) to access Target’s database so that no one had to actually come out and show up to log-in to do efficiency updates, it could all be done remotely…this is quite common, and not a problem if you keep your private information separate from your non-private. 

See, hackers unfortunately are often quite smart, and can find vulnerable points of entry into a database, especially a shared database that has several  points of entry.  Find another way besides the obvious  “secure entry point,” and then follow it all the way to the goldmine of private data.  This is what happened in Target’s case.  One of the HVAC’s worker’s credentials was stolen, and the hackers were able to insert the malware through this entry point and access the payment network through the maintenance network.  They were able to put this card-stealing malware on POS (Point of sale) cash registers at various stores, and after verifying it worked and that it was NOT detected, were able to access most of the Target stores nationwide, stealing card numbers in real time.

Visa, MasterCard and other Card payment systems do not require  that retail stores and other payment collectors keep their payment  networks  separate from their other operational networks, but it would kind of make sense, no?  Payment collectors ARE supposed to require a two-factor authentication system for remote login capability, and it appears that Target did not have such a system in place.

Had Target kept their sensitive (Customer financial data) separate from less sensitive operational data, they could still have allowed remote log-ins without putting their customers at risk.  

So the point is twofold:

1)Even as a small company (and Target is HUGE), do not be cheap with the security of your data, especially your customer’s financial data.  Yes, Target saved money in the short term by not buying software that kept their data separate and by having a two-factor authentication system in place.  But the huge financial cost of stolen data ALWAYS outweighs the smaller cost of preventing it in the first place, not to mention the larger cost that is not easily fixed: losing their customer’s trust.  

2) Keep your sensitive data separate. And yes, this goes for you too.  On your phone.  On your laptop (yes, that IS a mobile device).  Your iPad that your kiddo plays with at the dentists office or in the Target shopping cart while you shop.

Whether it’s your own device, or you own a business and need to keep you enterprise’s data safe, use software that helps you achieve separation.  With products as affordable as $20 why are you NOT doing this? Trust me, it will cost a lost more if someone steals your data or your identity.

 

 

Why many are dumping their MDM

It is here!!!!  If you’re ready to have excellent BYOD data security, without all the complications and cost of an MDM, check out:

 

 

 

http://www.cockpitcontrol.com

Putting you at the Helm of your Enterprise Data Security

Congratulations to AirWatch and VMWare

 

Congratulations to  Alan Dabbiere, John Marshall and all of AirWatch and  VMware! The announcement that AirWatch is being acquired by VMware was officially  announced today. We are super excited about this new chapter in the history of one of our favorite partner companies and we look forward to continuing that relationship with VMware.  It will be wonderful to see the AirWatch management team working closely together with Sanjay Poonen of VMware.  It’s great to see an industry leader such as VMware adopt a solid mobile strategy through an acquisition such as this…especially as BYOD just continues to grow and strategies for consistency and ease of use are a requirement for successful enterprises.

A little movie about TouchDown

Alex Fauske is a genius – we love what he did for us!

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??