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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Safeguard Catalogue - Communications Remarks<br />

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

S 5.47 Configuration of a Closed User Group<br />

Initiation responsibility: <strong>IT</strong> Security Management, PBX officer<br />

Implementation responsibility: Administrators<br />

Integrated Services Digital Networks (ISDN) allow the configuration of<br />

Closed User Groups (CUG). Such groups are characterised by the fact that all<br />

the subscribers in a CUG can communicate with each other via the public<br />

ISDN network; however, requests by external subscribers for establishing<br />

links with CUG subscribers can be rejected, just as requests by CUG<br />

subscribers for establishing links with subscribers in the public ISDN network.<br />

Mode of operation:<br />

All communications partners here are members of a Closed User Group<br />

configured by the network operator (e.g. Deutsche Telekom AG).<br />

Authorisation to communicate is checked by the digital exchange of the<br />

communications partner via an interlock code which is uniquely assigned to<br />

the CUG. To start with, the calling communications partner sends a call<br />

request to the digital exchange assigned to him. <strong>The</strong> digital exchange appends<br />

to this call request the ISDN number of the calling partner as well as the<br />

unique interlock code of the related Closed User Group. <strong>The</strong> digital exchange<br />

of the called communications partner uses this interlock code to identify<br />

whether the call request can be accepted. If identification is positive, the call<br />

request is forwarded to the communications partner being called.<br />

<strong>The</strong> advantage of this function is that unauthorised attempts at access can be<br />

rejected already by the digital exchange of the network operator, so that they<br />

do not reach the gateways of the communications partner.<br />

A disadvantage of this function is that changes in the membership of a CUG<br />

always need to be reported to the network operator, as only this party is<br />

capable of making the required modifications to the authorisation parameters.<br />

This also means that the network operator is in full control of the membership<br />

profile of a CUG and any changes made by the operator cannot necessarily be<br />

monitored by the users of a CUG. Furthermore, the configuration and<br />

operation of a CUG by a network operator generates one-time as well as<br />

running costs.<br />

<strong>The</strong> configuration of a Closed User Group by the operator of a public network<br />

is advisable wherever<br />

- Hardware and software for other processes (e.g. S 5.48 Authentication via<br />

CLIP/COLP) first need to be procured<br />

- <strong>The</strong> membership of a CUG rarely changes<br />

- <strong>The</strong> network operator is sufficiently trustworthy<br />

Additional controls:<br />

- Is clear and comprehensive documentation available on CUGs which have<br />

been configured? Is this documentation up-to-date?<br />

- Are regular checks made as to whether the CUG function - which usually<br />

costs money - is still required?<br />

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

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

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

Saved successfully!

Ooh no, something went wrong!