diff -r 43e37759235e -r 51a74ef9ed63 Symbian3/SDK/Source/GUID-39A995DC-F047-4B41-A60D-27063CE329BE.dita --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/Symbian3/SDK/Source/GUID-39A995DC-F047-4B41-A60D-27063CE329BE.dita Wed Mar 31 11:11:55 2010 +0100 @@ -0,0 +1,77 @@ + + + + + +Planning +system and software security +

Devices based on the Symbian platform are capable of joining both public +and private networks and often have the functionality of a normal desktop +computer. However, the average user does not perceive the device as a computer, +but rather as a regular phone that is safe from security threats. This creates +an opportunity for hostile attackers to infiltrate the device and wreak severe +direct or indirect damage (for example, by penetrating into the corporate +intranet).

+

It is, however, possible to anticipate these kinds of threats, and protect +applications by using the security features offered by the Symbian platform, +and by expanding security policies to cover mobile devices and services.

+

To develop system or software security, repeat the following steps:

+
    +
  1. Define and +evaluate all critical assets (resources, information).

  2. +
  3. Identify all +possible threats, vulnerabilities, and potential attacks, and estimate the +extent of possible damage.

    Areas to examine in the Symbian platform +are system resources, removable media, and communication between components.

    +
  4. +
  5. Prioritize +high-risk vulnerabilities, and select and implement corresponding security +features. If risks are sufficiently low, protective measures may be unnecessary.

    +
  6. +
  7. Repeat these +steps until the necessary level of protection is achieved.

  8. +
+

+Security development process +

The security development process is guided by cost, efficiency, and usability. +If security is too tight, this may be expensive and affect both performance +and the user's experience of the system or software. On the other hand, if +security is too slack, this may result in severe damage and, in the long run, +be even more costly.

+
Security methods +

The list below contains the most common and important security methods +used in the mobile world:

+
    +
  • Ciphering enables confidentiality. Information is +accessible only by authorized parties. With ciphering it is also possible +to maintain integrity.

  • +
  • Hash function (checksum) can be used to verify +integrity and detect information tampering.

  • +
  • Signing allows attaching of information to a certain +source.

  • +
  • Authentication ensures that the object is what it +claims to be.

  • +
  • Access control restricts unauthorized access to resources.

    +
  • +
  • Authorization is permission to perform tasks on behalf +of somebody else.

  • +
  • Certification is provided usually by a third party +to prove information validity.

  • +
  • Recovery mechanisms are usually implemented as redundancy +(duplication of information or routes).

  • +
  • In communication it is possible to use, for example, error +correction to repair transmission failures, random traffic generation to +keep the line occupied, and packet uniforming to blend important packets +into traffic.

  • +
+

Some of the methods above are interconnected (for example, certification +requires that the information is signed) and not all of them are of equal +importance, since some basic methods form a base for more complicated methods.

+
+
\ No newline at end of file