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

Remarks<br />

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

S 4.24 Ensuring consistent system management<br />

Initiation responsibility: Head of <strong>IT</strong> section, <strong>IT</strong> security management,<br />

Administrator<br />

Implementation responsibility: Administrators<br />

In many complex <strong>IT</strong> systems, e.g. under UNIX or in a network, there is an<br />

Administrator role which is not subject to any restrictions. Under UNIX, this<br />

is the superuser root; in a Novell network, it is the SUPERVISOR or admin.<br />

Lack of restrictions will result in a particularly high risk of error or abuse.<br />

In order to avoid errors, operations should be carried out under the superuser<br />

log-in only when this is necessary; other work should not even be carried out<br />

by the Administrator under the Administrator ID. In particular, no programs<br />

belonging to other users should be invoked under the Administrator ID. Also,<br />

routine system management (e.g. backup, installation of a new user) should be<br />

possible only via menu selection.<br />

Appropriate allocation of tasks, specification of guidelines, and measures for<br />

co-ordination are required to ensure that Administrators do not perform any<br />

inconsistent or incomplete operations. For instance, a file must not be edited<br />

and modified by several administrators at the same time, as, in that case, only<br />

the version saved last would be preserved.<br />

If there is a risk of the lines to the terminals being tapped, then, to prevent<br />

interception of passwords, the Administrator should only work at the console.<br />

When administering UNIX systems, communications can be encrypted using<br />

the Secure Shell protocol. This enables remote workstations to be<br />

administered securely (see also S 5.64 Use of Secure Shell).<br />

For all Administrators, supplementary user IDs which have only those<br />

restricted rights which the Administrators need for performing nonadministrative<br />

tasks must be configured. For non-administrative activities,<br />

Administrators should exclusively use these supplementary user IDs.<br />

All changes performed should be documented so that they can be traced back<br />

and also to facilitate task allocation (see also S 2.34 Documentation of<br />

changes made to an existing <strong>IT</strong> system). To review activities performed by the<br />

Administrator, a log can be prepared of the commands input using the UNIX<br />

command script. This command logs the entire terminal session in an ASCII<br />

file. Such a file can then if required be appended to an electronic or hard copy<br />

administration journal.<br />

Additional controls:<br />

- What steps are taken to ensure that intervention by an Administrator will<br />

not lead to inconsistencies?<br />

- Are backups made before any major intervention?<br />

- Do all Administrators have supplementary user IDs with restricted rights?<br />

- Are the supplementary user IDs used as default?<br />

- Is an administration journal maintained? Are all changes documented<br />

there?<br />

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

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

Do not work under<br />

superuser log-in<br />

Agreement among<br />

Administrators<br />

Use Secure Shell<br />

Document changes

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

Saved successfully!

Ooh no, something went wrong!