Personal Data Vault
From UrbanWiki
Contents |
[edit] Documentation
[edit] Introduction
[edit] What is PDV
For our immediate purposes, the data vault is a secure repository for time-location traces that allows controlled access to services authorized by the user, and provides for auditing, etc.
[edit] What PDV functions
- Store data securely
- Establish identities
- Authenticate for user and service provider
- Selective upload
- Filter in data based on policies set by designer and user
- Selective sharing
- Filter out data based on policies set by user
- Export minimum data based on sufficient statistics needed by the Derived data provider and Consumer
- Audit trace
- Log where, when and how data is used
- Only user can query the log
[edit] System Overview
PDV consists of three authorites basically
- Data Authority
- Identity Authority
- Audit Authority
[edit] Use Case Analysis
- The goal of use-case analysis is to take our understanding of the requirements in the system’s use cases and iteratively transform those requirements into representations that support the business concepts. In this stage, our description addresses only the WHAT not the HOW of PDV, trying to capture the operational requirements.
[edit] API Design by Kenny
[edit] API Design by Min
[edit] Use Case Design
[edit] Example use-case/user-interaction
- the private data vault is a storage container with encrypted data to and from which the owner of the data sets up filtered transfers.
- for example, assume that the input is relatively simple--a set of one or more encrypted personal data streams that can be generated from multiple inputs from the individual's phone, car, and other devices eventually. eventually we will also consider that you can pipe processed/derived streams back into the vault as well.
- the user might sign up for services and set up session keys that would last for a specified period of time with a relatively painless but still visible mechanism for renewal so that stopping/revocation is easy.
- the user would then receive audit logs on a regular basis confirming the existing active transfer sessions, what is being exported (what filter is being applied), and when the session agreement expires. as an analogy consider setting things up the way online transfers/electronic payments from a private bank account are managed.
