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.

Threats Catalogue Deliberate Acts Remarks<br />

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

T 3.39 Improper administration of the RAS system<br />

Improper administration of RAS components constitutes a potential risk which<br />

should not be overlooked. Once they get to a certain size and structure, RAS<br />

systems are complex systems which only trained system administrators can<br />

configure correctly and securely. Administrative errors generally have a<br />

pronounced effect on the stability and security as an administrator possesses<br />

privileged rights in the system. Some of the problems which can occur with<br />

RAS systems are set out below.<br />

- Security-relevant routine tasks on the RAS client are frequently neglected.<br />

<strong>The</strong>se include, for example, regular data backups or scanning for computer<br />

viruses. In particular, mobile RAS clients are taken around by their users<br />

and are therefore only seldom available to system administration staff.<br />

While it is possible for remote administration to be performed during an<br />

established RAS session, depending on usage profile, connection times<br />

may be too short to carry out systematic remote maintenance. But if the<br />

regular administrative tasks are not performed, different clients may have<br />

different configurations.<br />

- Remote administration of computers can be performed with the aid of<br />

commonly used software products and is often possible simply using<br />

mechanisms provided by the operating system. <strong>The</strong> use of unauthorised<br />

software (by the user or the administrator), often means that either nonpermitted<br />

protocols are used over a RAS connection or that settings are<br />

made which do not comply with the security guidelines in force and can<br />

therefore open up security loopholes.<br />

- If computer virus checking is performed exclusively on the server,<br />

encryption of data client-side can be a problem. Many application<br />

protocols can be processed over RAS connections so that transport of email,<br />

Web content or files is possible. Encrypted data can in this case no<br />

longer be checked for viruses using anti-virus software installed on the<br />

server.<br />

- <strong>The</strong>re is no anti-virus software installed on the RAS client or such software<br />

is out of date or disabled. As RAS clients are frequently operated in<br />

insecure environments with the result, for example, that the exchange of<br />

data media is in practice uncontrolled, computer viruses constitute a<br />

particularly serious threat. In particular, the danger exists that computer<br />

viruses or Trojan horses can find their way into the LAN through the RAS<br />

client.<br />

- If functions which place heavy demands on bandwidth are performed over<br />

RAS connections, then there is a danger that the user will terminate a RAS<br />

session and start another one because he believes there is a fault on the<br />

line. But in reality it is simply a case of the response time being<br />

unacceptably slow because the bandwidth is inadequate. This can not only<br />

result in inconsistencies in the application data due to unexpected<br />

termination of a connection, but repeated attempts by users to establish a<br />

connection followed by termination of the connection can also increase the<br />

loading on the RAS system.<br />

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

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

Neglect of securityrelevant<br />

routine tasks<br />

Unauthorised use of<br />

software for remote<br />

administration<br />

Encryption and virus<br />

protection<br />

Inadequate virus<br />

protection on RAS<br />

clients<br />

Long response times<br />

due to insufficient<br />

bandwidth

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

Saved successfully!

Ooh no, something went wrong!