Ericsson R320s White Paper page 14

Hide thumbs Also See for R320s:
Table of Contents

Advertisement

S S S S e e e e c c c c u u u u r r r r i i i i t t t t y y y y i i i i s s s s s s s s u u u u e e e e s s s s
The Ericsson R320s is based on the WAP 1.1 speciÞcations where security functionality is spe-
ciÞed (WTLS). However, the security part that is speciÞed in WAP 1.1 does not support a com-
plete standardized security solution. A secure WAP application will require proprietary
solutions, until a speciÞcation supporting full security is available. This diagram shows a simp-
liÞed example of the security that can be implemented within the current speciÞcation.
Figure 2. Example showing the limitations of the security implementation.
¥
The WTLS speciÞcation supports security between the wireless equipment and, for
example, the WAP Gateway.
¥
The speciÞcation does not support security beyond the Gateway as shown in the diagram
above. This means, for example, that WAP applications accessed on the Internet cannot
provide privacy, including data integrity and authentication, to the wireless equipment. The-
refore, the security part of the WAP 1.1 speciÞcation is not implemented in the WAP brow-
ser in Ericsson R320s.
¥
To provide a secure solution, for example a banking service, the Service Provider can design
a WAP application with its own WAP Gateway. Each user has their own username and pass-
word in the bankÕs WAP Gateway, which increases the security of the service. This can be
regarded in analogy to the solution provided by a Óphone bankingÓ service, but with WAP
functionality. An implementation of security with this method is supported by Ericsson
R320s.
14
GATEWAY
GATEWAY

Advertisement

Table of Contents
loading

Table of Contents