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 over the next few weeks. Thanks for all your past and future contributions.
Symbian Platform Security Model
There are three main modules in the Symbian Security Model:
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.
Data caging means that the applications and the users have access only to certain areas of the file system. In practice the applications can access their own private directories and directories that are marked as open. It means, for example, that one application cannot access another application’s private directory and data.
The access is restricted as follows:
Location for application icons, bitmaps, etc. Writing allowed only at application installation. Everyone can read the folder.
Location for binaries, including application installation registry and root certificates. Writing allowed only at application installation. Reading allowed to backup the application.
This is a private playground for each application. Reading and writing is only allowed to the application's own directory. Backup software has read and write access to this directory.
\all the rest
Access to all the other folders is free for all, for example, user’s own photos, music, and documents.
A capability grants access to a set of APIs and can be obtained through certification, for example Symbian Signed. The capabilities can be divided into four:
Open to all
- APIs in this category enable development of all the basic applications, for example, most of the single-player games.
- Generally speaking, about 60 percent of the APIs are freely available without any capability requirement.
Granted by the user at installation time
- Some capabilities can be granted by the user at the application installation phase.
- The application will have the capability until the application is removed from the device.
- This option may not be active in some devices by default. Thus the user has to activate the installation time capability granting separately.
Granted through Symbian Signed
- Some capabilities are available after passing Symbian Signed testing.
- More sensitive capabilities require declarative justification why the application needs access to such a capability. Passing the testing is required as well.
- The most sensitive capabilities require the developer to fill in the Capability Request Form and acceptance from the platform manufacturer. Passing the testing is required as well.
Granted by the manufacturer
- Submit your request via the Symbian Signed site, as above, but select Nokia as the device manufacturer. Manufacturer approval is needed if your request contains AllFiles, DRM, or TCB - or if you list more than 1000 IMEIs in your request.
- Symbian Signed for Nokia
- Developer certificate
- How to pass Symbian Signed for Nokia tests
- Application Signing
- Freeware signing
- Data caging