Assignment: Secure Email

For this assignment, your goal is to design and evaluate a new user interface for a secure email technology.

You can do this by yourself or you are allowed to work with a partner from class. When working with a partner, you both much submit the same thing to Canvas, and both members will receive the same grade.

Background: Identity-based Encryption

Imagine you work for a new startup company that wants to build a new way of doing encrypted email based on a cryptographic technique known as Identity-Based Encryption.

Identity-Based Encryption or IBE is an interesting way of doing encryption. It is based on the concept of public key cryptography

In public key cyptography, the sender of a message uses a “public key” to encrypt their message, and only the owner of a corresponding “private” key can decrypt and read the message. The public key can be published and given to anyone who wants to send a message, and other people who have the key cannot read messages because they do not have the private key.

One challege with public key cryptography is how do you know if you have the right public key? If you download my public key from the Internet, how do you know it is actually my key? What if someone else substituted their key? Then they could read your messages to me.

Identity-based encryption tries to solve this problem by using your email address as your public key. If Alice wants to message Bob, then Alice encrypts the message using Bob’s email address as his public key and sends the encrypted message to Bob. When Bob wants to read the message, he contacts a “Private Key Generator” (PKG), who sends him his own personal, specific private key. Bob can use that private key to read any message that is encrypted with his email address.

Alice knows she has the right public key because she sends the email to Bob’s email address, and his email address is his public key. The PKG knows that only Bob has the private key because they can send that key to Bob’s email address (or use some other, more secure method of verification and transfer) – and they only have to do this once, and then Bob can read all email sent to him.

Your imaginary startup company has built a PKG – a private key generator – and wants to operate this for the Internet. That is, anyone on the Internet can contact them and, after verifying their email address, can get the private key for that email address.

They also want to build an interface on Gmail that would allow people to use their technology to send and receive encrypted emails. They plan to build a plugin / interface on top of Gmail for this. They need you to to design this interface. What would it looks like? What buttons should it have? How should it work?

Part 1: Competitive Analysis

Identify one or more secure communication tool(s) and describe the security features / interface. It is unlikely that you will find one that used IBE; instead, focus on other ones that use some form of public key cryptography. Since your company wants to make encrypted email, look specifically for encrypted email systems.

As you did in the previous assignment, you should identify a list of features, and then use product documentation and product reviews to fill in a table that shows which email systems have which features.

Part 2: Interface Design

Next, think about how to create an interface for sending and receiving encrypted email using this hypothetical IBE system. Assume that the basic technologies exist (encryption, decryption, a PKG server, etc.) What would the interface need to look like? How would you make it look? What buttons would you add? What would they be labeled? How would you represent encrypted email to the user so they can understand enough about what is happening to use it?

To do this, you will need to think through the whole process of sending and receiving an encrypted email – typing the email, encrypting it, sending it, receiving it, decrypting it, reading it, retrieving the key, etc. You might also think about error cases, such as if the email doesn’t decrypt properly (e.g. because an adversary changed it). What interfaces are needed to make this work?

Part 3: Prototype Mockup

To support your design, you need to create a prototype. A prototype takes your interface ideas and makes them seem real, without actually having to build the underlying technology. You have two options for a prototype:

  1. If you know how to use Figma or other prototyping tool, use it to create a series of static prototype images of your interface.

  2. Create a paper prototype using printed paper.

Be sure to create a prototype for ALL interfaces / screens that are needed.

Part 4: User Evaluation

Now it is time to try out your design, and see if people can use it. You must conduct an evalation of your prototype with an actual user. Find someone who might want to use secure email, and then set up a time to meet them and use your prototype. Give them a realistic and reasonable task to do that involves sending an encrypted email, and ask them to use your prototype to do it.

You will need to actually give them two separate tasks. One task should involve sending an encrypted email to someone. The second task should involve receiving an encrypted email and needing to read it.

Since the prototype isn’t real, you will have to walk them through the various screens that you create.

The whole time, you should be taking notes. What is going well? What is the user stumbling over? Where tasks are the user able to figure out? Where does the user seem confused, or slow?

Part 5: Revised Version

Use the results of your user evaluation to revise your interface design / prototype. Now that you’ve seen the user, what might you do differently? What should you change? What is working well that you want to keep? Make the revisions.

Write a Design Report

Finally, you should write a report that contains all of your final design and the reasoning (including data) behind the design. Pretend that the company making this technology exists, and write up the design for them.

The report should contain:

  1. The final design that you arrived at, and the reasons why it is designed the way it is.

  2. A competitive analysis table that helped inform your initial design.

  3. The initial design you started with.

  4. Findings from your user evaluation

  5. A list of changed you made to your initial design, and the reasons behind those changes

The report might be short, but it also might be long because it should contain images with your designs. The actual text by itself (without images) should fit within 5-6 pages, but the document can be longer with design images.

Your report should also include an appendix that includes:

a. All sources of information (with links) that you used for your competitive analysis.

b. Your notes (with any sensitive information redacted) from the user evaluation.

c. Either a working link to your prototype, or photographs of the paper prototype that was used in the user evaluation.

Due: Thursday Nov 13, before class