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

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

<strong>The</strong> results of the acceptance should be set down in writing. <strong>The</strong><br />

documentation of the acceptance results should include.<br />

- Name and version number of the software and the <strong>IT</strong> procedure, where<br />

applicable<br />

- Description of the test environment<br />

- Test cases and results<br />

- Acceptance declaration.<br />

Acceptance of Standard Software<br />

If standard software is purchased, this should also be subject to acceptance<br />

and approval. <strong>The</strong> acceptance should include checks of whether<br />

- <strong>The</strong> software is free of computer viruses<br />

- <strong>The</strong> software is compatible with other products in use<br />

- <strong>The</strong> software can operate in the intended working environment and which<br />

parameters should be set<br />

- <strong>The</strong> software was delivered with the relevant manuals<br />

- <strong>The</strong> required functionality is fulfilled.<br />

Approval Procedure<br />

When the software has been accepted, the software has to be approved for use.<br />

It should first be determined who is entitled to approve the software. <strong>The</strong><br />

approval of software should be in writing and suitably filed.<br />

<strong>The</strong> approval declaration should include:<br />

- Name and version number of the software and the <strong>IT</strong> procedure, where<br />

applicable<br />

- Confirmation that the acceptance has been correctly carried out<br />

- Limitations for use (parameter setting, user group...)<br />

- Approval date from when the software may be used<br />

- <strong>The</strong> approval declaration itself.<br />

If possible from the point of view of <strong>IT</strong>, the software should be prevented<br />

from being altered or manipulated after approval. Otherwise, this should be<br />

stipulated in a provision.<br />

Even after intensive acceptance tests, it may be the case that errors in the<br />

software are detected when running. <strong>The</strong> procedure for such a case should be<br />

determined (contact person, troubleshooting, involvement of the relevant<br />

body, repetition of the acceptance and approval, version check).<br />

See Chapter 9.1 Standard Software for more details.<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!