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.75 Protecting against overloading the fax server<br />

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

Implementation responsibility: Administrator, fax mail centre<br />

A fax server can become overloaded with either incoming or outgoing fax<br />

transmissions. If the fax server is overloaded, this could mean that no further<br />

fax transmissions can be received or sent for the time being. It is also possible<br />

that overloading of the fax server could cause the operating system or the fax<br />

server application to crash so that the fax server is temporarily completely<br />

unavailable.<br />

<strong>The</strong> fax server can be said to be overloaded if all the channels available<br />

through the communications cards are blocked with incoming and outgoing<br />

fax transmissions. <strong>The</strong> result is that no more faxes can be received or sent<br />

until a channel becomes free again. If all the lines provided by the<br />

telecommunications company are busy with incoming and outgoing fax<br />

transmissions, this has the same result.<br />

Before purchasing one or more fax servers the likely volume of faxes should<br />

be estimated. Components which are capable of handling this volume should<br />

then be purchased. Care should also be taken to ensure that sufficient<br />

telecommunications lines are available.<br />

<strong>The</strong> fax server log files should be regularly examined so that if there are<br />

certain times when the server is overloaded or is functioning at the limits of its<br />

capacity, these can be identified.<br />

Overloading of the fax server can occur if an attempt is made to send out a<br />

large number of faxes from within the organisation. Under unfavourable<br />

conditions, this could cause the fax server application or the operating system<br />

to crash. This could be triggered, for example, by an attempt to send out a<br />

large number of serial faxes. During the test or pilot phase, tests should<br />

therefore be run so as to determine the loading limits. To avoid exceeding<br />

these limits, a maximum size should be imposed on users for serial fax<br />

transmissions, e.g. through an appropriate standard operating procedure<br />

(SOP). Very large serial fax transmissions should then be split into several<br />

smaller transmissions. At times when the fax server is heavily loaded, steps<br />

should be taken to ensure that faxes are only sent in urgent cases. This can be<br />

achieved either using an appropriate SOP or by appropriate permission<br />

settings on the fax server. One possible solution is to stipulate that where<br />

possible faxes are only to be sent after working hours, which also has the<br />

advantage of lower telephone charges.<br />

If it is established that the fax server is always blocked at certain times by the<br />

same originating numbers sending large numbers of faxes, first of all the<br />

identity of the originators and the nature of the fax transmissions concerned<br />

should be established. If the organisation really needs these faxes, one<br />

possibility is to negotiate times with the originators at which they should send<br />

their faxes so that they can be received without any problems. If the faxes are<br />

not actually needed (e.g. unsolicited advertising material), an attempt can be<br />

made to block these originator numbers via the fax server application or else<br />

via the private branch exchange. However, this is only possible if the<br />

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

<strong>IT</strong>-<strong>Baseline</strong> <strong>Protection</strong> <strong>Manual</strong>: Oktober 2000<br />

Procurement of suitable<br />

components<br />

Delayed transmission<br />

Agreement with the<br />

originator

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!