SecurityUI-UX

Please use "Edit with form" above to edit this page.

Status

Security UI / UX Experiments
Stage	Draft
Status	`
Release target	`
Health	OK
Status note	Idea initiation

{{#set:Feature name=Security UI / UX Experiments

|Feature stage=Draft |Feature status=` |Feature version=` |Feature health=OK |Feature status note=Idea initiation }}

Team

Product manager	Lucas Adamski
Directly Responsible Individual	Curtis Koenig
Lead engineer	`
Security lead	Curtis Koenig
Privacy lead	`
Localization lead	`
Accessibility lead	`
QA lead	`
UX lead	Stephen Horlander
Product marketing lead	`
Operations lead	`
Additional members	`

{{#set:Feature product manager=Lucas Adamski

|Feature feature manager=Curtis Koenig |Feature lead engineer=` |Feature security lead=Curtis Koenig |Feature privacy lead=` |Feature localization lead=` |Feature accessibility lead=` |Feature qa lead=` |Feature ux lead=Stephen Horlander |Feature product marketing lead=` |Feature operations lead=` |Feature additional members=` }}

Open issues/risks

`

Stage 1: Definition

1. Feature overview

We suspect that current security UI is confusing to users and does not accurately provide them understandable and actionable information that allows them to make proper choices.

Since we have never holistically evaluated the effectiveness of our security and privacy UI, we should do some broad user research to identify shortcomings and design improvements.

2. Users & use cases

Our UI falls into two main areas:

• inline: user is notified of some security or privacy relevant event, and (may) want/have to take action
  
• task driven: the user wants to perform some specific task such as changing a setting or understanding their situation

Some areas to investigate:

• context information about the current site ("am I on store.com")
• is the current site "secure" ("should I enter my password/credit card")
• historical information ("what information has this site stored on my computer")
• incident driven ("I read about this security issue and I want to disable a cert/feature/etc")
• inline warnings (this is a phishing/malware site, this site wants to install an <X>, mixed content, etc.)

Note the above parenthesized examples are not intended to be exhaustive (or even good).

3. Dependencies

`

4. Requirements

`

Non-goals

`

Stage 2: Design

5. Functional specification

`

6. User experience design

`

Stage 3: Planning

7. Implementation plan

`

8. Reviews

Security review

`

Privacy review

`

Localization review

`

Accessibility

`

Quality Assurance review

`

Operations review

`

Stage 4: Development

9. Implementation

`

Stage 5: Release

10. Landing criteria

` {{#set:Feature open issues and risks=` |Feature overview=We suspect that current security UI is confusing to users and does not accurately provide them understandable and actionable information that allows them to make proper choices.

Since we have never holistically evaluated the effectiveness of our security and privacy UI, we should do some broad user research to identify shortcomings and design improvements. |Feature users and use cases=Our UI falls into two main areas:

• inline: user is notified of some security or privacy relevant event, and (may) want/have to take action
  
• task driven: the user wants to perform some specific task such as changing a setting or understanding their situation

Some areas to investigate:

• context information about the current site ("am I on store.com")
• is the current site "secure" ("should I enter my password/credit card")
• historical information ("what information has this site stored on my computer")
• incident driven ("I read about this security issue and I want to disable a cert/feature/etc")
• inline warnings (this is a phishing/malware site, this site wants to install an <X>, mixed content, etc.)

Note the above parenthesized examples are not intended to be exhaustive (or even good). |Feature dependencies=` |Feature requirements=` |Feature non-goals=` |Feature functional spec=` |Feature ux design=` |Feature implementation plan=` |Feature security review=` |Feature privacy review=` |Feature localization review=` |Feature accessibility review=` |Feature qa review=` |Feature operations review=` |Feature implementation notes=` |Feature landing criteria=` }}

Feature details

Priority	Unprioritized
Rank	999
Theme / Goal	`
Roadmap	`
Secondary roadmap	Security
Feature list	`
Project	`
Engineering team	`

{{#set:Feature priority=Unprioritized

|Feature rank=999 |Feature theme=` |Feature roadmap=` |Feature secondary roadmap=Security |Feature list=` |Feature project=` |Feature engineering team=` }}

Team status notes

	status	notes
Products	`	`
Engineering	`	`
Security	`	`
Privacy	`	`
Localization	`	`
Accessibility	`	`
Quality assurance	`	`
User experience	`	`
Product marketing	`	`
Operations	`	`

{{#set:Feature products status=`

|Feature products notes=` |Feature engineering status=` |Feature engineering notes=` |Feature security status=` |Feature security health=` |Feature security notes=` |Feature privacy status=` |Feature privacy notes=` |Feature localization status=` |Feature localization notes=` |Feature accessibility status=` |Feature accessibility notes=` |Feature qa status=` |Feature qa notes=` |Feature ux status=` |Feature ux notes=` |Feature product marketing status=` |Feature product marketing notes=` |Feature operations status=` |Feature operations notes=` }}