Please talk to your vendor. They should be able to help you.
Regards,
--------------------------------------------------------------------------
Sunny Azah - sazah @
ibu .
sj .
nec .
com
Internet Business Unit, Home of the PrivateNet
NEC Technologies, Inc.
From firewalls-owner Sat Nov 16 03:18:01 1996
Received: (majordom @
localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id CAA17011 for firewalls-outgoing; Sat, 16 Nov 1996 02:59:15 -0800 (PST)
Received: from delta.ece.nwu.edu (delta.ece.nwu.edu [129.105.5.103]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id CAA17002 for <firewalls @
greatcircle .
com>; Sat, 16 Nov 1996 02:58:48 -0800 (PST)
Received: (from bonomi @
localhost) by delta.ece.nwu.edu (8.7.6/8.7.3) id EAA05306 for firewalls @
greatcircle .
com; Sat, 16 Nov 1996 04:59:05 -0600 (CST)
Date: Sat, 16 Nov 1996 04:59:05 -0600 (CST)
From: Robert Bonomi <bonomi @
delta .
ece .
nwu .
edu>
Message-Id: <199611161059 .
EAA05306 @
delta .
ece .
nwu .
edu>
To: firewalls @
greatcircle .
com
Subject: Re: name "Firewall"
Sender: firewalls-owner @
GreatCircle .
COM
Precedence: bulk
+ From: "Marcus J. Ranum" <mjr @
mail .
clark .
net>
+ To: firewalls @
GreatCircle .
COM, RAGHAVENDRA M <rohini!cs93318 @
uunet .
uu .
net>
+ Date: Fri, 15 Nov 1996 18:49:25 +0000
+
+ RAGHAVENDRA M <cs93318 @
rohini> writes:
+ > Can anyone tell me why the name 'FIREWALL'? And when
+ > was it first developed ?
+
[... snip ...]
+ The meaning of the term is (I believe) from the automotive context,
+ in which you have a firewall between the engine and passenger
+ compartment, in case the engine brews up. The term is also
+ used in architecture: there is a firewall between my neighbor's
+ house and mine. Many large buildings have internal firewalls and
+ firedoors for the same reason that large networks have them.
+ I *strongly* believe that the term "firewall" was first applied to
+ network devices as a damage limiting device, not as a security
+ device. But security coopted the term.
+
+ mjr.
The architectural use of the term **substantially** predates its use in
the automotive industry. Use dates to 1759, according to the on-line
Webster.
In construction, a "fire wall" describes an 'impermeable barrier' to
the spread of fire. It has to meet a -few- requirements:
1) Must be 'non-combustibale', in and of itself.
2) Must be a 'complete' barrier. No 'holes' or other openings that
provide free 'communication'/travel from one side to the other.
3) Must retain 'structural integrity' even in the event of 'fire'
4) Must prevent 'transfer' from one side to the other, even if not
breached. i.e., a simple layer of metal is -not- adequate, if
a fire on one side can get it hot enough to cause 'spontaneous
combustion' of somthing in contact with the far side.
The 'verb' form, as in "to firewall off", has meant "to seal up with an
impermeable barrier, leaving no openings". Whether protecting against
fire, or -other- things (e.g., heat, smoke, or noxious fumes).
In 'modern' construction, some things/'services' *do* pass through the
"fire wall". It is *controlled* access, and carefully crafted to allow
-only- the desired 'service' through, and not the 'other things'. 'Fire
doors' are allowed, but must be 'fail safe', and self-closing in the event
of fire. *AND* when closed, they have to provide an -equal- barrier as
does the wall itself.
The usage in reference to either network 'damage control', *or* with regard
to security is obvious. And, absolutely correct in -both- contexts.
I'm inclined to agree with Marcus with regard to the probability of first
use. If nothing else, on the basis that the need to 'block off' some piece
(or group) of "misbehaving" equipment was a more frequent occurance, at
least relative to an 'attack' on a network host.
References:
|
|
