SecurityUI-UX: Difference between revisions

Jump to navigation Jump to search
m
no edit summary
No edit summary
mNo edit summary
Line 17: Line 17:
|Feature users and use cases=Our UI falls into two main areas:
|Feature users and use cases=Our UI falls into two main areas:


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


Some areas to investigate:
Some areas to investigate:


a) context information about the current site ("am I on store.com")  
*context information about the current site ("am I on store.com")  
 
*is the current site "secure" ("should I enter my password/credit card")
b) 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")
c) historical information ("what information has this site stored on my computer")
*inline warnings (this is a phishing/malware site, this site wants to install an <X>, mixed content, etc.)
 
d) incident driven ("I read about this security issue and I want to disable a cert/feature/etc")
 
e) 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).
Note the above parenthesized examples are not intended to be exhaustive (or even good).
Confirmed users
717

edits

Navigation menu