03.12.2012 Views

Security - Telenor

Security - Telenor

Security - Telenor

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

The AAA systems supporting scalable Internet<br />

mobility are currently under development by the<br />

IETF. Radius and Tacacs, the commonly used<br />

AAA systems today, have major shortcomings<br />

with respect to support for roaming and mobility.<br />

The IETF is currently investigating<br />

the requirements and working on the solutions<br />

needed to support the future mobility services<br />

expected to be offered on a future mobile Internet.<br />

A PKI would be an ideal platform to build these<br />

AAA systems upon. Having a PKI available<br />

would enable easier mechanisms for trust across<br />

different security domains, allowing simpler<br />

roaming between different operators.<br />

Use of Hardware Tokens<br />

The SIM card (smartcard) in the GSM system<br />

has turned out to be a successful way of achieving<br />

secure user mobility.<br />

Using a relatively tamperproof secure storage<br />

and processing device as a smartcard, access<br />

control on the terminal may be enforced in a<br />

secure manner. In particular, storing and using<br />

private keys used in a Public Key Infrastructure<br />

on smartcards currently offers the best combination<br />

of user mobility and security available.<br />

Integrating the<br />

<strong>Security</strong> Technologies<br />

Each of the selected security technologies<br />

described in the previous section is important in<br />

order to protect the mobile users of the future.<br />

However, the security technologies described<br />

need all to be co-ordinated according to a<br />

defined security policy. This policy should be<br />

defined and managed by the security organisation<br />

on the corporate network for professional<br />

users, and maybe as a service for its customers<br />

from the ISP perspective.<br />

Take the professional corporate and mobile user<br />

on the Internet as a scenario. Let us say she has<br />

arrived in the UK on a business trip, having left<br />

<strong>Telenor</strong> R&D at Kjeller earlier the same day.<br />

Having arrived at the hotel in London, she<br />

decides to connect to the Internet using the<br />

offered WLAN connection at the hotel. Once<br />

connected, she establishes a VPN connection<br />

back to <strong>Telenor</strong> R&D to read the latest mail<br />

using a combination of Mobile IP and IPsec<br />

together with her smartcard for authentication<br />

purposes. However, the security policy requires<br />

several security services to be established before<br />

the home network accepts the VPN connection.<br />

A local firewall has to be configured properly, a<br />

virus scan has to be performed, the integrity of<br />

important files and system aspects need to be<br />

verified, important security logs need to be<br />

audited, etc.<br />

Telektronikk 3.2000<br />

The results of all these checks and configurations<br />

need to be securely reported to the home<br />

network before access is granted to internal<br />

resources at the corporate network. This is actually<br />

required if the home network is supposed to<br />

trust that the mobile terminal has not been compromised.<br />

Using the currently deployed state-ofthe-art<br />

security technology, users establish a<br />

secure VPN channel back to the corporate network<br />

based on proper authentication only, leaving<br />

the mobile terminal to be hacked by anyone<br />

without the home network ever finding out.<br />

The challenge is however to enforce the required<br />

policy, e.g. automatically configuring and checking<br />

the mobile terminal as presented above.<br />

A proper security policy may e.g. include:<br />

• What security services are needed;<br />

• The right order to enable the different security<br />

services;<br />

• How to configure the different security services;<br />

• How to verify that all services and checks<br />

have been performed successfully;<br />

• What to do if some services and/or security<br />

checks fail;<br />

• What to do if attempts to compromise the current<br />

policy is discovered once the policy has<br />

been successfully established;<br />

• How to inform the right entity on the corporate<br />

network about the attempt to compromise<br />

the current policy.<br />

Different users may have different security policies<br />

defined, according to e.g. the type of services<br />

the user is authorised to access. For each<br />

user, there may also be different security policies<br />

defined reflecting the current network access.<br />

Three examples of different scenarios include<br />

one for using dial-up connections to the corporate<br />

network, a second one to be enforced when<br />

connecting directly to the Internet and a third<br />

one to be enforced if being on a physically<br />

secured corporate network.<br />

The different security policies and its “enforcement<br />

software” need to be secured as well, making<br />

sure any attempts on modification is detected<br />

and properly handled according to the defined<br />

security policy.<br />

31

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!