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 - Organisation Remarks<br />

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

S 2.88 Licence management and version control of<br />

standard software<br />

Initiation responsibility: Agency/company management<br />

Implementation responsibility: Head of <strong>IT</strong> Section, Head of organisation<br />

Without suitable version control and licence control, experience shows that a<br />

wide assortment of versions rapidly comes to be used on an <strong>IT</strong> system or<br />

within an organisational unit, some of which may be used without a licence.<br />

Only licensed software must be used on all <strong>IT</strong> systems within an institution.<br />

This provision must be made known to all employees and the administrators<br />

of the various <strong>IT</strong> systems must ensure that only licensed software is used. To<br />

do this they must be equipped with suitable tools for licence control.<br />

Frequently, within an institution, different versions of standard software are<br />

used. Within the context of licence control it must also be possible to gain an<br />

overview of all versions used. In this way it can be guaranteed that old<br />

versions are replaced by newer ones as soon as this is necessary, and that<br />

when licences are returned, all versions are deleted.<br />

In addition to this, the various configurations of the installed software must be<br />

documented. As a result, it must be possible to acquire an overview of which<br />

<strong>IT</strong> system which settings, relevant to security on a standard software product,<br />

were specified by the approval and which were actually installed. Thus, for<br />

example, it can be rapidly clarified on which computers macro-programming<br />

has been installed on product XYZ and on which it has not.<br />

Additional controls:<br />

- Which provisions are in force?<br />

- Are different versions of a standard software product in use?<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!