Personal tools
You are here: Home Software Center do2gether PG Draft Features Security & Privacy Options
Document Actions

#22: Security & Privacy Options

Contents
  1. Definitions
  2. Motivation
  3. Assumptions
  4. Proposal
  5. Implementation
  6. Deliverables
  7. Risks
  8. Progress log
  9. Participants
Set of security & privacy user options.
Proposed by
TFF
Proposal type
Security/Privacy
State
being-discussed

Definitions

!!! - a "must have" feature

!! - a requested feature

! - a less desired feature

? - desired feature, but can be discussed for smaller changes

?? - a feature open for discussion

??? - a feature fully open for discussion in behaviour, ui, architecture...

CF - Criticality Factor. It is the multiplier number for each feature, to be used when calculating penalties on deliverables, in case of bugs or delivery missing. The higher, the most critical the feature is.

Motivation

 

Assumptions


Proposal

  • system runs permanently security checks against common attacks (DDoS, code injection, ajax security…) - !! CF 2   
  • Group owner can set custom security settings levels to enable a high-security group. Each of these settings affect: identification/authentication/privacy and its related cost ($). A graphic gauge bar shows messages from "No security" to "007 security" according to the configuration chosen - ??? CF 2
    • Options for login include: plain web authentication, HTTPS or combined code-card PIN;
    • For signup of a new member: phone confirmation (normal or with caller ID ON), fax confirmation.

Implementation


Deliverables


Risks


Progress log


Participants



Powered by Plone CMS, the Open Source Content Management System

This site conforms to the following standards: