battle@umbc3.UMBC.EDU (Rick) (05/08/89)
Greetings fellow netters: The University of Maryland is looking into the problems associated with providing some degree of management to microcomputers. The campus computer center is not interested in controlling micro-applications or use of the machines. Rather we are interesting in educating users about possible problems they may encounter in managing their area since more and more systems are built on the micro platform We have come up with a list of target areas. Please feel free to add to the list. Brainstroming is most welcome. Results will be posted to the net. 1. Backup 2. cross training so more than on person knows an application 3. documentation for both user and system 4. physical security for hardware, software, and data 5. access control, protection of source code, object code (how to, best methods) 6. Common sense guidelines, copy program disks, etc. 7. guidelines on disaster recovery, what to do when you have a problem, what not to do... 8. business continuity plan, what to do when your system goes south (similar to number 7, but different) 9. source document protection (paper sheets data was keyed from, how long to keep, how to store, etc.) 10. useful audit trails to track job flow, know what happened and when. 11. legal guidelines, copyright 12. policies on imported software, down loaded from public bbs, distribution of data after dl 13. appropriate use of micro for university business rather than wall street trading for fun and profit. 14. ownership of programs developed on university equipment, bag of worms but, it might be nice to avoid problems for all concerned. 15. LAN issues, shared files, etc. wide open area!!!! Again, feel free to lend your expertise to expand the list to develop content. Thanks many... Rick Battle UMAB