Please note that as of October 24, 2014, the Nokia Developer Wiki will no longer be accepting user contributions, including new entries, edits and comments, as we begin transitioning to our new home, in the Windows Phone Development Wiki. We plan to move over the majority of the existing entries. Thanks for all your past and future contributions.

Platform Security

From Wiki
Jump to: navigation, search
Article Metadata
Created: sellis (20 Feb 2007)
Last edited: hamishwillee (25 Jul 2012)



Symbian platform security was introduced in S60 3rd Edition with the implementation of Symbian OS V9 as the S60 platform's underlying operating system. Platform security enhances the existing security features of Symbian to deliver a more secure platform for mobile devices. This secure platform offers device users greater assurance about the security of their devices and the data they hold.

Platform security offers developers a larger, more confident base of mobile consumers, who are more willing to install applications. This page provides links to key resources that will help developers to embrace this new technology and answers to the most frequently asked questions about platform security. Security in general can be considered as one of the key aspects in quality application.


Platform security was designed to make the security impact of architectural decisions visible. Architecturally, software components can be divided to groups where the components trust each other to behave well. Boundaries between these groups are termed security boundaries.

In practice, this means that if a software component wants to run code from a shared library, it effectively brings that code within its own security boundary, and must therefore trust that code. In addition, when supplying services to a component outside its own security boundary, the component must do certain checks to see whether the other component is entitled to such services.

Both of these actions (making a trust decision for shared code, and checking permissions of a calling component) are facilitated through the use of capabilities.

The need for capabilities can be used as an architectural tool: the amount of capabilities required from a component reflects the trust that is placed on it. If the amount of capabilities seems excessive, this can be construed as a hint that security boundaries may be too large.


Trusted computing base

The trusted computing base is a collection of software that enforces capabilities and Data caging. It contains the kernel, the file system, and the software installer. This is the controlling part of the operating system for the platform security model.

See also


This page was last modified on 25 July 2012, at 06:37.
118 page views in the last 30 days.