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

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

S 5.77 Establishment of Subnetworks<br />

Initiation responsibility: Head of <strong>IT</strong> Section, <strong>IT</strong> Security Management<br />

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

<strong>IT</strong> systems in agencies and companies are typically integrated into local<br />

networks (LANs) which in turn are linked to other networks. Simply for<br />

technical reasons it is generally necessary with medium-sized and larger<br />

networks to divide a LAN into several subnetworks, for example because<br />

there is a limit on the number of <strong>IT</strong> systems per subnetwork or on the overall<br />

length of the cabling.<br />

However, the establishment of subnetworks is also recommended for reasons<br />

of <strong>IT</strong> security. Sensitive data can be restricted to certain areas within the LAN<br />

(confidentiality), while at the same time it is possible to prevent faults in or<br />

attacks on one subnetwork from impairing the operational capability of other<br />

subnetworks (integrity and availability).<br />

At the outset it is necessary to determine which <strong>IT</strong> systems should be operated<br />

in a common subnetwork. It is recommended here that reference is made to<br />

the results of the assessment of protection requirements and that the following<br />

procedure is adopted:<br />

- All <strong>IT</strong> systems and communications links in a subnetwork should have the<br />

same protection requirements as regards the basic parameter of<br />

confidentiality. This will ensure that sensitive data is confined if possible to<br />

specially protected subnetworks. <strong>The</strong> protective measures required can<br />

then be concentrated on these subnetworks.<br />

- <strong>IT</strong> systems and communications links with a high or very high protection<br />

requirement as regards availability or integrity should if possible be in a<br />

separate subnetwork. This will ensure that proper operation of these<br />

components is not impaired in the event of faults or problems on other<br />

subnetworks. Another advantage is that faults can be contained and<br />

rectified more quickly.<br />

<strong>The</strong> second step entails the selection of suitable components for linking the<br />

subnetworks which have been established. Recommendations on this point<br />

will be found in safeguard S 5.13 Appropriate Use of Equipment for Network<br />

Coupling.<br />

In particular, consideration should be given to the use of firewalls where<br />

subnetworks which contain components having a very high protection<br />

requirements are to be linked up. This will ensure that data flows to and from<br />

the subnetwork concerned in a selective and securely controlled manner.<br />

<strong>The</strong> diagram below illustrates an example of a possible overall structure for a<br />

LAN after a subnetwork having a high protection requirement has been split<br />

off from the residual subnetwork using an additional firewall. For the sake of<br />

simplification, the two firewalls are shown as single symbols, but generally<br />

they consist of several components (packet filters, application gateway etc).<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!