MyMIS
New solutions for organisations are becoming available, such as the Distributed
Intrusion Detection System (DIDS) or filtering network gateways. DIDS monitors
activities on a subnet. The filtering gateways are designed to enforce an
organisation’s network policy at the interface to the outside network. Such
solutions may allow the organisation to enjoy most (if not all) of the benefits
of network access and at the same time limit the hackers’ access.
4.4.7.3
Monitoring Tools
Information disclosure, modification, or destruction by use of monitoring devices
can be protected by:
(a) implementing use and storage controls over devices that monitor
or record information being transmitted on a network (e.g., protocol
analysers and Intrusion Detection System). The use of this equipment
must have the consent of the ICTSO;
(b) ensuring that employees understand, as part of their condition of
employment, that use of the organisation’s information processing
assets constitutes consent to monitoring; and
(c) continuing quality of controls must be ensured by maintaining an
audit trail.
Many intrusion detection systems (IDS) base their operations on analysis
of OS audit trails. This data forms a footprint of system usage over time.
It is a convenient source of data and is readily available on most systems.
From these observations, the IDS will compute metrics about the system’s
overall state, and decide whether an intrusion is currently occurring.
An IDS may also perform its own system monitoring. It may keep aggregate
statistics, which give a system usage profile. These statistics can be derived
from a variety of sources such as CPU usage, disk I/O, memory usage,
activities by users, number of attempted logins, etc. These statistics must
be continually updated to reflect the state of the current system state.
They are correlated with an internal model which will allow the IDS to determine
if a series of actions constitute a potential intrusion. This model may describe
a set of intrusion scenarios or possibly encode the profile of a clean system.
An intrusion detection system should address the following issues, regardless
of what mechanism it is based on:
(a) it must run continually without human supervision. The system must
be reliable enough to allow it to run in the background of the system
being observed. However, it should not be a ‘black box’. That is,
its internal workings should be examinable from outside;
(b) it must be fault tolerant in the sense that it must survive a system
crash and not have its knowledge base rebuilt at restart;
(c) on a similar note to the above, it must resist subversion. The system
can monitor itself to ensure that it has not been subverted;
(d) it must impose minimal overhead on the system. A system that
slows a computer to a crawl will simply not be used;
(e) it must observe deviations from normal behaviour;
Copyright MAMPU
Chapter 4 - 33
Select target paragraph3
Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents