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.85 Approval of standard software<br />

Initiation responsibility: Agency/company management<br />

Implementation responsibility: Head of Specialist Department, Head of <strong>IT</strong><br />

Section<br />

Before the acceptance of the standard software into actual operation comes the<br />

formal approval. Agency or company management are responsible for the<br />

approval of a product; however, they can delegate this to the management of<br />

the specialist department or the management of the <strong>IT</strong> Division. <strong>The</strong> specialist<br />

department can further restrict the approval provision specified by agency or<br />

company management by means of its own restrictions. <strong>The</strong> use of nonapproved<br />

software must be prohibited (see S 2.9 Ban on using non-approved<br />

software).<br />

Approval is always preceded by the successful completion of all necessary<br />

tests (see S 2.83 Testing Standard Software). An approval must not take place<br />

if unacceptable errors, e.g. serious deficiencies in security, were detected<br />

during the tests.<br />

Installation- and configuration provisions must be drawn up for approval.<br />

<strong>The</strong>ir level of detail depends on whether installation is to be undertaken by the<br />

system administration or the user. <strong>The</strong> installation- and configuration<br />

provisions are results of the tests carried out in the context of procurement<br />

(see S 2.83 Testing Standard Software). If different configurations are<br />

permissible, the effects of the individual configurations on security must be<br />

explained. In particular, it must be stipulated whether restrictions on product<br />

functionality or access rights are to be imposed on all, or just a few, users. <strong>The</strong><br />

staff- or works council, the data privacy officer and the <strong>IT</strong> security officer<br />

must be involved in establishing these marginal conditions at the appropriate<br />

time.<br />

Approval should take place in the form of a written approval notice. In the<br />

approval notice, statements should be made on the following points:<br />

- Program name and version number,<br />

- Designation of the <strong>IT</strong> procedure in which the product is to be used,<br />

- Confirmation that the <strong>IT</strong> components used comply with the technical<br />

requirements,<br />

- Date of the approval, signature of the person responsible for the approval,<br />

- Certificate of non-objection from the <strong>IT</strong> security officer, the data privacy<br />

officer and the staff- or works council,<br />

- Scheduled time of deployment in actual operation,<br />

- For which users the product is being approved,<br />

- Installation instructions, in particular the workstations at which it is being<br />

installed and with what configuration,<br />

- Who is authorised to install it,<br />

- Who has access to the installation data media and<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!