rtravsky@CORRAL.UWyo.Edu (Richard W Travsky) (01/29/91)
Below are some draft virus guidelines we're chewing over at our site
(the University of Wyoming). So far we've been real lucky and not had
a real problem with viruses; lately tho things have picking up. As
this list is very specific to our site, I'll stick explanatory notes
after some items. I'm posting this for the benefit of those in
similar circumstances or to elicit comment from those who've already
been around the track a few times, as it were. (I use "should be" and
"will be" below to distinguish between things that WILL be done no
matter what and things that should be done [but might not, matter is
still open to debate here].)
1. Viral Software
a. Viral scanning/cleaning software will not be used unless the
accompanying documentation has been read by the support person
doing the scan/cleanup.
b. Viral scanning/cleaning software should be kept reasonably up to date.
[As stated, we've had fairly low virus activity, so being up to date with
the latest is not real important - yet.]
c. More than software product should be used for cross checking purposes.
d. After removal of a virus, the machine/disk should be re-scanned to
verify removal.
2. Maintenance
[We maintenance machines owned by the University as well as those in the
student labs.]
a. All incoming machines should be checked for infection.
b. All returning spares will be checked for infection.
[We supply spares when possible so that the user is able to continue working.]
c. All diagnostic disks will have write protect tabs.
d. If software is being restored to someone's machine (like a backup,
format, and then a restore) the disks should be checked for infection.
3. Installs
[We install software - like PC SAS - on users' machines.
a. When possible, install disks will have write protect tabs.
b. When write protect tabs can not be used, the install disks will be
checked for infection upon return.
[Some software, like dBase 4 we found, writes to the install floppy during
installation.]
c. User's machine should be checked for infection.
[This would take care of b .]
4. Rentals, Loaners
[We provide rentals and loaners upon occaision.]
All rentals and loaned machines/software (for example, Lap Link) will be
checked for infection upon return.
5. Public access IT machines (Labs, OWA) with hard disks
Machines such as these should be checked periodically for infection.
Ideally, some resident software (preferably a TSR) should be in place
to help detect and prevent infection. The question of requiring users
to check their disks before insertion should be left open for the time
being.
6. User Support
a. User Support staff should periodically check their machines for
infection.
b. Users bringing in disks for aid should have said disks checked; barring
that the machine used to help them should be checked when done.
[People often bring in disks that are hammered or the software is not working
right for some reason (bad Word Perfect printer files, for example.)]
Richard Travsky Bitnet: RTRAVSKY @ UWYO
Division of Information Technology Internet: RTRAVSKY @ CORRAL.UWYO.EDU
University of Wyoming (307) 766 - 3663 / 3668