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.’

1392838742551
Long press on the attached certificate.

1392838748262
Choose import certificate.

I enter the password.

1392838754090
Enter the password.

1392838759967
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.

1392838771989
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.

1392838777326
Click Validate.

1392838782964
The certificate is valid.

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

1392838788105
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.

1392838798493
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.

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

Touchdown – Getting to know your Diagnostics

Today’s post comes from Dragonfly, our trusty, awesome and beloved iOS Support Guru.

Getting diagnostic information from TouchDown for iOS.

Occasionally during the troubleshooting process, a support technician may request a diagnostic log.  Here’s a visual guide on how to retrieve one from TouchDown for iOS:

There are two locations where you can get diagnostic information from the iOS version of TouchDown.

1. During configuration, which can be useful to determine where TouchDown is failing to connect.
2. The diagnostics menu.

In this blog post, I will cover the two methods of obtaining a diagnostic log.

Obtaining a configuration diagnostic:

When you open TouchDown for the first time, or any time after you reset the database, you will be  prompted to configure. On this screen, there is a toggle to Enable Logging. To get a configuration log, slide that to the ‘on’ position (see red circle below) and enter in your information.iosblog1

In the below screenshot, I intentionally entered wrong information and attempted to configure. Note  that as the configuration fails, there is an option to ‘Copy Log.’  Click that to put a copy of the log on your clipboard. Once you click it, you will get a notification that it has been added to your clipboard.

iosblogx

 

iosblogy

As I was unable to configure TouchDown, I entered my gmail account using the device web browser, and opened a new email to send to iossupport@Nitrodesk.com.  After long pressing on the body of the email, an option to paste appears. I click it, and it puts the contents of the diagnostic log into the body of the email:

iosblog3
After you paste the log into the email, send it to iossupport@nitrodesk.com with a description of the issue so the technicians there can see where the configuration is having issues.

Obtaining a regular diagnostic log:

If the support staff request an iOS diagnostic log of some specific behavior, here is how to retrieve it.  On the main mail screen, tap the circle triangle button, and choose the diagnostics button:

iosblog4

To ensure you get us a correct log, please tap ‘clear,’ which may return you to the main screen again. Enter diagnostics again via the circle triangle button, and enable logging:

iosblog6

Go back to TouchDown and perform the action you are having difficulty with.  Return to the diagnostics screen after you are done, and copy the log using the ‘copy’ button. You should receive a notification that it has been copied to the clipboard:

iosblog7

Open a new email, and long press on the body. An option to paste the log should appear. Select that, and you will have a diagnostic log pasted in the body of an email:

iosblog8

Thanks for reading and hope this was helpful in describing the different types of diagnostic logging in TouchDown for iOS.

Dragonfly