Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!ucsd!ucbvax!SRLVX0.SRL.FORD.COM!damian
From: damian@SRLVX0.SRL.FORD.COM ("Jerry Damian")
Newsgroups: comp.protocols.tcp-ip
Subject: Re: Reducing the risks when connecting to an Internet
Message-ID: <9011270314.AA29123@ucbvax.Berkeley.EDU>
Date: 26 Nov 90 17:32:00 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 10


Referencing <1990Nov26.151017.2023@hemel.bull.co.uk>. I agree completely
with all comments regarding host based security rather than network
imposed security. However, that is often not possible due to the internal
politics of an enterprise network and who administers its hosts. The majority
of hosts on my internet are administered by engineers NOT network managers
or systems programmers. The reality of my situation is that I cannot dictate
how individual hosts are to be configured because I do not own them. Yes,
this does lead to MANY problems... Limiting the visibility of an internet via
router/bridge filtering will buy time until you can get the job done right.