Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!apple!usc!polyslo!vlsi3b15!vax1.cc.lehigh.edu!ubu.cc.lehigh.edu!virus-l
From: kelly@uts.amdahl.com (Kelly Goen)
Newsgroups: comp.virus
Subject: Re: Virus policy
Message-ID: <0003.8906261553.AA06853@spot.CC.Lehigh.EDU>
Date: 22 Jun 89 01:19:00 GMT
Sender: Virus Discussion List <VIRUS-L@IBM1.CC.Lehigh.EDU>
Reply-To: VIRUS-L@IBM1.CC.Lehigh.EDU
Lines: 15
Approved: virus-l@ubu.cc.lehigh.edu

Hi margie,
         having dealt with this problem as a consultant at a couple of
silicon valley corps I have just one issue to raise from your article.
In most cases the person who is the human causative agent in the
spread of an infection is in most cases totally unaware that some of
the disk that he/she/it is using are infected... thus it is kind of
hard to discipline that person... what could be done instead is to set
up a test cpu that the software can be run on first to attempt to
detect evidence of infectious agents(of course if the virus in
question has a sufficiently long pre-trigger level even that may not
be sufficient) (n.b. a pre-trigger is used in this context to describe
an interval that the virus will not manifest its infectious
capability)
                                             kelly goen
                                             CSS Inc.