19.12.2012 Views

IT Baseline Protection Manual - The Information Warfare Site

IT Baseline Protection Manual - The Information Warfare Site

IT Baseline Protection Manual - The Information Warfare Site

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.

Safeguard Catalogue - Organisation Remarks<br />

____________________________________________________________________ .........................................<br />

Where <strong>IT</strong> systems are used to process sensitive data or are connected to a<br />

computer network, no mobile phone cards should be permitted (see also<br />

S 5.81 Secure transmission of data over mobile phones).<br />

<strong>The</strong>re is no foolproof way of protecting against the unauthorised transmission<br />

of data over mobile phones, especially by insiders. However, taking mobile<br />

phones into sensitive areas should be forbidden and checks should be made at<br />

regular intervals to ensure that this ban is being adhered to.<br />

Telephone directories<br />

Call numbers and the associated names and/or additional details can be stored<br />

in the telephone directory of a mobile phone. Telephone directories can be<br />

stored on the terminal device, i.e. on the mobile phone or SIM card. <strong>The</strong>y do<br />

not have to have the same content. PINs can be used to restrict access to a<br />

given telephone directory in the memory of the terminal device and/or of the<br />

SIM card.<br />

Whether it is best to hold telephone numbers in the mobile terminal or on the<br />

SIM card will depend on various factors, for example how easy it is to back up<br />

the data to other media (see S 6.72 Precautions relating to mobile phone<br />

failures). Generally it is recommended that the data is stored on the SIM card,<br />

since<br />

- if the SIM card is replaced, the data can be made available on other devices<br />

and<br />

- any sensitive data can be easily cleared from the device (this is important,<br />

for example, where repair work is necessary or a change of user occurs).<br />

If possible, only one type of storage should be chosen. All important call<br />

numbers should be stored in this telephone directory to ensure that they are<br />

available at all times. <strong>The</strong> stored call numbers should be checked from time to<br />

time to ensure that they are still correct and are necessary. All call numbers<br />

should be stored in such a way that they can be called from anywhere in the<br />

world, i.e. including the country and area codes. Since only the country code<br />

is internationally agreed, and not the zero, every call number should be<br />

entered with a "+" at the beginning, followed by the country code (e.g. +49 for<br />

Germany), area code without leading zero and then the actual phone number.<br />

For example, a possible entry might be +492289582369 GS hotline.<br />

If the mobile phone is used by several users, only phone numbers which are<br />

shared should be stored here. In addition, any facilities allowing the<br />

prevention of changes to the telephone directory via the existing blocking<br />

mechanisms should be used.<br />

Use of answerphone functionality<br />

Most network providers offer a service allowing an answerphone function on<br />

a mobile phone. Under such arrangements, incoming calls are stored at the<br />

network provider's in a mailbox or mobile box which can be retrieved by the<br />

user at any time. This can be very useful, but generally use of the service<br />

incurs additional costs.<br />

____________________________________________________________________ .........................................<br />

<strong>IT</strong>-<strong>Baseline</strong> <strong>Protection</strong> <strong>Manual</strong>: Oktober 2000<br />

<strong>Protection</strong> against<br />

transfer of data over<br />

mobile phones

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

Saved successfully!

Ooh no, something went wrong!