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 />

S 4.85 Design of suitable interfaces for crypto<br />

modules<br />

Initiation responsibility: <strong>IT</strong> Security Management<br />

Implementation responsibility: <strong>IT</strong> Security Management<br />

<strong>The</strong> design and configuration options of a crypto module should allow the<br />

entire flow of information to and from the module or even direct physical<br />

access to the data stock in the module to be controlled or restricted as<br />

necessary. Depending on the application or protection requirements, it may be<br />

advisable to use physically separate input and output ports. Whatever the case,<br />

the module interfaces should be set up such that the individual data channels<br />

are logically separated from each other, even though they may possibly share<br />

a common input or output port. In connection with the key management<br />

functions for the crypto module it must be guaranteed that the output channels<br />

are separated (at least logically) from internal key generation and the input<br />

port for manual key entry. In many cases there will be separate interfaces<br />

available for the connection of an external supply voltage or an external<br />

supply pulse and for exclusive use by repair or maintenance tasks. From the<br />

standpoint of the crypto module, therefore, it makes sense to divide these up<br />

and use them as follows:<br />

- Data input interface, which carries all the input data for the crypto module<br />

that is to be processed or edited in the module (e.g. cryptographic keys,<br />

authentication information, status information from other crypto modules,<br />

plaintext data etc.).<br />

- Data output interface, which carries all of the data from the crypto module<br />

that is to be passed from the module to its environment (e.g. encrypted<br />

data, authentication information, control information for other crypto<br />

modules, etc.).<br />

- Control input interface, which carries all control commands, control signals<br />

and control data for executive sequencing and setting the module’s mode<br />

of operation.<br />

- Status output interface, which outputs all signals, indications and data to<br />

the environment in order to indicate the internal security status of the<br />

crypto module.<br />

And finally:<br />

- Maintenance interface, which is used exclusively for maintenance and/or<br />

repair purposes.<br />

<strong>The</strong> documentation for a crypto component should contain a description of all<br />

components (hardware, firmware and/or software).<br />

Furthermore, the documentation should contain the complete specification of<br />

the module interfaces as well as the physical or logical ports, manual or<br />

logical control units, physical or logical indicating elements and their physical,<br />

logical or electrical properties. If a crypto component contains a maintenance<br />

interface, the documentation should also provide a full specification of the<br />

maintenance processes that have to be performed. All physical and logical<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!