Security/Contextual Identity Project: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
(added platform work)
 
(9 intermediate revisions by 3 users not shown)
Line 1: Line 1:
__NOTOC__
__NOTOC__
= Goal =
Enable users to gain sovereignty over their personal data, whether it is deliberately shared, passively tracked, inferred, or otherwise aggregated.
= Background =
<blockquote style="background:#eee;padding:3px;">"I am large, I contain multitudes." -- Walt Whitman, <em>Leaves of Grass</em> [http://www.gutenberg.org/files/1322/1322-h/1322-h.htm]</blockquote>
<blockquote style="background:#eee;padding:3px;">"I am large, I contain multitudes." -- Walt Whitman, <em>Leaves of Grass</em> [http://www.gutenberg.org/files/1322/1322-h/1322-h.htm]</blockquote>


Line 6: Line 10:
Managing these different personas is easier in meatspace than online. In meatspace, there are more clues about how your information will be shared, most information will eventually be forgotten,  and information leakage is easier to track and contain. By contrast, intuiting the total amount of personal information shared online that can be inferred via a vast array of technologies (cookies, web bugs, search engines, user-supplied application data, log data) is difficult. Yet many users would like the convenience of chatting, posting, gaming, and otherwise participating in all their multiple identities or personas without the cognitive burden of preventing information leakage between them.
Managing these different personas is easier in meatspace than online. In meatspace, there are more clues about how your information will be shared, most information will eventually be forgotten,  and information leakage is easier to track and contain. By contrast, intuiting the total amount of personal information shared online that can be inferred via a vast array of technologies (cookies, web bugs, search engines, user-supplied application data, log data) is difficult. Yet many users would like the convenience of chatting, posting, gaming, and otherwise participating in all their multiple identities or personas without the cognitive burden of preventing information leakage between them.


Firefox already has several features that enable users to manage contextual identities. There is a profile manager that allows users to have multiple sets of cookies, bookmarks, addons, and anything else in local storage [http://mzl.la/LL5Dxl]. Unfortunately it's too much work for people [https://bugzilla.mozilla.org/show_bug.cgi?id=214675#c53]. There's also Private Browsing Mode [http://dl.acm.org/citation.cfm?id=1929828], which isn't quite right either.
Firefox already has several features that enable users to manage contextual identities. There is a profile manager that allows users to have multiple sets of cookies, bookmarks, addons, and anything else in local storage [http://mzl.la/LL5Dxl]. Unfortunately it's too much work for people [https://bugzilla.mozilla.org/show_bug.cgi?id=214675#c53]. There's also Private Browsing Mode [http://dl.acm.org/citation.cfm?id=1929828], which is a great first step but doesn't address the whole problem space.


We need to understand what people really want before we can create software to serve them.  It's not about how people can operate our software, but rather how the software can operate as people expect. A large problem with complex systems like the Web is that peoples' expectations of how their identity and data is treated do not match up to reality.   
We need to understand what people really want before we can create software to serve them.  It's not about how people can operate our software, but rather how the software can operate as people expect. A large problem with complex systems like the Web is that peoples' expectations of how their identity and data is treated do not match up to reality.   
Line 16: Line 20:
This project will take three phases and produce clearly thought out revisions to Firefox and perhaps the web platform and identity-related efforts at Mozilla.
This project will take three phases and produce clearly thought out revisions to Firefox and perhaps the web platform and identity-related efforts at Mozilla.


;Principal Investigator: Monica Chew
;Principal Investigator: Tanvi Vyas
;Additional Team Members: Sid Stamm


[[File:Contextual_identity_plan.png]]
[[File:Contextual_identity_plan.png]]
Line 27: Line 30:
Deliverables:
Deliverables:


; Relationship to Manifesto : This project is core to the values held by Mozilla.  
; Relationship to Manifesto : This project is core to the values held by Mozilla. The underlying goal of this project is for users to gain sovereignty over their personal information, first by enabling them to inspect their data holistically, then allowing them to curate it to fit the desired contextual identities.
; Hypothesis and Estimated Outcome : Problem statement, criteria for measuring results.
; Hypothesis and Estimated Outcome : Problem statement: We suspect there are already common techniques for managing contextual identities, but have not catalogued or quantified them. Criteria for success: Design and run user studies for quantifying these common techniques.
; Research plan : What kind of investigation is necessary and what resources are needed.
; Research plan : What kind of investigation is necessary and what resources are needed.


Line 35: Line 38:
Deliverables:
Deliverables:


; Catalog of Related Work : other work in this area.
; [[Security/Contextual_Identity_Project/Related_Work|Catalog of Related Work]] : other work in this area.
; User Research Papers : What we learn from studying our users.
; User Research Papers : What we learn from studying our users.
; Platform Work: [http://www.scitepress.org/digitalLibrary/PublicationsDetail.aspx?ID=UoE90ECay%2fQ%3d&t=1 Extending the Same Origin Policy With Origin Attributes]
; Design Requirements / Use Cases : things we need to make our products live up to users' expectations.
; Design Requirements / Use Cases : things we need to make our products live up to users' expectations.


== Phase III: Implementation ==
== Phase III: Implementation ==


Deliverables: (list is a work in progress)
Check out https://wiki.mozilla.org/Security/Contextual_Identity_Project/Containers for the latest!
 
<table class="querytable sortable">
<tr>
<td class="header" style="width: 5%;">Pr</td>
<td class="header" style="width: 30%;">Feature</td>
<td class="header" style="width: 15%;">Team</td>
<td class="header" style="width: 15%;">Stage</td>
<td class="header" style="width: 20%;">Directly Responsible Individual</td>
<td class="header" style="width: 15%;">Theme</td>
</tr>
{{#ask: [[Category:Feature Page]] [[Feature theme::Contextual Identity]] [[Feature roadmap::Privacy]]
| ?#
| ?Feature name#
| ?Feature priority#
| ?Feature engineering team#
| ?Feature stage#
| ?Feature feature manager#
| ?Feature theme#
| mainlabel=-
| sort=Feature priority,Feature stage
| format=template
| limit=500
| template=FeatureListTable
}}

Latest revision as of 22:01, 29 September 2017

Goal

Enable users to gain sovereignty over their personal data, whether it is deliberately shared, passively tracked, inferred, or otherwise aggregated.

Background

"I am large, I contain multitudes." -- Walt Whitman, Leaves of Grass [1]

Whitman was not speaking of multiple personality disorder, but rather of the human tendency to present different aspects of self to different people. For example, many people want to keep professional and personal lives separate, or at least want to maintain different types of relationships (and thus share different information) with acquantainces versus say, parents. This problem has surfaced many times over the years: Carl Jung called this persona theory [2], Erving Goffman called it impression management [3], and more recently Lucas Adamski called it contextual identity [4].

Managing these different personas is easier in meatspace than online. In meatspace, there are more clues about how your information will be shared, most information will eventually be forgotten, and information leakage is easier to track and contain. By contrast, intuiting the total amount of personal information shared online that can be inferred via a vast array of technologies (cookies, web bugs, search engines, user-supplied application data, log data) is difficult. Yet many users would like the convenience of chatting, posting, gaming, and otherwise participating in all their multiple identities or personas without the cognitive burden of preventing information leakage between them.

Firefox already has several features that enable users to manage contextual identities. There is a profile manager that allows users to have multiple sets of cookies, bookmarks, addons, and anything else in local storage [5]. Unfortunately it's too much work for people [6]. There's also Private Browsing Mode [7], which is a great first step but doesn't address the whole problem space.

We need to understand what people really want before we can create software to serve them. It's not about how people can operate our software, but rather how the software can operate as people expect. A large problem with complex systems like the Web is that peoples' expectations of how their identity and data is treated do not match up to reality.

This project aims to discover exactly what people expect and identify ways to help the browser close this gap between what they want and how the web works.

Plan

This project will take three phases and produce clearly thought out revisions to Firefox and perhaps the web platform and identity-related efforts at Mozilla.

Principal Investigator
Tanvi Vyas

Contextual identity plan.png

Phase I: Problem Definition

The Firefox Vision Statement says, "People seek to regain more control over their online lives and expect more nuanced and contextual relationships with other people, websites and applications -- to share what they want about themselves on their own terms."

Deliverables:

Relationship to Manifesto
This project is core to the values held by Mozilla. The underlying goal of this project is for users to gain sovereignty over their personal information, first by enabling them to inspect their data holistically, then allowing them to curate it to fit the desired contextual identities.
Hypothesis and Estimated Outcome
Problem statement: We suspect there are already common techniques for managing contextual identities, but have not catalogued or quantified them. Criteria for success: Design and run user studies for quantifying these common techniques.
Research plan
What kind of investigation is necessary and what resources are needed.

Phase II: Research and Study

Deliverables:

Catalog of Related Work
other work in this area.
User Research Papers
What we learn from studying our users.
Platform Work
Extending the Same Origin Policy With Origin Attributes
Design Requirements / Use Cases
things we need to make our products live up to users' expectations.

Phase III: Implementation

Check out https://wiki.mozilla.org/Security/Contextual_Identity_Project/Containers for the latest!