×
Namespaces

Variants
Actions
(Difference between revisions)

User-data security design guidelines

From Nokia Developer Wiki
Jump to: navigation, search
Rahulsingh1m (Talk | contribs)
(New page: Category:Mobile_DesignCategory:Usability == A checklist for user data security == * Users data like images, videos, messages, contacts should not be altered without their permis...)
 
hamishwillee (Talk | contribs)
m (Text replace - "Category:Mobile Design" to "")
 
(10 intermediate revisions by 5 users not shown)
Line 1: Line 1:
[[Category:Mobile_Design]][[Category:Usability]]
+
[[Category:Usability]][[Category:Security]]
 +
{{Abstract|User data security is the practice of keeping user data protected from corruption and unauthorized access. Thus helping to ensure privacy. Applications should give high priority to user data and should not modify, delete or broadcast it. }}
  
 +
{{ArticleMetaData <!-- v1.2 -->
 +
|sourcecode= <!-- Link to example source code e.g. [[Media:The Code Example ZIP.zip]] -->
 +
|installfile= <!-- Link to installation file (e.g. [[Media:The Installation File.sis]]) -->
 +
|devices= <!-- Devices tested against - e.g. ''devices=Nokia 6131 NFC, Nokia C7-00'') -->
 +
|sdk= <!-- SDK(s) built and tested against (e.g. [http://linktosdkdownload/ Qt SDK 1.1.4]) -->
 +
|platform= <!-- Compatible platforms - e.g. Symbian^1 and later, Qt 4.6 and later -->
 +
|devicecompatability= <!-- Compatible devices e.g.: All* (must have internal GPS) -->
 +
|dependencies= <!-- Any other/external dependencies e.g.: Google Maps Api v1.0 -->
 +
|signing= <!-- Signing requirements - empty or one of: Self-Signed, DevCert, Manufacturer -->
 +
|capabilities= <!-- Capabilities required by the article/code example (e.g. Location, NetworkServices. -->
 +
|keywords= <!-- APIs, classes and methods (e.g. QSystemScreenSaver, QList, CBase -->
 +
|language= <!-- Language category code for non-English topics - e.g. Lang-Chinese -->
 +
|translated-by= <!-- [[User:XXXX]] -->
 +
|translated-from-title= <!-- Title only -->
 +
|translated-from-id= <!-- Id of translated revision -->
 +
|review-by= <!-- After re-review: [[User:username]] -->
 +
|review-timestamp= <!-- After re-review: YYYYMMDD -->
 +
|update-by= <!-- After significant update: [[User:username]]-->
 +
|update-timestamp= <!-- After significant update: YYYYMMDD -->
 +
|creationdate= 20090626
 +
|author= [[User:Rahulsingh1m]]
 +
}}
  
== A checklist for user data security ==
+
=== A checklist for user data security ===
  
 
* Users data like images, videos, messages, contacts should not be altered without their permission.
 
* Users data like images, videos, messages, contacts should not be altered without their permission.
 
 
* Access point information should not be modified without informing user.
 
* Access point information should not be modified without informing user.
 +
* For using GPRS, user confirmation should be taken.
 +
* Sending background SMS should be discouraged.
 +
* Secure information like Password should be encrypted.
 +
* Users should be given permission to delete their private data.
 +
* Users should be encouraged to take backup of their private data.
 +
* Application's sensitive data should be created in the private folder of the application, so that it is not accessible to other applications.
 +
* While sending data to the web, it would be pertinent to notify the user of the vulnerability of the data in case there exists one.
 +
* While deleting any data through the UI always display a confirmation dialog to the user to avoid inadvertant delete of data.
 +
* Allow some kind of backup/restore mechanism for application which contains lot of sensitive user data.
  
* For using GPRS, user permission should be taken.
+
===Some Technical Mechanism To Protect User Data===
 +
====Encryption====
 +
This security mechanism uses mathematical schemes and algorithms to scramble data into unreadable text. It can only by decoded or decrypted by the party that possesses the associated key.
  
* Sending background SMS should be discouraged.
+
====Strong User Authentication ====
 +
Authentication is another effective part of data security.The single sign-on scheme is also implemented into strong user authentication systems.
  
* Secure information like Password should be encrypted.
+
====Backup Solutions====
 
+
Data security wouldn't be complete without a solution to backup user critical information.
* Users should be given permission to delete their private data.
+

Latest revision as of 06:42, 9 May 2012

User data security is the practice of keeping user data protected from corruption and unauthorized access. Thus helping to ensure privacy. Applications should give high priority to user data and should not modify, delete or broadcast it.

Article Metadata
Article
Created: User:Rahulsingh1m (26 Jun 2009)
Last edited: hamishwillee (09 May 2012)

Contents

[edit] A checklist for user data security

  • Users data like images, videos, messages, contacts should not be altered without their permission.
  • Access point information should not be modified without informing user.
  • For using GPRS, user confirmation should be taken.
  • Sending background SMS should be discouraged.
  • Secure information like Password should be encrypted.
  • Users should be given permission to delete their private data.
  • Users should be encouraged to take backup of their private data.
  • Application's sensitive data should be created in the private folder of the application, so that it is not accessible to other applications.
  • While sending data to the web, it would be pertinent to notify the user of the vulnerability of the data in case there exists one.
  • While deleting any data through the UI always display a confirmation dialog to the user to avoid inadvertant delete of data.
  • Allow some kind of backup/restore mechanism for application which contains lot of sensitive user data.

[edit] Some Technical Mechanism To Protect User Data

[edit] Encryption

This security mechanism uses mathematical schemes and algorithms to scramble data into unreadable text. It can only by decoded or decrypted by the party that possesses the associated key.

[edit] Strong User Authentication

Authentication is another effective part of data security.The single sign-on scheme is also implemented into strong user authentication systems.

[edit] Backup Solutions

Data security wouldn't be complete without a solution to backup user critical information.

This page was last modified on 9 May 2012, at 06:42.
240 page views in the last 30 days.

Was this page helpful?

Your feedback about this content is important. Let us know what you think.

 

Thank you!

We appreciate your feedback.

×