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 5.91 Disabling of RAS access security mechanisms<br />

<strong>The</strong> security of RAS access depends significantly on correct use of the<br />

security mechanisms provided. However, it is generally possible to configure<br />

the RAS system (client and/or server) in such away that either weak or no<br />

security mechanisms are used. If, for example, the mechanisms used for data<br />

encryption are dynamically negotiated between client and server when a<br />

connection is established (e.g. this can occur if IPSec or SSL is used),<br />

generally this negotiation process entails the client offering the server a list of<br />

procedures supported (known as cipher suites) for selection, from which the<br />

server chooses one. <strong>The</strong> list of algorithms can be altered by making the<br />

appropriate configuration changes. Usually there is also a "no encryption"<br />

option.<br />

If an unencrypted connection is one of the options allowed between clients<br />

and server, then there is a risk that protection of the data transmitted will be<br />

disabled. This is particularly problematic where users are able in the event of<br />

problems to modify the RAS system configuration settings on RAS clients to<br />

fit local circumstances.<br />

Examples<br />

- RAS communications are to be protected by means of IPSec running under<br />

Windows 2000. <strong>The</strong> RAS server has been configured so that IPSec<br />

encryption is requested but is not enforced, so that RAS clients can<br />

potentially also establish insecure connections. As the loss of performance<br />

associated with encryption appears unacceptable to a RAS user who is<br />

working with an older laptop, he disables IPSec encryption. <strong>The</strong> RAS<br />

connection is now established in plaintext.<br />

- Under older Windows NT versions, encryption of the RAS connection<br />

using Microsoft Point to Point Encryption (MPPE) can only be performed<br />

if MS-CHAP has been specified as the authentication procedure.<br />

Consequently only if MS-CHAP is used are the parameters which are<br />

necessary for encryption exchanged between client and server. In order to<br />

use a standard authentication procedure, a user selects the CHAP procedure<br />

in the configuration settings. Encryption of the RAS connection is no<br />

longer possible using MPPE even though the appropriate option is enabled.<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!