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 - Hardware & Software Remarks<br />

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

consideration before using these clients, though. For example, Netscape<br />

Communicator is not able to grant access to LDAP servers which require a<br />

user name and a password. LDAP Services for NDS therefore recognises a<br />

user who uses this browser as a client as an anonymous user, and by default<br />

makes him a trustee of [Public], which typically comprises only a browse right<br />

for NDS. If additional rights are required, a proxy user must be set up who has<br />

the corresponding NDS rights. As well as this, the proxy user feature must<br />

also be enabled in the LDAP group object.<br />

As LDAP Services for NDS is fully integrated into NDS, an extension of the<br />

NDS scheme must be set up at the time of installation. This can only be done<br />

via an account with supervisor rights for the [Root] object. During installation<br />

of the first LDAP server in an NDS tree, the database scheme of NDS is<br />

extended so as to make two new NDS objects LDAP Server and LDAP Group<br />

available. LDAP Services for NDS is configured with the aid of these two<br />

objects. If additional LDAP servers are installed in this NDS tree, it is not<br />

necessary to install the scheme extension again because NDS already has the<br />

current database scheme.<br />

<strong>The</strong> configuration of LDAP Services for NDS is stipulated in the properties of<br />

the two objects, LDAP Server and LDAP Group. <strong>The</strong> settings must be made in<br />

accordance with the security strategy that has been devised. Some of the<br />

properties that are particularly relevant to the security of the system are<br />

examined below.<br />

Log file size limit (LDAP Server object)<br />

This property can be used to set the maximum size of the log file specified in<br />

the Log filename property. When the log file reaches the size specified here,<br />

the information in the Log filename file is copied to the file specified under<br />

Backup log file. All new log data is written to the Log filename file.<br />

Default: 1.000.000<br />

Minimum: 0 (unlimited file size)<br />

Maximum: 4.294.967.295<br />

If the size is set to zero, there is no size limit for the log file. In this case the<br />

file should not be stored on the SYS volume because the file is liable to grow<br />

to such an extent that the available storage space on the volume will be fully<br />

taken up. Inconsistencies within the NDS may occur as a result, and the<br />

availability of the server is reduced.<br />

In the LDAP Group object the following properties are particularly relevant to<br />

security:<br />

Suffix<br />

<strong>The</strong> Suffix box is where the subtree is defined that is made available to the<br />

LDAP clients. If this box is blank, the clients are granted access to the entire<br />

NDS tree, in other words from the [Root] object. If a client sends a request to<br />

the server relating to an object outside the defined subtree, an error is returned,<br />

unless a value is entered in the Referral box.<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!