Symbian OS Platform Security/07. Sharing Data Safely - Revision history

Craig: removed category, added copyright template

2011-01-17T11:53:16Z

removed category, added copyright template

Craig: chapter author, navigation links, formatting

2011-01-06T17:50:51Z

chapter author, navigation links, formatting

Show changes

Admin: 12 revisions: import from developer.symbian.org

2010-12-18T16:03:45Z

12 revisions: import from developer.symbian.org

Stichbury: moved Symbian OS Platform Security/7. Sharing Data Safely to Symbian OS Platform Security/07. Sharing Data Safely

2010-03-24T11:51:54Z

moved Symbian OS Platform Security/7. Sharing Data Safely to Symbian OS Platform Security/07. Sharing Data Safely

Hamishwillee: moved Chapter 7: Sharing Data Safely to Symbian OS Platform Security/7. Sharing Data Safely: move to sub page model

2010-03-17T22:23:12Z

moved Chapter 7: Sharing Data Safely to Symbian OS Platform Security/7. Sharing Data Safely: move to sub page model

Satudahl: /* Services Summary */

2010-03-16T12:12:04Z

‎Services Summary

Satudahl: /* Tampering */

2010-03-16T12:10:08Z

‎Tampering

Satudahl: /* Tampering */

2010-03-16T12:09:27Z

‎Tampering

Satudahl at 12:08, 16 March 2010

2010-03-16T12:08:01Z

Satudahl at 11:58, 16 March 2010

2010-03-16T11:58:37Z

Show changes

← Older revision		Revision as of 11:53, 17 January 2011
Line 1,049:		Line 1,049:
	mediated access to your data for trusted clients is paramount.		mediated access to your data for trusted clients is paramount.

−	~~[[Category:Book]]~~	+	{{SymbianOSPlatformSecurity_Copyright}}

@@ Line 992: / Line 992: @@
 {| Border="1"
 |-
 ! Characteristic/Service !! Persistency !! Volatility !! Size !! Exchange

@@ Line 362: / Line 362: @@
 '''Best practices'''
-#Make your process fault tolerant – that is, resistant to corrupted or unexpected data. Create a recovery strategy for all the situations you have identified in your threat model. This may be as simple as resetting the data back to a ‘default’ configuration for corrupted backup data. Choose a resilience strategy that is both simple and effective for your process, and also right for the type of data in question. If you are implementing a media player, you are likely to be accepting data from off the mobile phone (OTA or removable
+#Make your process fault tolerant – that is, resistant to corrupted or unexpected data. Create a recovery strategy for all the situations you have identified in your threat model. This may be as simple as resetting the data back to a ‘default’ configuration for corrupted backup data. Choose a resilience strategy that is both simple and effective for your process, and also right for the type of data in question. If you are implementing a media player, you are likely to be accepting data from off the mobile phone (OTA or removable media). If such a file were corrupt you would simply not play it.
 media). If such a file were corrupt you would simply not play it.
 #You may refuse unsolicited data but instead only use data that has been installed through the Software Install process. You can do this by not implementing support for a \import directory in your private data cage – see Chapter 8 for more information on import directories.
 #Return errors to clients of your data in a timely fashion, but make sure that a client can process the error. For example, you must not return an error for a method such as CancelTransaction().

@@ Line 349: / Line 349: @@
 *It may cause the user to unwittingly spend money – for example, by altering a phone number to a premium rate one.
 *It may lead to data capture, if connection information is altered.
-*Data on removable media is at high risk from this kind of attack – as we have already noted, this is out of our control when the media is
+*Data on removable media is at high risk from this kind of attack – as we have already noted, this is out of our control when the media is removed from the mobile phone.
 removed from the mobile phone.
 *Some attacks of this kind are specific to server processes that allow concurrency of access. These occur when inconsistent updates are performed on dependent compound data. There is a risk of being left in an unknown state unless atomic updates are executed.

@@ Line 992: / Line 992: @@
 the data.
 Characteristic Persistency Volatility Size Exchange
-Service
+{| Border="1"
-Publish and
+|+ '''Table 1:''' Your table heading
-subscribe
+|-
-Transient Any Prefer <512
+! Characteristic/Service !! Persistency !! Volatility !! Size !! Exchange
-bytes
+|-
-Asynchronous
+|Publish and subscribe || Transient|| Any|| Prefer <512 bytes|| Asynchronous
-Central
+|-
-repository
+| Central repository || Persistent|| Non-volatile|| <2 KB|| Asynchronous
-Persistent Non-volatile <2 KB Asynchronous
+|-
-DBMS Persistent Non-volatile Any Asynchronous
+| DBMS|| Persistent || Non-volatile|| Any|| Asynchronous
-File handles Transient Non-volatile Any Synchronous
+|-
-Custom server Any Any Any Synchronous
+| File handles||  Persistent|| Non-volatile|| Any|| synchronous
 =Summary=

← Older revision	Revision as of 16:03, 18 December 2010
(No difference)

← Older revision	Revision as of 11:51, 24 March 2010
(No difference)

← Older revision	Revision as of 22:23, 17 March 2010
(No difference)